Chat now with support
Chat mit Support

Rapid Recovery 6.3 - Command Line and Scripting Reference Guide

Rapid Recovery overview and system requirements Command Line Management Utility PowerShell Module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets
Add-CredentialsVaultAccount AddEncryptionKeytoProtectedMachine Add-EsxAutoProtectObjects Add-EsxVirtualMachines Add-HyperVClusterSharedVirtualDisks Add-HyperVClusterVirtualMachines Add-HyperVVirtualMachines Disable-HyperVAutoProtection Edit-ActiveBlockMapping Edit-AzureVirtualStandby Edit-EsxiVirtualStandby Edit-EsxServerProtectionRules Edit-ExcludedFilesAndFolders Edit-HyperVClusterProtectionRules Edit-HyperVServerProtectionRules Edit-HyperVVirtualStandby Edit-OracleDBVerifyNightlyJob Edit-OracleLogTruncationNightlyJob Edit-Replication Edit-ScheduledArchive Edit-VBVirtualStandby Edit-VMVirtualStandby Enable-HyperVAutoProtection Enable-OracleArchiveLogMode Get-ActiveJobs Get-CloudAccounts Get-Clusters Get-CompletedJobs Get-CredentialsVaultAccounts Get-ExchangeMailStores Get-Failed Get-FailedJobs Get-HyperVClusterSharedVirtualDisks Get-ListAzureVMSizes Get-Mounts Get-OracleInstanceMetadata Get-OracleInstances Get-Passed Get-ProtectedServers Get-ProtectionGroups Get-ProtectionRules Get-QueuedJobs Get-RecoveryPoints Get-ReplicatedServers Get-Repositories Get-ScheduledArchives Get-SqlDatabases Get-TransferQueueEntries Get-UnprotectedVolumes Get-Version Get-VirtualizedServers Get-Volumes Join-CredentialsVaultAccount New-AzureVirtualStandby New-Base New-BootCD New-CloudAccount New-EncryptionKey New-EsxiVirtualStandby New-FileSearch New-HyperVVirtualStandby New-Mount New-Replication New-Repository New-ScheduledArchive New-Snapshot New-VBVirtualStandby New-VMVirtualStandby Open-DvmRepository Push-Replication Push-Rollup Remove-Agent Remove-CredentialsVaultAccount Remove-EncryptionKey Remove-EsxAutoProtectObjects Remove-EsxVirtualMachines Remove-HyperVClusterSharedVirtualDisks Remove-HyperVClusterVirtualMachines Remove-HyperVVirtualMachines Remove-Mount Remove-Mounts Remove-RecoveryPoints Remove-Replication Remove-Repository Remove-ScheduledArchive Remove-VirtualStandby Restart-CoreService Resume-Replication Resume-ScheduledArchive Resume-Scheduler Resume-Snapshot Resume-VirtualStandby Set-AgentMetadataCredentials Set-CredentialsVaultAccount Set-DedupCacheConfiguration Set-License Set-OracleMetadataCredentials Set-ReplicationResponse Start-Archive Start-AttachabilityCheck Start-AzureDeploy Start-AzureExport Start-BackupSettings Start-ChecksumCheck Start-ConfigureAgentMigration Start-ConsumeSeedDrive Start-CopySeedDrive Start-EsxiExport Start-HypervExport Start-LogTruncation Start-MountabilityCheck Start-OptimizationJob Start-OracleDBVerifyJob Start-OracleLogTruncationJob Start-Protect Start-ProtectCluster Start-ProtectEsxServer Start-ProtectHyperVCluster Start-ProtectHyperVServer Start-RepositoryCheck Start-RestoreAgent Start-RestoreArchive Start-RestoreSettings Start-RestoreUrc Start-ScheduledArchive Start-VBExport Start-VirtualStandby Start-VMExport Stop-ActiveJobs Stop-CoreService Suspend-Replication Suspend-ScheduledArchive Suspend-Scheduler Suspend-Snapshot Suspend-VirtualStandby Update-Repository
Localization Qualifiers
Scripting

Start-ProtectEsxServer

You can use the Start-ProtectEsxServer cmdlet to add a VMware ESXi virtual machine to protection.

Usage

The usage for the command is as follows: 

Start-ProtectEsxServer -core [host name] -user [user name] -password [password] -repository [repository name] -server [name | IP address] -serverusername [user name] -serverpassword [password for server login] -serverport [port] -virtualMachines [virtual machines collection | all] -autoProtect [object ID or name collection]
Command Options

The following table describes the options available for the Start-ProtectEsxServer command:

Table 196: Start-ProtectEsxServer command options
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. 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. 
-repository
 Required. The name of the repository that is associated with the Core that you want to use to protect the virtual machine.
Note: You must enclose the name in double quotes. 
-server
 The name or IP address for the vCenter or ESXi server you want to protect. 
