Showing results for 
Search instead for 
Did you mean: 

backup vhd with file level restore

Level 4

what is best practice for backing up hyper-v  (vhd files) but also having the capability for file level restore?


is there any documentation on setting this up?


Level 6

There are best practice for all agent options in BackupExec, they are under the support site for the respective product.

All you need to do is install the remote agent in the guest, configure the Hyper-V backup to enable GRT.  Your backup target needs to be a disk target (note hyper-V doesn't dedupe unless that will change with BE2012.  So it'll have to be plain NAS or NTFS targets.

Then the backup commences.  The VHD is transferred, the agent catalogs meta data related to file restoration, and bob's your uncle!


Level 4

When installing the agent on my hyper v host servers should I check AOFO? By default it's NOT selected.

Level 6

No need for AOFO.  It's a dead feature from the Win2k days when VSS didn't exist.

   VIP    Certified

You don't have to back up to disk to get GRT.  You can also backup to tape.  When you restore from tape, the backup will be staged to disk before the GRT restore begins.

Level 6

The GRT restore process, works BEST, when you backup to disk and duplicate to tape.

Restores take LONGER when you backup to tape,and have to stage to disk.

Do you want to restore quick, or backup quick?  The answer should be pretty clear.

Level 4

my job is faiing with:


Backup- HV02 - AOFO: Initialization failure on: "VRTSRV::\\hvcluster01.domain.local\Hyper-V?HA?VM\SERVER". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
V-79-10000-11217 - VSS Snapshot error. The Microsoft Volume Shadow Copy Service (VSS) snapshot failed. Make sure that all provider services and tasks are running. Check the Windows Event Viewer for details.
VSSADMIN output of SERVER with issue.
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {7fc81896-aa36-4e45-a536-94ee52e26444}
   State: [1] Stable
   Last error: No error
Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {33cef096-f9d5-4404-8b63-90892959ea37}
   State: [1] Stable
   Last error: No error
Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {3573cd93-3832-479c-bad6-e8307f591ed4}
   State: [1] Stable
   Last error: No error
Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {7340dfe5-9e74-4bd1-aebc-93479f365377}
   State: [1] Stable
   Last error: No error
Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c1488dd3-f28c-4f13-95d4-5f018069cbd0}
   State: [1] Stable
   Last error: No error
Writer name: 'IIS Config Writer'
   Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
   Writer Instance Id: {a85fe124-8537-48a4-b6cd-28c2a10bc626}
   State: [1] Stable
   Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {6da625c7-221d-4e58-bb6b-76b46e3c2060}
   State: [1] Stable
   Last error: No error
Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {5698354a-28fc-4032-a7a7-80cfba1fccc6}
   State: [1] Stable
   Last error: No error
Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {c3839596-e7e5-41f1-800c-249297fc88fb}
   State: [1] Stable
   Last error: No error
Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {57c12d7d-9ac4-436f-8baa-3ff6e701c118}
   State: [1] Stable
   Last error: No error
Writer name: 'TermServLicensing'
   Writer Id: {5382579c-98df-47a7-ac6c-98a6d7106e09}
   Writer Instance Id: {d71ee5db-3565-492b-ab73-65e8a02f012d}
   State: [1] Stable
   Last error: No error

Level 3

you sound like your having the same problem as myself with your VSS writers. take a look at the event viewer and see if it is complaining about your VS service failing. If so let me know and I'll post the steps that I've taken to resolve this.


Also try doing a backup using Microsoft Server backup, it will help clear up issues deciding what is causing the issue, Microsoft or Symantec.


As far as Hyper-V is concerned, I've always gone about it 3 different ways.

