The Start-OptimizationJob command lets you perform optimize a repository on demand. 
 
Usage
The usage for the command is as follows: 
Start-OptimizationJob -core [host name] -user [user name] -password [password] -repository [repository name] | -all
 
Command Options
The following table describes the options available for the Start-OptimizationJob command: 
Table 171: Start-OptimizationJob 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. 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 | The name of the repository that you want to optimize. | 
| -all | Use this option to perform the optimization job on all repositories for this Core. | 
 
Example:
Start a repository optimization job: 
>Start-OptimizationJob -repository "Repository 1" -core 10.10.10.10 -user administrator -password 23WE@#$sdd
  
    
Use the command Start-OracleDBVerifyJob to start the DBVerify job for one or more specified recovery points on a protected server. 
 
Usage
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]
 
Command Options
The following table describes the options available for the Start-OracleDBVerifyJob command: 
Table 172: Start-OracleDBVerifyJob 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. 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 rpscommand to get the numbers). To start the job on multiple recovery points with one command, separate each recovery point number with a space. | 
 
Example:
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 command Start-OracleLogTruncationJob lets you start a log truncation job for a specified Oracle instance on a protected server. 
 
Usage
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]
 
Command Options
The following table describes the options available for the Start-OracleLogTruncationJob command: 
Table 173: Start-OracleLogTruncationJob 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. 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: 
"automatic""keepnewest""keepspecificnumber" | 
| -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-deletionpolicyoption, a retention duration value is required. | 
| -retentionunit | Optional. This option identifies the time unit for the -retentiondurationoption. It must be represented by one of the following values:
"day""week""month""year" | 
| -numberoffiles | Optional. This option sets the number of recent archive log files to keep. If using the "keepspecificnumber"value of the-deletionpolicyoption, a number of files value is required. | 
 
Examples:
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 command lets an administrator add a server under protection by a Core. 
 
Usage
Start-Protect -core [host name] -user [user name] -password [password] -repository [repository name] -agent [name | IP address] -agentusername [user name] 
-agentpassword [password] -agentport [port] -volumes [volume names]
 
Command Options
The following table describes the options available for the Start-Protect command: 
Table 174: Start-Protect 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 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. | 
| -agentport | Protected server port number. | 
| -volumes | List of volumes to protect. Values must be enclosed in double quotes and separated by a space. Do not use trailing slashes in volume names. For example, "c:" or "d:". | 
 
Example:
Put volumes of a server under protection: 
>Start-Protect -repository "Repository 1" -agentname 10.10.9.120 -agentusername administrator -agentpassword 12345 -agentport 5002 -volumes "c:" "d:"