EMC Solutions for NetWorker Procedure Generator

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye

Topic
Upgrading NetWorker

Selections Made
Which version are you upgrading from?: 7.4.x Which version are you upgrading to?: 7.6.x Which release of 7.6?: 7.6 SP2 Choose Installation Level: Server Operating System: Solaris Netware clients present?: No Virtual Machine Backups?: No NDMP?: No IPv6?: No EDL?: No JRE 1.6 Installed?: No JRE 1.5 Installed?: No LTO-4 Encyption Used?: No VCB backups?: No CIFS backups?: No LDAP Authentication for NMC Configured?: No Is HomeBase installed on this machine?: No Capacity Based licensing used?: No Existing Data Domain Backups?: No NetWorker module clients running 7.2.x or 7.3.x ?: No NetWorker Module for MEDITECH present?: No NetWorker Module for Oracle clients present?: No Dashboard installed?: No Is DPA/EBA installed on this machine?: No AlphaStor installed?: No Configure ConnectEMC (Windows x86 only): No Include Management Console configuration steps?: No Include basic Management Console navigation tips?: No

Procedure Generated on: 1/5/2012 1:03:25 PM

REPORTING PROBLEMS: If you find any errors in this procedure or have comments regarding this application, please send email to PG-Feedback@emc.com. .

Table of Contents

1.

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye Download the NetWorker Software and Documentation.......................................................................4 2. Pre-installation Considerations for all Operating Systems ............................................................4 Considerations for NetWorker server hosts file changes ....................................................................4

Pre-Installation Considerations on Solaris Operating Systems.........................................................................4

Tune shared memory use/open files for Solaris 9.......................................................................................5 Disable TCP Fusion on Solaris 10 ..............................................................................................................5 TCP Performance Tuning............................................................................................................................5 Configure Jumbo frames.............................................................................................................................6 Install the required Solaris 10 patch for x86/Sparc......................................................................................6 Install the required CDE/Motif patch on Solaris 10 Sparc V240...................................................................6 Solaris 10 on Sparc and x86 with Intel Gigabit Ethernet Card considerations.............................................6 Confirm that libm.so.2 is available for Direct SCSI backups........................................................................6 Disable the vold daemon with optical drives on Solaris 9............................................................................7 Server error when configuring LDAPS authority on Solaris.........................................................................7 SSL Key Length Limitation on Solaris AMD 64............................................................................................7 Java (JRE) is no longer shipped with NetWorker.........................................................................................7 Prevent drive ordering issues in a SAN environment...................................................................................8 Dedicated storage node support in local zones...........................................................................................8 Requirements for DSN support in Local Zones....................................................................................8

NetWorker 7.6.x Interoperability Considerations..............8

Update NetWorker clients............................................................................................................................8 Update NetWorker 7.3.x and earlier storage nodes ....................................................................................8 Update the NetWorker server before storage nodes...................................................................................8

Licensing Requirements and Changes..............................8 NetWorker Catalog Consistency Checking and Bootstrap Backup...........................................................................9 Backup the GST Database...............................................9 Uninstall the NetWorker Software on Solaris..................10 Install NetWorker Solaris Server....................................11
Optional Java installation...................................................................................................................11

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye Optional NetWorker Management Console installation.............................................................................12 Review customizations and start the daemons..................................................................................13

Post Installation Modifications for Solaris......................13

Tune TCP operating system parameters...................................................................................................13 Configure and restore lus driver configuration...........................................................................................14

Jukebox Considerations After Upgrading From 7.4.x.......14 Reconfigure a Jukebox...................................................14

Validate successful device operations in NetWorker.................................................................................14

Timeout Attribute Considerations for Storage Node Operations....................................................................14

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye

1.

Download the NetWorker Software and Documentation

To obtain the latest NetWorker software, and documentation: 1. [ ] Review the online NetWorker documentation, for example the Administration Guide, Installation Guide, and Release Notes for the latest information. 2. [ ] Obtain the online documentation on powerlink.emc.com at: Support > Technical Documentation and Advisories > Software ~ J-O ~ Documentation > NetWorker Family 3. [ ] Obtain the required NetWorker cumulative hotfix media kits that provide customers with the opportunity to install the latest version of NetWorker including important hotfixes. Cumulative builds are released approximately once a month and each build contains a rollup of the fixes in each previous build. If additional hotfixes are required in an environment where a cumulative build is installed, hotfixes can be generated for use with the latest cumulative version. The desired hotfixes for specific NetWorker releases are available in the following section on powerlink.emc.com: Home > Products > Software E-O > NetWorker > Key Enhancements/Support Notes Select the appropriate NetWorker version. Open the Cumulative Fix Summary document for details regarding fixes that are included in each build, knowledge base articles related to the fixes in each build, as well as download instructions. IMPORTANT: As new cumulative builds are released the corresponding Cumulative Build documentation is also updated. Click on the Alert Me! button to automatically receive an email notification whenever new NetWorker cumulative builds are released.