-serverusername
 The user name for logging in to the vCenter or ESXi server that you want to protect. 
-serverpassword
 The password for logging in to the vCenter or ESXi server that you want to protect. 
-serverport
 Optional. The port number for the vCenter or ESXi server that you want to protect. 
-virtualmachines
 Optional. This option lets you list the virtual machines that you want to protect. 
-autoprotect
 Optional. This option lets you list new virtual machines that you want to automatically protect.
Examples:

Protect specific virtual machines from a vCenter or ESXi server with the Core: 

>Start-ProtectEsxServer -core 10.10.10.10 -user admin -password password -repository "Repository 1" -server 10.10.8.150 -serverport 443 -serverusername root -serverpassword password -virtualmachines "VM1" "VM2" -autoprotect "Folder1"

Start-ProtectHyperVCluster

The Start-ProtectHyperVCluster cmdlet adds a Hyper-V cluster to protection by a Core using agentless protection.

Usage

The usage for the command is as follows: 

Start-ProtectHyperVCluster -core [host name] -user [user name] -password [password] -repository [name] -server [name | IP address] -serverusername [user name] -serverpassword [password] -serverport [port] -virtualmachines [virtual machines collection | all] -isagentprotection
Command Options

The following table describes the options available for the Start-ProtectHyperVCluster command:

Table 197: Start-ProtectHyperVCluster command options
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 must also provide a password. If none is provided, then the credentials for the logged-on user are used. 
-password
 Optional. 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. 
-repository
 Name of a repository on the Core to which the protected machine data should be stored. The name must be enclosed in double quotes. 
-server
 Name or IP address of the Hyper-V server that you want to protect. 
-serverusername
 User name for the Hyper-V server to be protected. 
-serverpassword
 Password for the Hyper-V server to be protected. 
-serverport
 Optional. Protected Hyper-V server port number. 
-virtualmachines
 Optional. List of virtual machines to protect. Values must be enclosed in double quotes and separated by a space. If you exclude this parameter, only the Hyper-V cluster container is protected. 
-isagentprotection
 Optional. Use this option to protect a cluster with an Agent in each guest virtual machine, which is false by default. 
-autoprotect
 Optional. This option enables the autoprotect feature for the Hyper-V server. It is not compatible with the -isagentprotection option.
Examples:

Protect specific virtual machines of a Hyper-V cluster: 

>Start-ProtectHyperVCluster -core 10.10.10.10 -username admin -password password -repository “Repository 1” -server 10.10.8.150 -serverport 443 -serverusername root clusterpassword password -virtualmachines “VM1” "VM2" -autoprotect

Start-ProtectHyperVServer

The Start-ProtectHyperVServer cmdlet adds a Hyper-V server to protection by a Core using agentless protection.

Usage

The usage for the command is as follows: 

Start-ProtectHyperVServer -core [host name] -user [user name] -password [password] -repository [name] -server [name | IP address] -serverusername [user name] -serverpassword [password] -serverport [port] -virtualmachines [virtual machines collection | all] -isagentprotection
Command Options

The following table describes the options available for the Start-ProtectHyperVServer command:

Table 198: Start-ProtectHyperVServer command options
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 must also provide a password. If none is provided, then the credentials for the logged-on user are used. 
-password
 Optional. 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. 
-repository
 Name of a repository on the Core to which the protected machine data should be stored. The name must be enclosed in double quotes. 
-server
 Name or IP address of the Hyper-V server that you want to protect. 
-serverusername
 User name for the Hyper-V server to be protected. 
-serverpassword
 Password for the Hyper-V server to be protected. 
-serverport
 Optional. Protected Hyper-V server port number. 
-virtualmachines
 Optional. List of virtual machines to protect. Values must be enclosed in double quotes and separated by a space. If you exclude this parameter, only the Hyper-V cluster container is protected.
Examples:

Protect specific virtual machines of a Hyper-V server: 

>Start-ProtectHyperVServer -core 10.10.10.10 -username admin -password password -repository “Repository 1” -server 10.10.8.150 -serverport 443 -serverusername root clusterpassword password -virtualmachines “VM1” "VM2"

Start-RepositoryCheck

The Start-RepositoryCheck PowerShell cmdlet lets you check the integrity of a DVM repository.

Usage

The usage for the command is as follows: 

Start-RepositoryCheck -name [repository name] | -all [check all repositories] -password [password] -force
Command Options

The following table describes the options available for the Start-RepositoryCheck command:

Table 199: Start-RepositoryCheck command options
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. 

-repository
 Required. The name of the repository that you want to check. 
-all
 Optional. Check all repositories associated with this Core. 
-force
 Optional. Perform the repository check without confirmation.
Examples:

Start checking a DVM repository: 

>Start-RepositoryCheck -repository newRepository1 -core 10.10.10.10:8006 -user administrator -password 23WE@#$sdd
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen