04-10-2014 07:49 AM
Hi!
I am evaluating Symantec System Recovery 2013 and backed up a Hyper-V VM from the Hyper-V host (Windows Server 2012 R2). This seems to work fine so far.
Unfortunately, the restoration of this VM caused me many headaches until I found out what was causing the problem. It looks like SSR is not able to keep the required file permissions when it restores a VM directory, i.e. all config files and VHDX files inside. This leads to the problem that Hyper-V Manger is not able to start the VM anymore because of missing permissions. Unfortunately, adding VM-specific permissions through the GUI's security tab is not possible so the command line has to be used for each file.
The only solution I found so far is this workaround: http://www.symantec.com/business/support/index?page=content&id=TECH64331
Is there any more straightforward solution without having to use XCOPY?
Thanks in advance.
Anguel
Solved! Go to Solution.
04-10-2014 08:06 AM
I don't believe there is any way around this unfortunately. Here is the issue:
http://www.symantec.com/docs/TECH200023
04-10-2014 08:06 AM
I don't believe there is any way around this unfortunately. Here is the issue:
http://www.symantec.com/docs/TECH200023
04-11-2014 12:03 AM
Chris, thank you for the clarification.
On the other hand it is ridiculous that SSR as an enterprise product claims to be able to handle virtualization but is not able to restore a simple file with the original permissions.
In this state a lot of manual work is required to be able to restore a simple VM. Very annoying and I wasted much time to find out what the reason was for the restore to fail.
Anguel
04-11-2014 12:36 AM
Just to clarify a bit: the issue described in the article I mentioned is not specific to virtual environments. You see the issue with any SSR backup and restore.
I do agree with you that this is not good though. As per that article, the issue is under consideration to be fixed in a future version of the product.