Forum Discussion

stwali005's avatar
stwali005
Level 4
10 years ago

Upgrading Windows Server

Hi All,

I have our old backup environment - running Netbackup 6.5.5, on a windows 2003 server. Due to an EOL project, this server will need to be decommissioned soon. When we require a restore from tape - between 2007 and 2013, we use this server and library to read the LTO4 tapes, works fine.

 

Currently we have a windows 2008 server, with 7.5 (about to be 7.6) that we use for current backups and restores using LTO5s.

 

My question is - how do i get rid of the old environment?

Is it best to build a windows 2008 server, name it exactly as the old server and install 6.5.5 on it again - which i believe is not supported, that way it is like the old backup environment has never changed - just the hardware and OS upgraded?

Is there some way to import the old catalog into the new system - so we can read the old tapes easily and run the restore.

Or do i have to run an import of the tapes everytime there is a restore request? And say there is 40 tapes for a month - how do you know which tape to import as importing all 40 tapes will take a very long time?

Many thanks for some thoughts on this.

 

Backup and Recovery
Best Practice
NetBackup
Restore
Uninstall
Upgrade
Windows Server (2003-2008)
  • Marianne's avatar
    Marianne
    10 years ago

    Other than importing all tapes, the only other solution is to get a Symantec Consulting Partner to merge the 2 environments.

    How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.
    http://www.symantec.com/docs/TECH31385

    PS:
    If you have a VM or Hyper-V environment, you may want to consider virtualizing the old master server, using same hostname as 6.5.5 master, just without devices.
    This will enable you to browse for backups, preview required media, followed by import of relevant media on media server in new environment.

5 Replies

Sort By
  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Other than importing all tapes, the only other solution is to get a Symantec Consulting Partner to merge the 2 environments.

    How to migrate the NetBackup catalog information from one platform to another (UNIX to Windows or vice versa), rename a Master Server, cluster an existing Master Server, or merge multiple NetBackup domains.
    http://www.symantec.com/docs/TECH31385

    PS:
    If you have a VM or Hyper-V environment, you may want to consider virtualizing the old master server, using same hostname as 6.5.5 master, just without devices.
    This will enable you to browse for backups, preview required media, followed by import of relevant media on media server in new environment.

  • stwali005's avatar
    stwali005
    Level 4
    10 years ago

    Hi Marianne,

     

    We do have a VM environment so will speak to one of the specialists about Virtualizing the old master server. Will reply with how i get on and mark as solution when completed. Thanks for your assistance again.

  • stwali005's avatar
    stwali005
    Level 4
    10 years ago

    Hi Marianne,

     

    Our old master server was called LN1XXXXX

    To put it into a Virtual - to comply with naming conventions to be in the correct patching cycle with SCCM etc - we have to call it LN1VXXXXX (with a V prefixed to the name)

    How does Netbackup identify the host name and is there anything in the registry that we can change so it seems as if the name is actually the same as the old physical server?

     

    Many thanks

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    NBU master hostname cannot be changed. 

    You will have to make an exception in this case.

    Only a Symantec Consulting Partner can change a master server hostname.

  • NathanNieman's avatar
    NathanNieman
    Level 6
    10 years ago

    call S.C.P.

     

    when we moved to a new server I named it the same.  Installed the same version of the old.  Did a full catalog on the old etc etc, and then imported everything into the new.  

     

    We did it by the book but still had issues.  So glad SCP was on the phone..  

     

    Once we get everything setup correct then we upgraded to the newest.