Code:
C:\Windows\system32>wbAdmin start recovery ?
wbadmin 1.0 - Backup command-line tool
(C) Copyright 2004 Microsoft Corp.
ERROR - Command syntax incorrect. Error: ?. See the command
syntax below.
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]
Description: Runs a recovery operation based on the parameters that you
specify.
To use this command, you must be a member of the Backup Operators group
or Administrators group.
Parameters:
-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
File.
-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
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 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
accurate.
-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.
Examples:
WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:Volume -items:d:
WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:App
-items:Registry -recoverytarget:d:\
WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:File
-items:d:\folder -recursive
WBADMIN START RECOVERY -version:03/31/2005-09:00 -itemType:Volume
-items:\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\
WBADMIN START RECOVERY -version:04/30/2005-09:00 -backupTarget:\\servername
\share -machine:server01
Remarks: To view a list of items available 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 command
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 (IFM) 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.
C:\Windows\system32>