Veritas NetBackup™ Upgrade Guide

Last Published:
Product(s): NetBackup (9.0)
  1. Introduction
    1.  
      About the NetBackup 9.0 Upgrade Guide
    2.  
      Available NetBackup upgrade methods
    3. About changes in NetBackup 9.0
      1.  
        Java GUI and JRE installation optional for some computers
      2.  
        Logging directory permissions require reset on rollback
      3.  
        Upgrades from NetBackup 7.6.0.4 and earlier are not supported
      4.  
        External certificate authority certificates supported in NetBackup 8.2 and later
    4.  
      About Veritas Usage Insights
    5.  
      Best practices for Veritas Usage Insights
  2. Planning for an upgrade
    1. General upgrade planning information
      1.  
        About planning a NetBackup 9.0 upgrade
      2.  
        How to plan for an upgrade to NetBackup 9.0
      3.  
        Known catalog backup limitation
      4.  
        About security certificates for NetBackup hosts
      5.  
        About automatic file changes from an upgrade
    2. About upgrade tools
      1.  
        About Veritas Services and Operations Readiness Tools
      2.  
        Recommended SORT procedures for upgrades
      3.  
        Recommended SORT procedures for new installations
      4.  
        About the NetBackup preinstall checker
    3. Upgrade operational notes and limitations
      1.  
        Creating the user account to support the NetBackup web server
      2.  
        About NetBackup 9.0 support for Fibre Transport Media Server with RHEL 7.5
      3.  
        MSDP changes in NetBackup 8.1
      4.  
        Potential required changes for NetApp clusters
      5.  
        Errors when Bare Metal Restore information is replicated using Auto Image Replication
      6.  
        Upgrade issue with pre-8.1 clients and 8.1 or later media servers
  3. Master server upgrade
    1.  
      About master server upgrades
    2.  
      Preinstall procedure for upgrading to NetBackup 9.0
    3.  
      Performing local, remote, or clustered server upgrades on Windows systems
    4.  
      Performing silent upgrades on Windows systems
    5.  
      Upgrading UNIX and Linux server software to NetBackup 9.0
    6.  
      Post-install procedure for upgrading to NetBackup 9.0
    7.  
      About NetBackup startup and shutdown scripts
    8.  
      Completing your system update after an upgrade
  4. Media server upgrade
    1.  
      Upgrading NetBackup media servers to NetBackup 9.0
    2.  
      Silently upgrading NetBackup media server software on UNIX and Linux
  5. MSDP upgrade for NetBackup
    1.  
      MSDP upgrade considerations for NetBackup 8.1
    2.  
      About MSDP rolling data conversion
    3.  
      About MSDP fingerprinting algorithm changes
  6. Client upgrade
    1.  
      About client upgrades
    2.  
      Upgrading UNIX and Linux clients with the NetBackup upgrade script
    3.  
      Upgrade of the UNIX and Linux client binaries with native installers
  7. NetBackup Deployment Management with VxUpdate
    1.  
      About VxUpdate
    2.  
      Commands used in VxUpdate
    3.  
      Repository management
    4.  
      Deployment policy management
    5.  
      Manually initiating upgrades from the master server using VxUpdate
    6.  
      Manually initiating upgrades from the media server or client using VxUpdate
    7.  
      Deployment job status
  8. Appendix A. Reference
    1.  
      NetBackup master server web server user and group creation
    2.  
      Generate a certificate on the inactive nodes of a clustered master server
    3.  
      About the NetBackup Java Runtime Environment
    4.  
      Add or Remove Java GUI and JRE after upgrade
    5.  
      About the NetBackup web user interface
    6.  
      About the NetBackup answer file
    7.  
      Persistent Java Virtual Machine options
    8.  
      About RBAC bootstrapping
    9.  
      About NetBackup software availability
    10.  
      Additional post-upgrade steps for NetApp clusters
    11.  
      Using NetApp disk arrays with Replication Director
    12.  
      About compatibility between NetBackup versions
    13.  
      Upgrade requirements for UNIX and Linux
    14.  
      Installation and upgrade requirements for Windows and Windows clusters
    15.  
      Requirements for Windows cluster installations and upgrades
    16.  
      Removing a clustered media server by migrating all data to a new media server
    17.  
      Disabling the connection between your OpsCenter server and your NetBackup Master Server
    18.  
      Post upgrade procedures for Amazon cloud storage servers
    19.  
      Upgrading clients after servers are upgraded
  9.  
    Index

Deployment policy management

Use the procedures that are shown to create, modify, and delete your deployment policies.

Creating a deployment policy

Note:

You must add packages to the VxUpdate repository before you can create a working deployment policy. You can create deployment policies without packages in the repository, but those policies fail to run successfully. More information about the management of the VxUpdate repository is available.

