Perhaps you are already aware of this.
Be sure to alter the filelist for the catalog backups!
check out this technote
Possible data loss during a catalog backup, with the ALTPATH file in place
Details:
If an ALTPATH file is in place, and correctly redirecting the image files to another location, you must specify that new location in the catalog backup paths. If you do not, the catalog backup just backs up the original path; i.e. the ALTPATH file itself, but not the redirected files.
The catalog backup will still complete with a status 0, since the path does exist, but you are not backing up anything redirected. This could lead to a data loss situation.
To check if you are using an ALTPATH file, open Windows Explorer and navigate to the following location: <install_path>\netbackup\db\images\<Client_name>
For example, if VERITAS NetBackup (tm) is installed in its default location and the client name is mars, the path to the image catalog is:
C:\Program Files\VERITAS\NetBackup\db\images\mars\ALTPATH
To check if your catalog backup has the correct path listed, open the NetBackup administration console and right-click on the word Catalog in the device tree on the left side. In the drop down box, select Configure NetBackup Catalog Backup. In the NetBackup Catalog Backup for Master Server window, select the Files tab. For the absolute pathname, make sure the new location that is in your ALTPATH file is listed. This will ensure that your images are being backed up with your catalog backup.
For more information regarding ALTPATH files and catalog backups, refer to the System Administrators Guide Volume 1, and look under the "Moving the NetBackup image Catalog" section. For convenience, here is an excerpt from the above mentioned guide, in regards to moving the NetBackup image catalog:
Moving the NetBackup Image Catalog:
If the NetBackup catalog is too large for its current disk partition you can move image information for individual clients to another partition.
- To move the NetBackup image catalog, perform the following steps:
1. Back up the NetBackup catalogs. (See "Backing Up the Catalogs Manually" on page 214.) This ensures that you can recover image information in case something is accidentally lost during the move.
2. 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.
3. Use the Services tab in Activity Monitor to stop the Request Manager and Database Manager services. This prevents jobs from starting and the database from being modified while you are performing this procedure.
4. Create a file named ALTPATH in the image catalog directory. For example, if NetBackup is installed in its default location and the client name is mars, the path to the image catalog is: C:\Program Files\VERITAS\NetBackup\db\images\mars\ALTPATH.
5. Create the directory to which you intend to move the image information. For example: E:\NetBackup\alternate_db\images\client_name
6. On the first line of the ALTPATH file, specify the path to the directory where you intend to move the clients image information. For example: E:\NetBackup\alternate_db\images\client_name. This will be the only entry in the ALTPATH file.
7. 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.
8. Add the new image directory to the NetBackup catalog backup configuration. (See "Catalog Files Tab" on page 211.) In the above example, you would add E:\NetBackup\alternate_db\images\mars.
Caution: Failure to add the alternate image directory to the catalog-backup configuration can result in loss of backup data if there is a disk failure.
9. Start the NetBackup Request Manager and NetBackup Database Manager services by using the Services tab in the Activity Monitor. Backups and restores can now resume for the client.
Bob Stump
Incorrigible punster -- Do not incorrige