Chatta subito con l'assistenza
Chat con il supporto

Rapid Recovery 6.9 - Commands and Scripting Reference Guide

Introduction to Rapid Recovery Command Line Management utility PowerShell module
Prerequisites for using PowerShell Working with commands and cmdlets Rapid Recovery PowerShell module cmdlets
Add-EsxAutoProtectObjects Add-EsxVirtualMachines Add-HyperVClusterSharedVirtualDisks Add-HyperVClusterVirtualMachines Add-HyperVVirtualMachines Disable-HyperVAutoProtection Edit-AzureVirtualStandby Edit-EsxiVirtualStandby 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-ExchangeMailStores Get-Failed Get-FailedJobs Get-HyperVClusterSharedVirtualDisks Get-ListAzureVMSizes Get-Mounts Get-OracleInstances Get-Passed Get-ProtectedServers Get-ProtectionGroups Get-QueuedJobs Get-RecoveryPoints Get-ReplicatedServers Get-Repositories Get-ScheduledArchives Get-SqlDatabases Get-TransferQueueEntries Get-UnprotectedVolumes Get-Version Get-VirtualizedServers Get-Volumes 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 Push-Replication Push-Rollup Remove-Agent Remove-EsxAutoProtectObjects Remove-HyperVClusterSharedVirtualDisks Remove-HyperVClusterVirtualMachines Remove-HyperVVirtualMachines Remove-Mount Remove-Mounts Remove-RecoveryPoints Remove-RemoteMount Remove-RemoteMounts Remove-Replication Remove-Repository Remove-ScheduledArchive Remove-VirtualStandby Restart-CoreService Resume-Replication Resume-ScheduledArchive Resume-Snapshot Resume-VirtualStandby Set-AgentMetadataCredentials Set-DedupCacheConfiguration Set-License Set-OracleMetadataCredentials Set-ReplicationResponse Start-Archive Start-AttachabilityCheck Start-AzureDeploy Start-AzureExport Start-ChecksumCheck 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-ScheduledArchive Start-VBExport Start-VirtualStandby Start-VMExport Stop-ActiveJobs Stop-CoreService Suspend-Replication Suspend-ScheduledArchive Suspend-Scheduler Suspend-Snapshot Suspend-VirtualStandby Suspend-VMExport Update-Repository
Localization Qualifiers
Scripting

Set-License

There may be times when you need to change the Rapid Recovery license applied to a machine, such as when moving from a trial license to a subscription or perpetual license. In such instances, you can change the license in the Command Prompt by using the Set-License command.

Usage

The usage for the command is as follows:

Set-License -core [host name] -user [user name] -password [password] -licensekey [license key] -licensepath [license file path] -licensenumber [license number] -email [email address]

Command Options

The following table describes the options available for the Set-License command:

Table 159: Set-License 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.
-licensekey
Optional. A 30-character key comprising six groups of five alphanumeric characters, each separate by a hyphen. Use this key when a license file is not available.
-licensepath
Optional. The path to the file that ends with the .lic extension. If a license file is available, you can use this option instead of the -licensekey.
-licensenumber
Optional. You may have received this nine-digit license number in an order confirmation email. If you provide this number, use the email address that received it for verification.
-email
Optional. If you use the -licensenumber, you must include the email address that received it for verification.

Examples:

Change the license key associated with this Core to JL09F-89FSD-6THFS-DSE34-KS3D5-65DF2:

>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensekey JL09F-89FSD-6THFS-DSE34-KS3D5-65DF2

Change the license key associated with this Core to the key contained in the license file:

>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensepath C:\MyLicenseFile.lic

Change the license number associated with this Core to 111-111-111 using john.doe@example.com to verify the license:

>Set-License -core 10.10.10.10 -user admin -password 676df#df -licensenumber 111-111-111 -email john.doe@example.com

Set-OracleMetadataCredentials

The Set-OracleMetadataCredentials command lets you set the metadata credentials for a specified Oracle instance.

Usage

The usage for the command is as follows:

Set-OracleMetadataCredentials -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -instancename [Oracle instance SID] -connectiontype [-basic | TNS] -hostname [host name | IP address] -port [port number] [-usesid] -instanceservicename [service name] -tnsnetworkalias [TNS alias] [-usewindowsauthentication] -oracleusername [user name] -oraclepassword [password] [-edit]

