Add-HyperVVirtualMachines
The Add-HyperVVirtualMachines cmdlet lets you add specific virtual machines (VMs) from a Hyper-V cluster under the protection of a Core.
Usage
The usage for the command is as follows:
Add-HyperVVirtualMachines -core [host name] -user [user name] -password [password] -repository [name] -protectedserver [name | IP address] -virtualmachines [virtual machines collection | all]
Command Options
The following table describes the options available for the Add-HyperVVirtualMachines command:
Table 83: Add-HyperVVirtualMachines command options
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
-repository |
Required. The name of the repository that is associated with the Core that you want to use to store the data of the virtual machine.
Note: You must enclose the name in double quotes. |
-protectedserver |
Use this option to edit Hyper-V objects for a specific virtual machine. |
-virtualmachines |
A list of the virtual machines that you want to protect, each separated by a comma. The name of the VM must be enclosed in double quotes. |
Example:
Add specific VMs of a Hyper-V cluster under protection by the Core:
>Add-HyperVVirtualMachines -repository "Repository 1" -protectedserver HVServer1 -virtualmachines "Win8x64-gen1", "Win2012x64-gen2"
Disable-HyperVAutoProtection
The Disable-HyperVAutoProtection cmdlet lets you disable the auto-protection feature, which automatically protects new virtual machines (VMs), on a Hyper-V host.
Usage
The usage for the command is as follows:
Disable-HyperVAutoProtection -core [host name] -user [user name] -password [password] -protectedserver [name | IP address]
Command Options
The following table describes the options available for the Disable-HyperVAutoProtection command:
Table 84: Disable-HyperVAutoProtection command options
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
-protectedserver |
The display name, host name, or IP address of the protected Hyper-V server. |
Example:
Disable auto protection of new virtual machines on the specified Hyper-V host:
>Disable-HyperVAutoProtection -protectedserver "10.10.1.1"
Edit-AzureVirtualStandby
You can use the Edit-AzureVirtualStandby cmdlet to change the parameters of an existing Azure virtual standby continuous export.
Usage
The usage for the command is as follows:
Edit-AzureVirtualStandby -core [host name] -user [user name for Core] -password [password for Core] -protectedserver [name | IP address] -volumes [volume names | all] -containername [container] -foldername [folder name] -subscriptionid [Azure subscription ID] -forceedit
Command Options
The following table describes the options available for the Edit-AzureVirtualStandby command:
Table 85: Edit-AzureVirtualStandby command options
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default, the connection is made to the Core installed on the local machine. |
-user |
Optional. The user name for the remote Core host machine. If you specify a user name, you must also provide a password. If none is provided, then the credentials for the logged-on user are used. |
-password |
Optional. The password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none is provided, then the credentials for the logged-on user are used. |
-protectedserver |
Protected machine with recovery points that you want to export. |
-volumes |
Optional. List of additional volume names to be exported. If you use the value all or use no value, then all volumes export. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volumes names; for example, use "c:" "d:". |
-containername |
The name of the container in the Azure storage account (classic). The name must container between three and 63 characters (lowercase letters, numbers, and hyphens only), and start with a letter or a number. Every hyphen must be preceded and followed by a letter or number. |
-foldername |
Optional. The name of a folder inside of the Azure storage container. A folder name cannot contain any of the following characters: \ / : * ? " < > |. |
-subscriptionid |
The identifier of a previously added Azure subscription. |
-forceedit |
Optional. This option lets you delete existing export files when you change an export location. |
Example:
Edit an Azure virtual standby export:
>Edit-AzureVirtualStandby -protectedserver 10.10.5.22 -subscriptionid "111111-22222-33333-4444-555555" -containername container1 -foldername folder2
Edit-EsxiVirtualStandby
The Edit-EsxiVirtualStandby command lets you use PowerShell to make changes to an existing virtual export to an ESXi virtual machine (VM).
Usage
The usage for the command is as follows:
Edit-EsxiVirtualStandby [-HostName <String>] [-HostPort <String>] [-HostUserName <String>] [-HostPassword <String>] [-DiskProvisioning <String>] [-DiskMapping <String>] [-ProtectedServer <String>] [-Volumes <String[]>] [-VMName <String>] [-UseSourceRam] [-Ram <String>] [-User <String>] [-Core <String>] [-Password <String>] [-Verbose] [-Debug] [-ErroAction<ActionPreference>] [-WarningAction<ActionPreference>] [-ErrorVariable String>] [-WarningVariable <String> [-OutVariable <String>] [-OutBuffer <Int32>]
Command Options
The following table describes the options available for the Edit-EsxiVirtualStandby command:
Table 86: Edit-EsxiVirtualStandby command options
-? |
Display this help message. |
-core |
Optional. Remote Core host machine IP address (with an optional port number). By default the connection is made to the Core installed on the local machine. |
-user |
Optional. User name for the remote Core host machine. If you specify a user name, you also have to provide a password.
If none are provided, then the logged-on user's credentials will be used. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a log on.
If none are provided, then the logged-on user's credentials will be used. |
-protectedserver |
Show jobs for a specific protected machine, indicated by IP address. |
-all |
Show all jobs, including those performed by the Core and all protected servers. |
-number |
Optional. Determine how many records to display. available values are:
all (display all jobs); l[number] or [number] (fetches ## most recent jobs sorted by execution and time); f[number] (displays first ## recovery jobs sorted by execution and time). By default, the 20 most recent jobs are shown. |
-jobtype |
Optional. Specifies the job type filter. Available values are: 'transfer' (data transfer), 'repository' (repository maintenance), 'replication' (local and remote replications), 'backup' (backup and restore), 'bootcdbuilder' (create boot CDs), 'diagnostics' (upload logs), 'exchange' (Exchange Server files check), 'export' (recovery point export), 'pushinstall' (deploy agents), 'rollback' (restoring from a recovery point), 'rollup' (recovery point rollups), 'sqlattach' (agent attachability checks), and 'mount' (mount repository). By default, all jobs of the specified type are returned. |
-time |
Optional. Filter output by date and time for the job started. Available types of input include:
#d or DD (where # is a number for the period of time of days before now until now)
#h or #H (where # is number for the period of hours before now until now)
“time date 1”, “time date 2” (to show a custom range of time from a specific date appearing before the comma to a specific date following the comma). |
Example:
Lists all active jobs on the local Core:
>Get-activejobs –all
