NetBackup 5200 2.0 Upgrade

  • Modified Date:
  • Article ID:000013590


  NetBackup 5200 2.0 README                                        August 12, 2011

This software update provides fixes for the NetBackup 5200 appliance series.
For additional information about new features, product fixes and enhancements,
known issues, and the current release content that are included in this
release update, refer to the following TechNote on the Symantec Support Web
Note that the above link is for the Upgrade to 2.0 from a previous version (,,, or 1.2).
For information on the full version (non-upgrade), visit this link:
















 -- NetBackup 5200 Appliance software version, or 1.2

    must be installed on a NetBackup 5200 media server appliance before you

    install this software release update.


 -- If the appliance is used in a Media Server Role, this upgrade requires a or higher Master Server.
    If using a previous version of the master serve,r please upgrade it to or higher before proceeding with this upgrade.


 -- It is recommended that the upgrade is run on the appliance console and

    should not be interrupted during the upgrade process.


 -- Before you begin this procedure, ensure that there are no backup jobs

    currently running or are scheduled to run during the process.


 -- As part of installing this release update, all NetBackup services are

    shutdown and restarted.


 -- Please make sure that the Netbackup Master server is UP and the NetBackup 

    processes are UP and Running on both the Master Server and Media Server.








Steps to install the 2.0 software update on the NetBackup 5200 Appliance:



1.  You should perform this procedure from a computer that is connected to the

    appliance as well as to the Internet. This ensures that you can download the

    release update from the Symantec Support Web site to the appliance.


2.  Open an SSH session and log on to the appliance as an administrator.


3.  Enter the following command to open the NFS and the CIFS shares:


       Main_Menu > Support > Software > Share Open


4.  Map or mount the appropriate appliance NFS or CIFS share directory using the

    steps below:  


       - UNIX: “mkdir –p /mount/<appliance-name>”

      “mount   <appliance-name>:/inst/patch/incoming   /mount/<appliance-name>”


       - Windows:  Map the network drive "\\<appliance-name>\incoming patches" on your computer.


    NOTE: On Windows systems, you are prompted to provide the user name,

          "admin", and its corresponding password.

    NOTE: When upgrading from 1.2 to 2.0,if you have an issue with login 

          using the admin credentials,please login to the appliance and reset 

          the password(it can be same as the original password).


5.  Download and Unzip or untar the release update from the Symantec Support

    site.The following URLindicates the download location for the 

    NetBackup 5200 release updates.


    For this release the release update rpm file name is split into multiple 

    files with the following filenames:







6.   Join these files using the command below:



     copy /b "SYMC_NB5200_update-"+"SYMC_NB5200_


     +"SYMC_NB5200_update-" "SYMC_NB5200_update-"



     cat "SYMC_NB5200_update-" "SYMC_NB5200_update-" "SYMC_NB5200_update-" 

     "SYMC_NB5200_update-" > "SYMC_NB5200_update-"


7.   Untar or unzip the file above and compute the md5 value and file size for 

     SYMC_NB5200_update- and verify that it matches the values below


     MD5 :5531b898b1b1e6443d10ea7ebd062ef1

     file size: 6.6 GB (7040293426 bytes)


8.  Copy this update rpm to the mounted share.


    NOTE: You should only copy the release update rpm and not the zip file.

    NOTE: During the copy process do not run any commands on the appliance.

          Doing so might cause the update install to fail.    


9.  Unmap or unmount the shared directory after you have copied the update rpm

    into the mounted share.


10.  Enter the following command to close the NFS and the CIFS shares:


      Main_Menu > Support > Software > Share Close


    Once the release update is located on the share directory, and you run

    the Share Close command, the update is moved from the share directory to

    its proper location. (You are not notified that this move has occurred.)


    NOTE:  If you run any of the following commands before you run the Share

           Close command, the update is moved from the share directory

           location to its proper location. Make sure that you have run the

           Share Close command to make sure that you close the NFS and the

           CIFS shares.


           -  List Version

           -  List Details All

           -  List Details Base

           -  Share Open

           -  Share Close


11.  Enter the following command to list the available release updates on

    the appliance.  Note the name of the uploaded release update.


       Main_Menu > Support > Software > List Available


12. Switch to the appliance console and enter the following command to install

    the release update. Use the name of the release update rpm in Step 8.


       Main_Menu > Support > Software > Install <patch_name>


    Where patch_name is the name of the release update to install. You must

    make sure that the name you enter matches the update name that you

    uploaded on the appliance.


13.The appliance reboots after the installation completes. You can use the command 


        Main_Menu > Manage > Software > List Version 


    and check that the appliance version is 2.0


14.After the reboot, the appliance will run a self diagnosis test after detecting 

   the disk pools are back online.Please refer to the results in

   /log/self_test__<date>.txt for the results of this self test.









 -- There is no rollback to the previous version of the appliance once the 

    upgrade is complete(current appliance version is 2.0).





Terms of use for this information are found in Legal Notices.



Did this article answer your question or resolve your issue?


Did this article save you the trouble of contacting technical support?


How can we make this article more helpful?

Email Address (Optional)