The Push-Rollup command forces rollup for a protected machine.
Usage
The usage for the command is as follows:
Push-Rollup -core [host name] -user [user name] -password [password] -protectedserver [machine name | IP address]
Command Options
The following table describes the options available for the Push-Rollup command:
Table 135: Push-Rollup command options
-? |
Display this help message. |
-all |
Force all protected machines. |
-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. |
-password |
Optional. Password to the remote Core host machine. If you specify a password, you also have to provide a user name. If none are provided, then the logged-on user's credentials will be used. |
-protectedserver |
Force for the current protected machine’s name. |
-user |
Optional. Login for the remote Core host machine. If you specify a login, you also have to provide a password. If none are provided, then the logged-on user's credentials will be used. |
Example:
Push rollup for a single protected machine:
>Push-Rollup -core 10.10.10.10:8006 -user administrator -password 23WE@#$sdd –protectedserver 10.10.5.22
Push rollup for all protected machines:
>Push-Rollup -all
The Remove-Agent PowerShell command lets you remove a machine from Rapid Recovery Core protection.
Usage
The usage for the command is as follows:
Remove-Agent -core [host name] -user [login] -password [password] -protectedserver [name | IP address] -deleterecoverypoints -all
Command Options
The following table describes the options available for the Remove-MountAgent command:
Table 136: Remove-Agent 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 |
Dismount all mounted recovery points for the current protected machine. |
-deleterecoverypoints |
Optional. Delete all recovery points for this protected machine. |
-all |
Optional. Delete all protected machines from the Core. |
Example:
Dismount all protected machines and their recovery points:
>Remove-Agent -core 10.10.10.10:8006 -user administrator -password 23WE@#$sdd -deleterecoverypoints -all
The Remove-EsxAutoProtectObjects cmdlet lets you remove specific objects on vCenter or ESXi server from protection by a Core.
Usage
The usage for the command is as follows:
Remove-EsxAutoProtectObjects -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -autoprotectobjects
Command Options
The following table describes the options available for the Remove-EsxAutoProtectObjects command:
Table 137: Remove-ESXAutoProtectObjects 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 |
Use this option to edit the vCenter or ESXi objects for a specific protected machine. |
-autoprotectobjects |
A list of vCenter or ESXi objects each enclosed in double quotes and separated by a comma. |
Example:
Remove specific vCenter or ESXi objects from protection auto-protection by the Core:
>Remove-EsxAutoProtectObjects -protectedserver 10.10.8.150 -autoprotectobjects "vm1", "vm2"
The Remove-HyperVClusterSharedVirtualDisks cmdlet lets you remove shared Hyper-V virtual disks from protection of a Core.
Usage
The usage for the command is as follows:
Remove-HyperVClusterSharedVirtualDisks -core [host name] -user [user name] -password [password] -shareddisks [shared virtual disks name or path collection | all]
Command Options
The following table describes the options available for the Remove-HyperVClusterSharedVirtualDisks command:
Table 138: Remove-HyperVClusterSharedVirtualDisks 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 |
Use this option to edit the shared virtual disks for a specific protected machine. |
-shareddisks |
A list of shared disks each separate by a comma. |
Example:
Remove one shared virtual disk from protection:
>Remove-HyprVClusterSharedVirtualDisks -protectedserver "HV-2012R2" -shareddisks "Shared Disk 1"
