Instant Recovery for HP StorageWorks Enterprise Virtual Array in CA+BC Configurations

# omnidbsmis –list –session –ir
Found 2 StorageWorks EVA SMI-S session(s) in the internal database:
Session ID Backup Specification
=======================================================
2006/06/20-5 VolDpdevpa2
2006/06/20-6 VolDpdevpa2
#
2. Identify the source objects and the CA link information.
Query the objects of the specific session using the omnidbsmis command. The example
shown is for the session that has an ID of 2006/06/20-5.
# omnidbsmis -show -session 2006/06/20-5
Info on session "2006/06/20-5":
Target volume virtual disk name : \Virtual Disks\SNEHA\DP-2006.06.20-5-04497CA1A\ACTIVE
Target volume virtual disk ID : 6005-08b4-0010-3a70-0000-9000-0661-0000
Target volume virtual disk WWN : 6005-08b4-0010-3a70-0000-9000-0661-0000
StorageWorks EVA name : DPCA
StorageWorks EVA ID : 5000-1fe1-5005-dc00
Target volume snapshot type : snapclone
Source volume virtual disk ID : 6005-08b4-0010-3a70-0000-9000-0042-0000
Session ID : 2006/06/20-5
Creation Date : Tue Jun 20 15:42:42 2006
IR flag : 1
Backup specification : VolDpdevpa2
Application System : dpdevpa2.india.hp.com
Backup System : dpdevpa2.india.hp.com
#
From the above output, the following information is gathered:
• Target/replica vDisk UUID, WWN, and the name:
1. WWN and UUID - 6005-08b4-0010-3a70-0000-9000-0661-0000
2. Name - \Virtual Disks\SNEHA\DP-2006.06.20-5-04497CA1A\ACTIVE
• Source (of the replica) vDisk UUID:
1. UUID - 6005-08b4-0010-3a70-0000-9000-0042-0000
• The EVA name and the WWN where the matched source and target volumes exist:
1. Name - DPCA
2. WWN - 5000-1fe1-5005-dc00
Using this information, the source storage volume and the EVA where it resides can be located. The
target storage volume or the target vDisk may also be located to verify that it still exists.
Connect to the Storage Management Appliance or any other CV EVA management host that manages
the specific EVA. Browse through the Virtual Disk Folder until the vDisk with a matching UUID is
found.
In the screenshot below, the source vDisk with a UUID of 6005-08b4-0010-3a70-0000-9000-0042-
0000 has been located: