Use the Start-OracleDBVerifyJob
cmdlet to start the DBVerify job for one or more specified recovery points on a protected server.
The usage for the command is as follows:
Start-OracleDBVerifyJob -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -recoverypointnumber [number | numbers]
The following table describes the options available for the Start-OracleDBVerifyJob
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. 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 |
Use this option to specify the protected machine for which you want to enable the Oracle DBVerify nightly job. |
-recoverypointnumber |
The sequential number of a recovery point that you want to export (use the /list rps command to get the numbers). To start the job on multiple recovery points with one command, separate each recovery point number with a space. |
Start the Oracle DBVerify job for the recovery points on the specified protected server:
>Start-OracleDBVerifyJob -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88 -recoverypointnumber 1 2
©
The Start-OracleLogTruncationJob
cmdlet lets you start a log truncation job for a specified Oracle instance on a protected server.
The usage for the command is as follows:
Start-OracleLogTruncationJob -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -instancename [instance SID] -deletionpolicy [automatic | keepnewest | keepspecificnumber] -retentionduration [duration value] -retentionunit [day | week | month | year] -numberoffiles [number of archive files to create]
The following table describes the options available for the Start-OracleLogTruncationJob
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. 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 |
Use this option to specify the protected machine for which you want to enable Oracle log truncation as a nightly job. |
-instancename |
The name of the Oracle instance for which you want to start log truncation. |
-deletionpolicy |
Optional. This option must be represented by one of the following values:
|
-retentionduration |
Optional. This value determines the length of time to keep a log before truncating and is constrained to positive integer values. If using the "keepnewest" value of the -deletionpolicy option, a retention duration value is required. |
-retentionunit |
Optional. This option identifies the time unit for the -retentionduration option. It must be represented by one of the following values:
|
-numberoffiles |
Optional. This option sets the number of recent archive log files to keep. If using the "keepspecificnumber" value of the -deletionpolicy option, a number of files value is required. |
Start the Oracle log truncation job for the ORCL instance on a specified protected server:
>Start-OracleLogTruncationJob -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88 -instancename ORCL
Start the Oracle log truncation job for the ORCL instance on a specified protected server and configure the deletion policy as "keepnewest" with the logs kept for 10 days:
>Start-OracleLogTruncationJob -protectedserver 10.10.34.88 -instancename ORCL -deletionpolicy keepnewest -retentionduration 10 -retentionunit day
The Start-Protect
cmdlet lets an administrator add a machine to protection on a Rapid Recovery Core.
Start-Protect -core [host name] -user [user name] -password [password] -repository [repository name] -agentname [name | IP address] -agentusername [user name] -agentpassword [password] -agentCredentialsVaultAccount [id | user name | description] -agentport [port] -volumes [all | volume names] -encryptionkeyname [encryption key name] -initialpause
The following table describes the options available for the Start-Protect
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 user name. If none are provided, then the logged-on user's credentials will be used. | ||
-repository |
Name of a repository on the Core where the protected machine's data is stored. | ||
-agentname |
Protected machine name or IP address. | ||
-agentusername |
Log on to the server to be protected. | ||
-agentpassword |
Password to the server to be protected. | ||
-agentCredentialsVaultAccount |
Optional. If you want to use credentials that are already defined in the Credentials Vault for your Core, specify the unique combination of user name, password, and description. | ||
-agentport |
Protected server port number. | ||
-volumes |
List of volumes to protect. Values must be enclosed in double quotes and separated by a space.
| ||
-encryptionkeyname |
Optional. If you want to use an encryption key to safeguard the snapshots for the machine you are adding to the Core for protection, provide the encryption key name. | ||
-initialpause |
Optional. If you want to delay protection of the specified machine until you explicitly tell the Core to resume (or start) protection, enter this parameter. |
Protected the specified volumes of a machine in your Core:
>Start-Protect -repository "Repository 1" -agentname 10.10.9.120 -agentusername administrator -agentpassword 12345 -agentport 5002 -volumes "c:" "d:"
The Start-ProtectCluster
cmdlet lets an administrator add a server cluster to protection on a Rapid Recovery Core.
Usage for the command is as follows:
Start-ProtectCluster -core [host name] -user [user name] -password [password] -repository [repository name] -clustername [name | IP address] -clusterusername [user name for cluster] -clusterpassword [password for cluster] -clusterport [port] -clustervolumes [volume names] -clusternodes [cluster nodes names and volumes]
The following table describes the options available for the Start-ProtectCluster
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 user name. If none are provided, then the logged-on user's credentials will be used. | ||
-repository |
Name of a repository on the Core where the protected machine's data is stored. The name must be enclosed in double quotes. | ||
-clustername |
The name of the cluster to protect. | ||
-clusterusername |
User name for the cluster to be protected. | ||
-clusterpassword |
Password to the cluster to be protected. | ||
-clusterport |
Port number for the cluster to be protected. | ||
-clustervolumes |
List of volumes to protect. Values must be in double quotes and separated by a space.
| ||
-clusternodes |
List of cluster nodes with volumes to protect. First specify label “nodename” and then type the name of the node. Then, specify label “volumes” and then type a list of volumes for the node.
For example: |
Protect nodes on a server cluster:
>Start-ProtectCluster -repository "Repository 1" -clustername 10.10.9.120 -clusterusername administrator -clusterpassword 12345 -clusterport 5002 -clustervolumes "c:" "d:" -clusternodes nodename 10.10.10.10 volumes “c:” “e:”
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center