Moving the image catalog
An image catalog may become too large for its current location. Consider moving the image catalog to a file system or disk partition that contains more available space.
NetBackup does not support saving the catalog to a remote NFS share. CIFS is supported on some SAN or NAS storage.
NetBackup only supports moving the image catalog to a different file system or disk partition. It does not support moving the other subdirectories that make up the entire NetBackup catalog.
For example, on Windows, do not use the ALTPATH mechanism to move install_path\NetBackup\db\error.
For example, on UNIX, do not move /usr/openv/netbackup/db/error. The catalog backup only follows the symbolic link when backing up the /images directory. So, if symbolic links are used for other parts of the NetBackup catalog, the files in those parts are not included in the catalog backup.
The directory that is specified in the ALTPATH file is not automatically removed if NetBackup is uninstalled. If NetBackup is uninstalled, you must manually remove the contents of this directory.
To move the image catalog on Windows
- Back up the NetBackup catalogs manually.
A backup of the catalogs ensures that you can recover image information in case something is accidentally lost during the move.
- Check the Jobs tab in the Activity Monitor and ensure that no backups or restores are running for the client.
If jobs are running, either wait for them to end or stop them by using the Jobs tab in the Activity Monitor.
- Use the Daemons tab in the Activity Monitor to stop the Request Manager and the Database Manager daemons. These services are stopped to prevent jobs from starting. Do not modify the database while this procedure is performed.
- Create a file named ALTPATH in the image catalog directory.
For example, if NetBackup is installed in the default location and the client name is mars, the path to the image catalog is:
C:\Program Files\Veritas\NetBackup\db\images\mars\ALTPATH
- Create the directory to which you intend to move the image information. For example:
E:\NetBackup\alternate_db\images\client_name
- On the first line of the ALTPATH file, specify the path to the directory where you intend to move the client's image information. For example:
E:\NetBackup\alternate_db\images\client_name
The path is the only entry in the ALTPATH file.
- Move all files and directories (except the ALTPATH file) that are in the current client directory to the new directory.
For example, if the images are currently in
C:\Program Files\Veritas\NetBackup\db\images\mars
and the ALTPATH file specifies
E:\NetBackup\alternate_db\images\mars
then move all files and directories (except the ALTPATH file) to
E:\NetBackup\alternate_db\images\mars
- Start the NetBackup Request Daemon, NetBackup Job Manager, and NetBackup Policy Execution manager in the Daemons tab.
Backups and restores can now resume for the client.
To move the image catalog on UNIX
- Check that no backups are in progress by running:
/usr/openv/netbackup/bin/bpps
- Stop bprd by running:
/usr/openv/netbackup/bin/admincmd/bprdreq -terminate
- Stop bpdbm by running:
/usr/openv/netbackup/bin/bpdbm -terminate
- Create the directory in the new file system. For example:
mkdir /disk3/netbackup/db/images
- Move the image catalog to the new location in the other file system.
- Create a symbolic link from /usr/openv/netbackup/db/images to the new location in the other file system.