Legato NetWorker ® Module for EMC CLARiiON for Oracle ® Legato NetWorker® ® Administrator’sRelease Guide 7.0 Release 1.
© 2003, Legato Systems, Inc. All rights reserved. This product may be covered by one or more of the following patents: U.S. 5,359,713; 5,519,853; 5,649,152; 5,799,141; 5,812,748; 5,835,953; 5,978,565; 6,073,222; 6,085,298; 6,145,089; 6,308,283; 6,324,654; 6,338,126. Other U.S. and international patents pending. Legato NetWorker, Release 7.
Legato Systems, Inc. End-User License Agreement THIS PRODUCT CONTAINS CERTAIN COMPUTER PROGRAMS AND OTHER PROPRIETARY MATERIAL, THE USE OF WHICH IS SUBJECT TO THIS END-USER LICENSE AGREEMENT (THE “AGREEMENT”). DO NOT PROCEED WITH THE INSTALLATION OF THIS PRODUCT UNTIL YOU (LATER DEFINED AS LICENSEE) HAVE READ THIS AGREEMENT AND AGREE TO BE BOUND BY AND BECOME A PARTY TO THIS AGREEMENT.
5. LIMITED WARRANTY 9. MISCELLANEOUS 5.1 Media and Documentation. Legato warrants that if the media or documentation are damaged or physically defective at the time of delivery of the first copy of the Software to Licensee and if defective or damaged product is returned to Legato (postage prepaid) within thirty (30) days thereafter, then Legato will provide Licensee with replacements at no cost. 9.1 Governing Law.
Contents Preface ......................................................................................................... 15. Audience.......................................................................................................................... 15. Product Documentation ................................................................................................... 15. Conventions.................................................................................................................
Contents Prerequisites.............................................................................................................. 28. How to Install and Configure the UNIX Operating System ........................................ 29. Task 1: Install the Operating System .................................................................. 30. Task 2: Configure the Operating System ............................................................ 30. Task 3: Configure the Devices and Test the Operating System ..
Contents Chapter 4: Windows Disaster Recovery ................................................... 47. Disaster Recovery Summary Procedures ....................................................................... 48. NetWorker Server Recovery Summary Procedure ................................................... 48. NetWorker Client or Storage Node Recovery Summary Procedure ......................... 50. Disaster Recovery of Multiple Computers ..................................................................
Contents Task 4: Recover the NetWorker Server Bootstrap.............................................. 72. Task 5: Rename the Resource Configuration Files ............................................ 74. Task 6: Reset and Inventory the Autochanger.................................................... 74. How to Reset and Inventory an Autochanger with Removable Storage Disabled........................................................................................................ 74.
Contents Task 3: Test the Operating System and Configure Devices............................... 94. Completing the Recovery Process............................................................................ 94. Recovering a NetWare NetWorker Server ...................................................................... 94. Prerequisites ............................................................................................................ 95. How to Recover a NetWare NetWorker Server..................
Contents Task 1: Take the Dependent Resources Offline...................................................... 113. Task 2: Replace the Hard Drive .............................................................................. 114. Task 3: Recover the Data to the Shared Disk ......................................................... 115. Task 4: Configure the Cluster to Include the Shared Disk....................................... 115. Replacing the Quorum Disk and Recovering Its Data..........................
Contents Chapter 8: Sun Cluster Disaster Recovery ............................................. 135. Prerequisites.................................................................................................................. 135. Restoring a Single Cluster Node ................................................................................... 135. How to Restore a Single Cluster Node ................................................................... 136. Restoring an Entire Cluster ..................
Contents Task 8: Locate the Server’s Client File Index Save Set IDs.............................. 148. Task 9: Recover the Server’s Client File Index ................................................. 149. Task 10: Re-create the Cluster ......................................................................... 150. Task 11: Recover the Cluster Data ................................................................... 150. Chapter 10: HP-UX Cluster Disaster Recovery ....................................... 153.
Contents Chapter 12: HACMP for AIX Disaster Recovery ..................................... 165. Recovering a Single Node............................................................................................. 165. How to Recover a Single Node ............................................................................... 166. Recovering an Entire Cluster......................................................................................... 166. How to Perform a Cluster-Wide Recovery ................
Contents 14 Legato NetWorker, Release 7.
Preface This guide contains information on how to prepare for a disaster before one strikes and how to recover from a disaster. Using the Legato NetWorker® software to back up data is the first step in a disaster recovery program. The next step is deciding how to recover data after a disaster.
Conventions Conventions This document uses the following typographic conventions and symbols to make information easier to access and understand. Convention Indicates Example boldface Names of line commands, daemons, options, programs, or scripts The nsradmin command starts the command line version of the administration program. italic in text Displayed messages are also written to Pathnames, filenames, computer names, new terms /nsr/logs/daemon.log.
Preface Information and Services Legato offers a variety of methods, including electronic, telephone, and fax support to obtain company, product, and technical information. General Information The Legato web site provides most of the information that customers might need. Technical bulletins and binary patches are also accessible on the Legato FTP site. For specific sales or training needs, e-mail or call Legato.
Licensing and Registration Licensing and Registration To license and register Legato products, go to the Legato licensing web site. To change contact information, transfer licenses, or ask questions about licensing, contact Legato using one of the following methods. Licensing and Registration Contact Legato licensing web site http://license.legato.com Telephone number (650) 812 6000 (option 3, option 2)a +31 23 554 8881b Fax number (650) 745-1477a +31 23 554 8808b E-mail licensing@legato.
Chapter 1: Introduction The Legato NetWorker Disaster Recovery Guide, Release 7.0 provides step-by-step instructions for recovering from a disaster on supported NetWorker 7.x client and server platforms.
Disaster Recovery Guide Overview Disaster Recovery Guide Overview The guide includes the following topics to help you prepare for and perform a recovery of NetWorker servers, clients, and storage nodes: 1 20 • “Chapter 2: Preparing for a Disaster” on page 21 • “Chapter 3: UNIX Disaster Recovery” on page 25 • “Chapter 4: Windows Disaster Recovery” on page 47 • “Chapter 5: NetWare Disaster Recovery” on page 89 • “Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.
Chapter 2: Preparing for a Disaster This chapter contains information on preparing for a disaster. This chapter includes the following sections: • “Preparing for Disaster” on page 21 • “Gathering the Key Information” on page 22 If you are viewing the online version of this guide, print out a hard copy and store it in a safe location. Preparing for Disaster You should back up important data on a scheduled basis.
Gathering the Key Information To recover from network-related disasters, you must have access to key information related to each computer that needs protection. Maintain a copy of this information on-site for easy access by those assigned to perform disaster recovery. Important: Having the correct information on hand in case a disaster occurs is a key element in recovering from a disaster as quickly as possible.
Chapter 2: Preparing for a Disaster Software Information Maintain the following up-to-date information regarding computer software: • Copies of the original operating system media and patches (and where they are located) • Software enabler and authorization codes • Software vendor contact information and contract number • The operating system version and patches installed • Operating system configuration • Emergency media that can be used to restore a computer in the event of a disaster • NetW
Software Information Table 1. Operating System Information (Part 2 of 2) Platform 2 Recovery/Repair Prerequisite Information Windows NT 4.0: Repairing a Windows NT 4.0 operating system installation “Repairing a Windows NT 4.0 Operating System Installation” on page 57 Windows 2000: Recovering a Windows installation “Recovering a Windows Installation” on page 60 Windows .
Chapter 3: UNIX Disaster Recovery This chapter explains how to recover from a disaster on a UNIX server, client, or storage node host computer running NetWorker 7.x software.
Disaster Recovery Procedures Disaster Recovery Procedures Table 2 on page 26 lists the disaster recovery procedures that you may have to perform depending on the damage caused by the disaster. Complete each procedure, as necessary, in the order listed in this table. Table 2. UNIX Disaster Recovery Procedures 3 If you are recovering... See...
Chapter 3: UNIX Disaster Recovery Replacing a Hard Drive The following sections provide important information to be aware of when replacing a hard drive as part of a disaster recovery: • “Prerequisites” on page 27 • “Replacing the Hard Drive” on page 27 • “Completing the Recovery Process” on page 28 Prerequisites To help ensure that you are prepared to replace and reconfigure a hard drive, maintain a current record of the system information.
Completing the Recovery Process Completing the Recovery Process To complete the recovery process after replacing the hard drive, recover the following: 1. The UNIX operating system, if necessary. For information, see “Installing and Configuring the UNIX Operating System” on page 28. 2. The NetWorker software corresponding to the type of NetWorker computer you are recovering. For more information, see: • “Recovering a NetWorker Server” on page 32. • “Recovering a NetWorker Storage Node” on page 40.
Chapter 3: UNIX Disaster Recovery • Computer properties: – Hostname – DNS domain name – Superuser password • Device and SCSI drivers • Boot files required for booting the kernel. For example: – /unix – /boot – /etc/default/boot – /stand/vmunix Important: To determine which boot files should not be overwritten during a recovery refer to the appropriate operating system documentation.
Prerequisites Task 1: Install the Operating System To install the operating system: 1. Install the same version and patch level of the UNIX operating system. Specify the same installation locations that were used in the predisaster installation of the operating system. For installation information, refer to the appropriate UNIX documentation. If you want to upgrade the operating system, recover the predisaster version of the operating system before performing any upgrades. 2.
Chapter 3: UNIX Disaster Recovery Task 3: Configure the Devices and Test the Operating System To configure the devices and test the operating system: 1. Configure any devices the NetWorker software requires, for example SCSI pass-through devices for autochangers. For information about configuring devices, refer to the Legato NetWorker Administrator’s Guide, UNIX Version. 2. Test that the: • Name to Address resolution and TCP/IP are functioning properly.
Completing the Recovery Process Completing the Recovery Process To complete the recovery process after installing and configuring the operating system, use the following procedures, depending on the type of NetWorker computer you are recovering. These procedures describe how to recover the NetWorker software as well as the computer’s application and user data: • “Recovering a NetWorker Server” on page 32. • “Recovering a NetWorker Storage Node” on page 40. • “Recovering a NetWorker Client” on page 43.
Chapter 3: UNIX Disaster Recovery Important: If the NetWorker server was also a Legato License Manager server, the License Manager lictype.res file is not restored when the server is restored. This is because the License Manager files and directories are not considered part of the NetWorker server. After recovering the NetWorker server, you must explicitly recover the License Manager as a client of the NetWorker server.
Prerequisites To re-create links to NetWorker directories: a. Stop the NetWorker daemons by entering the nsr_shutdown command at the command line: # nsr_shutdown -a b. Move the files to their original location. c. Create the links from the /nsr directory to the original location. d.
Chapter 3: UNIX Disaster Recovery Important: If you routinely move NetWorker backup media to an offsite location for safekeeping, and a subsequent file recover operation generates a mount request, the recover operation waits until an operator mounts the request media. To avoid delays when recovering files, use the mminfo -mv command to list the media that is associated with the file you want to recover and to retrieve the media from the offsite storage before starting the recover.
Prerequisites Task 4: Recover the NetWorker Server Bootstrap You can use the mmrecov command to recover the NetWorker server bootstrap. Note: In NetWorker release 6.0 and later, the mmrecov command is only used to recover the NetWorker server’s media database and resource database; the nsrck command is used to recover the server’s client file indexes. To recover the NetWorker server bootstrap: 1. Use the mmrecov command to recover the NetWorker server’s bootstrap (media database and resource database).
Chapter 3: UNIX Disaster Recovery Please insert the volume on which save set id 20076 started into /dev/rmt/0hbn. Once you have loaded the appropriate volume, the following message appears: Scanning /dev/rmt/0hbn for save set 20076; this might take a while... NetWorker then scans the volume for the appropriate save set and recovers it. The NetWorker media database and resource database are recovered when the following message appears: If your resource files were lost, they are now recovered in the ‘res.
Prerequisites Note: You can also restart the NetWorker server by running the NetWorker startup script for the appropriate platform. 5. After verifying that the NetWorker configurations are correct, remove the /nsr/res.orig directory. 6. Run the nsrjb -HE command to reset the autochanger. 7. If you are using an autochanger, run the nsrjb -Iv command to reinventory the autochanger; or run the nsrjb -Iv -S command to reinventory only the affected slots.
Chapter 3: UNIX Disaster Recovery Task 7: Recover the Application and User Data To recover the application and user data that was on the NetWorker server: 1. Log in as root. 2. Load and inventory the devices. This ensures that the NetWorker server can recognize the location of each volume. Note: If you load a clone volume, you must either delete the original volume from the media database or mark it as suspect in the media database.
Recovering a NetWorker Storage Node Recovering a NetWorker Storage Node The storage node allows you to access the volumes on which the backups for all of the network computers reside. If the storage node experiences a disaster, it must be recovered before you can restore application and user data to other computers on the network.
Chapter 3: UNIX Disaster Recovery Task 1: Install the NetWorker Storage Node To install the NetWorker storage node software: 1. Install the same version of the NetWorker storage node software into its original location. Note: If you want to upgrade the storage node software, first recover the storage node to its original state, and then perform the upgrade. 2. Install any NetWorker backup utility patches that were installed prior to the disaster. 3. Re-create any links to NetWorker directories. 4.
Prerequisites Important: Do not recover any UNIX operating system boot files that should not be overwritten during a recovery. For more information on boot files, see “Prerequisites” on page 28. 4. To set the recover options, select Recover Options from the Options menu. 5. In the Recover Options dialog box, selecting Overwrite Existing File.
Chapter 3: UNIX Disaster Recovery Recovering a NetWorker Client The following sections provide information on recovering a NetWorker client: • “Prerequisites” on page 43 • “How to Recover a NetWorker Client” on page 43 Prerequisites Before recovering the NetWorker client, ensure that the UNIX operating system is installed on the computer and that the NetWorker server is functional and available on the network.
Prerequisites 2. Install any NetWorker backup utility patches that were installed prior to the disaster. 3. Re-create any links to NetWorker directories. 4. Optionally, use the nwrecover program to perform a test recovery to ensure that the recovery process is functioning properly. Task 2: Recover the Application and User Data To recover the application and user data: 1.
Chapter 3: UNIX Disaster Recovery 7. Reboot the computer when the recovery is complete. The computer should now be restored as it was prior to the disaster. Note: By default, the directed recover option is enabled when you install the NetWorker client. If the directed recover option was disabled on the client before the disaster, you need to explicitly set this option to disable directed recoveries to this client. This option is set through the nsradmin command.
Prerequisites 3 46 Legato NetWorker, Release 7.
Chapter 4: Windows Disaster Recovery This chapter explains how to recover from a disaster on a host computer in the following configurations: • NetWorker release 7.x server or storage node on Microsoft Windows .NET or Windows 2000 • NetWorker release 7.x client on Microsoft Windows .NET, Windows XP Professional, Windows 2000, or Windows NT 4.0 Note: The term autochanger refers to a variety of robotic data storage devices, including autoloaders, carousels, datawheels, jukeboxes, and near-line storage.
Disaster Recovery Summary Procedures Disaster Recovery Summary Procedures The following summary procedures are intended to be used as a guide to the detailed procedures required for performing NetWorker disaster recovery on any supported Microsoft Windows platform. Experienced NetWorker administrators may find that these summary procedures are sufficient for most tasks. Users who want more information should refer to the detailed instructions in subsequent sections of this chapter.
Chapter 4: Windows Disaster Recovery Note: If the storage device required for a NetWorker server recovery is connected to a remote storage node, you might have to partially recover the storage node before you can recover the NetWorker server. For more information, see “Partial Recovery of a NetWorker Storage Node” on page 82. 5. If you know the bootstrap save set ID, recover the NetWorker media database and resource configuration files by running the mmrecov command from the command prompt.
NetWorker Client or Storage Node Recovery Summary Procedure 11. Recover the client’s data and SYSTEM save sets using the NetWorker User program. 12. Reboot the computer after the recovery is complete. 13. If you are using an autochanger with Removable Storage enabled: a. Use the Removable Storage MMC snap-in to mount the tape that contains the bootstrap. b. Run mmrecov to recover the NetWorker media database and resource configuration files. c. Stop the NetWorker services. d.
Chapter 4: Windows Disaster Recovery • For Windows 2000 NetWorker clients (or Windows .NET or Windows XP Professional clients for which an ASR disk or save set is not available), reinstall the operating system if necessary. For instructions, see “Recovering a Windows Installation” on page 60. • For Windows NT 4.0 NetWorker clients, repair the operating system if necessary. For instructions, see “Repairing a Windows NT 4.0 Operating System Installation” on page 57. 3.
Disaster Recovery of Clustered Computers Disaster Recovery of Clustered Computers For disaster recovery of a computer that was running NetWorker software in a cluster environment, see the appropriate chapter for procedures: • “Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0)” • “Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .
Chapter 4: Windows Disaster Recovery Performing Windows ASR Recovery Microsoft ASR is a feature of the Windows .NET and Windows XP Professional operating systems. For more information about NetWorker software support for ASR, including procedures for performing ASR backups and creating an ASR disk, refer to the Legato NetWorker Administrator’s Guide, Microsoft Windows Version. Important: The ASR recovery method is supported only for NetWorker clients on Windows .NET and XP Professional platforms.
ASR Recovery Requirements Important: To perform an ASR recovery, you must have an official Microsoft Windows installation CD for the version of Windows you are recovering. If you have only an OEM recovery CD that includes the Windows installation files, skip this section and proceed to “Recovering a Windows Installation” on page 60. Refer to the OEM documentation as necessary.
Chapter 4: Windows Disaster Recovery 4. When prompted, insert the ASR disk into the A: drive and press a key to continue. ASR formats the system partition, copies files, and begins the Windows installation. Note: Due to a Microsoft Windows XP Professional problem, when you are prompted to insert the ASR disk and press a key to continue, you may need to press a key several times before the system recognizes the disk and proceeds with the recovery. This problem does not occur on Windows .NET systems. 5.
Task 3: Verify the NetWorker Client Recovery For NetWorker clients with components that require special handling, do the following after ASR recovery: 1. Log on with administrator privileges to the target computer. 2. Start the NetWorker User program. 3. Click the Recover toolbar button. 4. In the Source Client dialog box, click OK to select the local client. 5. In the Destination Client dialog box, click OK to select the local client. 6.
Chapter 4: Windows Disaster Recovery Repairing a Windows NT 4.0 Operating System Installation This section explains how to use NetWorker software to create a Windows NT 4.0 Emergency Repair Disk (ERD), and how to use the ERD to repair a damaged Windows NT 4.0 operating system installation. To repair a Windows NT 4.0 operating system installation requires: • Windows NT 4.0 Setup Disks (three disks) • Windows NT 4.
Repairing Windows NT 4.0 • The NetWorker server you will use for the recovery includes in its Administrator list the account you will use to recover the REPAIRDISK save set. For details about meeting these requirements, refer to the Legato NetWorker Administrator’s Guide, Microsoft Windows Version. How to Use the NetWorker User Program to Create an ERD To create an ERD using the NetWorker User program: 1. Start the NetWorker User program. 2. Insert a blank, formatted disk in the A: drive. 3.
Chapter 4: Windows Disaster Recovery • Change to \bin before executing the recover.exe command. • At the command prompt, include the full path and filename to \bin\recover.exe. • Ensure that \bin occurs before %SystemRoot%\System32 in your PATH environment variable. To create an ERD using the NetWorker recover command: 1. On the NetWorker server, insert a blank, formatted disk into the A: drive. 2.
Recovering a Windows Installation 7. Follow the prompts on the screen to repair the Windows files: • Press [Enter] to repair the specified file. • Press [Esc] if you do not want to repair the specified file. 8. Reboot the computer. 9. The operating system should now be functional. If the operating system is not functional, see “Recovering a Windows Installation” on page 60.
Chapter 4: Windows Disaster Recovery • Host properties: – • Computer name – Fully qualified domain name – Administrator account password TCP/IP properties: – Adapter type – IP address – Default gateway – Subnet mask – DNS server – WINS server (if used) • Any other protocols installed • Removable Storage enabled/disabled settings • Virtual memory settings • Date and time properties • Localization properties 4 How to Recover the Windows Operating System To recover the operating
Recovery Requirements address as the original computer, you must reregister the NetWorker software. For information on registering NetWorker software, refer to the Legato NetWorker Installation Guide, Windows Version. Task 1: Install the Windows Operating System Important: If you want to upgrade Windows during the recovery, first recover the Windows version that was installed immediately prior to the disaster, then upgrade after you have completed the recovery. To install the Windows operating system: 1.
Chapter 4: Windows Disaster Recovery form the fully qualified domain name). For example, the fully qualified domain name for a computer named kingdome, might be kingdome.seattle.washington.com. e. Start the Control Panel Local Area Connection tool. f. In the Local Area Connection Status dialog box, click properties. g. In the Local Area Connection Properties dialog box, select Internet Protocol (TCP/IP) and click Properties. h.
Recovery Requirements 3. In the hosts file (%SystemRoot%\system32\drivers\etc\hosts) make an entry for the NetWorker server to be used in the recovery. NetWorker software requires this entry when: • DNS is not in use or no DNS server is available • The NetWorker server host you are recovering is also a DNS server The entry in the hosts file must include the IP address, the fully qualified domain name, and the computer name, all on the same line. For example: 123.56.890.474 kingdome.seattle.washington.
Chapter 4: Windows Disaster Recovery Task 2: Configure the Devices and Test the Operating System If the computer you are recovering is a NetWorker server or storage node, configure any devices required by the NetWorker software. To configure the devices and test the operating system: 1. Configure any devices required by the NetWorker software, for example SCSI pass-through devices for autochangers. 2. Ensure that Removable Storage is configured as it was prior to the disaster.
Recovering a NetWorker Server 4. To complete the recovery process: • For a NetWorker server, see “Recovering a NetWorker Server” on page 66. • For a NetWorker client or storage node, see “Recovering a NetWorker Client or Storage Node” on page 82. Recovering a NetWorker Server This section explains how to recover a NetWorker server on a Windows .NET or Windows 2000 host computer.
Chapter 4: Windows Disaster Recovery How to Recover a Windows 2000 NetWorker Server To recover a Windows 2000 NetWorker server, perform the following tasks in the order specified: • “Task 1: Install the NetWorker Server Software” on page 67 • “Task 2: Configure the NetWorker Server” on page 68 • “Task 3: Locate the NetWorker Server Bootstrap Save Set ID” on page 70 • “Task 4: Recover the NetWorker Server Bootstrap” on page 72 • “Task 5: Rename the Resource Configuration Files” on page 74 • “Task
NetWorker Server Recovery Requirements During the installation, keep the following points in mind: • If the NetWorker installation kit is available on a shared drive, you can install it over the network. • To update the NetWorker software, first recover the server to its state immediately prior to the disaster, then perform the update. • You do not need to reload the license enablers; they will be restored later in the recovery process.
Chapter 4: Windows Disaster Recovery autochanger does not support the -E option (to reinitialize the element status), use the sjiielm command to initialize the element status. d. If you need to determine which volume contains the bootstrap, inventory the autochanger by running the nsrjb -Iv command from the command prompt. If you know the slot number where the bootstrap is located, use the nsrjb -Iv -S # command to inventory that particular slot. e.
NetWorker Server Recovery Requirements Important: If the browse and retention policies are not long enough to cover all of the save sets you use, all of the NetWorker server’s records are recovered, but any records that are older than a month are discarded because the default browse policy is one month. 4. If the NetWorker server’s client file index has not been relocated from its original path, or if you are going to recover a relocated client file index from a backup created with NetWorker release 7.
Chapter 4: Windows Disaster Recovery a copy of the bootstrap information after each scheduled backup. The NetWorker server also writes the bootstrap information to the end of the savegrp.log file that is written for the backup. The following excerpt from a savegrp.log file shows a bootstrap save set ID of 1467388673 located on volume lacey.001. Also note the file and record numbers; having this information speeds the recovery process.
NetWorker Server Recovery Requirements Task 4: Recover the NetWorker Server Bootstrap In this task, you will recover the bootstrap save set. Recovering the bootstrap overwrites the media database in the \mm directory and recovers the resource configuration files to a temporary directory named \res.R. Note: The mmrecov command is used to recover only the media database and resource configuration files.
Chapter 4: Windows Disaster Recovery nsrmm -d volume_name For example, if the NetWorker software requests the original volume mars.1 but that volume is not available, run the following command to delete mars.1 from the media database: nsrmm -d mars.1 c. Restart the following NetWorker services: – NetWorker Backup and Recover Server – NetWorker Remote Exec Service d. Run the mmrecov command to recover the bootstrap. 4.
NetWorker Server Recovery Requirements The NetWorker software scans the volume for the appropriate save set and then begins the recovery. The NetWorker nsrmmdbasm command is used to recover the media database, and the uasm command is used to recover the resource configuration files. You can use the NetWorker Administrator program to monitor the recovery. Note: The media database might not be on the same volume as the resource configuration files.
Chapter 4: Windows Disaster Recovery 3. If you know which slots have changed configuration since the disaster, inventory only those slots.
NetWorker Server Recovery Requirements The following Removable Storage libraries have been detected: 1) scsidev@2.5.1: HP C1557A 2) scsidev@2.6.1: HP C1557A Which one do you want to install? 1 Name you would like to assign to the jukebox? rsmtemp Creating device \\.\Tape0... Jukebox has been added successfully Would you like to configure another jukebox? (yes/no) n 5. In the NetWorker Administrator Autochangers window, right-click the icon for the Removable Storage jukebox and select Operations. 6.
Chapter 4: Windows Disaster Recovery To recover the client file indexes: 1. To recover the client file indexes, run one of the following commands from the NetWorker server: • For all clients: nsrck -L7 • For a specific client: nsrck -L7 client_name 2. If you are recovering the client file indexes from a clone volume, you may be prompted to load the original volume. In that case: a. Enter [Ctrl]+[c] to exit nsrck. b.
NetWorker Server Recovery Requirements Task 8: Recover the NetWorker Server Data Important: Recovery of volume mount points and their data requires special handling. It cannot be done using save set recovery. If you attempt to recover a mount point and the mounted volume’s data in a single operation, the data will be recovered to the root of the host volume and recovery of the mount point will fail.
Chapter 4: Windows Disaster Recovery 4. Ensure that all drives that contained system information prior to the disaster are accessible. The system information includes the boot partition, system partition, and the partition that contains the databases and database logs for the system state components. 5. Start the NetWorker User program. 6. Click the Recover button. 7. In the Source Client dialog box, select the computer you are recovering and click OK. 8.
NetWorker Server Recovery Requirements If you do not select Overwrite Existing File, the recovery process pauses before any existing files are overwritten, and a Naming Conflict dialog box appears, prompting you to indicate how the NetWorker software should resolve filename conflicts. 13. Click Start to begin the recovery. Note: Files in the Windows Recycle Bin are not password protected. If the Password Protection dialog box appears, you can select Recover > OK to recover these files. 14.
Chapter 4: Windows Disaster Recovery 5. Start a Windows command prompt and change to the \bin directory. 6. From the command prompt, run the following command to recover the NetWorker server’s bootstrap: mmrecov 7. Stop the following NetWorker services: • NetWorker Backup and Recover Server • NetWorker Remote Exec Service 8. Rename the \res.R directory to \res. 9. Restart the NetWorker services. 10.
Recovering a NetWorker Client or Storage Node Recovering a NetWorker Client or Storage Node This section explains how to recover a Windows NetWorker client host computer or a Windows .NET or Windows 2000 storage node host computer. Notes: • For Windows .NET and Windows XP Professional systems, use the following procedure only as a last resort for recovering a NetWorker client or storage node. Instead, use the ASR recovery method if possible.
Chapter 4: Windows Disaster Recovery • Install the NetWorker client or storage node software to provide a storage device for the NetWorker server to use. For information, see “Task 2: Reinstall the NetWorker Client or Storage Node Software” on page 83. • Recover the NetWorker server. For information, see “Recovering a NetWorker Server” on page 66. • Perform the remaining tasks to recover the client or storage node.
Task 3: Recover the NetWorker Client or Storage Node Data 2. Install any NetWorker patches that were installed prior to the disaster. 3. Install the appropriate temporary enabler code for each Legato backup product. For temporary enabler codes, refer to the product installation guide. 4. If you are restoring a NetWorker storage node, ensure that the storage devices the NetWorker server will use are correctly configured. For details, refer to the appropriate NetWorker administrator’s guide. 5.
Chapter 4: Windows Disaster Recovery 2. Ensure that all drives that contained system information prior to the disaster are accessible. The system information includes the boot partition, system partition, and the partition that contains the databases and database logs for the system state components. 3. Start the NetWorker User program. 4. Click the Recover button. 5. In the Source Client dialog box, select the computer you are recovering and click OK. 6.
Task 4: Verify the NetWorker Client or Storage Node Recovery If you do not select Overwrite Existing File, the recovery process pauses before any existing files are overwritten, and a Naming Conflict dialog box appears, prompting you to indicate how the NetWorker software should resolve filename conflicts. 10. Click Start to begin the recovery. Note: Files in the Windows Recycle Bin are not password protected. If the Password Protection dialog box appears, select Recover > OK to recover them. 11.
Chapter 4: Windows Disaster Recovery • Errors regarding the recovery of Windows system-protected files For information about how the NetWorker software handles the Windows system state and system-protected files, refer to the Legato NetWorker Administrator’s Guide, Microsoft Windows Version. 3. Ensure that the storage node and the NetWorker server can detect the storage devices the NetWorker server is to use. 4. Perform a test recovery using each of the Legato backup products you have installed.
Recovery of DHCP and WINS Databases Important: To recover the DHCP database, you must have a NetWorker backup that includes the %SystemRoot%\System32\dhcp directory. To recover the WINS database, you must have a NetWorker backup that includes a local disk backup of the WINS database. For instructions on configuring DHCP and WINS servers to include these databases in scheduled NetWorker backups, refer to the Legato NetWorker Administrator’s Guide, Microsoft Windows Version. Note: For Windows .
Chapter 5: NetWare Disaster Recovery This chapter provides instructions on how to perform a disaster recovery on a NetWare system using the NetWorker software. Important: This chapter applies only to NetWorker clients and servers running NetWorker release 4.2.x, NetWare version.
Replacing a Hard Drive Replacing a Hard Drive To replace a hard drive: • “Obtain the Hard Drive Information” on page 90 • “Replace the Hard Drive” on page 90 • “Completing the Recovery Process” on page 91 Obtain the Hard Drive Information Before you replace the hard drive, you must obtain the following information about the drive: • Size of the drive • Size, format, and volume label assigned to each drive partition • NetWare Directory Services (NDS), the NDS tree topology, and the location of se
Chapter 5: NetWare Disaster Recovery Important: Do not delete any volume objects from the NDS tree. This would eliminate any references that other objects might have to a particular volume.
Prerequisites • Computer properties: – Computer name – DNS domain name – Administrator name and password • Device and SCSI drivers • Startup files, including autoexec.bat, config.sys, autoexec.ncf, and startup.ncf How to Recover the NetWare Operating System This section describes how to recover the NetWare operating system using the NetWorker software. Use this process to recover the NetWare operating system back to the original computer, or to a different computer with the same name.
Chapter 5: NetWare Disaster Recovery • Computer name • IPX network number and/or IP address For details, refer to the NetWare documentation. If you want to upgrade NetWare, first restore the operating system to its original state, and then perform the upgrade. 3. Install NDS into its original location using the install or nwconfig utility: • Use the same name as the original tree. • Use the same server name. • Use the same container and Administrator name.
Completing the Recovery Process Task 3: Test the Operating System and Configure Devices To test the operating system and configure the devices: 1. Configure any devices the NetWorker software requires. For example, SCSI pass-through devices for autochangers. 2. Perform a test to verify that the: • Name to Address resolution is correct. Test by running nslookup using the Fully Qualified Domain Name of the NetWare NetWorker backup server, client, or storage node.
Chapter 5: NetWare Disaster Recovery Prerequisites To recover the NetWorker server, you need the following: • Original version and patch level of NetWorker software • Original location of NetWorker software • Backup or clone volumes containing the: – NetWorker server media manager. By default, this directory is located in the SYS:NSR\MM directory. Important: Do not attempt to recover the legatomm file manually. Recover this file using the NetWorker Utilities Recover from a Disaster option.
Prerequisites Task 1: Install the NetWorker Software To install the NetWorker software: 1. Install the same version of NetWorker software into its original location. For installation instructions, refer to the Legato NetWorker Installation Guide, NetWare Version. • If you want to upgrade the NetWorker server, first recover the server to its original state, and then perform the upgrade. • You do not need to reload the license enablers if the NetWorker configuration files still exist.
Chapter 5: NetWare Disaster Recovery Task 3: Locate the Server’s Bootstrap Save Set ID This section describes how to locate the save set ID for the NetWorker server’s latest bootstrap. The NetWorker server’s bootstrap contains the server’s online file index, media index, and resource configuration files. Use the following steps to locate the save set ID of the most recent bootstrap if you do not have this information: 1.
Prerequisites 3. Enter the full name of the backup administrator (for example, “.cn=Admin.O= ‘top level container’”) into the User text box and the appropriate NetWare password into the Password text box and press [Enter]. The Device Selection window appears. 4. From the Device Selection window, select the device you intend to use and press [Enter]. 5. Insert the most recent media or clone volumes used for scheduled backups into the appropriate device.
Chapter 5: NetWare Disaster Recovery Task 5: Rename the NetWorker Server Configuration Files To rename the configuration files: 1. Unload all of the associated NLM files using nwdown. 2. Delete the existing files (NSR.RES and NSRJB.RES). 3. Rename the recovered files, which were renamed with a tilde (~) upon restore, to NSR.RES and NRJB.RES. 4. Restart the NetWorker software.
Prerequisites 7. From the [F2] File menu, select Start Recover, and press [Enter]. 8. If you have NDS data to restore, continue with “Task 7: Restore NDS Data” on page 100. If you do not have any NDS data to restore, continue with “Task 8: Complete the Server Recovery” on page 101. Task 7: Restore NDS Data Before performing an NDS backup or recover, refer to the Novell Application Notes section “Backing Up and Restoring Novell Directory Services in NetWare 4.11,” dated October 1996.
Chapter 5: NetWare Disaster Recovery Task 8: Complete the Server Recovery To complete the recovery of the server: 1. Use NetWorker software to recover the remaining data, including the client file indexes. In the Browser window, mark everything for recovery, and then unmark all still-operational volumes, LEGATOMM, the server’s LEGATODB, NSR.RES, NSRJB.RES, Schema, and NDS. Important: Recover each client file index by selecting the client folder from the indexes directory.
Recovering a Replicated NDS Partition Recovering a Replicated NDS Partition If the NetWare server did not contain an NDS partition (replicated or not), do not complete this section. Instead, complete only “Recovering the NetWare Operating System” on page 91 and “Recovering a NetWare NetWorker Server” on page 94. This section contains the following information on recovering a replicated NDS partition over the network: • “How to Recover a NetWare 4.10 SYS Volume” on page 102 • “How to Recover a NetWare 4.
Chapter 5: NetWare Disaster Recovery 3. Use NDS Manager or dsrepair to check the replica synchronization. If you see error messages, wait a few minutes and try again. 4. From the NetWorker server, perform a directed recover to restore the failed server’s Server Specific Info (SSI) files from a tape backup to a functioning NetWorker for NetWare client. The server-specific information files (SERVDATA.NDS, VOLSINFO.TXT, STARTUP.NCF, and AUTOEXEC.
Recovering a Replicated NDS Partition – Log in and specify the context for the server and its objects. Use the same context used before the disaster. – Edit the STARTUP.NCF and AUTOEXEC.NCF files to match the versions recovered with SSI. When the installation is complete, the server will contain all the files necessary to perform an SMS remote filesystem restore. For more information, see “Task 2: Restore the SMS Remote File System” on page 104.
Chapter 5: NetWare Disaster Recovery Task 3: Complete the Recovery of the NetWare 4.10 SYS Volume To complete the recovery of a NetWare 4.10 SYS volume: 1. If necessary, use NDS Manager or dsrepair to re-establish replicas on the repaired or replaced server. 2. Enter the following commands at the command prompt: LOAD TSA410 LOAD TSANDS LOAD TSA500 3. From the Recover Browser window, recover the server object, volume objects, and any objects that formerly referenced the recovered volume or server objects.
Recovering a Replicated NDS Partition Task 1: Recover the NetWare SYS Volume To recover a NetWare 4.11 or IntraNetWare SYS volume: To recover a SYS volume: 1. From the NetWorker server, perform a directed recover to restore the failed server’s Server Specific Info (SSI) files from a tape backup to a functioning NetWorker for NetWare client. The server-specific information files (SERVDATA.NDS, DSMISC.LOG, VOLSINFO.TXT, STARTUP.NCF, and AUTOEXEC.
Chapter 5: NetWare Disaster Recovery 4. Use dsrepair to perform an unattended full repair to ensure the ring is functioning properly. Refer to DSMISC.LOG to determine which replicas were stored on the failed server. If DSMISC.LOG shows that no other server has exactly the same replicas as the failed server, run dsrepair on any servers containing replicas of partitions on the failed server. 5. Shut down the failed server and replace any damaged hardware.
Recovering a Replicated NDS Partition e. Press [Enter], and both the files and NDS are copied to the new server. DSMISC.LOG, VOLSINFO.TXT, and AUTOEXEC.NCF are copied to the SYS:SYSTEM directory. STARTUP.NCF is copied to the C:\NWSERVER directory. f. The NDS restoration uses the information from SERVDATA.NDS (TSANDS.NLM is not needed). NDS is now fully functional on the server, but the partitions and replicas must still be reestablished. g.
Chapter 5: NetWare Disaster Recovery 3. Recover the filesystem for each volume affected by the failure. Do not recover the Schema and [Root]; they will be restored from a replica. You also do not need to recover Server Specific Info again. When prompted, suppress further prompting and overwrite files. If the failed server had non-SYS volumes that were not affected by the failure, no further action is needed because the SERVDATA.NDS file preserves the trustee assignments on these other volumes. 4.
Recovering a Replicated NDS Partition 5 110 Legato NetWorker, Release 7.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) This chapter describes how to recover one or more computers in a Windows NT 4.0 cluster.
Task 1: Evict Node_B from the Cluster Task 1: Evict Node_B from the Cluster To evict Node_B from the cluster: 1. Ensure that the cluster resources failed over to Node_A, the working node. This includes the quorum disk and any shared disks. 2. If any of the data that failed over from Node_B to Node_A is corrupt, use the NetWorker software to recover the data. Note: You may need to shut down some cluster resources that depend on this data. 3.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) Task 3: Reinstall the NetWorker Software To reinstall the NetWorker software, on Node_B: 1. Log on to the same domain as Node_A. 2. Install the NetWorker software. For instructions, refer to the Legato NetWorker Installation Guide, Microsoft Windows Version. Task 4: Recover the Data on Node_B To recover the data on Node_B: 1. Recover all the hives in the registry or system state. 2.
Task 2: Replace the Hard Drive 2. If the current shared disk’s resource group contains the shared disk and its dependent resources, move the cluster resources that represent the affected shared disk into the resource group you created in the previous step. 3. Take offline the resource group that contains the shared disk. Note: You do not need to create a new resource group if the shared disk’s resource group only contains resources that depend on it.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) Task 3: Recover the Data to the Shared Disk To recover the data that belongs to the shared disk: 1. Ensure that the NetWorker software is properly installed. For details, refer to the Legato NetWorker Installation Guide, Microsoft Windows Version. 2. Using the NetWorker User program, recover all the data that belongs to the shared disk. Note: If the resource group is a virtual server, you may need to perform a directed recovery.
Replacing the Quorum Disk and Recovering Its Data Replacing the Quorum Disk and Recovering Its Data This section provides information about the quorum resource and explains how to recover a quorum disk’s data. About the Quorum Resource If there is a communication failure between the nodes, the MSCS software uses the quorum resource in an arbitration process to determine the members of the cluster nodes.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) How to Replace the Quorum Disk and Recover Its Data To recover the quorum disk’s data: 1. Take offline any cluster resources or applications that depend on the quorum disk’s data. Important: Do not take the Cluster Service offline. 2. Change the quorum disk’s drive letter and replace the quorum disk with a new disk. Note: For detailed instructions, refer to the appropriate Microsoft documentation.
Task 1: Recover the System State and Quorum Data • “Task 2: Replace the Quorum Data with the Recovered Quorum Data” on page 118 • “Task 3: Evict Node_B from the Cluster” on page 119 • “Task 4: Install the Cluster Software and Patches on Node_B” on page 119 Task 1: Recover the System State and Quorum Data To recover the system state and quorum data: 1. Select a node in the cluster that has the good (and possibly the latest) backup of the system state and the quorum data.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) 3. Copy the existing quorum data from its original location to another directory. For example, copy: G:\MSCS to G:\TEMP\MSCS 4. Replace the existing quorum data with the recovered quorum data. For example, copy: G:\RECOVER\MSCS to G:\MSCS 5. Shut down Node_B. Task 3: Evict Node_B from the Cluster To evict Node_B from the cluster: 1. Reboot Node_A. 2. Open the Cluster Administrator and evict Node_B from the cluster.
Task 1: On Node_A, Install and Configure the Software In the following example: • Choose the node that has the most up-to-date backup of the cluster database (part of the registry) to serve as Node_A. • Defective nodes and shared drives have been replaced.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) 5. Install the MSCS software. 6. Install any required service pack software. Make sure that the version is greater than Service Pack 3. 7. If Node_A is a NetWorker server, configure the tape devices. 8. Log on to Node_A using the cluster account on the domain. Task 2: On Node_B, Install and Configure the Software To install and configure the software, on Node_B: 1.
Task 4: Perform a Disaster Recovery Task 4: Perform a Disaster Recovery To perform a disaster recovery: 1. Shut down Node_B. 2. Perform a NetWorker disaster recovery of Node_A. For details, refer to “Chapter 4: Windows Disaster Recovery” on page 47. 3. Restore the following directories: • Windows NT registry or system state • Windows NT system directory Select Overwrite and Suppress Messages. 4. Recover the quorum and the shared drives data. Follow the directed recovery procedure.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) 4. Replace the cluster shared disks. 5. Check the drive assignments through Windows Explorer. The “phantom” drives you see are the original shared disks. These drives cannot be deleted or disconnected from the Windows Explorer. 6. Remove the registry entries for the phantom disks: a.
Task 8: Join Node_B to the Cluster To check the disk signatures: 1. Replace the cluster shared disks with the new hardware: a. Using the Control Panel Services tool, start the Cluster Service with the -fixquorum startup option. This option allows you to fix or add a new quorum drive. b. Start the Cluster Administrator program and attach Node_A to the cluster you are restoring. c. Create the new disk resource for the quorum drive and place it in the Quorum Group.
Chapter 6: Microsoft Cluster Disaster Recovery (Windows NT 4.0) 4. Install the latest service pack software on Node_B. Make sure the version is greater than Service Pack 3. 5. If NetWorker Server is installed in Node_A as a failover server: a. Install NetWorker server software. b. Register the resource extension. This manages the NetWorker server resource type in Node_B. For more details, refer to the Legato NetWorker Installation Guide, Microsoft Windows Version. c.
Task 8: Join Node_B to the Cluster 6 126 Legato NetWorker, Release 7.
Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .NET) This chapter explains how to recover Microsoft Windows 2000 and Windows .NET MSCS host systems. Familiarity with MSCS concepts and operations is assumed. For complete information about MSCS, refer to the Microsoft documentation.
Recovering a Failed Quorum Disk Recovering a Failed Quorum Disk This section describes the procedure for recovering a failed quorum disk. The procedure requires the following: • The quorum disk is designated for exclusive use by MSCS. • The quorum disk resides in a drive array that is not a RAID. • A spare disk, identical in type to the quorum disk, must be available to replace the failed disk. The spare disk must have at least as much total disk space as the quorum disk that is being replaced.
Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .NET) where x is the drive letter of the old quorum disk. 12. Place the new disk resource in the Cluster Group. 13. Bring this disk resource online. 14. Right-click the cluster name and select Properties. 15. Select the Quorum tab and make the new drive the quorum resource. 16. Using the Computer Management Services tool, access the Cluster Service Properties dialog box and: a. Stop the Cluster service. b.
Recovering One Cluster Node To recover Node_B in this example scenario: 1. Using the Cluster Administrator on Node_A, evict Node_B from the cluster. 2. On Node_B, reinstall or clean up MSCS as follows: Windows 2000: a. Using the Control Panel Add/Remove Programs tool, uninstall the Windows component Cluster Service. b. Reboot Node_B. c. Log on to Node_B as Administrator for the domain in which the cluster nodes reside. d.
Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .NET) 8. In the Destination Client dialog box, select Node_A. 9. In the Recover window, mark the SYSTEM STATE save set. The cluster database is a component of the Windows system state, and is automatically backed up or restored with the SYSTEM STATE save set. Note: It is strongly recommended that you restore all of the SYSTEM save sets (SYSTEM STATE, SYSTEM DB, and SYSTEM FILES).
Recovering Multiple Cluster Nodes Recovering Multiple Cluster Nodes This section provides general guidelines for performing a cluster recovery in case both cluster nodes fail. In this scenario, the operating system is unusable on each node. Therefore, this recovery procedure includes reinstallation of Windows on each node, as well as NetWorker recovery of the cluster database.
Chapter 7: Microsoft Cluster Disaster Recovery (Windows 2000 and .NET) 6. For Windows 2000 systems, install the Cluster Service on Node_A: a. While Node_B is still detached from the shared SCSI bus, using the Control Panel Add/Remove Programs tool, add the Windows component Cluster Service. The Cluster Setup Wizard appears. b.
Recovering Multiple Cluster Nodes 7 134 Legato NetWorker, Release 7.
Chapter 8: Sun Cluster Disaster Recovery This chapter explains how to recover one or more computers in a Sun Cluster 3.x environment. This chapter includes the following sections: • “Prerequisites” on page 135 • “Restoring a Single Cluster Node” on page 135 • “Restoring an Entire Cluster” on page 136 Prerequisites To help prepare for a disaster, complete the Sun Installation and Planning Configuration worksheets.
Restoring an Entire Cluster How to Restore a Single Cluster Node To restore a single node: 8 1. Replace the damaged node and ensure that it is connected to the network. For information about replacing the hardware and verifying network connections, refer to the Sun Cluster 3.x Hardware Guide and the server documentation. 2. Reinstall the operating system and the Sun Cluster software on the recovered node and reconfigure the node to join the cluster.
Chapter 8: Sun Cluster Disaster Recovery Important: To help ensure a smooth recovery process, have a copy of the Sun Installation and Planning Configuration worksheets on hand. These worksheets are located in the Sun Cluster 3.0 Release Notes and should be completed before setting up the Sun Cluster. Task 1: Replace the Damaged Hardware To replace the damaged hardware: • Replace all damaged nodes and ensure that network connections are working.
Restoring an Entire Cluster Task 3: Recover the Data This section describes how to recover the NetWorker server as well as the physical and virtual NetWorker clients. 8 On the primary node for the NetWorker server: 1. Recover the highly available NetWorker server data as you would a stand-alone NetWorker server. For information about recovering a NetWorker server, see “Chapter 3: UNIX Disaster Recovery” on page 25.
Chapter 9: HP TruCluster Disaster Recovery This chapter explains how to recover one or more computers in an HP TruCluster Server environment, releases 5.0A to 5.1B. This chapter includes the following sections: • “Prerequisites” on page 139 • “Restoring One or More Nodes in a Cluster” on page 140 • “Restoring an Entire Cluster” on page 143 Prerequisites Preparing for a disaster involves two major tasks, recording information and backing up the cluster.
Back Up the Cluster • System topology information. Generate this information using the hwmgr -view command: # hwmgr -view hierarchy > sys_topology_file where sys_topology_file is a file to which you are saving output from the hwmgr -view hierarchy command. • The device layer information. Generate this information as follows: # hwmgr -view devices > device_layer 9 where device_layer is a file to which you are saving output from the hwmgr -view devices command.
Chapter 9: HP TruCluster Disaster Recovery How to Restore One or More Nodes in a Cluster To recover one or more physical cluster nodes, complete the following tasks: • “Task 1: Replace the Damaged Hardware” on page 141 • “Task 2: Verify Hardware Mappings” on page 141 • “Task 3: Partition the Down Node’s Boot Drive” on page 141 • “Task 4: Update the Cluster Configuration” on page 141 • “Task 5: Recover the Node-Specific Data” on page 142 9 Task 1: Replace the Damaged Hardware Replace the damaged
Restoring One or More Nodes in a Cluster To update the cluster configuration: 1. Delete the cluster node: # clu_delete_member -m member# where member# is the number of the cluster node. 2. Remove the node’s boot partition domain: # rmfdmn rootmember#_domain 9 3. Add the computer back into the cluster using the clu_add_member command. For more information about adding a cluster node, refer to the TruCluster documentation.
Chapter 9: HP TruCluster Disaster Recovery recover> delete dvrdevtab* recover> force recover> recover where cluster_default_alias is the name of the cluster and member# is the member ID of the down cluster node. 3. Use the NetWorker recover command to recover the node’s dev and devices directories, as in the following example. Note: The noforce option is used in this step so that the recovered files do not overwrite the existing files.
Restoring an Entire Cluster 9 • “Task 4: Install the NetWorker Software” on page 145 • “Task 5: Configure NetWorker Device and Autochanger Resources” on page 146 • “Task 6: Locate the Server’s Bootstrap Save Set ID” on page 146 • “Task 7: Recover the Server’s Bootstrap” on page 147 • “Task 8: Locate the Server’s Client File Index Save Set IDs” on page 148 • “Task 9: Recover the Server’s Client File Index” on page 149 • “Task 10: Re-create the Cluster” on page 150 • “Task 11: Recover the Clu
Chapter 9: HP TruCluster Disaster Recovery If you need to remap device numbers, use the -e option with the following command: # dsfmgr -e dsk10 dsk4 where dsk10 is the new disk enumeration value and dsk4 is the original disk enumeration value. Alternatively, if you want to move a device number, use the -m option. # dsfmgr -m dsk10 dsk4 9 Task 4: Install the NetWorker Software Perform this task if the NetWorker server was installed as a highly available cluster application.
Restoring an Entire Cluster Task 5: Configure NetWorker Device and Autochanger Resources To configure the Device and Autochanger resources: 9 • To recover data using a stand-alone device, ensure that the stand-alone Device resource exists (defined in the /nsr/res directory). If the stand-alone Device resource does not exist, create it using the NetWorker Administrator program. • To recover data using an autochanger, ensure that the Autochanger resource exists (defined in the /nsr/res directory).
Chapter 9: HP TruCluster Disaster Recovery 2. At the system prompt, switch to the directory where the NetWorker binaries and executables are located. 3. If you are using an autochanger, insert the first volume of the bootstrap save set into the first drive of the autochanger using the following command: # nsrjb -lnv -S slot -f device-name where: – slot is the slot where the first volume is located – device-name is the pathname for the first drive.
Restoring an Entire Cluster What is the name of the device you plan on using /dev/ntape/tape0_d1 3. When the following message appears, enter the save set ID for the latest bootstrap. If you are recovering a cloned version of the bootstrap, specify the save set ID associated with the clone. Enter the latest bootstrap save set ID []: 20076 4. When the following message appears, enter the file number to begin the recovery. If unknown, press [Enter]. 9 Enter starting file number (if known) [0]: 130 5.
Chapter 9: HP TruCluster Disaster Recovery To locate the client file index save set IDs, use the mminfo command to display the client file index’s save set ID: # mminfo -av -N index:cluster_default_alias where cluster_default_alias is the name of the cluster. Task 9: Recover the Server’s Client File Index In this task, you recover the most recent client file index from the last full backup and all subsequent incremental backups.
Restoring an Entire Cluster Task 10: Re-create the Cluster To re-create the cluster, run the clu_create command: # clu_create For more information about installing the cluster, refer to the TruCluster documentation. Note: Do not reboot after running clu_create. Remain in stand-alone HP Tru64 mode. 9 Task 11: Recover the Cluster Data To recover the cluster data: 1.
Chapter 9: HP TruCluster Disaster Recovery recover> delete etc/dfsl* recover> delete dvrdevtab recover> cd /cluster/members/member1 recover> delete boot_partition dev devices recover> delete etc/ddr* recover> delete etc/gen* 9 recover> delete etc/dfsl* recover> delete dvrdevtab where cluster_default_alias is the name of the cluster. 3. Repeat the following delete command for each cluster member, except for cluster members 0 and 1.
Restoring an Entire Cluster Note: When prompted to overwrite files, enter N to prevent files from being overwritten. 5. Unmount the /mnt directory: # unmount /mnt/var /mnt/usr /mnt 6. Shut down the system and boot the primary node off of its shared HP Tru64 member boot drive. 7. Although optional, you should recompile the kernel using doconfig on the primary node, and then reboot. 9 8.
Chapter 10: HP-UX Cluster Disaster Recovery This chapter explains how to recover one or more computers in an HP-UX MC/ServiceGuard cluster environment. This chapter includes the following sections: • “Recovering a Single Cluster Node” • “Performing a Cluster-Wide Recovery” on page 154 Recovering a Single Cluster Node This section describes how to recover a cluster server on one node. This scenario assumes that the operating system on the participating nodes has failed and must be reinstalled.
Performing a Cluster-Wide Recovery Performing a Cluster-Wide Recovery This section describes how to perform a complete cluster recovery, including reinstalling the operating system on all nodes in the cluster.
Chapter 10: HP-UX Cluster Disaster Recovery 3. Run the NetWorker NetWorker.cluster script located in the /opt/NetWorker/bin/ directory. Note: Do not re-create the legato.control and pkg.control files when prompted by the NetWorker.cluster script. 4. If the shared disk has to be replaced, configure the disk and filesystem of the replacement disk. 5. Create the filesystem, as follows: # vgchange -c n /dev/vg03 # vgchange -a y /dev/vg03 # newfs -F hfs /dev/vg03/rlvol1 # vgchange -a n /dev/vg03 6.
Performing a Cluster-Wide Recovery Task 4: Restore the Data To restore the data: 1. Perform a disaster recovery on the shared disk using mmrecov and recover. For more information about performing a disaster recovery, refer to the Legato NetWorker Administrator’s Guide, UNIX Version. When you shut down the NetWorker software during this step, use cmhaltpkg and not nsr_shutdown, as follows: # cmhaltpkg networker # exchange -a c /dev/vg03 # mount /dev/vg03/lvol1 /vg031 # mv /vg031/nsr/res /vg031/nsr/res.
Chapter 11: Legato AAM for AIX, HP-UX, and Linux Disaster Recovery This chapter explains how to recover one or more computers in an Automated Availability Manager (AAM) for an AIX, HP-UX, or Linux environment. This chapter includes the following sections: • “Recovering a Single Cluster Node” • “Performing a Cluster-Wide Recovery” on page 159 • “Renaming the Resource Directory” on page 164 Recovering a Single Cluster Node This section describes how to recover a failed node within a cluster.
Recovering a Single Cluster Node 4. Make sure to restore the following directories: AIX • /etc/rc* • $FT_DIR/config/* • $FT_DIR/log/* • $FT_DIR/ HP-UX • /etc/rc* • $FT_DIR/config/* • $FT_DIR/log/* • $FT_DIR/ Linux 11 • /etc/rc*.d • /etc/init.d • $FT_DIR/config/* • $FT_DIR/log/* • $FT_DIR/ 5.
Chapter 11: Legato AAM for AIX, HP-UX, and Linux Disaster Recovery If the virtual server fails to start on the node because of an outdated sites file, copy the following file from the active node: $FT_DIR/config/domain_name_sites 7. Run the networker.cluster script, as follows: AIX: /usr/bin/networker.cluster HP-UX: /opt/networker/bin/networker.cluster Linux: /usr/sbin/networker.cluster If you have already restored or copied the nw_ux.
Performing a Cluster-Wide Recovery 2. Install the AAM software. For detailed instructions, refer to the Legato Automated Availability Manager Installation Guide. 3. Install the NetWorker software. For detailed instructions, refer to the appropriate Legato NetWorker Installation Guide. 4. Make sure that the NetWorker client and server software are running locally. Task 2: Restore the Cluster 1.
Chapter 11: Legato AAM for AIX, HP-UX, and Linux Disaster Recovery 2. On the primary node, enter the scanner command to restore the following configuration files: scanner -S saveset_id device_path -x uasm -rv -i Y path_name where the device_path is the platform configuration and system files listed in step 1. Task 3: Configure NetWorker Software as a Highly Available Application On the primary node, configure the NetWorker software as a highly available application: 1. Run the envsh script.
Performing a Cluster-Wide Recovery Task 4: Restore the Data The procedures to restore the data on the primary and each of the remaining nodes in the cluster differ. For more information, see the following sections: • “On the Primary Node” on page 162 • “On Each of Remaining Node in the Cluster” on page 162 On the Primary Node To restore data on the primary node: 1. Use the mmrecov command to restore the indexes, media database, and resource files. 2.
Chapter 11: Legato AAM for AIX, HP-UX, and Linux Disaster Recovery 4. Recover or copy the following files from the active node: AIX • /usr/bin/nw_ux.lc • $FT_DIR/bin/envsh (envcsh for C-shell) HP-UX • /opt/networker/bin/nw_ux.lc • $FT_DIR/bin/envsh (envcsh for C-shell) Linux • /usr/sbin/nw_ux.lc • $FT_DIR/bin/envsh (envcsh for C-shell) For detailed instructions on using the recover and mmrecov commands, refer to the man pages or the Legato Command Reference Guide.
Renaming the Resource Directory Renaming the Resource Directory This section describes how to rename the resource directory. While performing a disaster recovery on a shared disk, you may need to rename the resource directory. To rename the resource directory: 1. Use the AAM Console to stop the NetWorker resource group. 2. Use the AAM Console to activate and mount the following: a. If using the Logical Volume Manager, activate the volume group by bringing the logical volume group datasource online. b.
Chapter 12: HACMP for AIX Disaster Recovery This chapter explains how to recover one or more computers in a High Availability Cluster Multiprocessing for AIX (HACMP for AIX) 4.5 environment.
Recovering an Entire Cluster How to Recover a Single Node To recover a single node: 1. Install the NetWorker software. 2. Start the NetWorker client. 3. From an unaffected node in the cluster, use the virtual NetWorker server to restore the node's data and software from a recent backup. 4. From an unaffected node in the cluster, use the SMIT utility to synchronize the cluster topology and resources.
Chapter 12: HACMP for AIX Disaster Recovery 2. From one node in the cluster: a. Determine the save set ID that contains the following configuration directories: – /etc/objres – /usr/es/sbin/cluster/etc/objres – /usr/es/sbin/cluster/etc/vg Note: The configuration directories in the previous list are valid for the HACMP Extended Scalability (HACMP/ES) version of HACMP. The actual configuration directory path may vary depending on your version of HACMP.
Recovering an Entire Cluster 2. Use the mmrecov command to restore the media database and resource files. 3. Complete the recovery of the resource database. In step 2, mmrecov recovered the resource directory to a temporary directory named res.R. This is because the resource database cannot be overwritten while the NetWorker software is running. To complete the recovery of the resource database: a. Stop the NetWorker resource group using the SMIT utility. b.
Glossary This glossary provides definitions for terms used in this guide. ACL An abbreviation for access control list. This is a list that specifies the permissions assigned to a specific file or directory. To recover a file that has an associated ACL, you must either be logged into the system as root, as Administrator, or as the file’s owner. active group A NetWorker backup group that has its Autostart attribute enabled.
Glossary Glossary annotation A comment that you associate with an archive save set to help identify that data later. Annotations are stored in the media index for ease of searching and are limited to 1,024 characters. archive The process by which NetWorker software backs up directories or files to an archive volume and then grooms them to free disk space. When data is archived, it is written to one or more storage volumes and then marked so that it is never subject to automatic recycling.
Glossary A code that is unique to your network that unlocks the software for permanent use. autochanger A mechanism that uses a robotic arm to move media among various components located in a device, including slots, media drives, media access ports, and transports. Autochangers automate media loading and mounting functions during backup and recovery. The term autochanger refers to a variety of robotic libraries, including autoloader, carousel, datawheel, jukebox, library, and near-line storage.
Glossary Glossary 172 browse policy A policy that determines how long entries for backup data remain in the client file index. carousel A tray or tape cartridge that holds multiple backup volumes. client A computer that accesses the NetWorker server to back up or recover files. Clients may be workstations, computers, or fileservers. client file index A database of information maintained by the NetWorker server that tracks every database object, file, or filesystem backed up.
Glossary To create a complete backup of a save set by merging the most recent level 1 save set with its corresponding full level save set. For more information, refer to the nsrssc man page or the Legato Command Reference Guide. continued save set Data associated with a save set that is continued from a previous volume. Continued save sets are created by the backup server when large save sets are being backed up, cloned, or archived to multiple volumes.
Glossary Glossary directive An instruction that directs the NetWorker software to take special actions on a given set of files for a specified client during a backup. domain controller A Microsoft Windows computer that stores directory data and manages user interactions with a domain, including logon, authentication, directory searches, and access to other shared resources. drive When DDS is enabled, refers to the physical backup object, such as a tape drive, disk, or file. See also device.
Glossary A system designed to prevent unauthorized access to or from a private network. All messages entering or leaving the intranet pass through the firewall, which examines each message and blocks those that do not meet the specified security criteria. There are several types of firewall techniques. The NetWorker software supports client backups from computers that are protected by packet filtering. fork A subprocess the NetWorker software creates to perform a requested operation.
Glossary level A measurement that determines how much data NetWorker software saves during a scheduled or manual backup. Glossary A full (f) backup backs up all files, regardless of whether they have changed. Levels one through nine [1-9] back up files that have changed since the last lower numbered backup level. An incremental (incr) backup backs up only files that have changed since the last backup. 176 library See autochanger.
Glossary The physical storage medium to which backup data is written. NetWorker software supports tape, magnetic or optical disk, and filesystems as backup media. See also volume. media database A database that contains indexed entries about the storage volume location and the life cycle status of all data and volumes the NetWorker server manages. See also volume.
Glossary Glossary 178 notification A message generated and sent to the NetWorker administrator about important NetWorker events. online indexes The databases located on the NetWorker server that contain all the information pertaining to the client backups (client file index) and backup volumes (media database). operator The person who monitors the server status, loads backup volumes into the server devices, and otherwise executes the day-to-day NetWorker tasks.
Glossary A set of constraints that specify how long an entry can remain in a client’s online file index. When a policy expires, the save sets associated with that policy are marked recyclable. Each Client resource uses two policies: a browse policy and a retention policy. pool A feature that enables you to sort backup data to selected volumes. A pool contains a collection of backup volumes to which specific data has been backed up.
Glossary A component of the NetWorker software that describes the NetWorker server and its clients. Devices, schedules, clients, groups, and policies are examples of NetWorker resources. Each resource contains a list of attributes that define the parameters to use for the specific NetWorker resource. resource database A database that contains information about each of the configured backup server’s resources. resource owner The cluster (logical, not physical) host that owns the resource.
Glossary The process that merges a level 1 backup with the last full backup of a save set to create a new full backup. See also level. save set ID An internal identification number that NetWorker software assigns to a save set. save set recover The recovery of specified save sets to the NetWorker server. save set status The NetWorker attribute that indicates whether a given save set is restorable, recoverable, or recyclable.
Glossary Glossary 182 SMS An abbreviation for system management software, which is a Microsoft-based software installation system that allows the wide-scale, automatic installation of software products on clients from a single remote server. SNMP An abbreviation for Simple Network Management Protocol, which is a protocol that defines the communication between a manager (sometimes called a monitor or management station) and an object (the item being managed).
Glossary versions The date-stamped collection of available backups for any single file. virtual cluster client A NetWorker client that is not permanently bound to a physical machine, but is instead managed by a cluster manager. It can be bound to more than one physical machine in the cluster and can own its own data disks. It is also referred to as a logical cluster client or a virtual client. virtual server The term used by Microsoft to denote a cluster server.
Glossary Glossary 184 Legato NetWorker, Release 7.
Index A AIX HACMP cluster, recovering 165 AIX, recovering AAM for AIX 157 application data recovering on NetWorker client UNIX 44 Windows 84 recovering on NetWorker server NetWare 99 UNIX 39 Windows 78 recovering on storage node UNIX 41 Windows 84 audience 15 autochanger NetWare resource, configuring 96 UNIX resetting 34 resource, creating 34 Windows removable storage disabled, restoring with 68 removable storage enabled, restoring with 80 resetting 74 Automated Availability Manager for AIX, HP-UX, Linux re
Index Index C-C recovering a single node 140 adding node 141 hardware mappings, verifying 141 partitioning boot drive 141 recovering unshared node date 142 removing/re-adding node 141 replacing hardware 141 recovering all nodes 143 configure cluster software 144 configure NetWorker software 146 hardware mappings, verifying 144 install NetWorker software 145 locating bootstrap 146 locating client file index 148 recovering bootstrap 147 recovering client file index 149 recovering the cluster data 150 re-cre
Index D-D Legato NetWorker, Release 7.0 Disaster Recovery Guide nsrmmdbasm 74 ping 60, 65 recover -c 59 recover.exe 58 scanner 71 scanner -B 49, 71 sjiielm 69, 75 uasm 74 Windows 2000 or .NET cluster chkdsk 132 net start clussvc 131, 133 net stop clussvc 130, 133 Windows NT 4.
Index E-I configuring 34 testing 31 Windows configuring 65 testing 65, 74 dfsmgr -e, HP TruCluster 145 disaster definition 19 preparing for 21 recovery prerequisites 22 documentation, product 15 drive replacing, NetWare 90 replacing, UNIX 27 replacing, Windows 52 drives, phantom 123 dsrepair, NetWare 90, 101, 103, 105–106, 109 Dynamic Host Configuration Protocol (DHCP) database 87 E Emergency repair disk creating, Windows NT 57 using, Windows NT 59 end user data See user data envsh, AAM for AIX, HP-UX, Li
Index J-N mmrecov, UNIX 36–37 mmrecov, Windows 49–50, 68–69, 72, 74, 81 mount, HP-UX cluster 156 mt, UNIX 31 multiple disaster recoveries performing in UNIX 26 performing in Windows 51 J jbconfig, HP TruCluster 146 jbconfig, UNIX 34 jbconfig, Windows 48–49, 68, 75 jukebox See autochanger N K key information before a disaster, gathering 22 L legatomm file 95 licensing and registration 18 limitations, Windows OEM recovery CD Linux, recovering AAM for Linux 157 load NETUTIL, NetWare 97 LOAD TSA, NetWare
Index Index O-O UNIX 34 Windows 68 installing NetWare 96 UNIX 33 Windows 67 locating bootstrap save set ID NetWare 97 UNIX 34 Windows 70 recovering NetWare 94 UNIX 32 Windows 66 recovering configuration files NetWare 99 UNIX 37–38 Windows 74 recovering user data on NetWare 99 UNIX 39 Windows 78 testing backup and recovery NetWare 101 UNIX 39 Windows 81 NetWorker storage node installing UNIX 41 Windows 83 recovering UNIX 40 Windows 82 NetWorker Utilities program, NetWare newfs, HP-UX cluster 155 nslookup,
Index P-R P packet-filtering, firewalls 175 partition, recovering a replicated NDS partition 102 partmgr, NetWare 102 phantom drives 123 ping, UNIX 31 ping, Windows 60, 65 policies browse, Windows 69 retention, Windows 69 preparing for a disaster 21 prerequisites automated system recovery, Windows Q quorum disk recovering, Windows 2000 or .NET 128 recovering, Windows NT 4.0 Cluster 116 R 53– 54 Legato NetWorker, Release 7.
Index Index S-S recovering IntraNetWare SYS volume 105 recovering multiple computers, consideration Windows 51 recovering NDS data 100 recovering NetWare 4.10 SYS volume 102 recovering NetWare 4.11 SYS volume 105 recovering NetWare 5.
Index T-W installing NetWorker NetWare 96 UNIX 33 Windows 67 recovering NetWorker NetWare 94 UNIX 32 Windows 66 shutdown NetWorker, UNIX 34 services information test 17 setting browse policy, Windows 69 retention policy, Windows 69 shutdown NetWorker server UNIX 34 sjiielm, HP TruCluster 146 sjiielm, UNIX 34 sjiielm, Windows 69, 75 storage node See NetWorker storage node summary recovery steps UNIX 26 Windows 48, 51 Sun cluster restoring all nodes 136 restoring single node 135 support, technical 17 SYS vol
Index W-W Windows Cluster, 2000 or .NET recovering multiple nodes 132 recovering quorum disk 128 recovering server 127 recovering single node 129 recovery prerequisites 127 Windows Cluster, NT 4.
