TechAlert: Under certain circumstances, backups of Windows 2008 clients that are performed with NetBackup 6.5.2, may exit with a status code 0 (successful), despite being incomplete.

Article:TECH87012  |  Created: 2008-01-09  |  Updated: 2008-01-02  |  Article URL http://www.symantec.com/docs/TECH87012
Article Type
Technical Solution


Environment

Issue



TechAlert: Under certain circumstances, backups of Windows 2008 clients that are performed with NetBackup 6.5.2, may exit with a status code 0 (successful), despite being incomplete.

Solution



Introduction:
Under certain circumstances, backups of Windows 2008 clients that are performed with NetBackup 6.5.2 may be incomplete despite a reported success (status code 0) of the backup stream.

Affected clients are Windows 2008 clients which have had software removed/uninstalled in such a way as to have created registry inconsistencies as documented in Microsoft KB Article 955078, referenced below.  These registry inconsistencies cause Volume Shadow Copy Services (VSS) System Writers to attempt to access files which no longer exist.  In NetBackup 6.5.2 (and 6.5.2A), when a VSS Writer encounters this error, NetBackup tells that Writer to complete and move onto the next VSS Writer, regardless of whether the Writer has items remaining to back up.  This can lead to a report of a successful backup in the Activity Monitor, exit status code 0; however, closer examination, the backup is found to be incomplete.

What is Affected:
Your environment is affected under the following conditions:
  • Running NetBackup 6.5.2 (or 6.5.2A)
  • Backing up Windows 2008 clients

How to Determine if Affected:

There are two ways to check your environment to determine if you are affected by this issue:

1.  Examine the bpbkar log of the client for entries similar to the following:

8:58:29.661 AM: [2068.1212] <2> <FROM BEDS>: Component Set System Files has 1 files missing on the snapshot

8:58:29.661 AM: [2068.1212] <2> ov_log::V_GlobalLogEx: ERR - beds_base::V_OpenForRead():FS_OpenObj() Failed! (0xE0009420:File not present on the snapshot.

8:58:29.661 AM: [2068.1212] <2> tar_base::V_vTarMsgW: WRN - can't open object: Shadow Copy Components:\System State\System Files\System Files (BEDS 0xE0009420: File not present on the snapshot.

8:58:29.661 AM: [2068.1212] <2> ov_log::V_GlobalLog: INF - v_beds::V_FindNext() EXIT Name: bRC:false LastError:0xFFFFFE07:0xa000fe07 (2684419591)

2.  Alternatively, examine the size of the backup streams on the client.  For example, a Shadow Copy Components:\ backup on Windows 2008 usually averages 10 gigabytes in size.  If a completed Shadow Copy Components:\ backup stream is found to be significantly smaller then 10 gigabytes, the Windows 2008 client may be encountering this issue.

Formal Resolution:
The formal resolution to this issue (Etrack 1408101) is included in the following patch release:
  • NetBackup 6.5 Update Release 3 (6.5.3)
This release is available at the support web site at:
 http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143

Workaround:
To ensure this issue does not occur, follow one of the resolution methods as described in the Microsoft support article at this link:
 http://support.microsoft.com/kb/955078

Or, contact Symantec Enterprise Technical Support for assistance.



Supplemental Materials

SourceETrack
Value1408101
DescriptionUnable to account for a significant number of files with a C:\ + Shadow Copy Components backup on Windows 2008


Legacy ID



308301


Article URL http://www.symantec.com/docs/TECH87012


Terms of use for this information are found in Legal Notices