HP 3PAR Recovery Manager Software for VMware vSphere Licenses - Manual (Page 58)

NOTE: Use quotes ("") for names that include spaces.
NOTE: If you specify the -both option during the CCR configuration, Recovery Manager
for Exchange first attempts to take a snapshot on the passive node, then it attempts to take a
snapshot on the active node. A success status indicates that at least one of the snapshots was
successfully created.
Examples
The following command will create a snapshot for the storage group sg2 on exchange server
bottlenosed
.
RMExch create -s bottlenosed -g sg2
NOTE: The target server to create snapshots upon the completion of remote copy process has to
have the same version of Recovery Manager Backup Server component installed. Refer to Remote
Copy Integration for more information on the Remote Copy setup.
NOTE: It is the user's responsibility to perform data integrity checking and transaction log
truncation to the virtual copy created with the -nc option. Skipping data integrity checking is not
recommend.
NOTE: VSS will wait for up to 10 seconds for the writers to freeze I/O, and this interval is not
configurable. In most cases 10 seconds is a sufficient window to successfully create a virtual copy.
However, in some circumstances under very heavy load, 10 seconds may not be enough and the
virtual copy will fail on this attempt, which is by design. VSS does not automatically retry the
shadow copy creation, you must retry the virtual copy creation using the Recovery Manager for
Exchange GUI or the command line.
NOTE: During virtual copy creation, Recovery Manager for Exchange dismounts and unmasks
the virtual copy device from the Windows server, and breaks the virtual copy away from VSS
control. During this process a “delayed write error” message may appear, or the message "the
system failed to flush data to the transaction log" may appear in the System Event Log. This is
normal.
58 Using the Recovery Manager CLI