Forum Discussion

fahis's avatar
fahis
Level 3
15 years ago

move catalog

Hi,

My catalog database is taking huge space and i want to move some part of the catalog into different drive.

My Setup is NetBackup 5.1 running on Solaris Server.

Can i move the catalog by client basis?

Regards,
Fahis
  • Yes you should move the directory used by the client ( /usr/openv/netbackup/db/images/clientname), and replace it with a symbolic link.

3 Replies

  • Yes you should move the directory used by the client ( /usr/openv/netbackup/db/images/clientname), and replace it with a symbolic link.
  • This is similiar to what Lu was talking about.

    The name of a VERITAS NetBackup client has been changed and it cannot browse backup images written under the previous name for a restore
    http://support.veritas.com/docs/241717

    This problem can be resolved by simply renaming the old client directory in the NetBackup database to reflect the new client name. It is advisable to create a NetBackup catalog backup before attempting this procedure to minimize the risk of problems. The backup images for each individual client can be found in /usr/openv/netbackup/db/images/<client_name>/ on the NetBackup master server.

    For example, if the old client name is OLD and the new client name is NEW:

      mv /usr/openv/netbackup/db/images/OLD  /usr/openv/netbackup/db/images/NEW


      If backups have already been performed using the new client name, the new directory will already exist. If this is the case, all subdirectories in the old directory need to be recursively copied to the new client directory while maintaining the original file permissions.

      Again, for example, if the old client name is OLD and the new client name is NEW:

        cp -pR /usr/openv/netbackup/db/images/OLD/*  /usr/openv/netbackup/db/images/NEW


        NOTE: The commands used in these examples are based on the UNIX operating system and may need to be revised according the target platform and this procedure should be carried out with care to prevent serious database inconsistencies occurring in the event of a mistake
  • if you want to move all of the clients then follow this technote

    DOCUMENTATION: How to move the image catalog on a UNIX Server
    http://support.veritas.com/docs/323700

    Manual: System Administrator's Guide for UNIX and Linux, Volume 1

    Page:  354

    Modification Type: Supplement

    Modification:
     
    This article details how to move the NetBackup for UNIX Servers' Image Catalog to a new location. This can be desirable when it has grown too large in size and is necessary to relocate the database to a place with more space available.
     
    In preparation for moving the NetBackup Image Catalog from one location to another, Symantec strongly recommends performing a FULL Catalog backup before proceeding.
     
    Note: Please perform the following steps carefully, as mis-configuration can cause problems.
     
    Note: NetBackup does not support saving the catalog to a remote file system. Therefore, Symantec advises against moving the image catalog to a remote file system such as NFS or CIFS.
     
    1. Shut down the NetBackup services on the master server. This may be done by running:
     
    /usr/openv/netbackup/bin/netbackup stop

    2. Copy the contents of the /usr/openv/netbackup/db/images directory to its new location, then rename the old images directory to images_bak as a backup copy.
     
    cp -pr /usr/openv/netbackup/db/images /disk8/netbackup/db/images


    3. Rename the old images directory to images_bak as a backup copy:
     
    mv /usr/openv/netbackup/db/images /usr/openv/netbackup/db/images_bak

    4. Create a symbolic link from /usr/openv/netbackup/db/images to the new location:
     
    ln -s /disk8/netbackup/db/images /usr/openv/netbackup/db/images

    5. Restart NetBackup services by running:
     
    /usr/openv/netbackup/bin/netbackup start


    6. Symantec recommends a full Hot NetBackup Catalog Backup after the relocation to test that the backup works correctly.
     
    Note: If you are using the legacy offline catalog backup from versions prior TO 6.x, make sure to update the Offline Catalog Backup from the administration console by selecting the Catalog tab then right click and select Configure Offline catalog backup, then update the previous backup location to point to the new location of the image database. (Caution: Be certain to add the path for the image catalog and not the link name. Without the path, NetBackup cannot back up the new location. In this example, the path is /disk8/netbackup/db/images)
     

     
    7. Check that you can search the Catalog and find images through the GUI and then if you wish, delete the images_bak folder created earlier.