EditHyperVServer
You can use the edithypervserver
command whenever you want to add or remove a Hyper-V server using agentless protection.
Usage
The usage for the command is as follows:
/edithypervserver -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] -add | -remove -virtualmachines [virtual machines collection | all]
Command Options
The following table describes the options available for the edithypervserver
command:
Table 22: EditHyperVServer 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 |
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. |
-protectedserver |
Use this option to specify Hyper-V objects for a specific protected machine. |
-add |
Use this option to add specific Hyper-V objects under protection. |
-remove |
Use this option to remove specific Hyper-V objects from protection. |
-virtualmachines |
Optional. This option lets you list the virtual machines that you want to protect. Separate the names by spaces and enclose the names of virtual machines in double quotes. |
Example:
Protect all of the virtual machines for a specific Hyper-V server:
>cmdutil /edithypervserver -protectedserver 10.10.8.150 -add -virtualmachines all
EditOracleDBVerifyNightlyJob
Use the command editoracledbverifynightlyjob
to enable or disable this nightly job for specific Oracle machines that are under protection.
Usage
The usage for the command is as follows:
/editoracledbverifynightlyjob -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] [-enable | -disable] [-global]
Command Options
The following table describes the options available for the editoracledbverifynightlyjob
command:
Table 23: EditOracleDBVerifyNightlyJob 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 |
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. |
-protectedserver |
Use this option to specify the protected machine for which you want to enable the Oracle DBVerify nightly job. |
-enable |
Use this option to enable the DBVerify nightly job for the specified protected machine. |
-disable |
Use this option to disable the DBVerify nightly job for the specified protected machine. |
-global |
Use this option to apply the specified setting as the default for this Core. |
-all |
This option applies the specified changes for every protected machine that has at least one Oracle instance installed. |
Example:
Enable the Oracle DBVerify nightly job for a protected server:
>cmdutil /editoracledbverifynightlyjob -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88 -enable
EditOracleLogTruncationNightlyJob
Use the command editoraclelogtruncationnightlyjob
to enable or disable this nightly job for specific Oracle machines that are under protection and to set the deletion policy and retention duration for the logs.
Usage
The usage for the command is as follows:
/editoraclelogtruncationnightlyjob -core [host name] -user [user name] -password [password] -protectedserver [name | IP address] [-enable | -disable] [-global] [-usedefault] -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 editoraclelogtruncationnightlyjob
command:
Table 24: EditOracleLogTruncationNightlyJob 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. |
-enable |
Use this option to enable log truncation for the specified protected machine. This is the default option and can be omitted. |
-disable |
Use this option to disable log truncation for the specified protected machine. |
-global |
Use this option to apply the specified setting as the default for this Core. |
-all |
This option applies the specified changes for every protected machine that has at least one Oracle instance installed. |
-usedefault |
Optional. Use this option to apply the default Core settings to the specified machine, which may also be set by using the -global option. |
-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 -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:
"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 -deletionpolicy option, a number of files value is required. |
Examples:
Enable the Oracle log truncation nightly job for a protected server:
>cmdutil /editoraclelogtruncationnightlyjob -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88 -enable
Enable the Oracle log truncation nightly job (when -enable is the default option) for a protected server and configure the deletion policy as "keepnewest" with the logs kept for 10 days:
>cmdutil /editoraclelogtruncationnightlyjob -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88 -deletionpolicy keepnewest -retentionduration 10 -retentionunit day
EnableOracleArchiveLogMode
Use the command enableoraclearchivelogmode
to enable or disable this mode for specific Oracle machines that are under protection.
Usage
The usage for the command is as follows:
/enableoraclearchivelogmode -core [host name] -user [user name] -password [password] -protectedserver [name | IP address]
Command Options
The following table describes the options available for the enableoraclearchivelogmode
command:
Table 25: EnableOracleArchiveLogMode 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 archive log mode. |
Example:
Enable the Oracle archive log mode for a protected server:
>cmdutil /enableoraclearchivelogmode -core 10.10.127.42 -user admin -password 676df#df -protectedserver 10.10.34.88