Knowledge Base Article
Was this article helpful?
@ Richard.
The only problem as I understand it is that if you try to target the actual SQL/Exchange or other protected files that are "always" in use, BEWS will try to back them up (opposed to skip them) and generate file in use excptions. IMO if you target these protected files directly through the file system rather than with agents you are asking for trouble anyway.
@ Colin.
Thanks for the update, could you please provide the "offiical" Symantec procedure when the DFSR is in the 2008R2 cluster with 2 or more possible hosts. There is no Shadow Copy components as the cluster name is the entry point. We cannot pick a specific host to backup as the host could be different each week due to normal scheduled maintenance and moving resources from 1 host to another.
When picking up at the share level with a single DFSR server it is workable and have done that in past
Have a DFSR cluster and all you see is:
======================
Job ended: Tuesday, 16 October 2012 at 9:11:51 AM
Completed status: Failed
Final error: 0xe00084af - The directory or file was not found, or could not be accessed.
Final error category: Job Errors
For additional information regarding this error refer to link V-79-57344-33967
Errors
Click an error below to locate it in the job log
Backup- MEL-DFS
Directory was not found, or could not be accessed.
None of the files or subdirectories contained within will be backed up.
V-79-57344-33967 - The directory or file was not found, or could not be accessed.
======================
The other thing is speed for ADBO, I see pretty much twice a much throughput with ADBO as to normal on host backup - 2.5TB @ 3200MB/min compared to 1.5TB @ 1700MB/min, both to Gen1 LTO4 @ 3gbps SAS.
I second Richard above that Symantec really need to look at this issue as dont see any problem as to why ADBO cannot be used with DFSR to picking up a flat file system.