This procedure is for encapsulating Data Domain devices on the VMAX array for new installations. Some of these steps may not be needed in all cases. To encapsulate the Data Domain devices on the VMAX array, complete the following steps on the
application recovery host. Use the application recovery host to access both the VMAX and Data Domain environments.
Before you begin
Verify that the following prerequisites are met:
l Before you begin, to determine the devices in use, use the commands in the Data Domain Operating System Administration Guide and the Solutions Enabler
functionality. Then use that information to complete the tasks in this section, as applicable.
l You must have already provisioned LUNs on the VMAX array to the application recovery host.
l You know or can obtain the geometry of the devices that are created on the VMAX array.
l You are logged in to the host where Solutions Enabler is installed.
l You complete some tasks in the VMAX environment, and other tasks in the Data Domain environment. Therefore, you must have one window open to the VMAX environment and one window open to the Data Domain environment.
l On the Data Domain system, complete the following tasks:
1. Log in to an SSH session on the Data Domain system.
2. Enable block services for ProtectPoint if not already enabled.
3. Create a block services for ProtectPoint device pool.
4. Create a block services for ProtectPoint device group.
5. Create block services for ProtectPoint devices that have the equivalent or larger geometry as the VMAX primary LUNs. Create two block services for ProtectPoint devices for every device that is created on the VMAX array, one for backups and one for restores.
6. Create an access group on the Data Domain.
7. Add the block services for ProtectPoint devices to the access group on the Data Domain.
8. Verify that the VMAX DX ports and the Data Domain endpoint ports are zoned together.
9. View the list of VMAX initiators on the Data Domain.
10. Add the VMAX initiators to the access group on the Data Domain.
l To complete the following steps on the VMAX array, use Solutions Enabler:
1. View the back end ports (DX ports) on the VMAX array and display the WWNs.
2. Display the LUNs that are visible for a specific WWN.
3. List the disk groups that are available on the VMAX array.
4. Use the FAST.X functionality to encapsulate the Data Domain disks on the VMAX array.
l Encapsulating an external LUN creates the VMAX LUN that enables access to the external LUN. Manually set the encapsulated LUN as the snapshot target.
Encapsulate Data Domain devices on the VMAX array 27
Encapsulating the block services for ProtectPoint restore LUNs is required for restoration operations.
l The VMAX array must have four paths to the Data Domain system to correctly enable the relationship between the two systems. ProtectPoint for VMAX prerequisites on page 18 provides more information about path requirements.
Procedure
1. From the application recovery host, log in to the Data Domain system as the system administrator, sysadmin.
2. In the Data Domain environment, enable the block services for ProtectPoint protocol if not already enabled.
a. To verify the block services for ProtectPoint license is enabled, type the following command:
license show
b. If a license is not already enabled, add the license by using the following command:
license add <license_key>
Output that is similar to the following appears:
License “AAAA-BBBB-CCCC-DDDD” added.
c. To enable block services for ProtectPoint, type the following command:
vdisk enable
Note
Enabling block services for ProtectPoint enables a limited set of DD Boost features for ProtectPoint clients only. To enable full access to DD Boost functionality for all clients, add a DD Boost license.
d. To verify block services for ProtectPoint are enabled, type the following command:
vdisk status
Output that is similar to the following appears:
VDISK admin state: enabled, process is running, licensed
3. To create a user to own the new block services for ProtectPoint device pool, type the following command:
user add <user> [role {admin | security | user | backup-operator | none}]
For example:
user add user1 role none
Note
The Data Domain Operating System Version Command Reference Guide provides more information about the user add command and its options.
4. To create the block services for ProtectPoint device pool, type the following command:
vdisk pool create <pool-name> user <user-name>
For example:
vdisk pool create demo-1 user user1
To name device pools, use the guidelines in Block services for ProtectPoint object hierarchy on page 21.
5. To create the required number of block services for ProtectPoint device-groups within the device pool, type the following command:
vdisk device-group create <device-group-name> pool <pool-name>
For example:
vdisk device-group create demo-devgrp pool demo-1
To name device-groups, use the guidelines in Block services for ProtectPoint object hierarchy on page 21.
Create a separate device-group for each application recovery host.
6. From the host running Solutions Enabler, to view the geometry of the VMAX devices, type the following commands:
a. To list the VMAX devices, type the following command:
symdev list -sid <SymmID>
Encapsulate Data Domain devices on the VMAX array 29
For example:
symdev list -sid 0129
Output that is similar to the following appears:
Symmetrix ID: 000196700129
b. To view the geometry of a specific device, type the following command:
symdev show [<device number>] -sid <SymmID>
For example:
symdev show 0001A -sid 0129
Output that is similar to the following appears:
...Geometry : Native
Use the geometry mappings in the following table to create the Data Domain block services for ProtectPoint devices.
Table 6 VMAX to Data Domain device geometry mappings
VMAX device geometry value Equivalent Data Domain device geometry value
Sectors per track Sectors per track
Table 6 VMAX to Data Domain device geometry mappings (continued)
VMAX device geometry value Equivalent Data Domain device geometry value
Tracks per cylinder Heads
Cylinders Cylinders
7. On the Data Domain system, to create the block services for ProtectPoint devices that matches the geometry of the devices that are created on the VMAX array, type the following command:
vdisk device create [count <count>] heads <head-count>
cylinders <cylinder-count> sectors-per-track <sector-count>
pool <pool-name>
device-group <device-group-name>
Output that is similar to the following appears:
vdisk device create heads 15 cylinders 109227 sectors-per-track 256 pool demo-1 device-group demo-devgrp
Create two devices on the Data Domain for each VMAX device, one for backup and one for restore.
8. (Optional) To display the block services for one or more ProtectPoint pools, device-groups, and devices, type one or more of the following commands:
vdisk pool show detailed pool <pool-name>
vdisk device-group show detailed <group-name>
vdisk device show detailed <device-name>
For example:
vdisk pool show detailed pool demo-1
vdisk device-group show detailed demo-devgrp
vdisk device show detailed device-demo
9. To create an access group, type the following command:
scsitarget group create <group-name> service vdisk
Encapsulate Data Domain devices on the VMAX array 31
For example:
scsitarget group create demo-accgrp service vdisk
10. To add the new block services for ProtectPoint devices to the access group, type the following command:
vdisk group add <group-name> {device <device-spec> | pool
<pool-name>
device-group <device-group-name> [device <device-spec>]} [lun
<lun>]
[primary-endpoint {all | none | <endpoint-list>}]
[secondary-endpoint {all | none | <endpoint-list>}]
For example:
vdisk group add demo-accgrp device vdisk-dev16
11. To view the list of initiators, type the following command:
scsitarget initiator show list
Output that is similar to the following appears:
Initiator System Address Group Service --- -- --- ---initiator-1 2a:10:00:21:88:00:82:74 n/a n/a initiator-2 2b:10:00:21:88:00:82:74 n/a n/a initiator-3 50:02:18:82:08:a0:02:14 n/a n/a initiator-4 50:02:18:81:08:a1:03:cc n/a n/a ucs16d_2a 21:00:00:24:ff:3f:25:1a n/a n/a ucs16d_2b 21:00:00:24:ff:3f:25:1b n/a n/a --- -- --- ---The list displays the VMAX back-end (DX) ports that have logged on to the Data Domain system.
12. To rename (alias) the initiators, type the following command:
scsitarget initiator rename <src-initiator-name> <dst-initiator-name>
For example:
scsitarget initiator rename initiator-1 vmax4d_3_08
Output that is similar to the following appears:
Initiator 'initiator-1' successfully renamed.
13. To add the initiators to the access group, type the following command:
vdisk group add <group-name> initiator <initiator-spec>
For example:
vdisk group add demo-accgrp initiator symm_9h0
14. Switch to the VMAX environment.
15. To review the list of DX ports, which are connected to the Data Domain system from the VMAX array, type the following command:
symsan list -sid <SymmID> -sanports -DX all -port all
For example:
symsan list -sid 0129 -sanports -DX all -port all
16. To copy the WWN for one of the ports and use the WWN to determine which LUNs are visible through this WWN, type the following command:
symsan -sid <SymmID> -dir All -p All list -sanluns -wwn <wwn>
For example:
symsan -sid 0129 -dir All -p All list -sanluns -wwn 2800002182DDB5D
The LUN is exposed but is not ready for use yet. The LUN must be encapsulated on to the VMAX array with FAST.X.
17. To create a VMAX storage group, type the following command:
symsg create <SgName>
For example:
symsg create storage-group-5
Note
If an existing device group is appropriate for the ProtectPoint implementation, you can use it instead of creating a device group. To see all the device groups on the VMAX array, type the symdg list -sid <SymmID> command.
Encapsulate Data Domain devices on the VMAX array 33
18. To add the source VMAX devices to the storage group, type the following command:
symsg -g <DgName> add dev <device_ID>
For example:
symsg -g storage-group-5 add dev 0001A
19. Encapsulate the Data Domain disk on the VMAX array. There are two ways to encapsulate disks:
l To encapsulate disks individually, type the following command:
symconfigure -sid <SymmID> -cmd "add external_disk, wwn=<wwn>, encapsulate_data=yes;" commit -v -nop
For example:
symconfigure -sid 0129 -cmd "add external_disk, wwn=6002189000002DDB5D0525EEE8A00011,
encapsulate_data=yes;" commit -v -nop
It takes approximately seven minutes to encapsulate each device.
l To encapsulate a group of devices, perform the following steps:
a. In a BASH shell on the application recovery host, to capture all the block services for ProtectPoint devices to encapsulate in a text file, type the following command:
ssh sysadmin@ {<DD-hostname>} vdisk device show list pool {<pool-name>} device-group {<device-group-name>} | awk '/^vdisk-dev/{print "add external_disk wwn=" $5 ", encapsulate_data=YES;"}' | sed 's/://g' > devs.txt
Note
The command fails if there are fewer than two devices that are specified in the text file.
b. On the application recovery host, to encapsulate the block services for ProtectPoint devices that are listed in the text file, type the following command:
symconfigure commit -f devs.txt
Output that is similar to the following appears:
…Establishing a configuration change session....Established.
Processing symmetrix 000196700129
Performing Access checks...Allowed.
Checking Device Reservations...Allowed.
Initiating COMMIT of configuration changes...Queued.
COMMIT requesting required resources...Obtained.
Step 008 of 064 steps...Executing.
…Step 091 of 214 steps...Executing.
…
Step 210 of 219 steps...Executing.
Local: COMMIT...Done.
New symdev: 0004C [DATA device]
New symdev: 000BA [TDEV]
Terminating the configuration change session...Done.
The configuration change session has successfully completed.
Note
The VMAX array returns a contiguous range of new device names whenever possible. However, the range of device names is not always contiguous.
The system performs the following steps:
a. Takes the device with the specified WWN. The device is now visible to the VMAX array.
b. Encapsulates the device.
c. Puts the device into the external device group.
d. Assigns a name to the device.
20. To add the encapsulated Data Domain target devices to the storage group, type the following command:
symsg -g <SgName> add dev <device-number> -tgt
For example:
symsg -g storage-group-5 add dev 0002A -tgt
21. To establish the relationship between the VMAX array and Data Domain system, and activate the snapshot, type the following command:
symsnapvx -sid <SymmID> -sg <SgName> establish -name
<SnapshotName>
For example:
symsnapvx -sid 0129 -sg storage-group-5 establish -name sg5-snap
Note
If additional devices or device groups are added to the ProtectPoint
environment after the initial configuration, this step must be repeated for the new devices or device groups.
Encapsulate Data Domain devices on the VMAX array 35
22. To move the data from the VMAX array on to the Data Domain system, type the following command:
symsnapvx sid <SymmID> sg <SgName> link copy -snapshot_name <SnapshotName>
For example:
symsnapvx sid 0129 sg storagegroup5 link copy -snapshot_name dg5-snap
This command moves the changed blocks on the source device to the target device.
Note
If additional devices or device groups are added to the ProtectPoint
environment after the initial configuration, this step must be repeated for the new devices or device groups.
23. (Optional) To set the data transfer rate for moving data from the VMAX array to the Data Domain system when a snapshot is created and activated for the first time, type the following command:
symqos -sid <SymmID> -sg <SgName> set clone pace {0-16 | stop
| urgent}
Note
If you must change the clone pace, start with a setting of 4. This value results in a moderate reduction of the copy rate for Gen0 backups, which lowers the response time overhead.
24. To check the status of the link copy operation, type the following command:
symsnapvx list -detail -sid <SymmID> {-sg <SgName> | -devs
<First DeviceInRange>:<LastDeviceInRange>} -linked
For example:
symsnapvx list -detail -sid 0129 -sg storage-group-5 -linked
25. If the environment is to use FAST.X restore operations, create a VMAX storage group for the restore LUNs, and then add the encapsulated devices to it.
The default storage group name is NsrSnapSG. To use a non-default name for the storage group, that name must be specified in the file system agent or application agent configuration files.
Perform the following steps:
a. To create a storage group, type the following command:
symsg -sid <SymmID> create ProtectPointRestoreGroup
For example:
symsg -sid 0129 create ProtectPointRestoreGroup
Note
The storage group name is case-insensitive.
b. To add the restore devices to the storage group, type the following command:
symsg -sid <SymmID> -sg ProtectPointRestoreGroup add dev
<device-number>