Step Upgrading to Veritas Netbackup 6

Step by Rakesh Khandelwal:

First check release notes to make sure H/W and O/S you are about to use is supported or not. Release Notes for UNIX and Windows (http://support.veritas.com/docs/279259 )
Symantec’s Upgrade Guide, Version “B” ( http://support.veritas.com/docs/285590 )

Assuming you have already checked databse consistency and resolved any known or preexisting consistency issues or catalog inconsistencies

Step 1 : Prepare, Upgrade and Patcvh the Master Server

  1. Backup the catalogs
  2. In a c clustered environment, take NetBackup offline.
  3. Deactivate all policies.
  4. On Solaris Only, uninstall the old version of NetBackup.
  5. Upgrade the software:
  6. Stop all services.
  7. run the installation.
  8. Apply the latest maintenance packs.
    NOTE : For Windows clustered environments, perform NetBackup upgrade installations from the system console, not from a Remote Terminal Services sessions.

Step 2: Populate the EMM database

  1. Ensure that the daemons or services and processes are running.
  2. Run nbpushdata -add on the ipgraded systems in the following order:
    a) The host that was the 5.x Global Device Database host
    b) All upgraded master servers
    c) All upgraded 5.x Volume Database hosts
  3. Restart the services/daemons.
  4. Run nbpushdata -modify_5x_hosts on all 6.0 master servers.


Step 3: Upgrade the NetBackup Remote Administration Console System and any addition components

1.Stop all services/daemons

2.Run the installation.

3.Apply the latest maintenace packs.

4.Restart the services/daemons.

5.Upgrade and add-on components.

6.Install the latest maintenance packs for the add-on components.


Step 4: Prepare, upgrade and Patch the Media servers

  1. On Solaris only, uinstall the old version of NetBackup.
  2. Upgrade the software:
    a) Stop all services/daemons.
    b) Run the instalation.
  3. Apply the latest maintenance packs.
  4. Restart the services/daemons.
  5. Populate the EMM database:
    nbpushdata -add

Step 5: Upgrade the clients

  1. Perform local or remote client upgrades.
  2. Install the latest maintenance packs.

Step 6: Complete and Test the upgrade

  1. Activate the policies
  2. Run test backup jobs.
  3. Backup the catalogs.

Additional Information from Dennis Strom:

here all the info I have on upgrading. I even included a link to this post since I really liked Rakesh’s post.

Other link:

Upgrading to Veritas NetBackup 6.0 on Supported Windows Platforms

VERITAS NetBackup 6.0 Release Notes, for UNIX, Windows, and Linux

Upgrading to Veritas NetBackup 6.0

VERITAS NetBackup 6.0

How to restore LTO1 or 2 on LTO 3 Drive

For many reason, I re-post again about this issue; How to restore LTO1 or 2 on LTO 3 Drive…

The procedure is as follows:

  1. Inject the tape into the ACS library, then perform a robot inventory of the ACS library.

  2. After the volume database is updated, the RobotType of the media will change to “ACS” and the tapes should be recognized as “hcart”.

  3. Run “vmchange -new_mt <new density> -m <media ID>” to change the density. <new density> should be “hcart3” for the LTO Gen-3 drive and <media ID> refers to the media barcode. An eg would be “vmchange -new_mt hcart3 -m dx0333”

  4. Run “vmquery -m <mediaID>” to check that the density have been updated to “hcart3” from “hcart”.

  5. Run “bpmedia -changeden -new <density> -ev <mediaID>”

  6. eg “bpmedia -changeden -new hcart3 -ev dx0333” Note: This command will take some time to complete. Please be patient and let it complete on it’s own. If terminated halfway, strange things may occur later.

  7. Run “bpmedialist -m <mediaID>” to check that the density have been updated.

  8. Run the normal restoration procedure to restore the data from the LTO Gen1 tapes using the ACS library.

  9. Once, we have completed the restoration, the tape should be ejected from the ACS library to prevent it from being used for future backups. If necessary, will need to execute the commands in Step 3 and 5 to change the density back to “hcart”.