This section provides an overview of the DRM set up tasks. Additional details are available in subsequent sections, also you will find a helpful checklist containing implementation considerations, see "Disaster Recovery Manager Checklist".
Set Up for Server Recovery
Set Up for Storage of Client Recovery Information
| Task | Required Privilege Class |
|---|---|
| Register license for Disaster Recovery Manager | System |
To add support for DRM you must register the DRM license. You can register the license by entering the following:
register license file=drm.lic
For additional information, see "Registering Licensed Features".
You can store information about the machine on which an ADSM server resides. This information is later retrieved as input to your disaster recovery plan file. During disaster recovery this information is necessary for rebuilding the replacement machine.
To store information about the machine that contains the ADSM server, issue the DEFINE MACHINE command (see "Defining Machine Information") and set the ADSMSERVER parameter to YES.
You can also include additional details about hardware, software, and boot media information by following the steps in "Defining Machine Information" and "Defining and Tracking Recovery Media".
Before creating a disaster recovery plan, create backup copies of your primary storage pools and your database. The order in which you create these backups is significant. You should always back up your primary storage pools prior to backing up your database. The following examples show the commands to do these tasks:
backup stgpool backuppool cstoragepf
backup db devclass=lib8mm type=full volumename=bk06
If you are manually sending your backup media offsite, see "Sending Server Backup Volumes Offsite". If you are using virtual volumes and need information about virtual volumes, see Chapter 4. "Storing Data on Another Server".
When your backup media has been marked offsite, you are ready to create a disaster recovery plan. For more information, see "Creating the ADSM Server Disaster Recovery Plan".
If you are manually sending your backup media offsite, see "Sending Server Backup Volumes Offsite". If you are using virtual volumes and need information about virtual volumes, see Chapter 4. "Storing Data on Another Server".
When your backup media is both located offsite and has been marked offsite, you are ready to create a disaster recovery plan.
When you issue the PREPARE command, DRM automatically queries the ADSM database and generates a disaster recovery plan file.
In the following example, the PREPARE command is issued with the PLANPREFIX parameter to generate the recovery plan file in directory /u/server/recoveryplans/:
prepare planprefix=/u/server/recoveryplans/
The plan file name always includes the date and time (yyyymmdd.hhmmss) when the PREPARE command is issued. For example:
/u/server/recoveryplans/19950925.120532
For details about specifying the location of the disaster recovery plan, see "Prefix for Recovery Plan File", and also refer to the PREPARE command in the ADSM Administrator's Reference.
DRM creates one copy of the disaster recovery plan file. It is recommended that you create multiple copies of your disaster recovery plan for safekeeping. For example, keep copies in print, on diskettes, or on NFS-mounted disk space that is physically located offsite.
Issue the PREPARE command or schedule it to run after the storage pools and database have been backed up and the volumes have been marked offsite. This ensures that your disaster recovery plan is current.
When you issue the PREPARE command any existing files are not deleted. You should periodically delete downlevel recovery plan files.
DRM allows you to store recovery information for client machines backed
up by the ADSM server.
| Task | Required Privilege Class |
|---|---|
| Defining machine information
Associating client nodes with machines Defining and tracking machine recovery media Associating recovery media with machines | System |
Machine information is used to store details about the machine on which a client node resides. In the event of a disaster, this information can help you identify what you need to rebuild or restore the replacement machines.
Define the following information in the ADSM database:
| Note: | The machine characteristics and machine recovery instructions do not have to be defined during the set up process. You can return to this step later. |
The following example defines machine mach22 in building 021, 2nd floor, in room 2929, and has a priority value of 1:
define machine mach22 building=021 floor=2 room=2929 priority=1
During disaster recovery, this association information is used to determine what ADSM client nodes resided on machines that have been destroyed. The file spaces associated with these client nodes should be restored. The following example associates node CAMPBELL with machine mach22:
define machnodeassociation mach22 campbell
You can query your machine definitions by issuing the QUERY MACHINE command. For an example, see the query machine output in "Recovering ADSM Clients Scenario".
The following partial output is from a query on an AIX client machine.
+--------------------------------------------------------------------------------+ |--1 Host Name: mach22 with 8 MB Memory Card | |--- 16 MB Memory Card | |--- | |--4 Operating System: AIX Version 3 Release 2 | |--- | |--- Hardware Address: 10:00:5x:a8:6a:46 | +--------------------------------------------------------------------------------+
Characteristics and recovery instructions must be specified with separate INSERT MACHINE commands.
insert machine mach22 1 characteristics="Host Name: mach22 with 8 MB Memory Card" insert machine mach22 2 characteristics="Operating System: AIX Version 3 Release 2"
insert machine mach22 1 - recoveryinstructions="Recover this machine for accounts receivable dept."
To help automate the insertion of client machine information, a sample awk script named machchar.awk.smp is shipped with DRM. The following example shows how to write a local procedure to insert machine characteristics.
The file, clientinfo.txt, is then processed by the awk script, which builds an ADSM macro of INSERT commands (one INSERT command for each line in the file).
The macro is then executed to load the data into the ADSM database.
From an AIX prompt, issue the following commands:
echo "devices" > clientinfo.txt lsdev -C | sort -d -f >> clientinfo.txt echo "logical volumes by volume group" >> clientinfo.txt lsvg -o | lsvg -i -l >> clientinfo.txt echo "file systems" >> clientinfo.txt df >> clientinfo.txt
Figure 64 is an example procedure named machchar to insert machine characteristics. The machchar.awk.smp script is shipped with DRM and is located in the /usr/lpp/adsmserv/bin directory.
Figure 64. Example of Awk Script File to Insert Machine Characteristics
# Read machine characteristics from a file and build ADSM macro commands
# to insert the information into the machine characteristics table.
# Invoke with:
# awk -f machchar.awk -v machine=acctrcv filewithinfo
BEGIN {
print "delete machine "machine" type=characteri"
}
{
print "insert machine "machine" "NR" characteri=\""$0"\""
}
END {
}
|
The machchar.awk script is then executed from a AIX prompt as follows:
awk -f machchar.awk -v machine=acctrcv clientinfo.txt > clientinfo.mac
> dsmadmc -id=xxx -pw=xxx macro clientinfo.mac
You can view your machine characteristics by issuing the QUERY MACHINE command with FORMAT=CHARACTERISTICS parameter.
Your client recovery information is now saved in the ADSM database.
Use the following commands to save a description of the bootable media required to reinitialize or reinstall an operating system on a client machine, and associate one or more machines with this media. You can also use these commands to associate non-executable media such as application user guides with client machines.
define recoverymedia tellerwrkstnimage volumenames=aix001,aix002,aix003 type=boot product="AIX 4.1" location="Building 21"
This command is usually only needed when a client machine configuration changes. For example, if you install a new level of AIX on the client machine and create a bootable image with mksysb, issue the DEFINE RECOVERYMEDIA command to create a new recovery media definition that can be used to track the new mksysb volumes.
To query your recovery media definitions, issue the QUERY RECOVERYMEDIA command with the FORMAT=DETAILED parameter.
During disaster recovery, this association information can be used to determine what boot media to use in the replacement machines.
The following example associates machine MACH255 with recovery media tellerwrkstnimage:
define recmedmachassociation tellerwrkstnimage mach255
The following example updates the location of boot media tellerwrkstnimage to Ironvault:
update recoverymedia tellerwrkstnimage location=ironvault
In a recovery scenario, you may want to have softcopy manuals that are on a CD-ROM. You can define this to DRM with the DEFINE RECOVERYMEDIA command.
The following example defines the AIX 4.1 manuals, a volume identifier of cd0001, and a type of OTHER because this is a manual:
define recoverymedia aix41manuals description="AIX 4.1 Bookshelf" - volumes=cd0001 type=other
DRM provides default settings for the management of the following:
However, you can use the DRM SET commands to override the default
settings. If you want to take the defaults or return to this subject
later, you can go now to "Customizing the Site-Specific Recovery Instructions". The recovery instructions are flat files containing instructions
that you create to guide you in the recovery process of your own site.
| Task | Required Privilege Class |
|---|---|
| Use SET commands to customize DRM | System |
This section describes the SET commands to configure DRM. For more information, refer to ADSM Administrator's Reference.
At installation, all primary storage pools are eligible for processing by the PREPARE command. Volumes in these storage pools are included in the plan file stanzas. You can use the SET DRMPRIMSTGPOOL command to specify the eligible primary storage pools. For example, to specify that primary storage pools PRIM1 and PRIM2 are eligible for processing, enter:
set drmprimstgpool prim1,prim2
To override this setting, use the PRIMSTGPOOL parameter of the PREPARE command.
By default, all copy storage pools are eligible to be managed by DRM. To limit which copy storage pools are managed by DRM you can use theSET DRMCOPYSTGPOOL command. This command generates a copy storage pools list that is used during PREPARE command processing.
Copy storage pools that you do not want DRM to manage can include onsite copy storage pools used for recovery from media failures. For example, specify that DRM manages copy storage pools with the pattern-matching expression of ONSITECOPY:
set drmcopystgpool onsitecopy*
To override this setting, use the COPYSTGPOOL parameter of the PREPARE command.
If the situation occurs when you need to restore an entire volume, the replacement volume must have a different name. The procedure for restoring a primary storage pool volume requires the original volume to be marked destroyed and a replacement volume created with a unique name. To meet the requirement of a different name, by default, DRM attaches the @ to the end of the replacement volumes names in the disaster recovery plan. For additional information about the restore process, see "How Restore Processing Works".
If you prefer or require a character other than @, you can change the character to be attached to the replacement volume names by issuing the SET DRMPLANVPOSTFIX command. When you are attempting to locate replacement volume names within the disaster recovery plan, the attached character makes the replacement volume names easily identifiable.
The following example defines the character identification as r:
set drmplanvpostfix r
Issue the SET DRMINSTRPREFIX command to specify the prefix portion of the path name for the recovery instructions source files.
The following example specifies the prefix as /u/recovery/plans/rpp:
set drminstrprefix /u/recovery/plans/rpp
The disaster recovery plan file will include the information from the following files:
/u/recovery/plans/rpp.RECOVERY.INSTRUCTIONS.GENERAL /u/recovery/plans/rpp.RECOVERY.INSTRUCTIONS.OFFSITE /u/recovery/plans/rpp.RECOVERY.INSTRUCTIONS.INSTALL /u/recovery/plans/rpp.RECOVERY.INSTRUCTIONS.DATABASE /u/recovery/plans/rpp.RECOVERY.INSTRUCTIONS.STGPOOL
You can override this SET command using the INSTRPREFIX parameter with the PREPARE command. For more information refer to ADSM Administrator's Reference.
Issue the SET DRMPLANPREFIX command to specify the prefix portion of the path name for the generated recovery plan file. This prefix is used by ADSM to identify the location of the recovery plan file. The plan prefix is also used to generate the ADSM macros and script file names included in the RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE and RECOVERY.SCRIPT.NORMAL.MODE.
The following example specifies the prefix as /u/server/recoveryplans/:
set drmplanprefix /u/server/recoveryplans/
The disaster recovery plan file name created by PREPARE processing will be in the following format:
/u/server/recoveryplans/19950603.013030
You can override this SET command using the PLANPREFIX parameter with the PREPARE command, for more information refer to ADSM Administrator's Reference.
This section describes how to configure DRM for offsite recovery media management.
| Note: | ADSM provides defaults for the information specified in the SET commands described in this section. You can take these defaults at this point, continue on to "Querying the Disaster Recovery Manager System Parameters", and return to this customization later if you wish. |
The MOVE DRMEDIA or QUERY DRMEDIA command processes the volumes in the MOUNTABLE state that are associated with the list of copy storage pool names specified by the SET DRMCOPYSTGPOOL command. If the COPYSTGPOOL parameter is specified with the MOVE DRMEDIA or QUERY DRMEDIA command, the copy storage pool names specified with the command will override those specified with the SET DRMCOPYSTGPOOL command.
Issue the SET DRMNOTMOUNTABLENAME command to specify the location name for storing media that are ejected from the library and to be shipped to an offsite location. At installation, the name of this location is set to NOTMOUNTABLE. After installation, you can use this command to modify the name of the location. The location name is used by the MOVE DRMEDIA command to set the location of volumes that are updated to the NOTMOUNTABLE state.
The following example specifies the location name as Local.
set drmnotmountablename Local
At installation, the name of the courier is set to COURIER. After installation, you can change the name of the courier. The MOVE DRMEDIA command uses the courier name to set the location of volumes that are changing from the NOTMOUNTABLE state to the COURIER state.
The following example specifies the courier name as Joe's Courier Service:
set drmcouriername "Joe's Courier Service"
Issue the SET DRMCHECKLABEL command to specify whether ADSM should read sequential media labels of volumes checked out with the MOVE DRMEDIA command. At installation, the value is set to YES. After installation, use this command to modify the value. This command does not apply to 349X library types.
The following example specifies that DRM should not read the volume labels:
set drmchecklabel no
A database series is eligible for expiration if all of the following conditions are true:
To set the expiration value to 30 days, issue the following command:
set drmdbbackupexpiredays 30
Issue the SET DRMFILEPROCESS command to specify whether the MOVE DRMEDIA or QUERY DRMEDIA commands should process backup volumes that are associated with a device class with a device type of FILE. You can use this command to test the DRM environment. At installation, the value is set to No.
set drmfileprocess yes
At installation, the vault name is set to VAULT. Use the SET DRMVAULTNAME command to change the vault name. The MOVE DRMEDIA command uses the vault name to set the location of volumes that are moving from the COURIER state to the VAULT state.
To specify the vault name the IRONVAULT, the contact name of J. SMITH, and the telephone number 1-555-000-0000 enter:
set drmvaultname "Ironvault, J. Smith, 1-555-000-0000"
You can use the MOVE DRMEDIA or QUERY DRMEDIA command to generate executable commands that are contained in a file. You can specify the name of that file with the SET DRMCMDFILENAME command. There is no default file name.
To set the file name as '/drm/orm/exec.cmds', issue the following command:
set drmcmdfilename /drm/orm/exec.cmds
To query the settings defined for DRM, issue the QUERY DRMSTATUS command. For example:
query drmstatus
ADSM displays information similar to the following:
+--------------------------------------------------------------------------------+ | Recovery Plan Prefix: /u/recovery/plans/rpp | | Plan Instructions Prefix: /u/recovery/plans/source/ | | Replacement Volume Postfix: @ | | Primary Storage Pools: PRIM1 PRIM2 | | Copy Storage Pools: COPY* | | Not Mountable Location Name: Local | | Courier Name: Joe's Courier Service | | Vault Site Name: Ironvault, D. Lastname, 1-000-000-0000 | |DB Backup Series Expiration Days: 30 Day(s) | | Check Label?: Yes | | Process FILE Device Type?: No | | Command File Name: /drm/orm/exec.cmds | +--------------------------------------------------------------------------------+
The PREPARE command includes recovery instructions for your site in the disaster recovery plan. Create files having the following names and add your recovery instructions to them:
The PREPARE command includes the information in these files in the disaster recovery plan.
+--------------------------------------------------------------------------------+ | Recovery Instructions for ADSM Server ACMESRV on system ZEUS. | | Joe Smith (wk 002-000-1111 hm 002-003-0000)is the primary system programmer. | | Salley Doe (wk 002-000-1112 hm 002-005-0000) is primary recovery administrator.| | Jane Smith (wk 002-000-1113 hm 002-004-0000) is the responsible manager. | | Security Considerations: | | Joe Smith has the password for the Admin ID ACMEADM. If Joe is unavailable, | | you will need to either issue SET AUTHENTICATION OFF or define a new | | administrative user ID at the replacement ADSM server console. | +--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+ | Our offsite vault location is Ironvault, Safetown, Az. | | The phone number is 1-800-000-0008. You need to contact them directly | | to authorize release of the tapes to the courier. | | Our courier's name is Fred Harvey. You can contact him at 1-800-444-0000. | | Since our vault is so far away, be sure to give the courier a list | | of both the database backup and copy storage pool volumes required. Fred | | is committed to returning these volumes to us in less than 12 hours. | +--------------------------------------------------------------------------------+
The disaster recovery plan file issues commands using the administrative client, for example, dsmadmc. Ensure the proper path to the administrative client is established prior to executing the scripts RECOVERY.SCRIPT.DISASTER.RECOVERY.MODE and RECOVERY.SCRIPT.NORMAL.MODE. For example, set the shell variable PATH or update the scripts with the appropriate path specification to find the ADSM administrative client. The following is example text for this file:
+--------------------------------------------------------------------------------+ | Most likely you will not need to reinstall the ADSM server and | | administrative clients because we use | | mksysb to backup the rootvg volume group, and the ADSM server code and | | configuration files exist in this group. | | However, if you cannot do a mksysb restore of the base server system, | | and instead have to start with a fresh AIX build, you may need | | to add ADSM server code to that AIX system. | | The install volume for the ADSM server is INS001. If that is lost, you | | will need to contact Copy4You Software, at 1-800-000-0000, and obtain | | a new copy. Another possibility is the local IBM Branch office | | at 555-7777. | +--------------------------------------------------------------------------------+
The following is example text for this file:
+--------------------------------------------------------------------------------+ | You will need to find replacement disk space for the server database. We have | | an agreement with Joe Replace that in the event of a disaster, he will | | provide us with disk space. | +--------------------------------------------------------------------------------+
The following is example text for this file:
+--------------------------------------------------------------------------------+ | Do not worry about the archive storage pools during this disaster recovery. | | Focus on migration and backup storage pools. | | The most important storage pool is XYZZZZ. | +--------------------------------------------------------------------------------+