dfsr

6 Topics

DFSR backup failing
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>
BharathAchar
5 years ago Place NetBackup
1.3KViews
0likes
4Comments
Suggestions for backing up a large VM with DFSR data
We have customer VM which is around 36 TB in size currently and expected to grow in the near future. The VM hosts DFSR data. Earlier, the VM used to have around 4 TB of DFSR data which we used to backup using a MS-Windows policy with backup selection of shadow copy components for backing up the DFSR data. Now since the customer had added multiple new vmdks/drives for hosting for DFSR data, I am looking for suggestions for a efficient backup method for backing up the complete VM. Total size of DFSR data is more than 32 TB. Any suggestions would help and if anyone has encountered such scenario, please advice. The method I can think of right now is to split the backup into multiple policies and backup each DFSR drive in its own policy and possibly take a weekly backup for each drive. Any suggestions for daily backup of the VM? My backup infra is a one master server and 3 media server ( all redhat) with Ceph storage and AWS Glacier.
anash7
6 years ago Place NetBackup
1.2KViews
0likes
2Comments
Best Practice for DFSR Backup of large data
Hi All, I'm trying to backup DFSR enabled folder whose size is around 1.2TB. With Shadow Copy Component the backup is taking almost around 20 hours to complete. Once I stop the replication service and takes a full backup, it takes 12 hours to complete.My acceptable backup windows is 14 hours and hence with SCC backup I'm not able to complete the backup on time. Also, does the SCC backup always behaves as a FULL backup? My incremental backup always backs up complete data and due to this I can't use this option for my incrementals also as it's exceeding the window. I would like to know any best practice available for DFSR backup with SCC. (Don't prefer to stop the dfsr service) Would accelerator do any good for this situation? My Environment: NetBackup Appliance 5230 acts as both Master & Media Server Appliance Version - 2.6.1.2 Master Server Netbackup Version - 7.6.1.2 Client Server - Windows 2012, NBU Version - 7.6.0.1
Solved
Vishnu721
8 years ago Place NetBackup
5.1KViews
0likes
6Comments
DFSR backup job that fail with status code 1 show NBU error in BAR
hi, I'm running a few DFSR share backups using the backup selection = Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\HomeShare\Home2 , for example. These are always to Disk target (open storage) and using Accelerator. backups of DFSR share will usually run clean and finish with status 0 but sometimes completes with a status 1. I can ususally rerun the backup the next morning and it's happy. The peculiar thing is if it's a status 1 and the logs don't show actual files skipped, BAR will then show an error if I try browsing the image for recovery: "Unable to obtain list of files using the specified search criteria" The "skipped" files seem to be the The shadow copy components themselves....resulting in a non-recoverable image. the logs of this scenario are as follows: 11/30/2016 5:00:00 PM - Info nbjm(pid=4396) starting backup job (jobid=2147876) for client cadc3dfsp004, policy DFSR_HomeShare_Home2, schedule Daily_DiffInc_Disk 11/30/2016 5:00:00 PM - Info nbjm(pid=4396) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2147876, request id:{E5CDA389-208A-444D-820C-23AB30B45037}) 11/30/2016 5:00:00 PM - requesting resource CACALDD002_PrimarySTU 11/30/2016 5:00:00 PM - requesting resource bkpnbmaster1.nal.local.NBU_CLIENT.MAXJOBS.cadc3dfsp004 11/30/2016 5:00:00 PM - requesting resource bkpnbmaster1.nal.local.NBU_POLICY.MAXJOBS.DFSR_HomeShare_Home2 11/30/2016 5:00:00 PM - granted resource bkpnbmaster1.nal.local.NBU_CLIENT.MAXJOBS.cadc3dfsp004 11/30/2016 5:00:00 PM - granted resource bkpnbmaster1.nal.local.NBU_POLICY.MAXJOBS.DFSR_HomeShare_Home2 11/30/2016 5:00:00 PM - granted resource MediaID=@aaaaX;DiskVolume=CACALDD002_STU;DiskPool=CACALDD002_Production;Path=CACALDD002_STU;StorageServer=CACALDD002.nal.local;MediaServer=cacalnbu005.nal.local 11/30/2016 5:00:00 PM - granted resource CACALDD002_PrimarySTU 11/30/2016 5:00:02 PM - estimated 79986824 Kbytes needed 11/30/2016 5:00:02 PM - Info nbjm(pid=4396) started backup (backupid=cadc3dfsp004_1480550402) job for client cadc3dfsp004, policy DFSR_HomeShare_Home2, schedule Daily_DiffInc_Disk on storage unit CACALDD002_PrimarySTU 11/30/2016 5:00:04 PM - started process bpbrm (1768) 11/30/2016 5:00:10 PM - Info bpbrm(pid=1768) cadc3dfsp004 is the host to backup data from 11/30/2016 5:00:10 PM - Info bpbrm(pid=1768) reading file list for client 11/30/2016 5:00:11 PM - Info bpbrm(pid=1768) accelerator enabled 11/30/2016 5:00:17 PM - connecting 11/30/2016 5:00:20 PM - Info bpbrm(pid=1768) starting bpbkar32 on client 11/30/2016 5:00:20 PM - connected; connect time: 0:00:03 11/30/2016 5:00:22 PM - Info bpbkar32(pid=3000) Backup started 11/30/2016 5:00:22 PM - Info bpbkar32(pid=3000) change time comparison:<enabled> 11/30/2016 5:00:22 PM - Info bpbkar32(pid=3000) accelerator enabled backup, archive bit processing:<disabled> 11/30/2016 5:00:22 PM - Info bptm(pid=2280) start 11/30/2016 5:00:22 PM - Info bptm(pid=2280) using 262144 data buffer size 11/30/2016 5:00:22 PM - Info bptm(pid=2280) setting receive network buffer to 1049600 bytes 11/30/2016 5:00:22 PM - Info bptm(pid=2280) using 30 data buffers 11/30/2016 5:00:25 PM - Info bptm(pid=2280) start backup 11/30/2016 5:00:25 PM - Info bptm(pid=2280) backup child process is pid 6572.2260 11/30/2016 5:00:25 PM - Info bptm(pid=6572) start 11/30/2016 5:00:25 PM - begin writing 11/30/2016 5:00:27 PM - Info bpbkar32(pid=3000) not using change journal data for <Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\HomeShare\Home2>: not supported for non-local volumes / file systems 11/30/2016 5:41:51 PM - Warning bpbrm(pid=1768) from client cadc3dfsp004: WRN - can't open object: Shadow Copy Components: (BEDS 0xE000FECB: A failure occurred accessing the backup component document.) 11/30/2016 5:41:51 PM - Warning bpbrm(pid=1768) from client cadc3dfsp004: WRN - can't open object: Shadow Copy Components:\User Data\Distributed File System Replication\DfsrReplicatedFolders\HomeShare (BEDS 0xE000FEDD: A failure occurred accessing the object list.) 11/30/2016 5:47:33 PM - Info bptm(pid=2280) waited for full buffer 1226 times, delayed 178286 times 11/30/2016 5:47:33 PM - Info bpbkar32(pid=3000) accelerator sent 1808810496 bytes out of 8746298368 bytes to server, optimization 79.3% 11/30/2016 5:47:34 PM - Info bptm(pid=2280) EXITING with status 0 <---------- 11/30/2016 5:47:35 PM - Info bpbrm(pid=1768) validating image for client cadc3dfsp004 11/30/2016 5:47:37 PM - Info bpbkar32(pid=3000) done. status: 1: the requested operation was partially successful 11/30/2016 5:47:37 PM - end writing; write time: 0:47:12 the requested operation was partially successful(1) The job was successfully completed, but some files may have been busy or inaccessible. See the problems report or the client's logs for more details. 12/1/2016 8:23:46 AM - job 2147876 was restarted as job 2148876 any clue to why this might be happening and why it isn't a full "backup bad, not usable" rather than a status 1 ? thank you ,
Solved
Sergio_Millan
9 years ago Place NetBackup
3KViews
0likes
10Comments
DFSR single dir backup fails
We backup all the relevant drives on box as per required method of doing DFSR ...that works fine and we can recovery individual components without any issues. We have been given the requirement to backup specific dirs on the same box with a different retention period. I assumed the best way to do this would be a regular MS-Windows policy listing only the individual dirs. But that appears not to function. The test policy will backup stuff on the OS drive successfully but anything on DFSR drives returns (90) media manager received no data for backup image Any ideas on what could be casuing this? NBU = 7.7.3 OS W2k8 X64 SP2 X64
Solved
Jim-90
9 years ago Place NetBackup
997Views
0likes
4Comments
Backup DFSR data in Netbackup 7.1 (Solution for Error-13 )
Environment: NetBackup 7.1, Windows 2008 R2 DFSR enabled File server in Cluster. Error: Backup partially completes or fails with error 13 without backing up actual data. Issue: Wrong policy configuration and backup job conflict on virtual server on same cluster node. Solution:
Nelson_Thomas
13 years ago Place Enterprise Data Services Community Blog
219Views
1like
0Comments