HP P6000 Replication Solutions Manager User Guide (T3680-96089, October 2012)

failure status. When the first command is encountered that is not a SetVariable or validation
command, the job is stopped with a success status.
Skip validation. If the line is a validation command it is ignored.
In the validate-only and skip validation cases, job transactions and branches within validation
commands are ignored.
Resource validation processing in transactions
Special cases exist for validation commands in a transaction block:
Validate-only. The validation command in the transaction block is not executed.
Skip validation. The validation command in the transaction block is executed.
See also job Transactions.
Wait/nowait argument
Some job commands include a wait/nowait argument. Values are:
Wait. When the job is run, issue the command, then wait until the command has been
completed before going to the next task in the job.
Nowait. When the job is run, issue the command, then immediately go to the next task in the
job.
In general, use wait when you need to ensure that all aspects of a command have been performed
by the command before any other task in the job is performed. Use nowait, when other tasks in
the job do not depend its completion.
Wait/nowait for discovery
When you include a local replication command in a job, the wait/nowait for discovery argument
requires that you specify whether or not to wait until the new replica is discovered before executing
the next step. Choices are wait and nowait. For example, in the job below, the replication manager
waits at line 7 until the new replica is discovered, before executing line 8.
TaskLine
...
$Rep1 = SnapshotHostVolume ( "%\\source_host\source_hostvol1%", FULLY_ALLOCATED, SAME, WAIT )
onerror pauseat E1:
7
//8
...
With both choices, the replica is instantly created on the storage system. With the nowait choice,
the replication manager immediately executes the next job step, whether or not its database of
resources has been updated with the new replica information. With the wait choice, the replication
manager does not execute the next step until its database of resources has been updated with the
new replica information.
Typical use of nowait with wait-for-discovery commands
The nowait for discovery option is typically used in conjunction with the
WaitForStorageVolumeDiscovery and WaitForStorageVolumesDiscovery commands to minimize
the amount of time that a database is suspended while being locally replicated.
For example, the general structure of a job to replicate a database might be:
190 Jobs