Video Screencast Help
Symantec Appoints Michael A. Brown CEO. Learn more.

NTFS Volume errors on Backup Jobs

Created: 16 Apr 2010 • Updated: 07 Jun 2010 | 4 comments
This issue has been solved. See solution.

Hello, I am currently on a trial with Backup Exec 2010.  My exchange and file server backups have been running well for almost a week until 2 nights ago when I got two different errors, one on each job that was running.  I have a job that does an Exchange 2003 incremental backup that gave this error. 
"Final error: 0xe0001200 - This operation requires a backup-to-disk folder on an NTFS volume on the media server. Check the job log for details. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-4608"

When I follow the link I see a workaround to Disable GRT.  Well I do not want to disable GRT because I want to be able to restore individual mailboxes.  Also it said to make sure the target device is a local backup to disk formatted with NTFS.  My server is already formatted with a 2TB NTFS partition.  That partition also has a Deduplication folder and all of the jobs that run go to that folder.

This is the second error I get is when I run another job that back up files of several file servers.

"Final error: 0xe0001200 - This operation requires a backup-to-disk folder on an NTFS volume on the media server. Check the job log for details. Final error category: Resource Errors For additional information regarding this error refer to link V-79-57344-4608". 

Both of these errors are basically saying the same thing.  That I am not backing up to a local NTFS drive which I am indeed doing.    And again, they were working and then out of the blue two nights ago the stopped.

Has anyone experienced this problem?  Are there any known fixes besides disabling the GRT option?

Thanks.

Comments 4 CommentsJump to latest comment

RahulG's picture

Try recreating the backupo to disk folder

SOLUTION
RCMORE's picture

I ended up deleting the dedupe folder and recreating it.  Thanks.

RahulG's picture

Oh ok Thanks for the update . Incase if that resolves the issue please mark the post as resolved ... Cheers!!!

opg's picture

Well... it's more like a workaround than a solution. This weekend my BE2010 started doing the same, and I really do not wish to delete more than a month's worth of backups just to avoid having my backups fail with this error. And will I have to do this frequently?

Edit: in the end it started giving other errors as well, so I deleted the dedup as a device in BE2010, but without touching the files. When re-creating it and pointing to the same folder, it seems to work correctly without any loss of data - so that's good. :)