HP 3PAR Recovery Manager Software - Manual (Page 59)

NOTE: Retention time restrictions are:
•
You must have a Virtual Lock license to use the -retain option.
•
The minimum retention period is 1 hour; the maximum is
43,800 hours/1,825 days (5 years).
•
The default retention time is 336 hours (14 days).
•
The retention time cannot exceed the value of the StoreServ's
VVRetentionTimeMax.
•
You can set a retention time regardless of whether the policy
is numeric or expiration-based.
•
The retention time cannot be longer than the expiration time
(if the policy is expiration-based).
•
During remote virtual copy creation for periodic modes, the
retention time set at the secondary backup server is used as
the time based policy. The policy set at the primary backup
server is ignored. In case of synchronous mode, the retention
value is applied to both, the local virtual copy and remote
virtual copy. Remote virtual copy creation cannot be done if
different values are set for retention at primary backup server
and secondary backup server for synchronous mode.
•
The retention time cannot be removed or reduced after it is set.
•
To set no retention time for this virtual copy, use a value of 0h
(or 0H) or 0d (or 0D).
-f Optional. When used with the -retain option, does not request
confirmation for the retention time modification.
EXAMPLES
The following command creates a virtual copy for the database test on the SQL server (SQLServer).
HpRmCli Sql create -s SQLServer -d test
The following command creates a virtual copy for the database test on a virtual SQL server
(SQLVirtualServer) on a cluster.
HpRmCli Sql create -s SQLVirtualServer -d test
The following command creates a Remote Copy snapshot for the database test on a virtual SQL
server (SQLVirtualServer) on a cluster to a secondary site server (SecondaryServer).
HpRmCli Sql create -s SQLVirtualServer -d test -rc SecondaryServer
NOTE: Use quotes ("") when an option value includes spaces.
NOTE: HP 3PAR VSS Software waits up to 10 seconds for a virtual copy operation; and this
interval can not be configured. In most of the cases, 10 seconds is a sufficient interval to successfully
create a virtual copy. However, in some circumstances under very heavy loads, 10 seconds may
not be enough time, and the virtual copy might fail on this attempt. This failure is a VSS framework
requirement on Microsoft’s part.
If such a failure occurs, VSS does not automatically retry the shadow copy creation. You must use
the Recovery Manager GUI or CLI to reattempt to create the virtual copy.
During virtual copy creation, the system creates a backup document in XML format. This document
contains current system information and can be used for restore purposes.
Recovery Manager Commands 59