2.

Pre-installation Considerations for all Operating Systems

Misconfigured loopback entries in the hosts file can cause backups to fail. When an entry is made in the hosts file for localhost, localhost must be entered before aliases (for example, loopback) the order is: acoe l as od dl h s r For example: IPv6 localhost entry: ::1 localhostloopbac k IPv4 localhost entry: 1 2 s a i l

NetWorker server always takes the first alias specified in the OS hosts file as the NetWorker server name. If the first alias in hosts file is different than the current NetWorker server name client resource, the next time the NetWorker daemons/services start, NetWorker will rename the NetWorker server to the first alias listed in the hosts file. This will assign a different clientid to the NetWorker servers client resource and will result in a failure to restore backups for both the NetWorker server and configured clients. To avoid this issue, when modifying the hosts file makes sure that the first alias for the ip address of the NetWorker server matches exactly the name defined for the client resource of the NetWorker server.

Pre-Installation Considerations on Solaris Operating Systems

This section describes pre-installation considerations for Solaris.

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye

Tune shared memory use/open files for Solaris 9

Tune shared memory open files on Solaris 9: 1. [ ] / e 2. [ ] Modify the values for the following parameters in / the values are lower than the if e recommended values listed below: s e s e s e s s e st s s h: emy s m h s s e m m s s s : : : : : s s s e s s y y y y y s s s s s g g m m m s s e e e Make a copy of the / file. For example: e

Note: Setting these values incorrectly can cause the system to become unbootable. To recover, type ,o bo type /t the name of the system file. and for e c

Disable TCP Fusion on Solaris 10

If used, TCP Fusion should be disabled on Solaris 10 NetWorker servers and storage nodes. To disable TCP Fusion: 1. [ ] 2. [ ] Edit the / and add this line: file e Reboot to enforce the change.

TCP Performance Tuning

For high-speed network interfaces, increase the size of TCP send/receive buffers from their default values as required: 1. [ ] Increase the maximum buffer size to control how large the send and receive buffers are set to by an application if below 10485760. .a Run npc tep /d determine current value. tot c/ d v .b Run n increase the value to d 2. [ ] Increase the maximum value of the TCP congestion window (cwnd) can grow to in bytes if below 10485760. .c Run npc tep /d determine current value. tot c/ d v .d Run nddto increase the value d m 10485760 set /dev/tcp tcp_cwn _ ax 3. [ ] Increase the TCP receive-Buffers if below 65 :5 3 c t / v e

.a Run n determine current value. to d p .b Run n increase the value to d 4. [ ]

Increase the TCP transmit Buffers if below 65536: t / v e d

.a Run n determine current value. to d p c

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye .b Run n increase the value to d

Configure Jumbo frames

It is recommended to use jumbo frames in environments capable of handling them. If both the source and the computers, and all equipment in the data path are capable of handling jumbo frames, increase the MTU to 9 KB: Use the following command to configure jumbo frames for an nxge device. where <# is replaced with the driver instance number > Note: To determine the instance number of a following device, run the command na c /g t pee xh/ t _

Install the required Solaris 10 patch for x86/Sparc

To avoid shared memory corruption causing possible hangs or failures of the NetWorker services on a NetWorker server, Sun patch142900-03 (or later) on Sparc or Sun Patch 142901-03 (or later) on x86 or later must be applied. To confirm this patch is applied: 1. [ ] 2. [ ] On Solaris Sparc servers, type this command: On Solaris x86 servers, type this command:

Note: This patch has dependencies on other system patches. Ensure that all requirements are met before applying the patch.

Install the required CDE/Motif patch on Solaris 10 Sparc V240

In order for nwrecover to function correctly, Sun patch 119280-10 (or later) on Sparc or Sun patch 119281-10 (or later) on x86 must be applied. To confirm this patch has been applied: 3. [ ] 4. [ ] On Solaris Sparc servers, run the following command: On Solaris x86 servers, type the following command:

Note: This patch has dependencies on other system patches. Ensure that all requirements documented in the patch are met before applying the patch.

