ET2847261 - NetBackup 7.5 customers using symlinks, junctions, or ALTPATH in the image database may result in loss of .f file

NOTE: If you are experiencing this particular known issue, we recommend that you
Subscribe
to receive email notification each time this article is updated. Subscribers will be the
first to learn about any releases, status changes, workarounds or decisions made.

Issue

During the image migration step in a NetBackup 7.5 upgrade, client subdirectories in the image database directory that are linked at the file system level (UNIX/Linux; ln -s) (Windows; mklink) and do not have an alias or client name defined in NetBackup may have their *.f removed.

For example:

db/images/ClientA is linked to:

db/images/ClientB

If ClientB has valid images but has not been backed up or defined by bpclient as an alias, the image cleanup process will incorrectly remove ClientB *.f files which results in the image no longer being browsable in the Backup, Archive, and Restore GUI. The image header is not expired so the media which contains the backup will not be overwritten.

Additionally, on Windows masters using the ALTPATH functionality:

\db\images\ClientA\ALTPATH

If ClientA has not been backed up or defined, the image cleanup process will incorrectly remove the ClientA *.f files which results in the image no longer being browsable in the Backup, Archive, and Restore GUI. The image header is not expired so the media which contains the backup will not be overwritten.

Cause

The initial image migration upon upgrade to 7.5 through 7.5.0.3 was not properly adding the symlink/ALTPATCH client name to the alias list during catalog migration.

Solution

Customers who have experienced the issue on 7.5 GA- 7.5.0.3 can upgrade to 7.5.0.4 and restore the needed .f files from a catalog backup.

The formal resolution for this issue (Etrack 2847261) is included in the following release:

NetBackup 7.5 Maintenance Release 4 (7.5.0.4)

Information on NetBackup 7.5.0.4 is available in the Related Article linked below.