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

Problem restoring files from a VM

Created: 23 Apr 2012 • Updated: 24 Apr 2012 | 4 comments
This issue has been solved. See solution.

Hi all,

I've been Googling for hours now trying to find a solution to this, but no joy, so I'm hoping someone here will be able to help!

We've got a Hyper-V server with various virtual servers running on it, one of which is our central filestore.

The backups have run fine and when I select the virtual server on the Backup and Restore view, I can indeed select last weekend's backup and browse and select the files.  However, the restores fail every single time (only from these virtual servers though - regular servers I can successfully restore from).

The error I get reads:

V-79-57344-4612 - The path (C:\TEMP) on the Backup Exec server for staging temporary data when restoring individual items must be on an NTFS volume that is local to the Backup Exec server.  Edit the properties for the restore job, and under Settings, click Advanced. Change the path, and then submit the job again.

(Click for big)
 

But C:\ is a local, NTFS drive.  One thing I read suggested that the problem could be that C:\ doesn't have enough free space.  No problem, I think, I'll put it on the D: drive instead.  So I went to the button in the top left corner -> Configuration and Settings -> Backup Exec Settings.  I went to the Granular Recovery Technology section and changed both cases of C:\TEMP to D:\Staging (which is an existing, empty folder) and pushed OK.

(Click for big)

I ran the job again... but get exactly the same error - still mentioning C:\TEMP!  I've restarted the server in case that was the issue, but still the same.

Then I re-read the error and noticed it says, "Edit the properties for the restore job, and under Settings, click Advanced. Change the path, and then submit the job again." But when I edit the job, at no point is there a "settings" option or an "advanced" button or option.

I've been through every options screen I can find and nowhere can I find anything pointing to or mentioning C:\TEMP anymore.

All the Googling I have done only seems to really mention Exchange issues, which this isn't.  I've tried some of the fixes anyway but no joy.  Anyone got any ideas?

(This is is my first post, so if I've left anything out or there's any more information you need, let me know!)

Comments 4 CommentsJump to latest comment

ALNS's picture

Just to add (I can't see an option to edit my above post)...

I've just tried a restore from another VM on there and although that fails with the same error, it is correctly reading D:\Staging rather than C:\TEMP:

V-79-57344-4612 - The path (D:\Staging) on the Backup Exec server for staging temporary data when restoring individual items must be on an NTFS volume that is local to the Backup Exec server. Edit the properties for the restore job, and under Settings, click Advanced. Change the path, and then submit the job again.

So if nothing else, I guess that rules out one thing.

CraigV's picture

Hi ALNS,

 

Is this a new installation, or an upgrade from a previous installation?

If a new installation, does your environment comply with the requirements as per the 2 Symantec TNs below?

http://www.symantec.com/business/support/index?page=content&id=HOWTO74088

http://www.symantec.com/business/support/index?page=content&id=HOWTO74092

Thanks!

Alternative ways to access Backup Exec Technical Support:

https://www-secure.symantec.com/connect/blogs/alte...

Sush...'s picture

Please check this technote which mentions this issue with Backup Exec 2012:

http://www.symantec.com/docs/TECH185813 : After upgrade to Backup Exec 2012 GRT restores from Hyper-V backups fail with staging error

Also this is captured in the Known Issue section of this Forum site:

https://www-secure.symantec.com/connect/issues/after-upgrade-backup-exec-2012-grt-restores-hyper-v-resources-fail-0xe0001204-path-media-serv

 

Thanks,

-Sush...

Hope this piece of Information Helps you... and if it does then mark this response as Solution....!!!

SOLUTION
ALNS's picture

Thank you CraigV - it was an upgrade from 2010 R3.

Thank you Sush - I don't know how I managed to not find that tech note in all my searching.  It turns out that although it still had my Hyper-V licence listed, it didn't have it installed under the "Options & Agents for this Server" section - added it in and it works now!

Thank you both for you help :)