Solaris 10 on Sparc and x86 with Intel Gigabit Ethernet Card considerations
Backups of large savesets may fail on Solaris 10 systems if an Intel Gigabit Ethernet card (e1000g driver) is used. To avoid this issue, Sun patch 102712-01 (or later) on Sparc or Sun patch 102711-01 (or later) on x86 must be applied. To confirm this patch has been applied: 1. [ ] 2. [ ] On Solaris Sparc servers, run the following command: On Solaris x86 servers, type the following command:

Confirm that libm.so.2 is available for Direct SCSI backups

Direct SCSI backup and restore is a NetWorker feature that allows back up to business continuance volumes (BCVs) on an EMC Symmetrix server. It also allows the backup and recover of raw devices

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye over a SCSI bus. Direct SCSI backups facilitate the migration of an EDM server using EDM OIM to backup and restore Symmetrix BCVs to a NetWorker server. On Solaris 9 and 10 servers, /usr/lib/libm.so.2 is required for Direct SCSI backup and restores: 1. [ ] 2. [ ] 3. [ ] On the Solaris server, c /s/ to . u l d r i b

Type l and confirm in the output that l s exists. i If l does not exist, link l using the following command:

Disable the vold daemon with optical drives on Solaris 9

To disable the vold daemon: 1. [ ] Log in as root on the NetWorker storage node, and remove or move all script files matching the following: 2. [ ] Type the following command:

Note: Beginning in NetWorker 7.5, Solaris 8 is not supported and NetWorker License Manager is not supported on Opteron.

Server error when configuring LDAPS authority on Solaris

Attempt to configure LDAPS authority with gstd running on Solaris will fail with the following error: ldap_set_option(LDAP_OPT_X_TLS,1) failedwith message 'Can't contact LDAP server Note: If LDAPS (LDAP over SSL) is used to authenticate users, and the NMC server must support LDAP v3 authentication, do not install the NMC server on the Solaris server. However, the NMC server can be installed on a Linux, Windows, AIX or HP-UX server for LDAPS authentication. The NMC server can be installed on a Solaris server if both LDAP and LDAPS, or only LDAP, protocols are enabled on the directory server.

SSL Key Length Limitation on Solaris AMD 64

The default OpenSSL library on Solaris for AMD 64 does not support AES key lengths greater than 128bits. To workaround this limitation, install the Solaris 10 Encryption kit for i386 architecture, which includes the SUNWcryman, SUNWcry, and SUNWcryr packages. The Solaris 10 Encryption kit supports 256-bit key length AES encryption. The Solaris 10 Encryption kit is available at, http://www.sun.com/download/index.jsp?tab=2. Scroll to S to locate the link. Note: If the encryption kit is not installed, the nsrd daemon might not start.

Java (JRE) is no longer shipped with NetWorker.

When the NMC client starts, if a supported version of Java is not detected on the client, a message displays with instructions on how to install the appropriate version of Java. Note: A supported version of JRE must be installed on the NMC server if the Console command line reporting functionality (gstclreport) is required.

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye

Prevent drive ordering issues in a SAN environment

Ensure that persistent binding is enabled in the fabric to prevent device target-id changes in the future. The HBA documentation provides details on how to setup persistent bindings in a SAN environment.

Dedicated storage node support in local zones

In NetWorker 7.6 and later, the ability to backup to a dedicated storage node (DSN) in a local zone was introduced. If all devices are in a single NetWorker data zone, the NetWorker software supports a DSN installed in a Solaris 10 local zone to: Backup directly to a physically attached device without sending data across the IP network Manage device sharing between multiple dedicated storage nodes or storage nodes that are installed in multiple local zones of a single physical host

Requirements for DSN support in Local Zones

This section lists requirements for DSN support in local zones: The NetWorker server and DSN versions must be NetWorker 7.6 or later Solaris 10 Update 5 or later that allows shared SCSI commands is installed More details on Solaris 10 Update 5 are available at Sun.

NetWorker 7.6.x Interoperability Considerations

This section identifies NetWorker 7.6.x interoperability considerations.

Update NetWorker clients

It is recommended that the NetWorker client version be the same as the NetWorker server. However, a NetWorker 7.6.x server supports NetWorker 7.4.x and later clients.

Update NetWorker 7.3.x and earlier storage nodes

