We help IT Professionals succeed at work.

Windows 2008 Server backup automated restore  related to: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/Windows_Server_2008/Q_27615189.html

I was given guidance as to how to run a script that would allow me to backup specific VHD's on a Core Server.

What I am looking for here is a supplement to that post.  I want to script a restore of specific VHD's on a Core Server. So let's say I have created backups VHD1 and VHD2 and VHD3 on a Core server as per the Wbadmin script in the prior Experts thread.  Now I would like to restore perhaps only VHD1 and VHD3 every morning at 8:00 AM for instance. Could WBAdmin do this and what would be the code to do that?

Thanks in advance.
Watch Question

The easiest way to restore is with the gui  see the following


This can be scripted too and example of this is as follows

 WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:File -items:d:\folder -recursive 

Open in new window

The sull syntax  can be found by typing

wbadmin start recovery /?

    -items:{<VolumesToRecover> | <AppsToRecover> | <FilesOrFoldersToRecover>}
    -itemtype:{Volume | App | File}
    [-backupTarget:{<VolumeHostingBackup> | <NetworkShareHostingBackup>}]
    [-recoveryTarget:{<TargetVolumeForRecovery> | <TargetPathForRecovery>}]
    [-overwrite:{Overwrite | CreateCopy | Skip}]

Description:  Runs a recovery operation based on the parameters that you
To use this command, you must be a member of the Backup Operators group
or Administrators group.

-version       Specifies the version of the backup to recover in
                MM/DD/YYYY-HH:MM format. If you do not know the version
                identifier, type WBADMIN GET VERSIONS.

-items         Specifies a comma-delimited list of volumes, applications,
                files, or folders to recover.
                -If -itemtype is Volume, you can specify only a single volume
                by providing the volume drive letter, volume mount point, or
                GUID-based volume name.
                -If -itemtype is App, you can specify only a single
                application. To be recovered, the application must have
                registered with Windows Server Backup. You can also use the
                value ADIFM to recover an installation of Active Directory
                Domain Services. See Remarks for more information.
                -If -itemtype is File, you can specify files or folders, but
                they should be part of the same volume and they should be
                under the same parent folder.

-itemtype      Specifies the type of items to recover. Must be Volume, App, or

-backupTarget  Specifies the storage location that contains the backup that
                you want to recover. The parameter is useful when the
                location is different from where backups of this computer are
                usually stored.

-machine       Specifies the name of the computer that you want to recover
                the backup for. The parameter is useful when multiple
                computers have been backed up to the same location. Should be
                used when -backupTarget is specified.

-recoveryTarget  Specifies the location to restore to. This parameter is
                useful if this location is different than the location that
                was previously backed up. It can also be used for
                restorations of volumes, files, or applications. If you are
                restoring a volume, you can specify the volume drive letter
                of the alternate volume.
                If you are restoring a file or application, you can specify
                an alternate recovery location.

-recursive     Valid only when recovering files. Recovers the files in the
                folders and all files subordinate to the specified folders.
                By default, only files which reside directly under the
                specified folders are recovered.

-overwrite     Valid only when recovering files. Specifies the action to take
                when a file that is being recovered already exists in the
                same location.
                -Skip causes Windows Server Backup to skip the existing file
                and continue with recovery of the next file.
                -CreateCopy causes Windows Server Backup  to create a copy
                of the existing file so that the existing file is not
                -Overwrite causes Windows Server Backup to overwrite the
                existing file with the file from the backup.

-notRestoreAcl Valid only when recovering files. Specifies to not restore
                the security access control lists (ACLs) of files being
                recovered from backup. By default, the security ACLs are
                restored (the default value is true). If this parameter is
                used, the ACLs for the restored files will be inherited from
                the location to which the files are being restored.

-skipBadClusterCheck  Valid only when recovering volumes. Skips checking
                the disks that you are recovering to for bad cluster
                information. If you are recovering to an alternate server or
                hardware, we recommend not using this parameter. You can
                manually run the command CHKDSK /B on these disks at any time
                to check them for bad clusters, and then update the file
                system information accordingly.
                Important: Until you run CHKDSK as described, the bad
                clusters reported on your recovered system may not be

-noRollForward  Valid only when recovering applications. This allows for
                previous point-in-time recovery if the latest version from
                the backups is selected. For other versions of the
                application that are not the latest, previous point-in-time
                recovery is done by default.

-quiet         Runs the command with no prompts to the user.
I hope this helps



Thanks for the link and the code. Just to doublecheck we're on the same page, the code would allow me to do an 'unattended' recovery?  Basically when I come in the office in the morning and the routine has run through successfully in the night all the VM's are up and running without further intervention - assuming I have scripted properly.


Still monitoring?

Explore More ContentExplore courses, solutions, and other research materials related to this topic.