Forum Discussion

Jeff_Talamini's avatar
Jeff_Talamini
Level 3
16 years ago
Solved

Need to rebuild server

We have a NetBackup 6.0 MP7 server with Windows 2003R2 SP2 which needs rebuilding. At this time the server only backups 4 remote servers to disk which is separate from the OS partition so our configuration is very basic with about a dozen policies. We are backing up the NetBackup database each night so would this be sufficient for when we reinstall Windows and NetBackup so that we won’t have to redo the configurations and policies?

Thanks for any help.

Jeff
7.1.x and Earlier
Backup and Recovery
Configuring
Installing
NetBackup
Tip-How to
  • John_Stockard's avatar
    John_Stockard
    16 years ago
    Yes, the catalog backup will preserve your NetBackup policies and catalog information, but you should keep the following things in mind when rebuilding the server:

    1. The catalog backup doesn't backup any of the NetBackup helper scripts (nbmail.cmd, bpstart_notify.cmd, etc.), nor does it backup any touch-files that you may have created to improve performance (such as the files to adjust the size and number of memory buffers).  If you have edited any of the scripts or created any of the touch-files, make sure you back them up manually (i.e. copy them to a USB flash drive) before you rebuild the server.

    2. Don't change the hostname or IP address of your NetBackup server when you rebuild it.  Very ugly things happen if the hostname of the master server changes (i.e., you may not be able to restore from backup images made prior to the name change).

    3. Make sure that the DSU (backup-to-disk) directory stays on the same drive letter and directory path after the rebuild.
  • John_Stockard's avatar
    John_Stockard
    Level 5
    16 years ago
    Yes, the catalog backup will preserve your NetBackup policies and catalog information, but you should keep the following things in mind when rebuilding the server:

    1. The catalog backup doesn't backup any of the NetBackup helper scripts (nbmail.cmd, bpstart_notify.cmd, etc.), nor does it backup any touch-files that you may have created to improve performance (such as the files to adjust the size and number of memory buffers).  If you have edited any of the scripts or created any of the touch-files, make sure you back them up manually (i.e. copy them to a USB flash drive) before you rebuild the server.

    2. Don't change the hostname or IP address of your NetBackup server when you rebuild it.  Very ugly things happen if the hostname of the master server changes (i.e., you may not be able to restore from backup images made prior to the name change).

    3. Make sure that the DSU (backup-to-disk) directory stays on the same drive letter and directory path after the rebuild.
  • stu1's avatar
    stu1
    Level 4
    16 years ago
    Are you rebuilding windows 2003 too?  or just NetBackup?

    Before anything else, make a catalog backup... this is the worst case scenario method to recover from any disaster.

    NOTE: this is a DO-AT-OWN-RISK tip, and very very HIGH level.  its meant to give you an idea on shortcuts to rebuilding the master server, if you REALLY need to.  SYMANTEC does not endorse nor support this method at all.

    Get another HD volume and copy VERITAS directory from 1 drive to another.
    If you relocate the various client images folder via ALTPATH file, protect those too.
    The HD you copy too should not be the HD where windows 2003 exist.

    Now that you have atleast TWO backups in form of a catalog, and a filesystem copy.

    Rebuild 2003.  Give it the same IP and Hostname.  If NBU was install to a different drive than system, rename that directory.  This is your THIRD copy.

    re-install NBU to that drive.  Make sure you have sufficient space.  Ensure NBU is configured to use the same hostname as the master server and EMM server as before.
    Once install finish, test starting NBU and run nbemmcmd -listhost to be sure emm is operational. 

    NOW apply the same patch level as before.  DO NOT PUT AN OLDER PATCH, OR A NEWER PATCH.

    Retest EMM again with nbemmcmd -listhost.  If it all works, shutdown.  Copy the EMMDB from your THIRD copy location\VERITAS\netbackupdb\data\*.db and *.log; restart NBU and check if EMM still works, and contains your previous info.  Do nbemmcmd -listmedia -allrecords, and see if it could see your tapes.

    If, so the hardest part is over.  Shutdown immediately incase NBU start de-assigning volumes, (because your images are not moved over).

    Now from your THIRD copy again, MOVE veritas.3rdcopy\netbackup\db to your NEW veritas\netbackup\ area.  Re-copy your EMM database just to be sure (chances are NBU already went and deassign tapes).  Restart NBU again, and check EMM first.  Then check images: bpimmedia -U.  If all looks good, go investigate other things you need to migrate over from the THIRD backup copy to the new one.

    If NBU wont start correctly, you need to do disaster recovery.  WHICH WILL NOT WORK WELL if you did not re-install NBU application to the same drive letter and directory.  recovery will always recover to same as previous paths.