Backup the VHD file (you can backup the rest in this directory if you'd like, assuming you point your VHD files to their own dir)

Backup the server within the guest

and setup a script to point a monthly backup to disk.

Personaly I always have a second backup running that takes a backup of the VHD file alone and saves it to a shared storage device. In the event that I have a failure its almost as simple as a copy and paste. If your looking for a file by file restore option then I believe you'd want to backup the guest server directly.


Lucky for you there are a ton of ways to get what you want done, its just a matter of what best suites you

Level 4



I am seeing this error on my remote agent servers.


Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57860
Date:  3/1/2012
Time:  1:47:42 PM
User:  N/A
Computer: SERVER
An error occurred while attempting to log in to the following server: "SERVER.domain.local".
 SQL error number: "0011".
 SQL error message: "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.

 For more information, click the following link:
0000: 11 00 00 00 00 00 00 00   ........
0008: 00 00 00 00 00 00 00 00   ........

Level 3

I'm no expert on the SQL backups as I'm not using it but I believe you are seeing two different errors. (1) for the VSS writers and (2) for SQL user accounts.


--- Part 1 (For your possible VSS errors)---

Here is a link for a post I setup that sounds pretty close to what you have

On there one of the guys helping me out refers to a script to reset the VSS writers, here is that procedure.



How to Re-register Volume Shadow Copy Service (VSS) Components on Windows 2008/Windows 2003.




VSS may not be working in one or more of the following ways:

1. Volume snapshots may fail with errors.
2. Backups using VSS may fail.
3. One or more VSS writers are missing when running the following command:

  • vssadmin list writers

4. Using Backup Exec for Window Servers, backup jobs may:

  • fail with VSS or snapshot errors.
  • hang at snapshot processing.

5. Using Backup Exec System Recovery, backup jobs may:

  • fail at 5%.
  • appear to be progressing, reach 90% or higher then fail.

Re-registering VSS in Windows 2008 & testing is done in 2 parts:

Part 1 - Create and Execute a batch file named, FIXVSS08.BAT:
Please note the following:

  • Run the batch file as Administrator.
  • This is only for Windows 2008, not Windows 2003.

After running the .bat file, reboot the server to bring all of the writers into a stable state.
Copy and paste the following into Notepad, then click Save As and save it as FIXVSS08.BAT.



net stop "System Event Notification Service"

net stop "Background Intelligent Transfer Service"

net stop "COM+ Event System"

net stop "Microsoft Software Shadow Copy Provider"

net stop "Volume Shadow Copy"

cd /d %windir%\system32

net stop vss

net stop swprv

regsvr32 /s ATL.DLL

regsvr32 /s comsvcs.DLL

regsvr32 /s credui.DLL

regsvr32 /s CRYPTNET.DLL

regsvr32 /s CRYPTUI.DLL

regsvr32 /s dhcpqec.DLL

regsvr32 /s dssenh.DLL

regsvr32 /s eapqec.DLL

regsvr32 /s esscli.DLL

regsvr32 /s FastProx.DLL

regsvr32 /s FirewallAPI.DLL

regsvr32 /s kmsvc.DLL

regsvr32 /s lsmproxy.DLL

regsvr32 /s MSCTF.DLL

regsvr32 /s msi.DLL

regsvr32 /s msxml3.DLL

regsvr32 /s ncprov.DLL

regsvr32 /s ole32.DLL

regsvr32 /s OLEACC.DLL

regsvr32 /s OLEAUT32.DLL

regsvr32 /s PROPSYS.DLL

regsvr32 /s QAgent.DLL

regsvr32 /s qagentrt.DLL

regsvr32 /s QUtil.DLL

regsvr32 /s raschap.DLL

regsvr32 /s RASQEC.DLL

regsvr32 /s rastls.DLL

regsvr32 /s repdrvfs.DLL

regsvr32 /s RPCRT4.DLL

regsvr32 /s rsaenh.DLL

regsvr32 /s SHELL32.DLL

regsvr32 /s shsvcs.DLL

regsvr32 /s /i swprv.DLL

regsvr32 /s tschannel.DLL

regsvr32 /s USERENV.DLL

regsvr32 /s vss_ps.DLL

regsvr32 /s wbemcons.DLL

regsvr32 /s wbemcore.DLL

regsvr32 /s wbemess.DLL

regsvr32 /s wbemsvc.DLL

regsvr32 /s WINHTTP.DLL

regsvr32 /s WINTRUST.DLL

regsvr32 /s wmiprvsd.DLL

regsvr32 /s wmisvc.DLL

regsvr32 /s wmiutils.DLL

regsvr32 /s wuaueng.DLL

sfc /SCANFILE=%windir%\system32\catsrv.DLL

sfc /SCANFILE=%windir%\system32\catsrvut.DLL

sfc /SCANFILE=%windir%\system32\CLBCatQ.DLL

net start "COM+ Event System"


Part 2 - Testing VSS by performing a System State Backup:

  • You must first open a command prompt by right-clicking on Command Prompt and select Run As Administrator.

The command to start a System State Backup is:

Wbadmin start systemstatebackup -backuptarget:F:

Additional Notes:

  • F: is the target drive where you wish to store the system state backup.
  • This shouldn't be a drive that is hosting any of the files included with System State.
  • For Windows 2003, please refer to the following article:

For additional details, refer to the following Microsoft Technet article:

Level 3

--- Part 1 (For your possible SQL errors)---

I'll keep this short as I said earlier, I'm no expert with SQL.

When backing up a SQL box make sure you test out the "Resource Credentials" as I believe it will test you connection to SQL, also you should be setting up an account within SQL for the backup procedure. I haven't had much luck with backups using a AD account so normally under the database I setup a user with admin rights and call it "backup". Once I get a good backup I trim the permissions down until it fails again.


I wish I could help more on this but thats about the extent of my BE knowledge.

But those error messages your seeing tell me two different problems "SQL logon error" and a vaulty VSS writer.


Best of luck buddy

Level 3

If I have well understood, if one of my VM has a 1Tb vhd and I want to restore a single file from this big vhd, my backup exec media server must have at leat 1tb of free space to first restore the vhd from tape, before it can extract the file and restore it ?