Example Backup Target Set Creation
3.4.16 nvsetmodify Modifies a set.
Syntax
nvsetmodify -setname <set name> -type <set type> - change <change description> [-parameters <parameter file>] [-assign <assignment character>] [-delimit <delimiter character>] [-version]
Options
-setname – Name of the set to be modified. -type – Type of the set to be modified. It can be:
BS – Backup Selections Set BO – Backup Options Set S – Schedule Set
BT – Backup Target Options Set AB – Backup Advanced Options Set RS – Restore Selections Set
AR – Restore Advanced Options Set
-change <change description> – Changes to be made to the set. More than one change option can be specified, if required. The <change description> variable is formatted as follows:
<item>[:<field>][:<old value>]=<new value>
The “<item>” variable refers to the name of the item in the set to be modified. The following values can be used as an <item> variable. For examples using “-change” option, refer to Examples on page 81.
Tree – Changes items in the selection tree (Backup Selection Sets and Restore Selection Sets only). Following are the values that can be specified as the “<field>” variable when Tree is set as the “<item>”. path – Specify the path that is to be changed in “<old value>” variable
and the new path to the data in “<new value>”. Alternatively, the <old value> can contain the name of the NVBU Client or plug-in, and the <new value> can be the new NVBU Client or plug-in.
Note: If no “<new value>” variable is specified, anything that is currently selected/ omitted in the “<old value>” will be considered de-selected by NVBU when this command is executed.
rename – Adds a new rename/relocation command to a restore selection set or modify an existing one. The “<old value>” variable refers to the full path to the item. The “<new value>” variable refers to the new name or the new path for the selected item.
Adding a New Rename/Relocation Command to an Existing Restore Selection Set – Specify the current rename/relocation target’s information as the “<old value>” variable and the new rename/relocation information as the “<new value>” variable. Modifying an Existing Rename/Relocation Command in an
Existing Restore Selection Set – Specify the exact rename/ relocation command syntax originally created as the “<old value>”
variable and the new rename/relocation syntax as the “<new value>” variable.
Note: For complete details on the proper syntax used for the Rename command, refer to the description of this option offered on page 70.
info – Modifies the plug-in information object attached to a node in the selection tree. The value specified as the “<old value>” variable shouldbe the full path (from the plug-in root node) to the required item. The value input as the “<new value>” variable should be the new values for the plug-in information object, separated by colons (“:”). If any field is to remain unchanged, no value should be given. Use a double colon in its place “::”.
<Node Name> or <ID> – Name of the root node marked for inclusion in the restore/backup job. This may either be the “node name” as recognized by the CLI or a numeric “ID” assigned to the node by NVBU. Both of these values are grouped under the “[Tree Nodes]” section in the “nvsetmodify.cfg” configuration file. For details, refer to The “nvsetmodify.cfg” File on page 17. Specify the node name or ID that applies to the existing node in place of the “<old value>” variable; and specify the new value for the new root node as the “<new value>” variable to modify the set. Note the following:
The actual “node name” should be specified as the “<old value>” variable when the selection tree for the target NVBU Client contains multiple nodes of the given type rather than the “ID” value.
If no “<new value>” variable is set, anything that is currently selected/omitted in the <Node Name> or <ID> named as the “<old value>” will be considered de-selected by NVBU.
Options – Adds or modifies the restore options if the plug-in provides any. The “Tag ID” of the window item to be set is required. This can either be the restore option name as recognized by the CLI or a numeric value assigned to the option by NVBU. Both of these values are grouped under the “[Plugin Options]” section in the “nvsetmodify.cfg” configuration file. For details, refer to The “nvsetmodify.cfg” File on page 17. Specify either of these values in place of the “<field>” variable. “<Value>” can be set to “True” to enable or “False” to disable the option.
Important: This option must be followed by a colon (“:”) without any spaces before the Tag ID (for example, “Options:<Tag ID>=True/False”).
Target – Changes items in the target tree (Restore Selection Sets only). The <field> variable is used to specify the type to be changed. The only permitted value is a valid NVBU Client name. The <new value> specifies the new target Client.
-parameters – Reads options and their arguments from a given parameter file so that you do not need to input them each time the command is run. You can create this file using any standard text editor. Enter one option (with its value) per line and omit “-” before the option. Use spaces or tabs to separate the option and values. For comments, begin the line with a # character. Such lines will be ignored.
Following is an example of a parameter file named example.txt: # nvsetmodify example file
setname BackSet1 type BS
This file can be used with the -parameters option as follows: ./nvjobmodify -parameters example.txt
-assign – Use this option to change the character used for assignment. It must be used if values contain the default assignment character “=”. -delimit – Use this option to change the character used as the delimiter. It
must be used if values contain the default delimiter “:”. -version – Displays the build date of the NVBU distribution.
Examples
A Restore Selection Set entitled “RestoreSet1” was created for a Windows- based Client to restore several directories, including the contents of the directory “C:\mail” to the target system “WinClient1”. Use the following syntax to restore the backup to Client “WinClient2”. In addition, a option is included to overwrite newer files, and restore the data to “C:\MyMail” instead of C:\mail on the new Client. Lastly, the leading character in the change description for the data relocation is the “@” character. This is done so that the “:” character may be used in the relocation path information.
nvsetmodify -setname BackSet2 -type RS -change target:client:WinClient1=WinClient2 -change options:nvfs_opt_overnew=true
-change @tree@path@c:\mail=c:\MyMail
3.4.17 nvtrigger
Triggers a job that has already been defined in the NVBU Console and saved as a triggered job using the Triggered option of the Schedule tab. For details, refer to the Quest NetVault Backup Administrator’s Guide. This command is located in the “...\bin” directory.
Syntax
Options
-server – Name of the NVBU Server that will administer the job. If the job is to be administered by a remote NVBU Server, this option must be used to name that specific server. If the local instance of the server is to be used to
administer the job, this option can be left out of the syntax. The server name is case sensitive.
-wait – Add this option to tell NVBU to wait until this task has completed before moving forward.
-verbose – Displays additional information when the job is initiated and finishes. The details displayed when the job is initiated include Job ID, Instance ID, Job Title, and Start Time. When the job completes, the finish time is displayed.
-killonexit – Use this option with -wait to abort a job by terminating the trigger execution.
<trigger name> – Name of the trigger to be used. This must be the last parameter when the tool is invoked as shown in the example below: nvtrigger -server <server name> -wait -verbose -killonexit <triggername>)
Notes
The nvtrigger command will return a numerical value after its associated job has completed/ended. This number indicates the status of the job performed. The return values and the corresponding job status are listed below:
0 – Backup Completed 1 – Backup Failed
2 – Backup Completed with Warnings 3 – Backup Aborted
Without the -wait option, the nvtrigger command will support multiple jobs. With this option, the nvtrigger command can only be used to trigger a single job. This limitation also applies to -wait -killonexit options. As a result, you cannot use this option for policy jobs that contains multiple job definitions. If the -wait option is included in a script, control is returned to the script after
the triggered job completes its execution. If there is no -wait option, then control is returned immediately back to the script even if the triggered job is still executing.