Dell EMC VMAX, Configuration And Best Practices Technical Notes

Page: 43 / 82

43
Product Revision : 5977
Device WWN : 60000970000197800129533030303133
Device Emulation Type : FBA
Device Defined Label Type: N/A
Device Defined Label : N/A
Device Sub System Id : N/A
Cache Partition Name : DEFAULT_PARTITION
Bound Pool Name : SRP_1
Device Block Size : 512
Device Capacity
{
Cylinders : 27307
Tracks : 409605
512-byte Blocks : 104858880
MegaBytes : 51201
KiloBytes : 52429440
Geometry Limited : No
}
Device External Identity
{
Device WWN : 60000970000195703184533030313538
...
Note: the native identities of devices can be displayed by adding the –native option to syminq. Also with the release of
PowerPath 6.2 both native and effective IDs will be displayed.
USE THE RECOVER COMMAND
The recover command can be used if a migration step fails due to some problem in the environment, such as a connectivity issue
between the source and target arrays or the failure of a command to complete that leaves an NDM operation only partially finished. In
this example, a create failed because of a transient issue on the target array. The transient issue resolved itself within seconds and a
recover operation was immediately run. The recover operation picks up where the create command failed and completes the create
operation.
C:\>symdm create -src_sid 3184 -tgt_sid 0129 -sg lcseb246_sg -nop
A DM 'Create' operation is
in progress for storage group 'lcseb246_sg'. Please wait...
The migration session is not in a valid DM state for this operation
C:\>symdm -sid 0129 -sg lcseb246_sg list
Symmetrix ID : 000197800129
Storage Group: lcseb246_sg
Total
Source Target Capacity Done
Array Array State (GB) (%)
------------ ------------ -------------- --------- ----
000195703184 000197800129 CreateFailed 200.0 N/A
The recover operation picks up where the create command failed and completes the create operation.