cancel
Showing results for 
Search instead for 
Did you mean: 

DFSR backup failing

BharathAchar
Level 4

10 May, 2020 7:19:40 PM - begin writing
10 May, 2020 7:19:46 PM - Error bpbrm (pid=17654) from client client1230020: ERR - Unable to backup System State or Shadow Copy. Please check the state of VSS and associated Writers.INF - Estimate:-1 -1
10 May, 2020 7:19:46 PM - Info bptm (pid=17662) waited for full buffer 1 times, delayed 448 times
10 May, 2020 7:19:46 PM - Error bpbrm (pid=17654) from client client1230020: 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
10 May, 2020 7:19:46 PM - Info bptm (pid=17662) EXITING with status 90 <----------
10 May, 2020 7:19:46 PM - Critical bpbrm (pid=17654) unexpected termination of client client1230020
10 May, 2020 7:19:47 PM - Info server0717a0.Site.domain.com (pid=17662) StorageServer=PureDisk:server0717a0.Site.domain.com; Report=PDDO Stats for (server0717a0.Site.domain.com): scanned: 3 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled
10 May, 2020 7:19:47 PM - Info bpbkar (pid=76600) done. status: 50: client process aborted
10 May, 2020 7:19:47 PM - end writing; write time: 0:00:07
client process aborted  (50)

 


C:\Users\ad_acharbha>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error

Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error

Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error

Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {5f357fd4-da83-4845-9d62-b4f906ec7caa}
State: [1] Stable
Last error: No error

Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {0bdee2ca-1f4a-49a0-8e18-49ae165c47c9}
State: [1] Stable
Last error: No error

Writer name: 'DFS Replication service writer'
Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
Writer Instance Id: {c3c0ec55-b351-4cb5-99ab-454b16e7fb03}
State: [1] Stable
Last error: No error

Writer name: 'FSRM Writer'
Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
Writer Instance Id: {0ea27a80-1f79-41e5-84f1-81c3701f4856}
State: [1] Stable
Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {ee7b977c-7f32-4141-94a5-1e75ddcd4141}
State: [1] Stable
Last error: No error

Writer name: 'Dedup Writer'
Writer Id: {41db4dbf-6046-470e-8ad5-d5081dfb1b70}
Writer Instance Id: {372d7eb3-6fe4-41c1-90c9-719b4e8e0393}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {79d807c1-5184-4748-9594-c77fd3f03dcf}
State: [1] Stable
Last error: No error

Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {89abaa05-9cb6-4893-a709-a0766f588b99}
State: [1] Stable
Last error: No error

Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {238d1fa2-ba97-471c-9e2d-9c30977d541b}
State: [1] Stable
Last error: No error

Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {80577a73-5362-4ec7-b328-c1af2c833499}
State: [1] Stable
Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'
Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
Writer Instance Id: {9f012b43-258e-4353-8bc3-2b28609c9fce}
State: [1] Stable
Last error: No error


C:\Users\ad_acharbha>

 

 

C:\Users\ad_acharbha>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.

Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
Provider type: Software
Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
Version: 1.0.0.1

Provider name: 'Microsoft CSV Shadow Copy Provider'
Provider type: Software
Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
Version: 1.0.0.1

Provider name: 'Microsoft File Share Shadow Copy provider'
Provider type: Fileshare
Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
Version: 1.0.0.1

Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7


C:\Users\ad_acharbha>

 

 

4 REPLIES 4

Tape_Archived
Level 6
   VIP   

What is the backup selection for this backup policy??

If it's ALL_LOCAL_DRIVES can you try running only "System State" backup and check if it works??

Later, you can include individual drives & system state to backup the entire system, if above workaround is successful.

I know this is wired but it has worked for me!

 

My backup selection is something like this, backing up through Shadow copy components:

/Shadow Copy Components/User Data/Distributed File System Replication/DfsrReplicatedFolders/ut

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

@BharathAchar 

We are trying to make assumptions based on very little info that you are giving us. 

Based on your last post, its seems that you have broken down the backup selection as per this TN?   https://www.veritas.com/support/en_US/article.100038589

Could you please share exact details of Backup Selection? 

If multiple streams, are you seeing the error with one particular folder? Or all? 

Have you checked bpfis and bpbkar logs on the client for more details?

Due to potential large size of bpbkar log, I would start with level 1 log. 
If this does not help you, increase logging level to 3, and check logs for errors after the next failure. 

Nicolai
Moderator
Moderator
Partner    VIP   

From my experience

1: No more than two concurrent backup streams under shadow copy components -> DFSR.

2: No other backups using VSS snapshots, while running backup of DFSR under shadow copy components. If backup of DFSR is running and a new backup is scheduled to make backup of c:\, then the VSS snapshot of C: will interfer with the VSS snapshot of the DFSR area.

Also - status code 50 is a pure client side error. Take a look in the bpfis and bpbkar debug logs.