The forceoptimizationjob
command lets you perform optimize a repository on demand.
The usage for the command is as follows:
/forceoptimizationjob -repository [repository name] | -all -core [host name] -user [user name] -password [password]
The following table describes the options available for the forceoptimizationjob
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. |
-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. |
Force a repository optimization job:
>cmdutil /forceoptimizationjob -repository "Repository 1" -core 10.10.10.10 -user administrator -password 23WE@#$sdd
Use the forcereplication
command to force a one-time transfer of replicated data from the source core to the target core. You can replicate one specific protected server or replicate all protected servers. The protected servers must be already configured for replication.
The usage for the command is as follows:
/[forcereplication |frep] -core [host name] -user [user name] -password [password] -targetcore [host name] -all | -protectedserver [name | IP address]
The following table describes the options available for the forcereplication
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 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 |
-targetcore |
Host name of the target core against which replication should be forced. |
-protectedserver |
The protected machine you want to replicate. |
-all |
Force replication for all machines being replicated to the target core. |
Force replication for a protected server on a specific target core:
>cmdutil /forcereplication -target core 10.10.10.10 -protectedserver 10.20.30.40
Use the forcerollup
command to force the rollup of recovery points on a protected machine.
The usage for the command is as follows:
/[forcerollup | fro] -core [host name] -user [user name] -password [password] -protectedserver [name | IP address]
The following table describes the options available for the forcerollup
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 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 |
-protectedserver |
Optional. Protected machine against which to perform rollup. |
Force rollup for agent 10.10.10.1 on the Core:
>cmdutil /forcerollup -core 10.10.10.10 - user administrator -password 23WE@#$sdd -protectedserver 10.10.10.1
The forcescheduledarchive
command lets you force an archive to occur outside of its regularly scheduled time.
The usage for the command is as follows:
/forcescheduledarchive -core [host name] -user [user name] -password [password] -all -ids [id | id1 id2]
The following table describes the options available for the forcescheduledarchive
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. |
-all |
Use this option to force all scheduled archives. |
-ids |
The identifier (ID) or IDs separated by spaces of the scheduled archives that you want to force. |
Force all scheduled archives:
>cmdutil /forcescheduledarchive -all
Force one scheduled archive:
>cmdutil /forcescheduledarchive -ids 6c123c39-5058-4586-bd0c-7c375e72017b
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center