HP 3PAR Recovery Manager 1.1.0 Software for Microsoft Hyper-V User Guide (QL226-96343, June 2013)

Create-vCopy
The create-vCopy Cmdlet creates a new Virtual Copy of a VM and includes the following
supported parameters. The first five parameters are for user authentication and is optional if a
successful Login-Rmh and/or login-InServ Cmdlets are executed previously.
Preconditions
The user must first login with Login-Rmh.
Syntax
Any optional parameters require square brackets [ ] around them.
Create-vCopy -RmhServerName <RmhServerName> -HypervName <HypervName>
-VmNamesUuids <VmNamesUuids> [-VcNamePrefix] [-Expiry] [-Retention]
[-SavedStateBackups] [-Verbose]
Table 28 Create-vCopy parameters
DescriptionOptional/RequiredParameter
Host name of the RMH Server. This is
FQDN or IP address.
Required-RmhServerName
Optionally select Hyper-V host/cluster
to use. If not specified, Hyper-V
Required-HypervName
host/cluster must be selected using
Select-Hyperv. This is FQDN or IP
address. Synonyms for Hyper-V are
supported. The localhost is not
supported.
Comma separated VM names (or
UUIDs) .
Required-VmNamesUuids
For best practice, if more than one VM
name specified, ensure all VMs use the
same Storage System volume.
The Virtual Copy name prefix. A unique
timestamp will be generated for this
Optional-VcNamePrefix
new Virtual Copy and appended to this
prefix. If not specified, the VC name
will be vc-timestamp where
timestamp is generated for this new
Virtual Copy.
Integer value followed by letter h or d
for Hours and Days respectively Default:
use the RMH Policy.
Optional-Expiry
Integer value followed by letter h or d
for Hours and Days respectively Default:
use the RMH Policy.
Optional-Retention
Disabled or enabled.Optional-SavedStateBackups
Default: use the RMH policy.
Displays progress messagesOptional-Verbose
This Cmdlet returns a list of custom objects of type RmhCreateVirtualcopyResult, each for
every VM being used and includes following properties:
• VM Name or UUID
• Success/Failure status of the create-vCopy operation for the VM
50 Using PowerShell Snap-in Command Line Interface