Remove-CredentialsVaultAccount
The Remove-CredentialsVaultAccount cmdlet removes the Credentials Vault account from the specified Core.
Usage
The usage for the command is as follows:
Remove-CredentialsVaultAccount [-AccountId <string>] [-User <string>] [-Core <string>] [-Password <string>] [<CommonParameters>]
Command Options
The following table describes the options available for the Remove-CredentialsVaultAccount command:
| Option | Description |
|---|---|
-? |
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. |
-accountid |
Required. The identifier of the Credentials Vault account that you want to remove. |
Examples:
Remove a Credentials Vault account from the Core:
>Remove-CredentialsVaultAccount -accountid CVaccount1 -core 10.10.10.10
Remove-EncryptionKey
The Remove-EncryptionKey cmdlet lets you add specific VMs on vCenter or ESXi server under the protection of a Core.
Usage
The usage for the command is as follows:
Remove-EncryptionKey -core [host name] -user [user name] -password [password] -keyname [name of the encryption key]
Command Options
The following table describes the options available for the Remove-EncryptionKey command:
| Option | Description | ||
|---|---|---|---|
-? |
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. | ||
-keyname |
Optional. The name of the encryption key. Specify this option if you know the name of the encryption key that you want to set for the protected machine.
|
Examples:
Remove an encryption key from the Core:
>Remove-EncryptionKey -core 10.10.10.10 -user admin -password password -keyname EKname
Remove-EsxAutoProtectObjects
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:
| Option | Description |
|---|---|
-? |
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. |
Examples:
Remove specific vCenter or ESXi objects from protection auto-protection by the Core:
>Remove-EsxAutoProtectObjects -protectedserver 10.10.8.150 -autoprotectobjects "vm1", "vm2"
Remove-EsxVirtualMachines
The Remove-EsxVirtualMachines cmdlet lets you remove specific virtual machines (VMs) on a vCenter or ESXi server under the protection of a Core.
Usage
The usage for the command is as follows:
Remove-EsxVirtualMachines -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -virtualmachines [virtual machines collection | all] -deleterecoverypoints
Command Options
The following table describes the options available for the Remove-EsxVirtualMachines command:
| Option | Description |
|---|---|
-? |
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. |
-virtualmachines |
A list of virtual machines each separate by a comma. |
-deleterecoverypoints |
Deletes the recovery points of the removed machine from the repository. If you omit this option, then the repository retains the recovery points of the removed machine. |
Examples:
Remove two VMs from a vCenter or ESXi server under protection by the Core:
>Add-EsxVirtualMachines -protectedserver 10.10.10.10 -virtualmachines "vm1", "vm2"