Compaq SANworks Application Notes Maximizing Efficiency Through Data Replication Manager Data Movement Part Number: AA-RPJ3A-TE First Edition (October 2001) Product Version: ACS Version 8.6-1P This document describes the topics of data backup, data distribution, data migration, and data mining. It provides procedures and examples that show how these items may be accomplished in a Data Replication Manager environment.
© 2001 Compaq Computer Corporation. Compaq, the Compaq logo, StorageWorks, SANworks, Tru64, and OpenVMS are trademarks of Compaq Information Technologies Group, L.P. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation. UNIX is a trademark of The Open Groups. All other product names mentioned herein may be trademarks of their respective companies. Confidential computer software. Valid license from Compaq required for possession, use or copying. Consistent with FAR 12.211 and 12.
Application Notes Contents Application Notes Contents These Application Notes cover the following major topics: • “Data Backup” on page 4 • “Data Distribution” on page 9 • “Data Migration” on page 10 • “Data Mining” on page 13 • “Procedures and Examples” on page 13 Intended Audience This document is intended for customers who purchased the Compaq SANworks™ Data Replication Manager HSG80 ACS Version 8.6-1P solution.
About This Document About This Document DRM is a storage-based data replication and workload migration solution that copies data online and in real time to remote locations via an extended Storage Area Network (SAN). With a DRM solution and the peer-to-peer functionality of the HSG80 controller software, data can be moved for several useful purposes. These Application Notes discuss four services that are possible using the built-in functionality of DRM with HSG80 Array Controller Software (ACS) Version 8.
Data Backup Backup Site Site A Site B Site C Note: Data transfer to a backup site would occur sequentially, and not simultaneously as depicted. CXO7696A Figure 1: Backup concentration model Disk-to-Disk Backup A clone is a point-in-time exact copy of a Just a Bunch of Disks (JBOD), mirrorset, stripeset, or striped mirrorset that can be physically moved to an archival facility (see Figure 2 for the steps required when using the CLONE utility). RAIDsets (3/5) cannot be cloned.
Data Backup Unit Unit Temporary mirrorset Disk10300 Disk10300 New member Unit Temporary mirrorset Unit Copy Disk10300 Disk10300 New member Clone Unit Clone of Disk10300 CXO5510A Figure 2: Steps the CLONE utility follows for duplicating unit members Three member striped mirrorset 1 2 3 Unit D0 1 Striped mirrorset - Cloned 2 Clone Today Vault (Yesterday) Unit D0 Striped mirrorset - After rotation 1 2 3 Day before Unit D0 CXO7723A Figure 3: Three-member striped mirrorset cloning operation 6
Data Backup Automatic normalization is a benefit of using the remote copy set function of DRM. If an operations manager wants to make a copy of a unit for archival or backup, a simple backup method would be to replace the target copy with a “new” logical unit number (LUN). This makes the backup copy immediately available, and normalization creates another copy at the target site. Refer to “Data Backup by Disk Rotation” on page 17 for this backup procedure.
Data Backup Before Snapshot created and after Snapshot deleted Write operations to a Source Unit that has a Snapshot Server Server Controller cache bitmap check 0 to 1 Write new data Write old data Source Unit Source unit Snapshot unit Read operations to Snapshot Unit Server Read 0 Controller cache bitmap check 1 Read Read Source unit Snapshot unit 0 = Data on Source Unit at time of Snapshot is unchanged 1 = Data on Source Unit at time of Snapshot transferred to Snapshot Unit CXO7300A Fig
Data Distribution Considerations to keep in mind when using a tape backup solution with DRM are: • Compaq recommends that backups be performed only at the target site. • The solution must allow the host with the backup utility full access to the LUNs through both paths. This ensures the utility will survive a single-path failure. If an operations manager wanted to perform a backup in spite of an initiator or target site failure, then two tape subsystems are required (one for each site).
Data Migration Copies of data can be distributed using remote copy sets from an initiator pointing to a different target subsystem. An initiator subsystem can have only one target subsystem, but the target can be redirected to another location. Then normalization can occur between the remote copy set units to provide a data copy at the new location.
Data Migration Site A (Initiator) Site B (Target) Initiator role Site A (Initiator) Site B (Target) Target role Site A (Target) Site B (Initiator) CXO7689A Figure 7: Role reversal Application Notes - Maximizing Efficiency Through Data Replication Manager Data Movement 11
Data Migration Site A (Initiator) Site B (Target) Site C Site B (Initiator) Site C Site B (Initiator) Site C (Target) Initiator role Site A (Target) Target role Site A CXO7722A Figure 8: Initiator and target site movement Migration to a Larger Storage Capacity It is common for a storage volume to reach a point where more capacity is needed.
Data Mining Data Mining Organizations accumulate large and growing amounts of data in various formats and in different databases. Data Mining is the process of moving or copying this raw data to a location where it can be examined and processed by analytical tools to produce useful and understandable patterns of information. Correlations or patterns can be discovered within numerous fields in large relational databases.
Procedures and Examples In the examples provided later for each topic, some displays show confirmation messages with the event log symbol (%EVL) and an instance code. Information about instance codes and their meanings can be found in the Compaq StorageWorks HSG80 Array Controller ACS Version 8.6 Troubleshooting Reference Guide. The few instance codes that appear in the examples are described in Table 3.
Procedures and Examples Heterogeneous Configuration Procedures Whenever configurations are changed or LUNs are created in the data movement procedures that follow, actions must be taken to enable the hosts to recognize these changes. These actions are platform specific. The following steps are actions for each operating system currently supported in your DRM configuration. 1. Compaq OpenVMS: Allow the hosts to recognize new units. a. If you have shut down the host, boot it.
Procedures and Examples 6. Novell NetWare: Allow the hosts to recognize new units. a. If the hosts are shut down, boot them. Booting the hosts allows Novell NetWare to recognize the drives. b. If the hosts are already up and running or if they do not recognize the drives, issue the following command from the console before mounting the volumes: SCAN FOR NEW DEVICES You can also use the NWCONFIG utility to issue this same command. 7. Sun Solaris: Allow the hosts to recognize new units. a.
Procedures and Examples Data Backup by Disk Rotation Procedure This procedure achieves data backup by removing the physical disk and replacing it with a new disk. BuildngA (Initiator) BuildngB (Target) D1 Storage Site D1 2 1 Store LUN Remove LUN from RCS BuildngA D1 BuildngB D1 D1 4 Add new LUN to RCS 3 Replace and recreate LUN CXO7690A 1 Remove the target LUN to be backed up from the remote copy set. 2 Physically remove the target LUN and store in another location.
Procedures and Examples I 1. Issue this command to show all units configured to the initiator controller: SHOW REMOTE FULL Example Display 1 shows a sample output of this command.
Procedures and Examples T 5. Physically replace the target LUN and re-create this new disk with the following commands (refer to callout 3 on Figure 9).
Procedures and Examples Example Display 5 %EVL--BUILDNGA Top-> --15-JAN-2001 11:12:27 (time not set)-- Instance Code: 0E050064 . . . Instance Code: 0E050064 I 8. Verify that the remote copy set is assigned to the initiator and is normalized. Issue the following command: SHOW REMOTE_COPY_SETS FULL Example Display 6 shows a sample output from the SHOW command.
Procedures and Examples BuildngA (Initiator) BuildngC (Other Site) BuildngB (Target) RCS1 D1 D1 1 2 Suspend Delete D1 and Recreate Log Disk BuildngA D10 RCS10 3 D10 Create new RCS BuildngC BuildngB RCS1 D1 D1 Resume (Merge) Log Disk D10 RCS10 6 5 Delete D10 and Recreate 4 D10 Delete RCS CXO7691A 1 Suspend all remote copy sets between the initiator and the target sites that are used with the LUN you want to copy.
Procedures and Examples Example Several SHOW commands are included at the beginning of this procedure to show the initial conditions at the initiator site. NOTE: There is an association set with a write history log disk on the LUN with data to be moved. I 1. Issue this command to show all units configured to the initiator controller: SHOW UNITS Example Display 7 shows a sample output of this command.
Procedures and Examples Example Display 9 Name Association Uses Used by -----------------------------------------------------------------------------AS1 I association RCS1 RCS3 4. Display the status of individual association sets using the following command: SHOW AssociationSetName Example: show as1 Example Display 10 shows a sample output of this command.
Procedures and Examples SET UnitNumber PREFERRED_PATH=THIS_CONTROLLER Example: set d10 preferred_path=this_controller SET UnitNumber MAXIMUM_CACHED_TRANSFER_SIZE=Number Example: set d10 maximum_cached_transfer_size=128 SHOW UnitNumber Example: show d10 Example Display 12 shows a sample output from the SHOW command.
Procedures and Examples T 8. From the target site, create a remote copy set between the renamed target LUN (D10) and the available LUN at the third site (refer to callout 3 on Figure 10). Use the following command: ADD REMOTE_COPY_SETS RemoteCopySetName InitiatorUnitName RemoteNodeName\TargetUnitName Example: add remote_copy_sets rcs10 d10 BUILDNGC\d10 Refer to Example Display 13 for a sample completion message. The instance code confirms that the action was performed.
Procedures and Examples Example Display 15 %EVL--BUILDNGB Top-> --16-JAN-2001 07:23:10 (time not set)-- Instance Code: 0E020064 . . . Instance Code: 0E020064 T 11. Delete the LUN (D10) that was created at the target site, and re-create and rename it as the original LUN (D1). Refer to callout 5 on Figure 10).
Procedures and Examples I 12. From the initiator site, resume the original remote copy set and allow it to merge any new data that may have been written since starting the data movement (refer to callout 6 on Figure 10). Use the following command: SET RemoteCopySetName RESUME=ControllerName\DeviceName Example: set rcs1 resume=BUILDNGB\d1 Refer to Example Display 17 for a sample completion message. The instance code confirms that the data merging has commenced.
Procedures and Examples I 14. Check that the newly merged remote copy set matches the initial parameters that existed in the original remote copy set (step 2). Use the following command to make the comparison: SHOW REMOTE_COPY_SETS FULL Refer to Example Display 19 for a sample display output from the SHOW command.
Procedures and Examples Non-Disaster Tolerant Data Movement to an Alternate Site Procedure If the data being moved is in a non-disaster tolerant environment, then it can be moved with fewer steps than when it has to be protected from loss. This method can be used to move data to another site in a non-disaster tolerant environment. Refer to Figure 11. This procedure is used for Data Distribution, Data Migration, and Data Mining.
Procedures and Examples I 2. Show the initial conditions of the LUN with data to be moved. Use the command: SHOW UnitNumber Example: show d1 Example Display 21 shows a sample output of this command.
Procedures and Examples SET UnitNumber ENABLE_ACCESS_PATH=HostIDs Example: set d1 enable_access_path=BUILDNGAa,BUILDNGAb,BUILDNGAc,BUILDNGAd SET UnitNumber PREFERRED_PATH=THIS_CONTROLLER Example: set d1 preferred_path=this_controller SET UnitNumber MAXIMUM_CACHED_TRANSFER_SIZE=Number Example: set d1 maximum_cached_transfer_size=128 SHOW UnitNumber Example: show d1 Example Display 23 shows the characteristics of the created LUN.
Procedures and Examples Target Node Name: "BUILDNGB" Target Unit Number: 1.(00000001) Number of Targets: 1.(00000001) Remote Copy Set Name: "RCS1" Association Set Name: "" Log Unit Number: Not Available Instance Code: 0E010064 I 8. Verify the LUN has finished normalizing by issuing the following command: SHOW RemoteCopySetName Example: show rcs1 Example Display 25 shows a sample display.
Procedures and Examples BuildngA (Initiator) BuildngB (Target) Host A JBOD D1 Host B 1 Remove target LUN I/O I/O D1 9 GB 27 GB 9 GB HSG80 Switch Switch HSG80 27 GB Larger JBOD D1 Host A JBOD D1 4 Host B 3 Add new target LUN to RCS I/O I/O HSG80 Switch Switch HSG80 5 Failover to target 7 Create larger LUN Host A I/O I/O 27 GB HSG80 10 Allow host access Switch Host A Switch Larger JBOD D1 Host B 8 Create RCS and normalize I/O HSG80 I/O 27 GB 27 GB Larger JBOD D1 Larger
Procedures and Examples Example The following example demonstrates how to migrate from one data set type to another. The example uses two controller pairs. The initiator site uses controller pair BUILDNGA and the target site uses controller pair BUILDNGB. NOTE: For simplification, there are no association sets established for the remote copy sets in this example. I 1. We begin by showing the initial conditions of the LUNs by issuing two SHOW commands.
Procedures and Examples Example Display 28 Name Uses Used by -----------------------------------------------------------------------------RCS1 RCS3 I remote copy D1 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0095 Switches: OPERATION_MODE = SYNCHRONOUS ERROR_MODE = NORMAL FAILOVER_MODE = MANUAL OUTSTANDING_IOS = 200 Initiator (BUILDNGA\D1) state: ONLINE to this controller Not reserved Target state: BUILDNGB\D1 is NORMAL remote copy D3 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0093 Swit
Procedures and Examples SET UnitNumber ENABLE_ACCESS_PATH=HostIDs Example: set d1 enable_access_path=BUILDNGAa,BUILDNGAb,BUILDNGAc,BUILDNGAd SET UnitNumber PREFERRED_PATH=THIS_CONTROLLER Example: set d1 preferred_path=this_controller SET UnitNumber MAXIMUM_CACHED_TRANSFER_SIZE=Number Example: set d1 maximum_cached_transfer_size=128 I 5. From the initiator controller, add the new target LUN to the remote copy set (refer to callout 3 on Figure 12).
Procedures and Examples T 8. From the target site, break the intersite link so that a failover can be performed. Issue the following commands: SET THIS_CONTROLLER PORT_Number_TOPOLOGY=OFFLINE Example: set this_controller port_2_topology=offline SET OTHER_CONTROLLER PORT_Number_OFFLINE Example: set other_controller port_2_topology=offline Several completion messages display that confirm the link has been broken. T 9. Begin failover of your remote copy sets (refer to callout 5 on Figure 12).
Procedures and Examples Example Display 34 Name Uses Used by ------------------------------------------------------------------------------ I RCS1 remote copy D1 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0095 Switches: OPERATION_MODE = SYNCHRONOUS ERROR_MODE = NORMAL FAILOVER_MODE = MANUAL OUTSTANDING_IOS = 200 Initiator (BUILDNGB\D1) state: ONLINE to this controller Not reserved Target state: BUILDNGA\D1 is NORMAL RCS3 remote copy D3 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0093
Procedures and Examples SET UnitNumber PREFERRED_PATH=THIS_CONTROLLER Example: set d1 preferred_path=this_controller SET UnitNumber MAXIMUM_CACHED_TRANSFER_SIZE=Number Example: set d1 maximum_cached_transfer_size=128 T 14.
Procedures and Examples T 17. Return all remaining unchanged remote copy sets back to the original initiator. Use the following command for each remote copy set: SET RemoteCopySetName INITIATOR=InitiatorNodeName\InitiatorUnitName Example: set rcs3 initiator=BUILDNGA\d3 I 18. From the initiator site, failback the controller to the original initiator site (refer to callout 9 on Figure 12).
Procedures and Examples RCS3 I remote copy D3 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0093 Switches: OPERATION_MODE = SYNCHRONOUS ERROR_MODE = NORMAL FAILOVER_MODE = MANUAL OUTSTANDING_IOS = 200 Initiator (BUILDNGA\D3) state: ONLINE to this controller Not reserved Target state: BUILDNGB\D3 is NORMAL 20. Reconnect the intersite link. A normalization does not occur and all remote copy sets are back in use with disaster-tolerant LUNs (refer to callout - on Figure 12).
Procedures and Examples RCS3 I remote copy D3 Reported LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-0093 Switches: OPERATION_MODE = SYNCHRONOUS ERROR_MODE = NORMAL FAILOVER_MODE = MANUAL OUTSTANDING_IOS = 200 Initiator (BUILDNGA\D3) state: ONLINE to this controller Not reserved Target state: BUILDNGB\D3 is NORMAL 22. Check the size of the replaced LUN by using the following command: SHOW UNITS FULL Refer to Example Display 42 for a sample output.
Procedures and Examples T 24. Check the status of remote copy sets with the following command: SHOW REMOTE_COPY_SETS Example Display 43 shows a remaining remote copy set. Example Display 43 Name Uses Used by -----------------------------------------------------------------------------RCS1 T remote copy D1 25. Remove the remote copy set from the target site.
Procedures and Examples BuildngA (Initiator) BuildngB (Target) Host A Host B 3 Add RCS and normalize I/O I/O D1 D10 HSG80 Switch Switch Create LUN with 2 access to initiator controller 1 Enable access to target controller Host A 5 I/O HSG80 Host B 4 Delete RCS I/O I/O D1 D10 HSG80 D10 D1 D10 Switch Switch HSG80 6 Create new LUN 9 Delete LUNs I/O 7 Create RCS and normalize Host A I/O Host B I/O D10 D1 11 10 Create another LUN HSG80 Switch Caution: Do not INIT device 8 Del
Procedures and Examples Example In this example, assume that both subsystems are running ACS 8.xP and that the connections have been named. The first two commands are issued to show the initial conditions. I 1. Issue this command to show all units configured to the initiator controller: SHOW UNITS Example Display 44 shows a sample output of this command. Example Display 44 LUN Uses Used by -----------------------------------------------------------------------------D1 I DISK10000 2.
Procedures and Examples I 4. Set LUN D1 to a preferred path with the following command: SET UnitNumber PREFERRED_PATH=THIS_CONTROLLER Example: set d1 preferred_path=this_controller T 5. View the initial conditions at the target site. Use the command: SHOW UNITS A message appears with information for all units configured to the controller. T 6. Prepare a LUN on the target subsystem (refer to callout 2 on Figure 13).
Procedures and Examples I 7. From the initiator site, create a remote copy set to copy data to the new LUN on the target subsystem (refer to callout 3 on Figure 13). Use the following command: ADD REMOTE_COPY_SETS RemoteCopySetName InitiatorUnitName RemoteNodeName\TargetUnitName Example: add remote_copy_sets rcs1 d1 BUILDNGB\d10 Example Display 48 shows a sample completion message. The instance code confirms the action was completed.
Procedures and Examples I 9. Delete the remote copy set. Refer to callout 4 on Figure 13. Use the command: DELETE RemoteCopySetName Example: delete rcs1 Example Display 50 shows a sample completion message. The instance code confirms the action was completed. Example Display 50 %EVL--BUILDNGA Top-> --23-JAN-2001 08:58:58 (time not set)-- Instance Code: 0E020064 . . . Instance Code: 0E020064 I 10.
Procedures and Examples Example Display 51 %EVL--BUILDNGB Top-> --17-JAN-2001 01:47:16 (time not set)-- Instance Code: 0E010064 . . . Instance Code: 0E010064 T 13. Verify that the LUN has finished normalizing by using the following command: SHOW RemoteCopySetName Example: show rcs1 Example Display 52 shows a sample display. Note that normalization is complete when the target state is NORMAL.
Procedures and Examples Example Display 54 LUN Uses Used by -----------------------------------------------------------------------------D10 I DISK60300 LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-009E NOIDENTIFIER Switches: RUN NOWRITE_PROTECT READ_CACHE READAHEAD_CACHE WRITEBACK_CACHE MAX_READ_CACHED_TRANSFER_SIZE = 128 MAX_WRITE_CACHED_TRANSFER_SIZE = 128 Access: BUILDNGBA, BUILDNGBB, BUILDNGBC, BUILDNGBD State: ONLINE to the other controller PREFERRED_PATH = THIS_CONTROLLER Size: 35556389 blocks Geome
Procedures and Examples Initiator and Target Site Movement Procedure This procedure demonstrates how to move an initiator and a target site to different site locations. Refer to Figure 14. This procedure is used for Data Migration.
Procedures and Examples Example Display 55 LUN Uses Used by -----------------------------------------------------------------------------D1 I DISK10000 BUILDNGA\RCS1 LUN ID: 6000-1FE1-0000-1530-0009-9231-4229-009A NOIDENTIFIER Switches: RUN NOWRITE_PROTECT READ_CACHE READAHEAD_CACHE WRITEBACK_CACHE MAX_READ_CACHED_TRANSFER_SIZE = 32 MAX_WRITE_CACHED_TRANSFER_SIZE = 32 Access: HOST6A, HOST6B, BUILDNGBA, BUILDNGBB, BUILDNGBC, BUILDNGBD State: ONLINE to this controller Not reserved PREFERRED_PATH = THIS_CON
Procedures and Examples Host PORT_1: Reported PORT_ID = 5000-1FE1-0000-1533 PORT_1_TOPOLOGY = FABRIC (fabric up) Address = 210013 Host PORT_2: Reported PORT_ID = 5000-1FE1-0000-1534 PORT_2_TOPOLOGY = FABRIC (fabric up) Address = 210113 REMOTE_COPY = BUILDNGA Cache: 256 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache CACHE_FLUSH_TIMER = 1 (seconds) Mirrored Cache: 256 megabyte write cache, version 0012 Cache is GOOD No unflushed data in cache Battery: NOUPS FULLY CHARGED Expires:
Procedures and Examples TT 7. Verify that the new target has access to the new initiator controller with the following command: SHOW CONNECTIONS Example Display 59 shows a sample output of this command. Example Display 59 Connection Name . . .
Procedures and Examples Example Display 60 Connection Name . . .
Procedures and Examples Example Display 62 RCS1 remote copy D1 Reported LUN ID: 6000-1FE1-0008-D4E0-0001-8290-1711-06A2 Switches: OPERATION_MODE = SYNCHRONOUS ERROR_MODE = NORMAL FAILOVER_MODE = MANUAL OUTSTANDING_IOS = 200 Initiator (BUILDNGB\D1) state: ONLINE to this controller Not reserved Target state: BUILDNGC\D1 is NORMAL %EVL--BUILDNGB Top-> --23-JAN-2001 10:31:01 (time not set)-- Instance Code: 0E030064 . . . Instance Code: 0E030064 T 14.
