HP StorageWorks Storage System Scripting Utility reference (September 2005)

Switches

SAVE_ALL_WORLD_WIDE_LUN_NAME

This option saves lunwwids for all the vdisks, exc ept co ntainer and destination DR members.

SA VE_DIFFEREN

T_WORLD_WIDE_LUN_NAME

This option saves the lunwwids for the vdisks where the lunwwid was changed from its original value.

This option applies to all the vdisks except container an d destination DR mem b ers.

NOTE:

CAPTURE CONFI

GURATION by default does not save lunwwid of any vdisk. You need to explicitly specify

oneoftheabovetwooptions.

ST ART_AT=

This option allows you to specify at which step (1a, 1b, 1c, 2, 3) CAPTURE CONFIGURATION has to

start. The user doesn’t have to recapture everything when the ﬁrst step works, but a later step f ails.

Examples

CAPTURE CONFIGURATION c:\sales.txt START_AT=2

This example starts the capture conﬁguration operation from step 2.

Step 1 scripts

The division of step 1 into three smaller steps facilitates data replication (DR) recovery.

Step 1A script

Creates the array, disk groups, hosts, and virtual d isks that are not used for data replication and LUNs for

the created disks. Step1A creates a basic system that does not include DR virtual disks or DR Groups.

CAPTURE CONFI G always creates this step.

Step 1B script

Creates all source virtua l disks used in DR Groups on this controller.

Step 1C script

Presents all source virtual disk s (creates LUNS) that are used for DR Groups to their hosts. This step exists

to assist in recovering from a DR failure in which a source site was lost. LUNs can be presented in their

original conﬁguration by running the correct step 1C script.

Step 2 script

Recreates all DR-speciﬁcconﬁguration information for which this array is the source. This involves the

conﬁguration's source DR _G ROUPs and their members only. Presentations of remote virtual disks are not

restored by this command (see step 3).

This step provides ﬂexibility when a site is completely lost. Both source and destination have separate

CAPTURE CONFIGURATION scripts, so you must run step 1A, step 1B, and step 1C on the source array

and then run step 1A, step 1B, and step 1C on the destination arrays before step 2 can be run.

Utility command reference