My setup is as follows: Master server - windows 2003 SP2 STD edition NBU version 7.0 Media server - windows 2003 SP2 STD edition NBU version 7.0 Client - windows 2008 R2 with DFSR replication NBU version 7.0 with DFSR fix applied (ET1940549) Backup selection - ALL_LOCAL_DRIVES When the backup kicks off, it does everything right and stays at begin writing......after 30 or so minutes the backup fails with either error 13 (mostly) or 24. Not a single byte is wriiten. The problem seems to be the shadow copy components backup that fail. I have tried selecting drives e.g C:\ and the backup works perfectly. I tried the directive shadow copy components only but the backup fails....here is the exact error from activity monitor; 18/08/2010 11:31:15 AM - Warning bpbrm(pid=13460) from client client_server_name: WRN - can't open object: Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\IISConfig (BEDS 0xE000FEDD: A failure occurred accessing the object list.) 18/08/2010 11:31:16 AM - Error bpbrm(pid=13460) from client client_server_name: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - EXIT STATUS 69: invalid filelist specification 18/08/2010 11:31:17 AM - Error bpbrm(pid=13460) could not send server status message 18/08/2010 11:31:17 AM - end writing; write time: 00:32:41 file read failed(13) I have checked the vss writers state and providers. This is ok.

Tech doc 340189 (Etrack 1940549) http://seer.entsupport.symantec.com/docs/340189.htm

Yes, and the fix has been applied. The concerning factor is that no backup takes place just fails with error 13. On the article it says backups complete with status 0 even though the DFSR data has been skipped.

Wild guess, but knowing you you have probably already had a look at this: http://seer.entsupport.symantec.com/docs/354674.htm It also doesn't explain why it's working when you backup C:\. Maybe you've discovered another bug? Do you have a bpbkar log?

Yes, I checked that too...I have mailed you the bpbkar log...I logged a call with Symantec yesterday as critical and had to re-assign the ticket yesterday 1 pm CAT but still no word from them. So it looks like I will downgrade the client to 6.5.4 or 6.5.5. I know 6.5.4 works in windows 2003 not sure on windows 2008......

Each file name in bpbkar is enumerated, but all of them fail with: WRN - can't open file: Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\xxx\xxx (WIN32 3: Unknown error) Before this, there seems to be a snapshot problem as well. Do you have a bpfis log? Seems there's no knowledge of a prior full backup and that the sched is Incr (not sure if this is causing the problem...Do you get the same result when running a Full?): 12:56:59.682 PM: [3192.4316] <4> SnapshotAssociation::AdjustUnboundedAssocations: INF - QueryDiffAreasForVolume returned failure status; no Diff areas for this volume 12:57:02.334 PM: [3192.4316] <16> VssSnapshot::V_VssVolumeSnapshot(): INF - VSS Volume Set prepare failed ..... 12:57:02.366 PM: [3192.4316] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================ 01:30:33.284 PM: [3192.4316] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x400 Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata. W2008 support listed on p. 27 of Compatibility Guide. Hope Symantec Support contacts you SOON! Maybe wait with downgrade until they're happy that they have all the logs that they need.

Problem backing up Windows 2008 with DSFR on NBU 7.0

16 Replies

J_H_Is_gone
Level 6
15 years ago
Tech doc 340189 (Etrack 1940549)

http://seer.entsupport.symantec.com/docs/340189.htm
Gerald_W__Gitau
Level 6
15 years ago
Yes, and the fix has been applied. The concerning factor is that no backup takes place just fails with error 13. On the article it says backups complete with status 0 even though the DFSR data has been skipped.
Marianne
Level 6
15 years ago

Wild guess, but knowing you you have probably already had a look at this:

http://seer.entsupport.symantec.com/docs/354674.htm

It also doesn't explain why it's working when you backup C:\.

Maybe you've discovered another bug?
Do you have a bpbkar log?
Gerald_W__Gitau
Level 6
15 years ago
Yes, I checked that too...I have mailed you the bpbkar log...I logged a call with Symantec yesterday as critical and had to re-assign the ticket yesterday 1 pm CAT but still no word from them. So it looks like I will downgrade the client to 6.5.4 or 6.5.5. I know 6.5.4 works in windows 2003 not sure on windows 2008......
Marianne
Level 6
15 years ago
Each file name in bpbkar is enumerated, but all of them fail with:

WRN - can't open file: Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\xxx\xxx (WIN32 3: Unknown error)

Before this, there seems to be a snapshot problem as well. Do you have a bpfis log?

Seems there's no knowledge of a prior full backup and that the sched is Incr (not sure if this is causing the problem...Do you get the same result when running a Full?):

12:56:59.682 PM: [3192.4316] <4> SnapshotAssociation::AdjustUnboundedAssocations: INF - QueryDiffAreasForVolume returned failure status; no Diff areas for this volume
12:57:02.334 PM: [3192.4316] <16> VssSnapshot::V_VssVolumeSnapshot(): INF - VSS Volume Set prepare failed

.....

12:57:02.366 PM: [3192.4316] <4> dos_backup::V_InitializeShadowCopy: INF - ============================================
01:30:33.284 PM: [3192.4316] <2> ov_log::V_GlobalLog: ERR - BEDS_AttachToDLE():FS_AttachToDLE() DeviceName:'System?State' BackupReason:0x400 Failed! (0xE000FEC9:A failure occurred accessing the Writer metadata.

W2008 support listed on p. 27 of Compatibility Guide.

Hope Symantec Support contacts you SOON! Maybe wait with downgrade until they're happy that they have all the logs that they need.
Gerald_W__Gitau
Level 6
15 years ago
bpfis does not log anything when doing shadow copy components.....but it does when doing normal backup.

The full backup also fails.

I will downgrade to 6.5.6 tonight and let you know how it went. Thanks for your help.
Gerald_W__Gitau
Level 6
15 years ago
Ok..I downgraded the client to 6.5.6, but still the backup failed exactly like 7.0. So I went a step down to 6.5.5 and now I get a status 1 error. Much better but still all shadow copy components not backing up.

I managed to call Symantec and refused to hangup till I spoke to a Techie, we have been on webex for the last 3 hrs and still no backup. Took a break and will continue troubleshooting again. I hope to have this resolved before close of business today...
Marianne
Level 6
15 years ago
Hi Gerald

Any progress on this? Hopefully working backups by now?
tbl
Level 3
15 years ago
Hello,

have you had any information about symantec ?

I have the same problem with a client in 6.5.4 and servers in 6.5.5

the backup stops when processing the directive Shadow Copy Components.

thomas
KEELIN_HART_2
Level 4
15 years ago
Hi Gerald / Thomas. Did you find a resolution? We are having similar issue with NBU 6.5.4 server and client.

Thanks.