Data Replication manager with Compaq Tru64 UNIX Logical Storage Manager
Table Of Contents
- Application Notes – Data Replication Manager with HP Tru64 UNIX Logical Storage Manager
- Application Notes Contents
- HP StorageWorks Technical Support
- Introduction
- DRM Configuration Variations
- Administering LSM
- Augmented Failover, Failback, and Role Reversal Procedures
- All Procedures Description
- Augmented Procedures with Scripts
- Chapter 6: Unplanned Site Failover with Full Failback Procedure
- Chapter 7: Resumption of Operations After Unplanned Loss of Target Site Procedure (Failsafe Mode)
- Chapter 8: Resumption of Operations After Unplanned Loss of Target Site Procedure (Normal Mode)
- Chapter 9: Short Planned Site Failover with Fast Failback Procedure
- Chapter 10: Extended Planned Site Failover With Full Failback Procedure
- Chapter 11: Resumption of Replication After Extended Planned Loss of Target Procedure (Failsafe M...
- Chapter 12: Unplanned Site Failover With Failback To New Hardware Procedure
- Chapter 13: Planned Site Role Reversal Procedure
- Augmented Procedures with Command Line Interpreter
- Chapter 2: Unplanned Site Failover with Full Failback Procedure
- Chapter 3: Resumption of Operations After Unplanned Loss of Target Site Procedure (Failsafe Mode)
- Chapter 4: Resumption of Operations After Unplanned Loss of Target Site Procedure (Normal Mode)
- Chapter 5: Short Planned Site Failover with Fast Failback Procedure
- Chapter 6: Resumption of Replication After Short Planned Loss of Target Procedure
- Chapter 7: Extended Planned Site Failover With Full Failback Procedure
- Chapter 8: Resumption of Replication After Extended Planned Loss of Target Procedure (Failsafe Mode)
- Chapter 9: Unplanned Site Failover With Failback To New Hardware Procedure
- Chapter 10: Planned Site Role Reversal Procedure
- Chapter 11: Disaster Recovery After Role Reversal Procedure

DRM Configuration Variations
Application Notes – Data Replication Manager with HP Tru64 UNIX Logical Storage Manager 7
• Prepares the system to start LSM upon system reboot
• Starts the vold and voliod daemons
NOTE: You do not have to use the rootdg disk group for volume creation, but you must have a rootdg
disk group before you can create any other disk groups.
IMPORTANT: The disk used for the rootdg cannot be part of a remote copy set.
Follow these steps to initialize LSM and the rootdg disk group for each site (you must be superuser):
Using the volsetup Utility
If you are in single user mode, set up the host name with the hostname command, then execute the
volsetup script, as shown in the following example.
NOTE: Do not specify the boot disk as one of the disks you stipulate to be used to initialize the rootdg.
If you want, you can encapsulate the root and swap partitions and add them to the rootdg disk group
later.
Example: Using the volsetup Script for LSM Initialization
The following is an example of the screen display you can expect to see when using the volsetup script
for LSM initialization. Example user inputs are indented.
# /usr/sbin/volsetup
Approximate maximum number of physical disks that will be managed by LSM?
[10]
<Return>
Enter the disk(s) to add into the rootdg disk group.
NOTE: Enter a blank line to end the list of disks.
? dsk2b dsk3b dsk9b dsk10b
? <Return>
<Return>
Specified partition /dev/rdisk/dsk9b is marked in use.
Also partition(s) which overlap /dev/rdisk/dsk9b are marked in use.
If you continue with the operation you can possibly destroy existing data.
Would you like to continue using dsk9b?? [y,n,q,?] (default: n)
< y >
Initialize vold and the root disk group:
Add disk dsk2b to the root disk group as dsk2b:
Addition of disk dsk2b as dsk2b succeeded.
Add disk dsk3b to the root disk group as dsk3b:
Addition of disk dsk3b as dsk3b succeeded.
Add disk dsk9b to the root disk group as dsk9b:
Specified partition /dev/rdisk/dsk9b is marked in use.
Also partition(s) which overlap /dev/rdisk/dsk9b are marked in use.
If you continue with the operation you can possibly destroy existing data.