text stringlengths 0 4.23k |
|---|
-overwrite |
Valid only when recovering files. Specifies the action to take when a file that is being recovered already exists in the same location. The valid options are: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 modified.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 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 you are recovering to for bad cluster information. If you are recovering to an alternate server or hardware, we recommend that you don't 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.Important: Until you run chkdsk /b, the bad clusters reported on your recovered system might not be accurate. |
-noRollForward |
Valid only when recovering apps. Allows for previous point-in-time recovery of an app if you select the latest version from the backups. Previous point-in-time recovery is done as the default for all other non-latest versions of the app. |
-quiet |
Runs the command without prompts to the user. |
Important: Until you run chkdsk /b, the bad clusters reported on your recovered system might not be accurate. |
Remarks |
To view a list of items available to recover from a specific backup version, run the wbadmin get items command. If a volume didn't have a mount point or drive letter at the time of backup, then this command returns a GUID-based volume name that should be used for recovering the volume. |
If you use a value of ADIFM to perform an install from media operation to recover 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. |
Examples |
To run a recovery of the backup from March 31, 2020, taken at 9:00 A.M., of volume d:, type: |
wbadmin start recovery -version:03/31/2020-09:00 -itemType:Volume -items:d: |
To run a recovery to drive d of the backup from March 31, 2020, taken at 9:00 A.M., of the registry, type: |
wbadmin start recovery -version:03/31/2020-09:00 -itemType:App -items:Registry -recoverytarget:d:\ |
To run a recovery of the backup from March 31, 2020, taken at 9:00 A.M., of the d:\folder and folders subordinate to d:\folder, type: |
wbadmin start recovery -version:03/31/2020-09:00 -itemType:File -items:d:\folder -recursive |
To run a recovery of the backup from March 31, 2020, taken at 9:00 A.M., of the volume \\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\, type: |
\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\ |
wbadmin start recovery -version:03/31/2020-09:00 -itemType:Volume -items:\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\ |
To run a recovery of the backup from April 30, 2020, taken at 9:00 A.M., of the shared folder \\servername\share from server01, type: |
\\servername\share |
wbadmin start recovery -version:04/30/2020-09:00 -backupTarget:\\servername\share -machine:server01 |
wbadmin start sysrecovery |
Performs a system recovery (bare metal recovery) using your specified parameters. |
To perform a system recovery using this command, you must be a member of the Backup Operators group or the Administrators group, or you must have been delegated the appropriate permissions. |
Important |
The wbadmin start sysrecovery command must be run from the Windows Recovery Console, and isn't listed in the default usage text for the wbadmin tool. For more information, see Windows Recovery Environment (WinRE). |
Syntax |
wbadmin start sysrecovery -version:<VersionIdentifier> -backupTarget:{<BackupDestinationVolume> | <NetworkShareHostingBackup>} [-machine:<BackupMachineName>] [-restoreAllVolumes] [-recreateDisks] [-excludeDisks] [-skipBadClusterCheck] [-quiet] |
Parameters |
Parameter |
Description |
-version |
Specifies the version identifier of the backup to recover in MM/DD/YYYY-HH:MM format. If you don't know the version identifier, run the wbadmin get versions command. |
-backupTarget |
Specifies the storage location that contains the backup(s) you want to recover. This parameter is useful when the storage 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 must be used when the -backupTarget parameter is specified. The -machine parameter is useful when multiple computers have been backed up to the same location. |
-restoreAllVolumes |
Recovers all volumes from the selected backup. If this parameter is not specified, only critical volumes (volumes that contain the system state and operating system components) are recovered. This parameter is useful when you need to recover non-critical volumes during system recovery. |
-recreateDisks |
Recovers a disk configuration to the state that existed when the backup was created.Warning: This parameter deletes all data on volumes that host operating system components. It might also delete data from data volumes. |
-excludeDisks |
Valid only when specified with the -recreateDisks parameter and must be input as a comma-delimited list of disk identifiers (as listed in the output of the wbadmin get disks command). Excluded disks aren't partitioned or formatted. This parameter helps preserve data on disks that you don't want modified during the recovery operation. |
-skipBadClusterCheck |
Valid only when recovering volumes. Skips checking the disks you are recovering to for bad cluster information. If you are recovering to an alternate server or hardware, we recommend that you don't 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.Important: Until you run chkdsk /b, the bad clusters reported on your recovered system might not be accurate. |
-quiet |
Runs the command without prompts to the user. |
Warning: This parameter deletes all data on volumes that host operating system components. It might also delete data from data volumes. |
Important: Until you run chkdsk /b, the bad clusters reported on your recovered system might not be accurate. |
Examples |
To start recovering the information from the backup that was run on March 31, 2020 at 9:00 A.M., located on drive d:, type: |
wbadmin start sysrecovery -version:03/31/2020-09:00 -backupTarget:d: |
To start recovering the information from the backup that was run on April 30, 2020 at 9:00 A.M., located in the shared folder \\servername\share for server01, type: |
\\servername\share |
wbadmin start sysrecovery -version:04/30/2020-09:00 -backupTarget:\\servername\share -machine:server01 |
wbadmin start systemstatebackup |
Creates a system state backup of the local computer and stores it on the location specified. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.