To manually initiate an upgrade of all media servers or clients in a policy from the administration console

1. In the NetBackup Administration Console, navigate to Deployment Management > Deployment Policies.
2. In the middle pane, expand the master server, and select the policy you want to run.
3. Right-click on the policy you want to start, and select Manual Deployment.
4. Alternatively, after selecting the policy you want to run, you can select Actions > Manual Deployment.

To manually initiate an upgrade of a specific host in a policy from the administration console

1. Select NetBackup Management > Host Properties > Media Servers or NetBackup Management > Host Properties > Clients in the NetBackup Administrative Console.
2. Right click on the host you want to upgrade in the right pane.
3. Select Upgrade Host.
4. In the Upgrade Host dialog:

   • Select the package you want to use from the Package drop-down.

     Note:

     Specifying a package that supports external certificate authority certificates presents you with an additional button titled Configure. That button is covered in the next step.

   • Specify the type of schedule you want to run from the Type drop-down.

   • Select the media server you want to use from the Media server drop-down.

     When you upgrade media servers, the Media server drop-down is automatically set to the master server and cannot be changed.

   • Confirm that the host you want upgraded is listed under Selected hosts.

5. (Conditional) If present, click on the Configure button to configure external certificate authority information.

   By default, the Use existing certificates when possible option is selected. This option instructs NetBackup to use the existing NetBackup CA or external CA certificates, if certificates available.

   Note:

   If you specify this option and certificates are not available, the upgrade fails.

   Deselecting the Use existing certificates when possible option lets you specify the location for external certificate authority information for both UNIX and Linux computers and Windows computers.

6. Windows clients have Use Windows certificate store selected by default.

   You must enter the certificate location as Certificate Store Name\Issuer Distinguished Name\Subject Distinguished Name.

   Note:

   You can use the $hostname variable for any of the names in the certificate store specification. The $hostname variable evaluates at run time to the name of the local host. This option provides flexibility when you push NetBackup software to a large number of clients.

   Alternatively, you can specify a comma-separated list of Windows certificate locations. For example, you can specify: MyCertStore\IssuerName1\SubjectName, MyCertStore\IssuerName2\SubjectName2, MyCertStore4\IssuerName1\SubjectName5

   Then select the Certificate Revocation List (CRL) option from the radio buttons shown:

   • Do not use a CRL. No additional information is required.

   • Use the CRL defined in the certificate. No additional information is required.

   • Use the CRL at the following path: You are prompted to provide a path to the CRL.

7. For both UNIX and Linux clients and Windows clients that select the From certificate file path (for file-based certificates) option, specify the information as shown:

   • Certificate file: This field requires you to provide the path to the certificate file and the certificate file name.

   • Trust store location: This field requires you to provide the path to the trust store and the trust store file name.

   • Private key path: This field requires you to provide the path to the private key file and the private key file name.

   • Passphrase file: This field requires you to provide the path of the passphrase file and the passphrase file name. This field is optional.

   • Then specify the correct CRL option for your environment:

     • Do not use a CRL. No additional information is required.

     • Use the CRL defined in the certificate. No additional information is required.

     • Use the CRL at the following path: You are prompted to provide a path to the CRL.

8. Select OK to launch the upgrade.

   Note:

   You can also launch a client upgrade job from the Policies section of the NetBackup Administrative Console. Select NetBackup Management > Policies in the NetBackup Administrative Console. In the middle pane, select Clients. Then right-click on the client you want to upgrade in the right pane and select Upgrade Host. Then follow the procedure shown. This procedure is only applicable to clients, not media servers.

To manually initiate an upgrade from the command line for all media servers or clients in a policy

Use this procedure to manually start an upgrade for all media servers or clients in a policy.

1. Open a command prompt and navigate to the directory shown:

   Windows: install_path\netbackup\bin

   UNIX or Linux: /usr/openv/netbackup/bin

2. Use the nbinstallcmd command as shown to launch a policy:

   nbinstallcmd -i -policy policy_name -schedule schedule [-master_server master]

   Where policy_name is the name of the deployment policy, schedule is the name of the schedule, and master is the name of the master server.

   Be aware that use of the -i option prevents a scheduled start of same policy and schedule. This behavior prevents duplicate jobs.

To manually initiate an upgrade from the command line for selected hosts in a policy

Use this procedure to manually start an upgrade for selected hosts in a policy.

1. Open a command prompt and navigate to the directory shown:

   Windows: install_path\netbackup\bin

   UNIX or Linux: /usr/openv/netbackup/bin

2. Use the nbinstallcmd command as shown:

   nbinstallcmd -policy policy_name -schedule schedule {-hosts filename|-host_filelist client1, client2, clientN}

   Where:

   • policy_name is the name of the deployment policy

   • schedule is the name of the schedule

   • filename is the name of a file that contains a list of media servers or clients to upgrade.

   • client1, client2, clientN is a list of media servers or clients to upgrade.