cancel
Showing results for 
Search instead for 
Did you mean: 

Shadow Copy DFS backup is failing.

09/12/2013 19:59:50 - Info bpbrm(pid=9745) sct01fil01 is the host to backup data from     
09/12/2013 19:59:50 - Info bpbrm(pid=9745) reading file list from client        
09/12/2013 19:59:51 - Info bpbrm(pid=9745) accelerator enabled           
09/12/2013 20:00:15 - Info nbjm(pid=5004) starting backup job (jobid=93517) for client sct01fil01, policy SCT-Windows-Accelerator-DFS-sctfil01, schedule Daily_Incr  
09/12/2013 20:00:15 - estimated 7215680 Kbytes needed
09/12/2013 20:00:15 - Info nbjm(pid=5004) started backup (backupid=sct01fil01_1386619215) job for client sct01fil01, policy SCT-Windows-Accelerator-DFS-sctfil01, schedule Daily_Incr on storage unit stu_disk_sct01bck04
09/12/2013 20:00:16 - started process bpbrm (9745)
09/12/2013 20:01:18 - Info bpbrm(pid=9745) starting bpbkar on client         
09/12/2013 20:01:23 - Info bpbkar(pid=5440) Backup started           
09/12/2013 20:01:23 - Info bpbrm(pid=9745) bptm pid: 9963          
09/12/2013 20:01:23 - Info bptm(pid=9963) start            
09/12/2013 20:01:23 - Info bptm(pid=9963) using 262144 data buffer size        
09/12/2013 20:01:23 - Info bptm(pid=9963) using 64 data buffers         
09/12/2013 20:01:23 - Info sct01bck04(pid=9963) Using OpenStorage client direct to backup from client sct01fil01 to sct01bck04  
09/12/2013 20:01:50 - connecting
09/12/2013 20:01:51 - connected; connect time: 00:00:01
09/12/2013 20:01:58 - begin writing
10/12/2013 01:18:31 - Critical bptm(pid=9963) sts_close_handle failed: 2060012 call should be repeated      
10/12/2013 01:18:31 - Critical bptm(pid=9963) cannot write image to disk, media close failed with status 2060012  
10/12/2013 01:18:31 - Info sct01bck04(pid=9963) StorageServer=PureDisk:sct01bck04; Report=PDDO Stats for (sct01bck04): scanned: 256023247 KB, CR sent: 1166344 KB, CR sent over FC: 0 KB, dedup: 99.5%
10/12/2013 01:18:31 - Critical bptm(pid=9963) sts_close_server failed: error 2060005 object is busy, cannot be closed   
10/12/2013 01:18:59 - Info bptm(pid=9963) EXITING with status 87 <----------        
10/12/2013 01:19:00 - Info bpbkar(pid=5440) done. status: 87: media close error       
10/12/2013 01:19:33 - end writing; write time: 05:17:35
media close error(87)
 
Environment:
Windows 2008 R2
Netbackup 7.5.0.6
 
1 Solution

Accepted Solutions
Accepted Solution!

The issue resolved after I

The issue resolved after I disabled the client side dedup in the Policy. 

 

Thank you all for your effort. 

View solution in original post

7 Replies

Using OpenStorage client

Using OpenStorage client direct ..............

Seems you have Client Dedupe enabled?

As far as I know, Client side dedupe is not supported for DSF backups. 
Will see if I can find documentation.....

 

Yes, The client side dedupe

Yes, The client side dedupe is enabled. also I checked the VSS writer for DFS is also in a waiting for completion state. 

Thanks. 

Seems dedupe is supported for

Seems dedupe is supported for DFS. See this discussion: https://www-secure.symantec.com/connect/forums/best-practice-backup-dfsr-server10-tb-data-using-nbu-...

... the VSS writer for DFS is also in a waiting for completion state. 

Not sure if this is causing the issue. A reboot may fix this. Please also check Microsoft Support site for VSS hotfixes.

You may want to change dedupe options for this client if 'Always use client-side deduplication' is selected to 'Prefer to use client-side deduplication'.

Hopefully someone else will suggest something more helpful.....

Your job is using Accelerator

Your job is using Accelerator as well as client side de-dupe and your error actually relates to getting a handle on the disk storage itself

There is a gap from 20:01 when it starts writing up to 01:18 when it fails

It could be that you are hitting a timeout or a keep_alive timeout - it may also be that the fragement size on the de-dupe storage unit is too large and causing these timeouts

It looks like it only passed 1GB of data in 5 hours - so i would say it is hitting a timeout somewhere here - or the de-dupe isunder too much load causing it to run very slowly

What sort of de-dupe is it? PureDisk, MSDP, Appliance? -- It may need to be tuned or cleaned up

Thanks Mark for your

Thanks Mark for your input. 

It is using appliance for dedupe, may be you are right I have to check and try to cleaned up. 

Ok - usual stuff with keeping

Ok - usual stuff with keeping on top of queue processing - but if you are suing accelerator in an appliance then you should also tune it so that it doesnt run out of content router threads (which may be part of your issue)

So edit (vi) the /disk/etc/puredisk/contentrouter.cfg file and change the value for WorkerThreads from 64 to 128

It needs at least a NetBackup service re-start to take effect but i like to clean up the queues and then give the appliance a reboot to make sure that this setting gets put into action

This should help with the issue you are experiencing but also check under usr/openv/netbackup/db/ for any DPS_PROXY*** files

You really only want to have one in there which is DPS_PROXYDEFAULTRECVTMO and it should have a vlaue of 800 in it

You can also add this file to the same location on your master server - just keeps the disk checks more efficient in a busy ststem and stops disk showing as downduring very busy periods

These two really should help out - but do check that the client is OK and not struggling with doing client side dce-dupe and accelerator or if it has Anti Virus or anything holding it back

Accepted Solution!

The issue resolved after I

The issue resolved after I disabled the client side dedup in the Policy. 

 

Thank you all for your effort. 

View solution in original post