Exclude and include lists are being recognized by user backups and archives and catalog backups. This may lead to unintended exclusions during backup and archive. (Updated April 28, 2011)
|Article:TECH137767|||||Created: 2010-08-13|||||Updated: 2013-07-08|||||Article URL http://www.symantec.com/docs/TECH137767|
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)
April 28, 2011: User archives were added to affected job types.
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.
In addition, a potential for data loss exists during user archive jobs as well. Files in the exclusion list are excluded from being backed up, but NOT excluded from archiving. This may result in files or directories which are not backed up as part of the archive job but are nonetheless removed after the archive job is complete.
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.
The formal resolution to this issue (Etrack 2099769) is included in the following release:
- NetBackup 7.1
A fix for this issue has been posted for NetBackup 7.0.1 and can be obtained by accessing the attachment at the bottom of this document.
Additional policies can be created exclusively for user backups and archives which do not use exclude/include lists.
Global exclude/include lists can be changed to be specific to policies where user backups would not be taken.
It is recognized that these steps are likely an unfeasible workaround in many environments.
If this condition is experienced with NetBackup 7.0 clients which cannot immediately be upgraded to 7.0.1 (where the attached fix can then be installed), please contact Symantec technical support and reference this document to obtain a fix for this issue.
Symantec strongly recommends the following best practices:
1. Always perform a full backup prior to and after any changes to your environment.
2. Always make sure that your environment is running the latest version and patch level.
3. Perform periodic "test" restores.
4. Subscribe to technical articles.
How to Subscribe to Email Notification:
Directly to this Article:
Subscribe to this article by clicking on the "Subscribe via email" link on this page to receive notification when this article is updated with Release Information.
If you have not received this TechNote from the Symantec Email Notification Service as a Software Alert, you may subscribe via email and/or RSS using the links provided at the following page:
Installation Location: client
(ET2115722) Exclude and include lists are being recognized by user and catalog backups. This may lead to unintended exclusions during backup.
Note: This package is intended to address a specific condition or issue within an environment which meets the criteria documented above. DO NOT install this package if your environment is not experiencing the specific issue or does not match the criteria in which the issue could occur.
Please follow the EEB Installer instructions available at the following link:
Please choose the appropriate platform after download:
eebinstaller.2115722.2.freebsd6.0 FreeBSD Installation
eebinstaller.2115722.2.hp11.11 HP-11.11 Installation
eebinstaller.2115722.2.hpia11.31 HP-IA64 Installation
eebinstaller.2115722.2.linuxR_x86_2.6 x64/x86 RedHat Enterprise Linux Installation
eebinstaller.2115722.2.linuxR_IA64_2.6 IA64 RedHat Enterprise Linux Installation
eebinstaller.2115722.2.linuxS_x86_2.6 x64/x86 SuSE Linux Enterprise Installation
eebinstaller.2115722.2.linuxS_IA64_2.6.16 IA64 SuSE Linux Enterprise Installation
eebinstaller.2115722.2.macOS10_5 Mac OS Installation
eebinstaller.2115722.2.plinuxR_2.6 Power RedHat Enterprise Linux Installation
eebinstaller.2115722.2.plinuxS_2.6 Power SuSE Linux Enterprise Installation
eebinstaller.2115722.2.solaris9 Solaris SPARC Installation
eebinstaller.2115722.2.solaris10 Solaris 10 SPARC Installation
eebinstaller.2115722.2.solaris_x86_10_64 Solaris 10 x86/x64 Installation
eebinstaller.2115722.2.rs6000_53 AIX Installation
621801405 223625 freebsd6.0/bpbkar
3180126392 1033296 hp11.11/bpbkar
1465263618 1376720 hpia11.31/bpbkar
670305077 459176 hpia11.31/versioninfo
3098577243 544616 linuxR_ia64_2.6/bpbkar
4187205967 528321 linuxR_x86_2.6/bpbkar
4242574115 541281 linuxS_ia64_2.6/bpbkar
3694822625 517223 linuxS_x86_2.6.16/bpbkar
2434762869 37853 linuxS_x86_2.6.16/versioninfo
1295322136 489532 macosx10_5/bpbkar
2161153977 316240 plinuxR_2.6/bpbkar
3092489037 327348 plinuxS_2.6/bpbkar
389672740 883491 rs6000_53/bpbkar
234078901 806080 solaris10/bpbkar
2244037560 803224 solaris9/bpbkar
232600132 406256 solaris_x86_10_64/bpbkar
216840880 333022 zlinuxR_2.6/bpbkar
3536754956 325052 zlinuxS_2.6/bpbkar
Recommended service state:
No jobs should be running on the NetBackup client system the fix is being applied to.
exclude and include lists are being recognized by the USER type backups.
Article URL http://www.symantec.com/docs/TECH137767