Upgrading NetWorker - 1
Upgrading NetWorker - 1
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
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
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
1.
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.
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.
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
120086233.doc 12/11/2012 10:36 a12/p12 Last saved by vjaye .b Run n increase the value to d
Note: This patch has dependencies on other system patches. Ensure that all requirements are met before applying the patch.
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:
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:
Note: Beginning in NetWorker 7.5, Solaris 8 is not supported and NetWorker License Manager is not supported on Opteron.
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.
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.
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
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
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.
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.
2. [ ]
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.
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.
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:
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:
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
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.
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