User guide

40 EMC Avamar 7.0 Release Notes
Known problems and limitations
N/A Certain Avamar warnings that appear in Windows Server 2008 System State restore
can be ignored
When performing a Windows client System State Restore in Windows Server 2008
using Avamar, warnings like the following can be ignored:
2013-06-27 21:24:48 avtar Warning <7834>: Access denied due to
security constraints, path:"C:\ProgramData\Application Data".
2013-06-27 21:24:48 avtar Warning <7870>: Pre-existing directory
cannot be restored, path:"C:\ProgramData\Application Data".
2013-06-27 21:24:48 avtar Warning <7834>: Access denied due to
security constraints, path:"C:\ProgramData\Desktop".
2013-06-27 21:24:48 avtar Warning <7870>: Pre-existing directory
cannot be restored, path:"C:\ProgramData\Desktop".
N/A Windows Server Update Services role may not be recovered correctly
When performing a disaster recovery of a Windows Server 2008 R2 computer with the
Windows Server Update Services (WSUS) role, the WSUS role may not be recovered
correctly and the following errors might appear:
The Reporting Web Service is not working
The API Remoting Web Service is not working
The Server Synchronization Web Service is not working
The Client Web Service is not working
The SimpleAuth Web Service is not working
The DSS Authentication Web Service is not working
To work around this issue, reconfigure the WSUS role after recovery.
N/A VSS-based backup fails when a VHD is on a critical volume
Microsoft states that Volume Shadow Copy Service (VSS) does not support creating a
shadow copy of a virtual volume such as a VHD file (for example drive D), and the
system drive (for example drive C), in the same snapshot set. This VSS limitation
applies to any VSS-based backup by any vendor, and is not an Avamar limitation. The
Microsoft TechNet article "Servicing and Backing Up Virtual Hard Disks"
http://technet.microsoft.com/en-us/library/gg318053%28v=WS.10%29.aspx
describes best practices and recommendations for setting up VHDs so that they can be
backed up with VSS snapshots.
The solution is to adhere to the following requirements:
• Store critical data outside of or on a separate volume from the VHD file (drive D), by
storing it on the system drive (drive C), which is a non-VHD critical disk.
• Use Avamar Windows File System to back up a VHD file (drive D).
• Use Avamar Windows VSS plug-in to back up critical volumes required for BMR
(drive C) -- the system drive and non-VHD disks containing third-party services.
Table 10 Windows backup client known problems (page 2 of 2)
ID Description