NetWorker 7.6.x server does not support storage nodes running NetWorker 7.3.x and earlier (NetWorker Storage Node for OpenVMS 7.3.4 is the exception and is supported). If required, update the NetWorker server and storage nodes at the same time. It is recommended that the NetWorker storage node version is the same as the NetWorker server. However, a NetWorker 7.6.x server supports NetWorker 7.4.x and later storage nodes. Note: All new features may not be supported if the storage node is running at an earlier version than the NetWorker server. Refer to esg83215 for further details

Update the NetWorker server before storage nodes

NetWorker servers earlier than version 7.6.x do not support 7.6.x NetWorker storage nodes. Ensure that the NetWorker server is updated to 7.6.x before updating any storage nodes to NetWorker 7.6.x.

Licensing Requirements and Changes

In NetWorker 7.6 and later, the installation process detects if a previous version of the NetWorker software is installed. If an upgrade is performed from a version of NetWorker earlier than 7.5.x, the update enabler code is automatically added. When the server is upgraded, the update enabler code must be

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye authorized within 45 days or the server will be disabled. An update enabler code is not generated, or required when upgrading from 7.5.x to NetWorker 7.6.x. Note: Contact EMC Licensing within 45 days of upgrading to permanently authorize the enabler and ensure uninterrupted operations of the NetWorker server. These licenses are no longer required in NetWorker 7.4 Service Pack 3 and later: ClientPak licenses to backup clients with different operating systems than the NetWorker server. Client licensing is based solely on client connection enablers. Cluster Client Connection licenses to backup cluster clients. During upgrade, any installed cluster Client Connection licenses are converted to Client Access Licenses and each physical node in a cluster will use one client connection license. In NetWorker 7.4 SP2 and later, VSS licenses to backup Windows Vista, Windows 2003 and Windows 2008 VSS savesets.

NetWorker Catalog Consistency Checking and Bootstrap Backup

Before the software update: 1. [ ] Ensure that the NetWorker catalog is consistent by running the following commands:

Note: Do not copy and paste above command, enter these commands manually from a command prompt 2. [ ] Use the NetWorker software to back up the client file index and the media database. Ensure that you back up all the client file indexes and generate a bootstrap for the server. For example, to save only the indexes and bootstrap information, type this command:
svp -e GO ag group r

where group is the name of the group containing the client(s). Note: Ensure that all clients are included in the group or groups that are backed up. The backup pool must be associated with the specific group with available append able media. This command can run more than once to save the indexes for clients in more than one group. A bootstrap backup will be performed for each run. 3. [ ] Record the latest bootstrap save set ID (ssid) including the file, record numbers, and the associated volume label, type this command: The following is an example of mminfo -B output: Sample output: 4. [ ] If the NetWorker software is not currently installed in the default location, record the location of the client file indexes.

Backup the GST Database

Ensure there is a current backup of the GST database for the NetWorker Management Console (NMC) server. If a Client resource was not created when the NMC was installed and configured, create the Client resource:

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye 5. [ ] 6. [ ] From the Console window, click Setup. From the Setup menu, select Set Database Backup Server.

7. [ ] In the NetWorker server attribute, type the name of the NetWorker server to back up the NMC server database. 8. [ ] 9. [ ] 10. [ ] 11. [ ] Select the Create Client resource on this server attribute. In the Client name attribute, type the name of the NMC server. Click Ok. Complete the Client resource with the following attributes:

Name: the name of the NMC server computer. Save set: where server_name is the short name of the host on which the NMC server was installed. Backup Command: 12. [ ] Add this client to a group and perform a full backup. To perform a full backup of this client in a defined group: where: <le client name of the NMC server. is n c the i <r the name of the group containing the NMC server. is g o

Uninstall the NetWorker Software on Solaris

To uninstall the NetWorker software on Solaris: 1. [ ] 2. [ ] Log on to the Solaris machine as root user. Create a backup copy of NetWorker script files:

Note: Customizations to the NetWorker startup script files are overwritten when NetWorker is installed. Be sure to make a copy of any customizations required after an installation. 3. [ ] Create a backup copy of the lus driver configuration.

Note: This is not required on Solaris 10. 4. [ ] 5. [ ] 6. [ ] Shutdown the NetWorker daemons when there are no backups and recoveries running: Confirm that all NetWorker daemons have been stopped: Determine which packages need to be removed:

7. [ ] Uninstall all of the NetWorker packages listed in the p output in the order listed below. k Exclude packages not listed by the pgn command: kf i o Note: Do not choose the default option Al remove the NetWorker software packages. Choosing this l to option removes all the software packages (not just NetWorker software) that were installed on the computer using the p utility. Also, do not remove the /nsthe NMC database folders after uninstalling k or the software.

