Forum Discussion

NBU2010's avatar
NBU2010
Level 6
10 years ago

Catalog Backup Shift

HI Forum,

Need to shift Catalog backup which is currently happending on local disk to be shifted to external SAN storage.

What all steps needs to be performed to successfully shift the same without hampering current production env.

NBU version is 7.6

 

Thanks in Advance.

  • You are now changing the picture completely.

    Your opening post said CATALOG BACKUP needs to change. This implies that a Disk Storage Unit needs to be moved or recreated.

    Now it seems you want to move entire NBU installation, right?

    In order to do this, you need a knowledgeable OS admin to help you with this.

    We cannot give you specific instructions/commands as this makes us responsible if a mistake is made.

    Steps:

    • Perform Catalog backup to external storage - tape preferably.
    • Stop NBU.
    • Mount SAN volume to temp mountpoint.
    • Copy everything in /opt/openv to new mountpoint (use a command such as tar or cpio to ensure permissions and ownership is correctly transfered with files and folders).
    • Rename openv folder.
    • Unmount SAN volume and then mount as /opt/openv.
    • Start NBU.
    • Perform tests to verify functionality. (e.g. restore from old backups and create and run small test policy)
    • If NOT okay - unmount /opt/openv and rename folder back to openv.
      DON'T carry on or do production backups that will change catalogs.
    • If all is good, delete renamed folder on local disk.
    • Add new SAN volume to /etc/vfstab to mount /opt/openv at boot time.
  • What type of Netbackup storage unit does the local disk consist off ?

    What storage unit type will the new SAN disk consist off ?

  • Simple..

    Create Storage unit in the SAN storage space...

    ( SAN storage space is should be mounted in master or media server as file system, and you need to create the basic disk storage unit )

    once you creat the storage unit , chage the newly created storage unit in the catalog policy attributes to move the next jobs to the storage unit.

  • It's a T5-2 solaris server disks.

    What if i need to move the whole /opt/openv/ to external storage.

  • You are now changing the picture completely.

    Your opening post said CATALOG BACKUP needs to change. This implies that a Disk Storage Unit needs to be moved or recreated.

    Now it seems you want to move entire NBU installation, right?

    In order to do this, you need a knowledgeable OS admin to help you with this.

    We cannot give you specific instructions/commands as this makes us responsible if a mistake is made.

    Steps:

    • Perform Catalog backup to external storage - tape preferably.
    • Stop NBU.
    • Mount SAN volume to temp mountpoint.
    • Copy everything in /opt/openv to new mountpoint (use a command such as tar or cpio to ensure permissions and ownership is correctly transfered with files and folders).
    • Rename openv folder.
    • Unmount SAN volume and then mount as /opt/openv.
    • Start NBU.
    • Perform tests to verify functionality. (e.g. restore from old backups and create and run small test policy)
    • If NOT okay - unmount /opt/openv and rename folder back to openv.
      DON'T carry on or do production backups that will change catalogs.
    • If all is good, delete renamed folder on local disk.
    • Add new SAN volume to /etc/vfstab to mount /opt/openv at boot time.
  • Have 1 query...if i do so as suggested then how about the restoration request for the earlier data which got backed up with reference to old CATALOG.Will it be able to find the earlier backup details.

    regards

     

  • Have 1 query...if i shift the catalog to diff location (From Local disk to SAN), then how about the restore if any comes it will refer to the catalog which was kept in local disk....???

    How to take care of the restore part after catalog location shift.

     

  • If you follow Marianne's advice then you will have, by that time, moved the catalog to new storage, but kept the path the same - i.e. to all intents and purposes the catalog appears to be in the same location - but you know that the it is actually on different storage.

    When doing a catalog recovery, then the catalog backup always needs to be restored to the same/original location from whence it came.  So, because it would be going back to the same path - you shouldn't have a problem.

    One item to consider is... Physically, where is my catalog backup stored?  If the catalog itself, and the location of the storage unit which contains the catalog backup are both on the same storage array - then yu may want to consider either a) using another location as the catalog backup target, AND/OR b) duplicating the catalog backup to another storage location or storage medium.