Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

e0001212 - The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must not be shared through Distributed File System. See the job log for more details.

Created: 20 Jun 2013 | 2 comments

Hello,

We seem to receive this error message on the Exchange backup ever 20 days or so.

 

e0001212 - The volume that is used for the staging location must be a writable NTFS volume that is local to the Backup Exec server. Also, the volume must not be shared through Distributed File System. See the job log for more details.

For additional information regarding this error refer to link V-79-57344-4626

The Article it links to is completely useless. I have had a look around in the forums and on the Internet but they only seem to refer to when you are doing a restore, whereas this is during an Exchange Backup.
We are using Backup Exec 2010 R3 service pack 2 with the Exchange plug in on an SBS 2011 server (standard)
It is a single disk exchange server and no dfs is configured or used.
The backup job only contains the Exchange database, no other files are included.
The only way we have found to resolve this issue is to recreate the job, it then works for roughly 20 days again then comes up with the same message.
Rebooting the server doesn't help.
There is plenty of disk space free, the exchange database is roughly about 50GB, there is 700GB free on that disk.
We have checked the temporary dump location and everyone has permissions to it (this was only a temporary change).

If you need anymore information just let me know
Cheers

 

 

 

 

Operating Systems:

Comments 2 CommentsJump to latest comment

MusSeth's picture

Vff extend timeout registry key... you can try creating this registry key and set the value to 600 once done reboot the server and than retry with job...

However please backup registry before you perform this step or make any changes in registry
Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes.

...below is the link to technote which has info how to create that key its for different error however solution from this technote I.e registry can still be tried as troubleshooting step...please let me know if this resloves your issue....

http://www.symantec.com/docs/TECH67493