To restore from secondary Data Domain system and use VMAX FAST.X LUNs as app agent's restore devices, you should encapsulate the vdisk devices created in the previous section on VMAX.
Before you begin
Ensure that the following requirements are met:
l The app agent restore devices are configured on the secondary Data Domain system.
l The secondary Data Domain system and the VMAX can see each other over FS SAN.
l You have obtained the geometry of the source devices created on the VMAX array.
Encapsulate secondary Data Domain system vdisk devices on VMAX 77
Procedure
1. Switch to the VMAX environment.
2. 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
3. Copy the WWN for one of the ports and use the WWN to determine which LUNs are visible through this WWN.
The LUN is exposed but is not ready for use yet. The LUN must be encapsulated on to the VMAX array with FAST.X.
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
4. 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 symsg list -sid <SymmID> command.
5. 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, complete 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 operations:
a. Takes the device with the specified WWN. The device is now visible to the VMAX array.
Encapsulate secondary Data Domain system vdisk devices on VMAX 79
b. Encapsulates the device.
c. Puts the device into the external device group.
d. Assigns a name to the device.
6. 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
7. As the environment uses 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.
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>
Provision FAST.X restore LUNs to the application recovery host
Provision FAST.X LUNs on the VMAX array for new installations.
Before you begin
Ensure that Fibre Channel zoning is complete.
To determine the devices in use, use Solutions Enabler.
To provision the VMAX FAST.X LUNs to the application recovery host, complete the following tasks on the VMAX array:
l Create a storage group.
l Add the devices to the storage group.
l Create a port group.
l Add the front end ports to the port group where the server is zoned.
l Create an initiator group.
l Add the initiator WWNs of the application recovery host to the initiator group.
l Create a masking view.
l Discover newly provisioned LUNs on the application recovery host.
Procedure
1. From the application recovery host, to configure the VMAX FAST.X devices, use Solutions Enabler.
2. To view the existing VMAX devices, perform the following steps:
a. To list the VMAX devices, type the following command:
symdev list -sid <SymmID>
b. To view a specific FAST.X device, type the following command:
symdev show [<device number>] -sid <SymmID>
3. To create a storage group, type the following command:
symaccess -sid <SymmID> create -name <GroupName>
-type storage [devs <SymDevStart>:<SymDevEnd> |
<SymDevName>[, <SymDevName>[, <SymDevName>. . .]]
| <-g <DgName> [-std] [-bcv] [-vdev] [-tgt]> | <sg
<SgName> [, <SgName1>, <SgName2> . . . <SgNamen>]>
<-file <DeviceFileName> [src] [tgt]> [-reserve_id <ResvID>
[, <ResvID> [, <ResvID>. . .] ] ] ]
For example:
symaccess -sid 0129 create -name group1 -type storage
Note
This storage group is different from the NsrSnapSG mentioned in the
Encapsulating secondary Data Domain system vdisk devices on VMAX section.
4. To add FAST.X devices to the storage group, type the following command:
symsg -sg <SgName> -sid <SymmID> [-i <Interval>] [-c
<Count>] add dev <SymDevNumber>
For example:
symsg -sg group1 -sid 0129 add dev 0001A
Provision FAST.X restore LUNs to the application recovery host 81
5. To create a port group, type the following command:
symaccess -sid <SymmID> create -name <GroupName> -type port [-dirport <Dir>:<Port> [, <Dir>:<Port>..]]
For example:
symaccess -sid 0129 create -name group1 -type port
6. To add the front end ports to the port group, type the following command:
symaccess -sid <SymmID> -name <GroupName> -type <port> [-dirport <Dir>:<Port>[, <Dir>:<Port>[, <Dir>;:<Port>. . .]][-ckd] add [-celerra] [-rp]
For example:
symaccess -sid 0129 -name group1 -type port add -dirport 1e:8
The front end ports are the ones that connect the application recovery host to the VMAX array.
7. To create an initiator group, type the following command:
symaccess -sid <SymmID> create -name <GroupName> -type initiator [-wwn <wwn> | -iscsi <iscsi> | -file
<InitiatorFilename> | -ig <InitiatorGroupName>] [-consistent_lun]
For example:
symaccess sid 0129 create name group1 type initiator -consistent_lun
Note
The -consistent_lun option forces all devices that are masked to the initiator group to connect to the same LUN with all available ports.
8. To add the initiator WWNs to the initiator group, type the following command:
symaccess sid <SymmID> name <GroupName> type initiator -wwn <-wwn> | -iscsi <iscsi> | -ig <InitiatorGroupName> | -f
<InitiatorFilename> add
For example:
symaccess -sid 0129 -name group1 -type initiator -wwn 6002188000002ddb5d0525eee8a00011 add
Initiators can be added to an existing initiator group by specifying the initiator type (-wwn or -iscsi), the initiator group name, or by using an input file.
9. To create a masking view, type the following command:
symaccess create view -sid <SymmID> -name <ViewName> -sg
<StorageGroupName> -pg <PortGroupName> -ig
<InitiatorGroupName> [-reserve_id <ResvID> [, <ResvID>[,
<ResvID>...] ] ] [-lun addr] [-ckd] [-celerra] [-rp]
For example:
symaccess create view -sid 0129 -name view1 -sg group2 -pg portgroup1 -ig initator_group1
After you put the storage group, the port group, and the initiator group in the masking view, the initiators in the initiator group can see the devices via the port in the port group.
10. To update the local symapi database on the application recovery host, type the following command:
symcfg discover