VSS error in DFS error

[gopi_enovate]

We are backing up DFS data from DFS central server.

A total of 37 folders are being replicated to this server. There are few folders with same name (from different branch servers). Hence, folders with same name are backed up using folder name followed by GUID like below.

Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Users (824BCE18-25B0-4DF6-991D-0ABD7A5E8B40-89D8562F-2715-4672-952B-D30C17B8D2BF

However, two replicated folders from the same server are not being backedup. It is failing with below errors.

6/15/2015 6:21:32 PM - Error bpbrm(pid=14160) from client epn-bf4: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.

6/15/2015 9:34:20 PM - Error bpbrm(pid=14160) from client epn-bf4: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.dir - 3 128 904 37349 6502703 -1 174 16832 root root 0 1434418366 1434418366 1434418366 1 /Shadow Copy Components/User Data/Distributed File System Replication/DfsrReplicatedFolders/Share (CBE8E267-1079-4036-B33F-14D4F033E5AA-819977D8-49BE-45F6-AF1D-F23B43A23DDE)/
 

There are few other replicated folders which do exist in the drive as this one. However, we are still not able to find the corresponding folder for the first error.
What could be the possible issue?
 

VSS writer state:
Writer name: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {79c100bf-bc24-4995-afc4-897877040333}
   State: [1] Stable
   Last error: No error

[sdo]

There are quite a few references to DFS in the latest (version 8) EEB guide for NetBackup v7.6:

https://support.symantec.com/en_US/article.DOC6085.html

...so, without knowing your specific versions (of all components) in place, there's probably not a lot else that any of us can say/offer, unless someone has seen this exact problem before.

[sdo]

Sounds like a question for Microsoft.  Remember, NetBackup leverages VSS, and so usually the only time that one can point a finger at NetBackup is with version compatibility and/or the names / paths / directives in a backup policy.  But seeing as the backup job is failing and telling you that there's a problem with VSS... well, I think you need Microsoft support.

As usual, others may be able to offer more specific help... if... you can tell us exact versions of all elements / servers / OS / NetBackup Client and NetBackup Server.

[gopi_enovate]

OS : Windows 2008 R2 64bit Enterprise
Netbackup master/media/client 7.6.1.

Backup policy is scheduled to backup individvual replicated folders.

6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Accounting>: not supported for non-local volumes / file systems
6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Archive>: not supported for non-local volumes / file systems
6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\backup>: not supported for non-local volumes / file systems
6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Shared>: not supported for non-local volumes / file systems
6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Users>: not supported for non-local volumes / file systems
6/16/2015 6:03:36 PM - Info bpbkar32(pid=14876) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\Company>: not supported for non-local volumes / file systems
 

37 replicated folders are present in two drives. VSS does a shadow copy of a drive and not any folder.
If 35 replicated folders are backedup successfully using the shadow copy of these two drives, then these two should be succcessful as well or alteast shouldnt throw a VSS issue.

Will Netbackup create shadow copy for each component, deletes it and creates a new one for the next component mentioned in the policy or it jus creates one shadow copy for the entire drive and does backup all components from the drive?

I have taken the issue with platform team. They are not convinced with the fact that it can work for 35 folders and not for the rest two within same drives.
VSS flush was completed with a reboot.

[sdo]

For the client name, is there a master server client attributes record, and is it using 'global drive shapshot' or 'individual drive snapshot' for the WOFB_usage field?  Maybe try changing?  And what about the WOFB_error option of 'disable and continue' ?  Maybe try this too?

C:\>bpclient -L -client myclient
Client Name: myclient
 Current Host:
        Hostname: myclient
 Dynamic Address:       no
 Free Browse:   Allow
 List Restore:  Not Specified
 Max Jobs This Client:  4
 WOFB Enabled:  yes
 WOFB FIM:      VSS
 WOFB Usage:    Individual Drive Snapshot
 WOFB Error Control:    Disable and Continue
 Client Direct: Deduplication on the media server or
                Move data via media server
 Client Direct Restore: Move data via media server
 OST Proxy:     Off
 OST Proxy Server:      Unspecified
Connect options:        2 2 3
 Offline:       No

[sdo · Accepted solution]

On the problem client, at the time of backups, how many shadow copies are in existence?

> vssadmin list shadows | find /c "Shadow Copy ID"

I believe that Windows VSS has a maximum of 64.

[gopi_enovate]

I have set it to WOFB and Individual drive snapshot.

Does a global drive snapshot be a good option for multiple folders spread across different drives


Client Name: 
 Current Host:
        Hostname: 
 Dynamic Address:       no
 Free Browse:   Allow
 List Restore:  Not Specified
 Max Jobs This Client:  Not Specified
 WOFB Enabled:  yes
 WOFB FIM:      VSS
 WOFB Usage:    Individual Drive Snapshot
 WOFB Error Control:    Abort on Error
 Client Direct: Deduplication on the media server or
                Move data via media server
 Client Direct Restore: Move data via media server
 OST Proxy:     Off
 OST Proxy Server:      Unspecified
Connect options:        2 2 3
 Offline:       No

[sdo]

To be honest... I really don't know.  It's a stab in the dark, nothing more than simply something to try.

[gopi_enovate]

Let me check the number of snapshots created during backup.

Worst part is that we are still not able to find out the corresponding replicated folder for the below error.

6/15/2015 6:21:32 PM - Error bpbrm(pid=14160) from client epn-bf4: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.