Command Options

The following table describes the options available for the Set-OracleMetadataCredentials command:

Table 160: Set-OracleMetadataCredentialscommand 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.
-protectedserver
The name or IP address of the protected machine.
-instancename
The Oracle SID from which you want to fetch metadata.
-connectiontype
Use this option to identify the connection type. It must be represented by either basic or TNS.
-hostname
Optional. The name of the Oracle host. Use it for the basic connection type.
-port
Optional. A port number. Use it for the basic connection type.
-usesid
Optional. This option uses the -instancename to identify the Oracle instance. Use it for the basic connection type.
-instanceservicename
Optional. The Oracle instance service name. Use it when the -usesid is not specified and for the basic connection type.
-tnsnetworkalias
Optional. Use this option to identify the TNS network alias when using the TNS connection type.
-usewindowsauthentication
Optional. This option lets you authenticate with your Windows credentials.
-oracleusername
Optional. The user name for the Oracle instance.
-oraclepassword
Optional. The password for the Oracle instance.
-edit
Optional. This option lets you omit any number of options.

Examples:

Set the metadata credentials for the ORCL instance on a protected server using the basic connection type:

>Set-OracleMetadataCredentials -core 10.10.127.42 -user admin -password -676df#df -protectedserver 10.10.34.88 -instancename ORCL -connectiontype basic -hostname localhost -port 1521 -usesid -oracleusername User-ORA -oraclepassword 676df#df

Set the metadata credentials for the ORCL instance on a protected server using the TNS connection type and Windows authentication:

>Set-OracleMetadataCredentials -core 10.10.127.42 -user admin -password -676df#df -protectedserver 10.10.34.88 -instancename ORCL -connectiontype TNS -tnsnetworkalias ORCL_ALIAS -usewindowsauthentication

Set-ReplicationResponse

Use the Set-ReplicationResponse command to manage pending replication requests.

Usage

The usage for the command is as follows:

Set-ReplicationResponse -core [host name] -user [user name] -password [password] -id [replication ID] -accept | -deny | -ignore -protectedserver [name | IP address]

Command Options

The following table describes the options available for the Set-ReplicationResponse command:

Table 161: Set-ReplicationResponse 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
-id
The identifier for the replication job or pending replication request. It can be a remote Core ID, host name, customer ID, email address, or pending replication request ID.
-accept
Accepts the replication request.
-deny
Denies the replication request.
-ignore
Ignores the replication request.
-protectedserver
When responding to a replication request, use this option to apply your response to list of protected servers with a repository name or ID. Use the parameter "all" to apply response to all requested machines.

Examples:

Accept a pending replication request for one protected machines:

>Set-ReplicationResponse -id customer@email.address -accepted -protectedserver 10.10.1.1 Repository1 10.10.1.2 Repository2 -responsecomment A response comment

Deny a pending replication request:

>Set-ReplicationResponse -id customer@email.address -deny

Start-Archive

Businesses often use long-term storage to archive both compliant and non-compliant data. The archive feature in Rapid Recovery is used to support the extended retention for compliant and non-compliant data. The administrator can save an archive on the local storage or network location by specifying the /Path command and credentials.

Usage

The usage for the command is as follows:

Start-Archive -path -startdate -enddate [-all] | -protectedserver [machine name] or [IP]] -core [host name] -user [user name] -password [password]

Command Options

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

Table 162: Start-Archive command options
Option Description
-?
Display this help message.
-path
Location path. Example path: ‘D:\work\archive’ or network path: ‘\\servername\sharename’.
-all
Archive recovery points for all machines on the Core.
-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.
-startdate
Start date of the date range for the created recovery points. Should be in the format specified by the OS on the current PC.
-enddate
End date of the date range. Defaults to the current time.
-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
Archive recovery points for the specified 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.
-archiveusername
Optional. Required for network path only.
-archivepassword
Optional. Required for network path only.
-comment
Optional. Example: -comment 'Before install new application'.

Example:

Archive all recovery points for all machines on the Core:

>Start-Archive -path D:\work\archive -startdate 'Example 04/30/2012' –all
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione