Forum Discussion

Matthew_J's avatar
Matthew_J
Level 4
8 years ago

Hardware refresh for combined master/media server

We are getting ready to do a hardware refresh on our single combined master/media server. The old OS is server 2008 and the new OS is server 2012 R2. We are on 7.7.3. We utilize Exagrid disk storage appliances with their OST plugin. Our catalog backup is on the Exagrid devices, but on a standard CIFS share and NOT on an OST share.

I've found tech article TECH77447 that outlines procedure to do a catalog backup and restore using the DR file to hardware refresh a master server. My question is, is this all we need, or is there more to this process since we also have a media server role? Will this process move across our policies, disk pools, storage units, etc... or will we be left to manually recreate those?


We have the new machine loaded with the OS, updated with windows patches, and it has 7.7.3 same patch level installed to all the same directories as existing server. It is named the same as the old master/media server at this point. Our plan is to...


1. Shut down old backup server


2. Boot new, assign same IP to it and join it to domain with same domain acct as old one


3. Perform catalog recovery by pointing Netbackup to DR file and CIFS share with catalog backup.


4. Install Exagrid OST plugin


5. Test backups.


What I feel I'm missing is... steps between 3/4/5. I'm trying to figure out if we are going to need to reconfigure all of our storage units, disk pools, policies and such, or if the catalog recovery is going to include that information.


Can anyone offer any guidance here?

7.7
windows server 2012
  • Michael_G_Ander's avatar
    Michael_G_Ander
    Level 6
    8 years ago

    I would add

    6. Test restores

    Policies should be included in the catalog backup, some media server stuff like storage units might not be. Also check if any tuning you have done is kept. Like buffer sizes & numbers

    Don't know exagrid, but think the changing MSDP host in the deduplication admin guide would be a good starting point.

     

  • Marianne's avatar
    Marianne
    Level 6
    8 years ago

    I like the fact that you are using Basic Disk (CIFS) for catalog backups - certainly the easiest to restore from.

    All catalogs and configurations will be restored with catalog recovery.

    I would adjust steps as follows:

    1. Shut down old backup server

    2. Boot new, assign same IP to it and join it to domain with same domain acct as old one

    3. Install NBU to same path as original server - same NBU version and patch level (if applicable)

    4. Install Exagrid OST plugin 
        Test network comms between Exagrid and master (ping)
         Ensure NBU services are started as correct user (http://www.veritas.com/docs/000121409)

    5. Perform catalog recovery by pointing Netbackup to DR file and CIFS share with catalog backup.

    6. Restart NBU

    7. Confirm Storage Server and Disk Pool(s) are UP

    8. Test backups.

    8. Test restores

    • Matthew_J's avatar
      Matthew_J
      Level 4
      8 years ago

      We are right in the thick of this process and have run into a problem that is halting our progress.

      We've completed a full catalog backup, have shut off the services on the old server, and shut its network port.  We have NBU 7.7.3 on the new 2012 R2 server installed successfully to the exact same path as the old server, and have a disk attached to the new server with the same drive letter as the old server for the catalog.  

      We have run the catalog recovery wizard, and have pointed it to the DR file.  The catalog recovery wizard runs all the way through and restores the entire catalog, and then hangs at the end and never "finishes" so we can move forward.  In looking at the tail end of of the restore log file, we see this:

      17:36:42 (3.001) TAR - Z:\db\images\169.254.1.247\1412000000\catstore\RR_Datacenter_VMs_1412384791_FULL.f_imgUserGroupNames0
17:36:42 (3.001) TAR - Z:\db\images\169.254.1.247\1412000000\catstore\RR_Datacenter_VMs_1412384791_FULL.f_imgStrings0
17:36:43 (3.001) TAR - Z:\db\error\cbu_1496127600
17:36:43 (3.001) TAR - Z:\db\error\log_1495954800
17:36:43 (3.001) TAR - Z:\db\error\log_1496041200
17:36:43 (3.001) INF - TAR EXITING WITH STATUS = 0
17:36:43 (3.001) INF - TAR RESTORED 439219 OF 439219 FILES SUCCESSFULLY
17:36:43 (3.001) INF - TAR KEPT 0 EXISTING FILES
17:36:43 (3.001) INF - TAR PARTIALLY RESTORED 0 FILES
17:36:44 (3.001) Status of restore from copy 1 of image created 5/30/2017 8:28:57 AM = the requested operation was successfully completed

17:36:44 (3.xxx) INF - Status = the requested operation was successfully completed.

17:36:46 ERR - Failed to find last backup image record for client ccpudbck, client_type 7, with policy Netbackup_Catalog and sched_type 0 (227)

      The last line seems to be where it is hanging up.  Everything I can find online says that this could be due to a different install path on the new server vs old server.  We have double and triple checked and Netbackup is installed to the same path on the new server as the old server.  The catalog drive letter is the same.  

      Can anyone help here?  My colleague is on the phone with support right now working on a high severity case, because we absolutely have to have this cut over and working before the weekend.  If we can't figure this out, we need to revert back to our old server and start this process all over again next week.  Help!

       

      • quebek's avatar
        quebek
        Moderator
        8 years ago

        Hi

        Please run bpdbjobs to figure out the active job id, then run bpdbjobs -jobid XX -all_columns

        check in there what is not OK. You can do the same by running another JAVA GUI... I am hoping you did create all logs catalogs by running mklogdir script inside netbackup/logs - those would be needed to troubleshoot further...