Exclude and include lists are being recognized by user and catalog backups. This may lead to unintended exclusions during backup. (Updated September 20, 2010)
評価: 0 0
August 30, 2010: Updated with location of TechFile fix for NetBackup 7.0.1
September 20, 2010: New information for issue subscription - new location of 7.0.1 hotfix (attached to this doc)
In NetBackup, exclude and include lists are only supposed to be used by automatic backups and not by user backups. It was recently discovered in NetBackup 7.0 that user backups were using exclude and include lists. This can lead to a data loss situation if user backups are taken with unexpected exclusions - a success and status code 0 are reported in the Activity Monitor, but excluded data will not be available for restore as may be expected.
Similarly, catalog backups may complete with crucial data excluded if an exclude_list on the master server happens to contain entries which would match paths of catalog components.
What is Affected:
All NetBackup 7.0 and 7.0.1 UNIX clients where exclude lists are in use have the potential to be affected by this issue.
Note: All master and media servers are also clients.
Windows clients are NOT affected by this issue.
How to Determine if Affected:
If exclude lists (and, optionally, include lists) exist on the client, the client has the potential to be affected by this issue. These lists are found in /usr/openv/netbackup with filenames using the following syntax:
exclude_list and include_list are global and apply to all policies on the client. If the <policyname> suffix is used, it will only apply to the specific policy on that client, and likewise appending <schedulename> will limit the exclusions to the particular schedule of that particular policy.
Please go to this URL and download:
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):