10

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye

Install NetWorker Solaris Server

To install the NetWorker Solaris server: 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] Make a copy of the following files which the NetWorker software installation modifies: Use the command line to navigate to the downloaded the NetWorker package. Unzip the downloaded file to access the tar file: Extract the individual package files from the archive: Type the following command:

The following output displays:

6. [ ]

Based on the above example, type 1, 8, 9 and applicable language paks if desired.

Note: There is also the option to install other NetWorker components such as the NetWorker License Manager. Type the number of the other optional components to install. .To install the NetWorker Management Console (NMC), it is recommended to install it on a client machine. However, do not install it at this time. Install the NMC later, as described in Optional NetWorker Management Console installation, in this procedure. With 7.6.x, the HomeBase agent is automatically installed. 7. [ ] When all selections are made, press Enter to proceed.

8. [ ] When prompted to change the installation directory, press Enter to accept the default /var/nsr, or type the required path, and press Enter. 9. [ ] When prompted to add to the Servers file, type y and press Enter to add the hostname of the NetWorker servers. The client can only be backed up by NetWorker servers in this list. Note: If no servers are listed in the Servers file, any NetWorker server can backup this client. 10. [ ] 11. [ ] 12. [ ] When prompted to start the NetWorker daemons, type n and press Enter. When prompted to continue the installation, type y and press Enter. When the installation completes, type q to quit.

13. [ ] If not installing the NMC server on this host, proceed to Review customizations and start the daemons.

Optional Java installation

To install JRE: 1. [ ] Before installing NMC, Java Runtime Environment 1.5 or later must be installed.

Note: On Solaris 10, JRE 1.5 versions earlier than 1.5.0_09 are not supported. On Solaris 9, NMC help will not launch on JRE versions earlier than 1.5.0_09. 2. [ ] location: Java is no longer shipped with NetWorker, and Java can be obtained from the following

https://cds.sun.com/is-bin/INTERSHOP.enfinity/WFS/CDS-CDS_DeveloperSite/en_US/-/USD/ViewProductDetail-Start?ProductRef=jre-6u12-oth-JPR@CDS-CDS_Developer

11

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye Note: The download location might change in the future. 3. [ ] Select the platform and language, make the appropriate choices, agree to the Java License and click Continue. Note: If running in a pure IPv6 environment or NMC bundled with 7.6 SP1, install JRE version 1.6. 4. [ ] At the final download screen, click the JRE available under Available Files to begin the download. 5. [ ] 6. [ ] 7. [ ] 8. [ ] A security warning might display. Click Save to continue the download. Select a location to save the JRE, and click Save. When the download completes, navigate to the java file from the command line. Change the file permissions to allow it to run:

Note: The file name can change depending on the version of Java. 9. [ ] Navigate to the downloaded Java files, and run the install script

The script creates an install directory where it is run. 10. [ ] When prompted to accept the licensing agreement, review the License Agreement, type yes and press Enter to continue. 11. [ ] Proceed to the NMC installation.

Optional NetWorker Management Console installation

To install the NMC: 1. [ ] Install NMC:

The following output displays:

2. [ ]

Based on the above example, type 7.

Note: If the environment has only LDAPS (also known as LDAP over SSL), and there is no native NetWorker user authentication, do not install the NMC server on a Solaris server. 3. [ ] When prompted to install NMC, type a path with enough free space.

Note: NMC requires a minimum of 350 MB however, it is recommended to have more space available for NMC reporting features. 4. [ ] When prompted to specify a user/group with limited privileges for NMC to run the web server, set it for a non-root user. For example, Solaris operating systems have a default user/group [nobody/nobody] to use. Note: If the default group [nobody/nobody] does not exist, and a user/group has not been created with limited privileges, create a non-root user/group with limited privileges. 5. [ ] When prompted for the web server port, press Enter to accept the default, or type the required port number, and press Enter.

12

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye 6. [ ] When prompted for the GST server port, press Enter to accept the default, or type the required port number, and press Enter. 7. [ ] When prompted for the NMC database, press Enter to accept the default, or type the required path, and press Enter. If prompted to keep the old database, choose y and press Enter. 8. [ ] When prompted for the installation location for the NetWorker binaries, press Enter to accept the default, or type the required path and press Enter. 9. [ ] When prompted to start the daemons, type n. 10. [ ] If the install folder (/opt/LGTOnmc by default) does not exist, when prompted to create the directory, type y and press Enter. 11. [ ] 12. [ ] When prompted to continue the installation, type y. When the installation completes, type q to quit.

