data migration strategy (srdf via “swing frame”)education.dellemc.com/content/dam/dell-emc/...we...
TRANSCRIPT
Data Migration Strategy (SRDF via “swing frame”)
Ken Guest
EMC Proven Profesional Knowledge Sharing 2009
Ken GuestSr. Systems ManagerA Large Telecommunications [email protected]
Sejal Joshi
Sejal JoshiSr. Technical Team LeadA Large Telecommunications [email protected]
2
Table of Contents
INTRODUCTION ...........................................................................................................................................................3 PURPOSE OF ARTICLE .................................................................................................................................................................. 3
A LARGE TELECOMMUNICATIONS CASE STUDY..................................................................................................4 OBJECTIVES................................................................................................................................................................................. 4 REQUIREMENTS ........................................................................................................................................................................... 4 PROCESS...................................................................................................................................................................................... 5
Initial Replication Steps.......................................................................................................................................................... 6 Final Replication Steps........................................................................................................................................................... 7 High-level Steps ...................................................................................................................................................................... 8 Detailed Configuration Steps Using Command Line ............................................................................................................. 9
Initial Configuration Steps for DMX-2 frames and devices ....................................................................................................................9 Initial Configuration Steps for DMX-3 Frames and Devices ................................................................................................................10 Cut-over Steps (Required Down Time) .................................................................................................................................................13
OVERALL RDF PROCESS FLOW FOR SOURCE, SWING AND TARGET FRAMES............................................................................. 15 CONCLUSION.............................................................................................................................................................16
APPENDIX A – DATA COLLECTION TIP .................................................................................................................17
APPENDIX B – RDF COMMAND LINE TIP ...............................................................................................................17
APPENDIX C - RELATED DOCUMENTATION .........................................................................................................23
GLOSSARY.................................................................................................................................................................23
BIOGRAPHY: SEJAL JOSHI ....................................................................................................................................25
BIOGRAPHY: KEN GUEST.......................................................................................................................................25
Disclaimer: The views, processes or methodologies published in this compilation are those of the authors. They do not necessarily reflect EMC Corporation’s views, processes, or methodologies
3
Introduction Data Center power and cooling challenges are increasing and impacting the ability of IT
infrastructures to scale and meet business demands. Storage consolidation provides relief for
power/cooling and also reduces the Total Cost of Ownership (TCO). Businesses use storage
consolidation to simplify storage infrastructures and ease the tasks involved in their management.
Massive data growth over the past several years has forced businesses to scale their storage
infrastructures to accommodate capacity, performance, and high-availability requirements.
A large telecommunications company consolidated ~40 TB’s of data spread across 12 storage
frames to a single frame. Initially, we used the host-based method to move this data, but it did not
work as we expected. The Oracle databases pushed high volumes of data and the hosts
consistently ran at a high utilization rate causing performance issues. We were given ten (10)
days to consolidate ~40 TB’s of data to the target array. In this limited time frame, our only option
was to use storage based replication. Throughout the planning and execution phases, our biggest
challenge was having Oracle databases spanning across DMX-2 arrays on (5670) code and
DMX-3 arrays on (5771) code without having enough time to upgrade DMX-2’s to 5671. This led
to our decision to use the swing frame replication methodology.
Purpose of Article The purpose of this article is twofold. First, we will present a case study about how our company
migrated and consolidated multiple Oracle databases spanning across 12 storage arrays to a
single Symmetrix® DMX-4 array, using EMC’s Symmetrix Remote Data Facility (SRDF®) solution.
Second, we will include general guidelines and configuration steps for using storage-based
replication to migrate/consolidate data from multiple storage arrays to just a few arrays.
Note: A total of eight (8) EMC Source DMX-3 arrays, four (4) EMC Source DMX-2 arrays, one (1)
EMC DMX-2 swing array, and one (1) EMC DMX-4 target array were involved in the overall
replication process.
4
A Large Telecommunications Case Study
Objectives Consolidating Tier-1 storage frames using the SRDF storage-based replication method to migrate
12 source frames to one DMX-4 frame was the initial objective in our storage migration plan. Four
DMX-2 source arrays were running (5670) code, eight DMX-3 Source arrays were running (5771),
and the target DMX-4 array was running the (5772) code.
SRDF is not supported for direct replication from (5670) to (5772) codes; therefore, our objective
became to migrate data using SRDF from the (5670) to (5772) code using a swing frame method
(DMX-2) running the (5671) code. We knew the DMX-3 arrays running (5771) could replicate data
directly to DMX-4 array running (5772) code, but DMX-2 arrays running (5670) could not.
Requirements We determined that our data migration strategy needed to meet the following requirements:
• Consolidate data from (12) storage frames to (1) with minimum down time and without
impacting performance on host.
• Maintain database consistency on the target frame.
• Use the SRDF solution to migrate the data to a new frame.
• Use a DMX-2 frame running 5671 code to migrate data from all source DMX-2 frames
running 5670 code.
• Exclude Oracle Re-do logs devices from the replication
5
Process To accomplish our revised objective, we had to replicate data from Source DMX-2 arrays to the
swing array (DMX-2) running (5671) code, and then issue a “restore” from the swing array to the
target DMX-4 array for the final replication step. All Source DMX-3 arrays replicate data directly to
the target DMX-4 array. We knew that maintaining data consistency was very important since this
consolidation also involved multiple Oracle databases.
After the restore process was successfully initiated from the swing frame to the target frame, we
allow each host to import the volume and start mounting the file system and database.
The following graphic depicts a high-level replication process:
6
Initial Replication Steps
• 2 RF ports were used on each of the 4 Source DMX-2 frames and started SRDF replication
process, in Adaptive Copy Write pending mode, to Swing DMX-2 frame. A total of 8 RA ports were
configured on the Swing DMX-2 frame.
• 2 RF ports were used on each of the 8 Source DMX-3 frames and started SRDF replication
process, in Adaptive Copy Write Pending mode, to target DMX-4 frame. A total 16 RA ports were
configured on the target DMX-4 frame.
• Wait until each source and target device is “Synchronized” for all 12 Source frames.
• Initial step completed in approximately 3-4 days. Our goal was to copy all data on target DMX-4.
7
Final Replication Steps
We performed the final step during a maintenance window to swing everything to single DMX-4
frames.
We shut down databases residing on source frames.
6 RF ports were used on Swing DMX-2 frame and started SRDF restore process (R2 to R1) to
target DMX-4 frame. We removed RF and device pairing from the Original source to target
frames.
As soon as the restore process initiated successfully, hosts were allowed to start volume and
mount file system; the database was started on the new frame.
The Restore process continued to run in the background; this process took approximately 30
hours to complete.
8
High-level Steps The high-level process steps follow:
1. Bin File request to enable SRDF (Convert FA to RF) on 12 source frames and 1 target frame, ensuring that dynamic SRDF is enabled.
2. Create mapping between R1 and R2. (Devices from 12 source frames are going to be R1 and 1 target/swing frame is going to become R2).
3. Perform appropriate zoning changes within SAN for each source and target RF ports.
4. Create necessary RDF groups on appropriate frames.
5. Prepare the dynamic SRDF environment for the source and target frames. Enable dynamic RDF flag on each R1 and R2 device.
6. Create a pairing relationship between the source and target frames.
7. Change SRDF mode to Adaptive Copy Write pending mode.
8. Start the initial sync for all 12 Source frames.
9. Source DMX-2 frames copy data initially to the swing frame running 5671 code.
10. Source DMX-3 frames copy data directly to the target DMX-4 frame running 5672 code.
11. Use the SRDF Adaptive Copy Write Pending mode, and change to the Adaptive copy disk mode if you experience any performance issue on the host.
12. Wait until all source devices 100% synchronized.
13. Shut down the applications and databases on the production servers.
14. Unmount all the file systems associated with the SRDF copy.
15. Change the RDF mode to Sync, and initiate a checkpoint.
16. Verify that the SRDF devices are in "synchronized" mode, and perform the split operation.
17. Suspend all the SRDF links from the sources to the target frame.
18. Delete the dynamic SRDF device pairing between the source and target frames, and remove the RDF groups
19. Associate the relationship between the DMX2 (swing) and target DMX4 frame. (Create an RDF group, and include R1 & R2 associations.)
20. Perform a full restore from the swing DMX-2 frame to the target DMX-4 frame.
21. Mask the new devices from the target DMX-4 frames to the production servers.
9
22. After the restore is initiated successfully, allow host to import a volume group using the new devices from the target DMX-4 frames.
23. Start the database and application while the restore operation runs in the background.
24. After the restore is completed successfully, split the devices.
Detailed Configuration Steps Using Command Line The following sections detail the configuration steps we took.
Initial Configuration Steps for DMX-2 frames and devices We dedicated RF ports on the target frame for each source frame (4 Source frames each
configured with 2 RF port and total 8 RF ports on Swing frame):
The following is example of one Source and target DMX-2 frame configuration -
Source Frame: 0113
Target Frame: 0232
RA ports on Source and Target frame: 8D, 9D
Source (R1) devices: 0D60,0D68,0D70
Target (R2) devices: 0043,004B,0053
The following configuration steps are an example of one DMX-2 frame being replicated to a
Swing DMX-2 frame. Follow the same steps for all source frames and devices that need to
be migrated. Assuming dynamic SRDF is enabled on the source and target frames:
1. Add zones in fabric so Source and Target RF directors can communicate with each other.
2. Create an RDF group:
symrdf addgrp -label grp11 -rdfg 11 -sid 0113 -dir 8D,9D -remote_rdfg 11 -remote_sid 0382 -
remote_dir 8D,9D –nop
3. Create a file that has source and target device mapping:
0113_0382_R1_R2.pair
0D60 0043
0D68 004B
0D70 0053
4. Set the Dynamic RDF flag on the host devices:
10
0113_set_dyn_rdf.cmd
set dev 0D60 attribute=dyn_rdf;
set dev 0D68 attribute=dyn_rdf;
set dev 0D70 attribute=dyn_rdf;
symconfigure –sid 0113 –f 0113_set_dyn_rdf.cmd commit –nop
5. Set the Dynamic RDF flag on the target devices:
0382_set_dyn_rdf.cmd
set dev 0043 attribute=dyn_rdf;
set dev 004B attribute=dyn_rdf;
set dev 0053 attribute=dyn_rdf
symconfigure –sid 0382 –f 0382_set_dyn_rdf.cmd commit –nop
6. Make the R2 (target devices) write-disabled:
symdev -sid 0382 write_disable 0043 -nop
symdev -sid 0382 write_disable 004B -nop
symdev -sid 0382 write_disable 0053 –nop
7. Create a pairing relationship, and create RDF device group 0113_0382_R1_R2:
symrdf createpair -file 0113_0382_R1_R2.pair -sid 0113 -rdfg 11 -invalidate r2 -type rdf1 -g
0113_0382_R1_R2 –nop
8. Query the RFD disk group:
symrdf –g 0113_0382_R1_R2 query
9. Set the Mode to Adaptive copy write pending mode:
symrdf –g 0113_0382_R1_R2 set mode acp_wp
10. Start the Initial Establish:
symrdf –g 0113_0382_R1_R2 est
Wait until all devices in each RDF device group are 100% synchronized. This copy is running in the
background without impacting the production database or application. Data is being copied from
Source DMX-2 frames to swing DMX-2 frames.
________________________________________________________________________________
Initial Configuration Steps for DMX-3 Frames and Devices
We dedicated RF ports on the target frame for each source frame (8 Source frames each
configured with 2 RF port and total 16 RF ports on Target frame):
11
An example of one Source DMX-3 and target DMX-4 frame configuration follows.
Source Frame: 0531
Target Frame: 3975
RA ports on Source frame: 7D, 10D
RA ports on Target frame: 8D, 9D
Source (R1) devices: 16F3,16FB,1703
Target (R2) devices: 13A1,13A9,13B1
The following configuration steps are an example of one DMX-3 frame being replicated to a
target DMX-4 frame. Follow the same steps for all source frames and devices that need to
be migrated. Assuming dynamic SRDF is enabled on the source and target frames:
1. Add zones in fabric so RF directors can communicate with each other.
2. Create an RDF group:
symrdf addgrp -label grp12 -rdfg 12 -sid 0531 -dir 7D,10D -remote_rdfg 12 -remote_sid 3975 -
remote_dir 8D,9D
3. Create a file that has source and target device mapping:
0531_3975_R1_R2.pair
16F3 13A1
16FB 13A9
1703 13B1
4. Set the Dynamic RDF flag on the host devices:
0531_set_dyn_rdf.cmd
set dev 16F3 attribute=dyn_rdf;
set dev 16FB attribute=dyn_rdf;
set dev 1703 attribute=dyn_rdf;
symconfigure –sid 0531 –f 0531_set_dyn_rdf.cmd commit –nop
5. Set the Dynamic RDF flag on the target devices:
3975_set_dyn_rdf.cmd
set dev 13A1 attribute=dyn_rdf;
12
set dev 13A9 attribute=dyn_rdf;
set dev 13B1 attribute=dyn_rdf;
symconfigure –sid 3975 –f 3975_set_dyn_rdf.cmd commit –nop
6. Make the R2 (target devices) write-disabled:
symdev -sid 3975 write_disable 13A1 -nop
symdev -sid 3975 write_disable 13A9 -nop
symdev -sid 3975 write_disable 13B1 –nop
7. Create a pairing relationship, and create RDF device group 0531_3975_R1_R2:
symrdf createpair -file 0531_3975_R1_R2.pair -sid 0531 -rdfg 12 -invalidate r2 -type rdf1 -g
0531_3975_R1_R2 -nop
8. Query the RFD disk group:
symrdf –g 0531_3975_R1_R2 query
9. Set the Mode to Adaptive copy write pending mode:
symrdf –g 0531_3975_R1_R2 set mode acp_wp
10. Start the Initial Establish:
symrdf –g 0531_3975_R1_R2 est
Wait until all devices in each RDF device group are 100% synchronized. This copy is running in
the background without impacting the production database or application. Data is being copied
from the source DMX-3 frames to the target DMX-4 frames.
________________________________________________________________________________
13
Cut-over Steps (Required Down Time) The data from all four source DMX-2 frames has been copied to the swing DMX-2 frame. The
data from all eight source DMX-3 frames has been copied to the target DMX-4 frame.
Now, schedule down time to move the data from the swing frame to the target DMX-4 frame. We
performed the following steps: 1. Shut down the Oracle listeners, and switch the logs to clear the online redo logs.
2. Mark the System Change Number (SCN) of each database, and shut down the databases.
3. Unmount all the file systems from the production servers associated with the SRDF copy.
4. Change the RDF mode to Sync for each RDF device group. This will ensure that the source and
target devices are in sync and that each write makes it to the target side:
symrdf -g 0113_0382_R1_R2 set mode sync –nop
symrdf -g 0531_3975_R1_R2 set mode sync -nop
5. Initiate the checkpoint:
symrdf –g 0113_0382_R1_R2 checkpoint
symrdf –g 0531_3975_R1_R2 checkpoint
6. Verify that the SRDF devices are in synchronized mode:
symrdf –g 0113_0382_R1_R2 query
symrdf -g 0531_3975_R1_R2 query
7. Split each RDF device group, and make sure the invalid track count is not increasing:
symrdf -g 0113_0382_R1_R2 split -nop
symrdf -g 0531_3975_R1_R2 split –nop
8. Suspend the SRDF links from the sources to the target frame:
symrdf -f 0531_3975_R1_R2.pair suspend -sid 0531 -rdfg 12 –nop
symrdf -f 0113_0382_R1_R2.pair suspend -sid 0113 -rdfg 11 -nop
9. Delete the dynamic SRDF device pairing between the source and target frames:
symrdf deletepair -g 0113_0382_R1_R2 -nop
symrdf deletepair -g 0531_3975_R1_R2 –nop
10. Remove the RDF group:
symrdf -v removegrp –sid 0531 -label grp12 –nop
symrdf -v removegrp –sid 0113 -label grp11 –nop
14
11. Associate the relationship between the DMX2 (swing frame) and target DMX4 frame. (Create an
RDF group, and include the new R1 and R2 association.)
12. Add an RDF group between the swing DMX-2 frame and the target DMX-4 frame. This RDF
group will be used for the restore process, so use more RF ports to avoid performance issue on the
production servers:
symrdf addgrp -label grprestore -rdfg 30 -sid 3975 -dir 7D,8D,9D,10D -remote_rdfg 12 -
remote_sid 0382 -remote_dir 7D,8D,9D,10D
13. Create a pairing relationship between the source and the target. (The swing frame is R2 and
devices on DMX-4 frame is R1.):
3975_0382_R1_R2.pair
16F3 13A1
16FB 13A9
1703 13B1
symrdf createpair -file 3975_0382_R1_R2.pair -sid 3975 -rdfg 30 -type rdf1 –invalidate r1 -g
0382_2_3975_Restore -nop
14. Perform a full restore from the swing frame to the target DMX-4 frame.
15. Restore process, invalidate R1, and start a copy from the target (R2) to the source (R1):
symrdf -g 0382_2_3975_Restore restore -full
16. LUN Mask new devices from the target DMX-4 frames to the production servers.
17. After the restore has initiated successfully, allow host to import the volume group using new
devices from the target DMX-4 frames.
18. Copy all the archive logs, and recover each database to its previously determined SCN.
19. Start the application while the restore operation is running in the background.
20. After the restore operation is completed, split the devices:
symrdf -g 0382_2_3975_Restore split -nop
________________________________________________________________________________
15
Overall RDF Process Flow for Source, Swing and Target frames
16
Conclusion We were able to accomplish our data migration in a very short amount of time, compared with the
time it would have taken us (several weeks) had we used host-based migration.
Also, host-based migration consumes CPU cycles from the host—a very time consuming process.
There are advantages and disadvantages to using storage-based and host-based migration
methods:
In storage-based replication, we were able to consolidate data quickly; however, we were not able
to change the file system layout. Host-based migration allows for file system layout changes,
which improves performance.
We saved approximately $156K on recurring Storage frame maintenance costs by consolidating
databases on a single frame.
Our over-all application performance improved due to innovations in the newer storage frame
technology.
Migrating data to a single frame helps troubleshoot critical performance issues quickly; before we
had to check twelve different storage frames.
This article provided guidelines for migrating data by using the storage-based replication method
(SRDF) from multiple DMX-2 and DMX-3 arrays to a single DMX-4. If a business does not have
the time, resources, or capital to upgrade the code on legacy storage frames (due to out of family
code concerns) we learned that storage-based migration is the most efficient and economical
migration option.
17
Appendix A – Data Collection tip Data collection is one of the important factors in implementing an RDF solution successfully.
Collect data for each source/target frame and device, as detailed in the following table. This data
collection makes the RDF operation very easy to implement.
R1 R2
Frame Model Mcode Version SymDev Meta Hyper
Cylinder Total
Cylinder Tracks VXVM_DG Host Frame Sym Dev
1214 DMX3-24 5771 179B 8xWay 24074 192592 2888880 nbmcmdbdg dhpnbm2a 3975 1013
1214 DMX3-24 5771 17A3 8xWay 24074 192592 2888880 nbmcmdbdg dhpnbm2a 3975 101B
0572 3000-M2 5670 0613 8xWay 24074 192592 2888880 nbmcmdbdg dhpnbm2a 3975 2013
0572 3000-M2 5670 061B 8xWay 24074 192592 2888880 nbmcmdbdg dhpnbm2a 3975 201B
Appendix B – RDF Command Line tip If R1 devices is BCV, add “-bcv” argument to every symrdf command.
• To set mode for adaptive copy disk mode
symrdf -g <grp> set mode acp_disk
• To set mode for adaptive copy write pending mode
symrdf -g <grp> set mode acp_wp
• To start establish while devices are in Split status. Establish will make target devices “not ready”.
If target devices are used on host, un-mount file system and export volume before starting
establish.
symrdf establish -g <grp>
18
symrdf establish -g SRDF_NBI_0691_1168 Execute an RDF 'Incremental Establish' operation for device group 'SRDF_NBI_0691_1168' (y/[n]) ? y An RDF 'Incremental Establish' operation execution is in progress for device group 'SRDF_NBI_0691_1168'. Please wait... Suspend RDF link(s).......................................Done. Merge device track tables between source and target.......Started. Devices: 0BE7-0C06 ...................................... Not Merged. Devices: 1F4D-1F6C in (0691,011)......................... In Progress. Snippet for example purpose -- Devices: 1F6D-1F8C in (0691,011)......................... In Progress. Devices: 1F4D-1F6C in (0691,011)......................... Merged. Merge device track tables between source and target.......Done. Resume RDF link(s)........................................Started. Resume RDF link(s)........................................Done. The RDF 'Incremental Establish' operation successfully initiated for device group 'SRDF_NBI_0691_1168'.
• To start resume RDF Copy from last Suspend status.
symrdf resume -g <grp>
• To start force suspend while devices are in “Sync in Progress” status (be careful while using “–
symforce” option).
symrdf suspend -g <grp> -force –symforce
• To check the status of RDF copy. You have to add “-rdfa” during SRDF/A operation.
symrdf -g <grp> query
• To verify all devices are Synchronized or not
symrdf -g <grp> -verify -synchronized
19
• To check statistics of rdf copy
symstat -sid <sid> -ra all -i 5 -c 30
• To split the copy after all devices synchronized. Split make remote devices Read/Write and
available for host to mount.
symrdf split -g <grp>
symrdf –g SRDF_NBI_0691_1168 split Execute an RDF 'Split' operation for device group 'SRDF_NBI_0691_1168' (y/[n]) ? y An RDF 'Split' operation execution is in progress for device group 'SRDF_NBI_0691_1168'. Please wait... Suspend RDF link(s).......................................Started. Suspend RDF link(s).......................................Done. Read/Write Enable device(s) on SA at target (R2)..........Done. Read/Write Enable device(s) on RA at target (R2)..........Done. Suspend RDF link(s).......................................Started. Suspend RDF link(s).......................................Done. The RDF 'Split' operation successfully executed for device group 'SRDF_NBI_0691_1168'.
• To split the copy while Sync in Progress
symrdf split -g <grp>-force –symforce
• To initiate full restore from R2 to R1. This will start data copy from R2 to R1. Host can able to
access data once restore operation initiated successfully.
symrdf –g <grp> restore –full
• List Device Group on SYMAPI Server
“symdg list” or “symcg list”
20
“symdg list” is for regular disk group and “symcg list” is for composite disk group.
• How to create device pairing relationship?
symrdf createpair –file <file name with device pairing> -sid <source SID> -rdfg <RDF Grp # > -invalidate r2 -noprompt -type rdf1 -g <new group name> An RDF 'Create Pair' operation execution is in progress for device file '/home/smccal/NBI_srdf/device_pairs_REDO.txt'. Please wait... Create RDF Pair in (0691,011)....................................Done. Mark target device(s) in (0691,011) for full copy from source....Started. Devices: 00BF-00C6 in (0691,011)............................... Marked. Mark target device(s) in (0691,011) for full copy from source....Done. The RDF 'Create Pair' operation successfully executed for device file '/home/smccal/NBI_srdf/device_pairs_REDO.txt'.
• Initiate Checkpoint before Split activity symrdf –g <grp> checkpoint symrdf -g SRDF_NBI_0691_1168 checkpoint ... Waiting 46 seconds for the checkpoint ... Check-point passed!
• Verify RDF consistent state symrdf –g <grp> verify -consistent symrdf -g SRDF_NBI_0691_1168 verify -consistent All devices in the group 'SRDF_NBI_0691_1168' are in 'Consistent' state.
• How to change mode to Asynchronous mode? symrdf –g <grp> set mode async symrdf –g SRDF_NBI_0691_1168 set mode async Execute an RDF Set 'Asynchronous Mode' operation for device group 'SRDF_NBI_0691_1168' (y/[n]) ? y An RDF Set 'Asynchronous Mode' operation execution is in progress for device group 'SRDF_NBI_0691_1168'. Please wait...
21
The RDF Set 'Asynchronous Mode' operation successfully executed for device group 'SRDF_NBI_0691_1168'.
• Enable SRDF/A and Consistency symrf –g >grp> enable symrdf -g SRDF_NBI_0691_1168 enable Execute an RDF 'Enable' operation for device group 'SRDF_NBI_0691_1168' (y/[n]) ? y An RDF 'Enable' operation execution is in progress for device group 'SRDF_NBI_0691_1168'. Please wait... The RDF 'Enable' operation successfully executed for device group 'SRDF_NBI_0691_1168'.
• How to delete Pairing Relationship? Symrdf –g <grp> deletepair –force -symforce symrdf -g SRDF_NBI_redo deletepair -force -symforce Execute an RDF 'Delete Pair' operation for device group 'SRDF_NBI_redo' (y/[n]) ? y An RDF 'Delete Pair' operation execution is in progress for device group 'SRDF_NBI_redo'. Please wait... Delete RDF Pair...........................................Done. The RDF 'Delete Pair' operation successfully executed for device group 'SRDF_NBI_redo'.
• How to create new RDF group? symrdf addgrp-label <Grp name> -rdfg <rdfg #> -sid <source SID> -dir RF,RF –remote_rdfg <remote rdfg #> -remote_sid < remote SID> -remote_dir RF,RF symrdf addgrp -label DYNGRP21 -rdfg 21 -sid 0512 -dir 8d,9d -remote_rdfg 21 -remote_sid 1168 -remote_dir 8d,9d
• How to display RDF group information? symcfg -sid <frame#> -ra all list symcfg -sid 0691 -ra all list
22
Symmetrix ID: 000190100691 S Y M M E T R I X R D F D I R E C T O R S Remote Local Remote Ident Symb Num Slot Type Attr SymmID RA Grp RA Grp Status RF-8D 08D 56 8 RDF-BI-DIR - 000190101168 11 (0A) 11 (0A) Online - 000190101160 10 (09) 10 (09) RF-9D 09D 57 9 RDF-BI-DIR - 000190101168 11 (0A) 11 (0A) Online - 000190101160 10 (09) 10 (09)
• To create a device group named groupname and of type dg_type, enter:
symdg -type dg_type create groupname
There are three types of groups:
REGULAR Non-RDF volumes (the default)
RDF1 R1 volumes
RDF2 R2 volumes
• Add each volume by its Symmetrix volume number vol_num using the symld command:
symld -g groupname -sid symm_id add dev vol_num • If you want to populate the device group with all of the SRDF/A enabled devices, identify the RDF
group number. To identify the RDF group number, examine the output of the symrdf -rdfa list
command. Look at the column labeled “RDF Typ:G”. The column will be either R1:N or R2:N
where N is the RDF group number.
Once you have identified the RDF group number, you can add all of the devices with that RDF group
number rdfg_num using the symld command:
symld -g groupname -sid symm_id -RDFG rdfg_num addall
23
Appendix C - Related Documentation The following EMC manuals and white papers provide information related to concepts discussed in this
paper:
• Solutions Enabler Symmetrix SRDF CLI Product Guide, P/N 300-000-877
• EMC Symmetrix Remote Data Facility (SRDF) Product Guide P/N 300-001-16
• TECHBOOKS- Choosing a Data Migration Solution for EMC Symmetrix Solution Guide
Glossary The following are terms used within this document.
SRDF – EMC Symmetrix Remote Data Facility to copy data from one Symmetrix frame to other.
R1 (Source/Primary) Used for SRDF as the primary storage volumes for an application. Each R1 volume
is paired with an R2 volume in a Symmetrix at the remote site. Data is then copied from the R1 volumes
to the R2 volumes. A Symmetrix may contain both R1 and R2 volumes (though not for the same data).
R2 (Target/Remote) Used for SRDF as the remote storage volumes for an application. Each R2 volume
is paired with an R1 volume in a Symmetrix at the primary site. Data is then copied from the R1 volumes
to the R2 volumes. In the event of a disaster, an application maybe failed over to a host which has
access to the R2 volumes.
TCO – Total Cost of Ownership. It is financial estimate to assess direct and indirect costs and to
determine the economic value of an investment.
SAN – Storage Area Network
SRDF/AR – EMC Symmetrix Remote Data Facility/Automated Replication
SRDF/A - EMC Symmetrix Remote Data Facility/Asynchronous Replication
24
SRDF/S - EMC Symmetrix Remote Data Facility/Synchronous Replication
DMX - Direct Matrix Architecture EMC Symmetrix Storage frame
FA Port – Front End Adapter Port
RF Port – RDF Director Port
Swing Frame – Intermediate Storage frame to copy data from one storage frame to other.
SCN - The system change number (SCN) is an increasing value that uniquely identifies a committed
version of the database. Oracle records a new SCN every time a user commits a transaction. You can
obtain SCNs in a number of ways, for example, from the alert log. You can then use the SCN as an
identifier for recovery. Oracle uses SCNs in control files, datafile headers, and redo records. Every redo
log file has both a log sequence number and a low and high SCN. The low SCN records the lowest SCN
recorded in the log file, while the high SCN records the highest SCN in the log file.
5670 - Enginuity Symmetrix Operating System running on Source DMX-2 frames
5671 - Enginuity Symmetrix Operating System running on Swing DMX-2 frame
5771 - Enginuity Symmetrix Operating System running on Source DMX-3 frames
5772 - Enginuity Symmetrix Operating System running on target DMX-4 frame
25
Biography: Sejal Joshi Sejal Joshi has more than 15 years of experience in the IT industry. He completed a Bachelor of
Engineering degree in Electronics in India in 1993, and is currently working for a large telecommunication
company as a Sr. Technical Team Lead in the SAN/Storage Operations team. He and his colleagues
manage Storage frames and SANs from multiple vendors. Also, he provides support for local and remote
replication. Sejal’s primary responsibilities include storage provisioning, automation, performance
monitoring/evaluation, and SAN/Storage implementations.
Professional Certifications
• HP Certified IT Professional (HP-UX Operating System) • SUN Certified System and Network Administrator (SUN Solaris Operating System) • EMC Technology Foundation (EMC) • IT Service Management (ITIL) • Brocade Certified Fabric Professional (BCFP) • Brocade Certified SAN Manager (BCSM) • Brocade Certified Fabric Designer (BCFD) • Brainbench Certified UNIX Administration (HP-UX 11.00)
Biography: Ken Guest Ken Guest has been working in the IT Industry since 1998. He received his Bachelors of Business
Administration from Texas A&M University in 1998. Since then, he has worked for several companies in
va rious IT roles including UNIX Systems Administration, Database Administrator, SAN/Storage
Administration, Implementation Consultant and Technical Consultant. During the past 4 years, he has
been working in the SAN/Storage Arena supporting Large Multi-Vendor Multi-Data Center Environments.
As a Sr. Systems Manager/Automation Lead for a large telecommunications company, his day-to-day
responsibilities include: storage provisioning, automation, performance monitoring/evaluation,
SAN/Storage implementation and developing/implementing custom scripts that create/enforce standards
and procedures.
Professional Certifications
HP Certified IT Professional SUN Certified System and Network Administrator EMC Technology Foundations IT Service Management (ITIL) SNIA Storage Network Foundations