See Repository management.

  1. In the NetBackup Administration Console, in the left pane, select Deployment Management > Deployment Policies.
  2. From the Actions menu, select New Deployment Policy.
  3. Enter a unique name for the new policy in the Add a New Deployment Policy dialog box.
  4. Click OK.
  5. Specify the information that is shown on the Attributes tab in the Change Deployment Policy window:
    • Package: Select the package that you want deployed from the drop-down menu.

      Note:

      Specifying a package that supports external certificate authority certificates presents you with an additional tab titled Security. That tab is covered later in this procedure.

    • Media server: Specify the media server from drop-down. The media server that is specified is used to connect and transfer files to the NetBackup hosts that are included in the policy. The media server also caches the files from the NetBackup repository. The media server must be version NetBackup 8.1.2 or later. Since the repository resides on the master server, the master server is the default value for the media server field.

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

    • Java GUI and JRE: Specify if you want the Java GUI and the JRE upgraded on the target systems. The three options include:

      • INCLUDE: Install or upgrade the Java GUI and JRE components on the specified computers.

      • EXCLUDE: Exclude the Java GUI and JRE components from the specified computer. Any preexisting NetBackup Java GUI and JRE packages are removed.

      • MATCH: Preserve the current state of the Java GUI and JRE components. The components are upgraded if they are present on the pre-upgraded system. The components are not installed if they are not present on the pre-upgraded system.

    • (Conditional): Select the Limit simultaneous jobs option and specify a value for jobs to limit the total number of concurrent jobs that can run at a time. The minimum value is 1 and the maximum value is 999.

      If the check box is selected, the default value is 3. If you do not select the check box, no limit is enforced for the simultaneous upgrade jobs.

      You can set unlimited simultaneous upgrade jobs through command line interface by setting the value as 0.

    • Select hosts: Select hosts from the Available hosts list and select Add to add hosts to the deployment policy. The list is generated from hosts in the host database and backup policies. Once you select Add, the hosts are shown under Selected hosts.

      Deployment policies can contain either media servers or clients but not both. When you select the package you want installed, the list of available hosts is filtered to media servers or clients.

      Note:

      To upgrade a 7.7.x or 8.0 media server, the media server must be in a backup policy. The policy does not need to be active and you do not need to run the policy. Once the media server is upgraded to post NetBackup 8.1 version, you can remove the policy. The policy only needs to have the media server in the client list. You do not need to specify a file list, schedule, or any other policy attributes.

      If the media server is not in a policy, the operating system for the media server is listed as Unknown. A tool tip suggests this issue is a missing package. Package for the selected host's operating system is missing. Add the required missing packages to the repository using the nbrepo command line. While it may be true the package is not in the repository, you should also add the media server to a backup policy. If the tool tip persists after the media server is added to a policy, you probably need to add the required package.

  6. Select the Schedules tab in the Change Deployment Policy window.

    You can see a summary of all schedules within that policy.

  7. Select New.
  8. Specify the information that is shown in the Add Deployment Schedule window.
    • Name: Enter a name for the new schedule.

    • Type: Specify the type of schedule you want created.

      Schedule types:

      • Precheck

        Performs the various precheck operations, including confirming there is sufficient space on the client for the update. The precheck schedule type does not exist for EEB packages.

      • 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 the stage package operations. If you already performed the stage package operation, the install schedule does not move the package again.

      Note:

      Please be aware that adding multiple different schedule types to the same deployment schedule window has unpredictable results. VxUpdate has no defined behavior to determine which schedule type runs first. If a single deployment schedule window has precheck, stage, and install jobs, there is no way to specify the order in which they run. The precheck or the stage schedules can fail, but the install completes successfully. If you plan to use precheck, stage, and install schedules, it is recommended that you create separate schedules and separate windows for each.

    • Starts: Specify the date and time you want the policy to start in the text field or with the date and the time spinner. You can also click the calendar icon and specify a date and time in the resulting window. You can select a schedule by clicking and dragging over the three-month calendar that is provided at the bottom of the window.

    • Ends: Specify the date and time you want the policy to end as you specified the start time.

    • Duration: Optionally, you can specify a duration in days, hours, minutes, and seconds instead of an end time for the policy. The minimum value is 5 minutes and the maximum is 99 days.

    • Select Add/OK and the schedule is created. Select OK to save and create your policy.

  9. A Security tab appears when you select a deployment package that contains support for external certificate authorities.

    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 available.

    Note:

    If you specify this option and certificates are not available, your 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.

  10. 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.

  11. For both media servers and 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.

To change a deployment policy

  1. Right click on the deployment policy and select Change.
  2. Navigate through the deployment policy tabs and make any necessary changes to the policy.
  3. Select OK and the policy is updated.

Deleting a deployment policy

  1. Right click on the deployment policy and select Delete.
  2. Select OK.
  3. Confirm the deletion of the policy.