Veritas NetBackup™ Commands Reference Guide
- Introduction
- Appendix A. NetBackup Commands
Name
nbinstallcmd — used to create and launch deployment jobs
SYNOPSIS
-policy policy -schedule schedule {-hosts filename | -host_filelist client1, client2, clientN} [-master_server name]
-i -policy policy_name -schedule schedule_name [-master_server name]
-operation_type {precheck | stage | install} -package item... -media_server name [-limit_jobs max_concurrent_jobs] [-master_server name]
On UNIX systems, the directory path to this command is /usr/openv/netbackup/bin
On Windows systems, the directory path to this command is install_path\netbackup\bin
DESCRIPTION
Use the nbinstallcmd command to create and launch VxUpdate jobs. The command launches client update jobs. You can launch it from both the client and the master server. Jobs that you launch can be part of a policy, but a policy is not required to launch an update job. The options available for the command depend on the job launched. Jobs that are associated with policies have one set of options, non-policy related jobs have a second set of options. Review the command synopsis for details.
Logs for the nbinstallcmd command are located in the legacy logging directory. For UNIX and Linux, the logs are found in /usr/openv/netbackup/logs
. On Windows, the logs are in install_path\Veritas\NetBackup\logs
.
OPTIONS
- -host_filelist client1, client2, clientN
Used to specify multiple client names. The client names are separated with commas.
- -hosts filename
Used to specify a file name that contains the names of all the clients being updated. Each client name is on a separate line.
- -i
Forces the policy job to run immediately. If you do not specify this option, the policy is launched the next time there is an available schedule window in the specified policy. Use of the -i option prevents a scheduled start of same policy and schedule. This behavior prevents duplicate jobs.
- -limit_jobs max_concurrent_jobs
The maximum number of jobs that are allowed per client.
- -media_server name
The name of the media server with which that the client communicates. Files are cached to the specified media server. The repository resides on the master server. The files are cached to media server to prevent a communications overload on the master server.
- -master_server name
If the client has multiple master servers, the master_name specified is the one that contains the repository.
- -operation_type {precheck | stage | install}
Specifies what sort of operation you want to start. Valid options are:
precheck: Performs the various precheck operations, including confirming there is sufficient space on the client for the update.
stage: Moves the update package to the client, but does not install it. Also performs the precheck operation.
install: Installs the specified package. Also performs the precheck and stage operations. If you already performed the stage operation, the install command does not move the package again.
- -package item
The name of the package you want installed.
- -policy policy_name
The name of the deployment policy you want to start.
- -schedule schedule_name
The name of the schedule you want to start.
EXAMPLES
Example 1: Launches the sched-precheck schedule in the policy-deployment20 policy, and launches it immediately.
nbinstallcmd -policy policy-deployment20 -schedule sched-precheck -i
Example 2: Starts an installation of the 8.1.2 package from the media1 media server.
nbinstallcmd -operation_type install -package 8.1.2 -media_server media1
SEE ALSO
See nbrepo.