Wbadmin start recovery
Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Server 2012 R2, Windows Server 2012, Windows 8
Runs a recovery operation based on the parameters that you specify.
To perform a recovery with this subcommand, you must be a member of the Backup Operators group or the Administrators group, or you must have been delegated the appropriate permissions. In addition, you must run wbadmin from an elevated command prompt. (To open an elevated command prompt, click Start, right-click Command Prompt, and then click Run as administrator.)
For examples of how to use this subcommand, see Examples.
Syntax
wbadmin start recovery
-version:<VersionIdentifier>
-items:{<VolumesToRecover> | <AppsToRecover> | <FilesOrFoldersToRecover>}
-itemtype:{Volume | App | File}
[-backupTarget:{<VolumeHostingBackup> | <NetworkShareHostingBackup>}]
[-machine:<BackupMachineName>]
[-recoveryTarget:{<TargetVolumeForRecovery> | <TargetPathForRecovery>}]
[-recursive]
[-overwrite:{Overwrite | CreateCopy | Skip}]
[-notRestoreAcl]
[-skipBadClusterCheck]
[-noRollForward]
[-quiet]
Parameters
Parameter |
Description |
||
|---|---|---|---|
-version |
Specifies the version identifier 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.
|
||
-itemtype |
Specifies type of items to recover. Must be Volume, App, or File. |
||
-backupTarget |
Specifies the storage location that contains the backup that you want to recover. This 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. This parameter is useful when multiple computers have been backed up to the same location. It should be used when the -backupTarget parameter 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 in 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.
|
||
-notRestoreAcl |
Valid only when recovering files. Specifies to not restore the security access control lists (ACLs) of the files being recovered from the 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 that you do not use 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.
|
||
-noRollForward |
Valid only when recovering applications. Allows for previous point-in-time recovery of an application 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 as the default. |
||
-quiet |
Runs the subcommand with no prompts to the user. |
.jpeg)
ImportantRemarks
To view a list of items that are available for recovery from a specific backup version, use wbadmin get items. If a volume did not have a mount point or drive letter at the time of backup, then this subcommand would return a GUID-based volume name that should be used for recovering the volume.
When the -itemtype is App, you can use a value of ADIFM for -item to perform an install from media operation to recover all the related data needed for Active Directory Domain Services. ADIFM creates a copy of the Active Directory database, registry, and SYSVOL state, and then saves this information in the location specified by -recoveryTarget. Use this parameter only when -recoveryTarget is specified.
Note
Before using wbadmin to perform an install from media operation, you should consider using the ntdsutil command because ntdsutil only copies the minimum amount of data needed, and it uses a more secure data transport method.
Examples
To run a recovery of the backup from March 31, 2013, taken at 9:00 A.M., of volume d:, type:
wbadmin start recovery -version:03/31/2013-09:00 -itemType:Volume -items:d:
To run a recovery to drive d of the backup from March 31, 2013, taken at 9:00 A.M., of the registry, type:
wbadmin start recovery -version:03/31/2013-09:00 -itemType:App -items:Registry -recoverytarget:d:\
To run a recovery of the backup from March 31, 2013, taken at 9:00 A.M., of the d:\folder and folders subordinate to d:\folder, type:
wbadmin start recovery -version:03/31/2013-09:00 -itemType:File -items:d:\folder -recursive
To run a recovery of the backup from March 31, 2013, taken at 9:00 A.M., of the volume \\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\, type:
wbadmin start recovery -version:03/31/2013-09:00 -itemType:Volume
-items:\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\
To run a recovery of the backup from April 30, 2013, taken at 9:00 A.M., of the shared folder \\servername\share from server01, type:
wbadmin start recovery -version:04/30/2013-09:00 -backupTarget:\\servername\share -machine:server01
Additional references
Start-WBFileRecovery cmdlet
Start-WBHyperVRecovery cmdlet
Start-WBSystemStateRecovery cmdlet
Start-WBVolumeRecovery cmdlet