Review customizations and start the daemons

To review the customizations and start the daemons: 1. [ ] /td ec/ w t e n / . i 2. [ ] / e Note: Do not overwrite the new files with the contents of the old 7.xx files. The old customizations must be included in the new script and configuration file. 3. [ ] Start the NetWorker daemons and the NetWorker NMC daemon (gstd) if it was installed. Make the necessary modifications to the following file: Review the startup script file that was copied during the uninstall operation:

Note: A NetWorker 7.5.x and later server does not support the use of a storage node running 7.2.x. Ensure all 7.2.x storage nodes are upgraded. It is recommended that the storage nodes be at the same NetWorker version as the server.Start the NetWorker daemons and the NetWorker NMC daemon (gstd) if it was installed.

Post Installation Modifications for Solaris

This section describes required modifications for Solaris.

Tune TCP operating system parameters

To tune TCP parameters: 1. [ ] Review the values set for key tcp parameters to determine if they are set to recommended defaults (recommendations in brackets):

Note: The ndd parameters can be set in the /e script before echo starting NetWorker dem .d/: / vn > es ao 2. [ ] Modify the following parameters if the values are lower than what is recommended:

.a The maximum number of pending non-processed TCP requests:

13

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye .b The queue size for un-established TCP connections: .c The time that sockets are left in a WAIT state: .d The TCP keepalive interval:

Configure and restore lus driver configuration

To configure and restore the lus driver configuration on Solaris 9 and earlier: 1. [ ] Run the lu script to addvs s_add _fp_d HBAs to the /se e file. ur/ v r d / l n k

2. [ ] Compare the new /ure original that was saved at the beginning of the upgrade in /se to r sn /k v d / l the and u/ re k r n l / d r v x 7 f n o c . s u update the new / sr if r u appropriate. . s v d / l e n k / no c u l

Jukebox Considerations After Upgrading From 7.4.x

After upgrading the NetWorker server or storage node from 7.4.x to 7.6.x, in some situations the jukebox might not change to a ready state due to a change in the control port setting. To correct this issue:

Reconfigure a Jukebox
To reconfigure a jukebox: 1. [ ] 2. [ ] Connect to the NetWorker server via NMC and click Devices. Click Libraries to list all jukeboxes in the data zone.

3. [ ] Right mouse click on the affected jukebox and select Properties. Ensure Enabled is set to No in the Status section. Click Ok. 4. [ ] Right mouse click on the jukebox and select Re-configure Library. 5. [ ] In Configure devices on various storage node using existing drive connectivity, ensure all devices are selects and click on Start Configuration. 6. [ ] library. In the library Log window, confirm that there is an entry for a successful reconfigure

7. [ ] Right mouse click on the affected jukebox and select Properties. Ensure Enabled is set to Yes in the Status section. Click Ok.

Validate successful device operations in NetWorker

To verify if the device operation was successful: 1. [ ] In the Library window, drag an unlabeled volume or a volume with a valid NetWorker label into this device. If device restrictions are set in pools, ensure the chosen volume is labeled for a pool for which this device has permissions. 2. [ ] In the library status window, confirm that there is a message stating the operation succeeded.

Timeout Attribute Considerations for Storage Node Operations

As remote non-NDMP devices are added to a datazone, two key values must be adjusted to limit the number of RPC calls that the NetWorker server makes to the remote storage node to ensure the a nsrmmd process is available.

14

120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye The nsrmmd polling interval (default value of 3 minutes), defines the number of minutes between storage node polls. For datazones with less than 100 remote devices, the recommended value is 15 minutes For datazones with 100 or more remote devices, the recommended value is 30 minutes The nsrmmd restart interval (default value of 2 minutes) defines the number of the minutes the NetWorker oftware waits before restarting the nsrmmd process For datazones with less than 100 remote devices, the recommended value is 10 minutes For datazones with 100 or more remote devices, the recommended value is 20 minutes Note: The above recommendations are guidelines only and further adjustments and tuning might be required to meet the requirements of the datazone. To increase these values: 1. [ ] 2. [ ] 3. [ ] 4. [ ] 5. [ ] Connect to the NetWorker server by using NMC, and click Configuration. From the View menu, select Diagnostic Mode. Right-click the NetWorker server in the left navigation pane and select Properties. In the Media tab, adjust the nsrmmd polling interval and the nsrmmd restart interval. Click Ok.

15