wbadmin get versions
You could enter the following to get information on recoverable backups stored on the F drive:
wbadmin get versions -backupTarget: f:
Or you could enter the following to get information on recoverable backups stored on the F drive on Server96:
wbadmin get versions -backupTarget: f: -machine: server96
Many Wbadmin commands use the -backupTarget and -machine parameters. The backup target is the storage location with which you want to work and can be expressed as a local volume name, such as F:, or as a network share path, such as \\FileServer32\backups\Server85. The -machine parameter identifies the computer you want to work with for backup or recovery operations.
Working with Wbadmin commands
You use Wbadmin commands to manage the backup configuration of your servers. These commands work with a specific set of parameters. The following sections provide an overview of the available commands and their most commonly used syntaxes.
Using general-purpose commands
The following general-purpose commands are provided for getting information about backups and the system with which you are working:
■ GET DISKS Lists the disks that are currently online for the local computer. Disks are listed by manufacturer name, type, disk number, GUID, total space, used space, and associated volumes.
wbadmin get disks
■ GET ITEMS Lists items contained in a specified backup.
wbadmin get items -version: VersionIdentifier
[-backupTarget:{VolumeName | NetworkSharepath}] [-machine: BackupMachineName]
■ GET STATUS Reports the status of the currently running backup or recovery job.
wbadmin get status
■ GET VERSIONS Lists details about the available backups stored in a specific location, including the backup time and backup destination.
wbadmin get versions [-backupTarget:{VolumeName | NetworkSharepath}]
[-machine: BackupMachineName]
Using backup management commands
You can manage backups and their configurations by using the following commands and command-line syntaxes:
■ DELETE SYSTEMSTATEBACKUP Deletes the system state backup or backups from a specified location.
wbadmin delete systemstateBackup [-backupTarget:{VolumeName}]
[-machine: BackupMachineName]
[-keepVersions: NumberOfBackupsToKeep | -version: VersionIdentifier |
— deleteOldest]
[-quiet]
■ DISABLE BACKUP Disables scheduled daily backups so that they no longer run.
wbadmin disable backup [-quiet]
■ ENABLE BACKUP Enables or modifies a scheduled daily backup.
wbadmin enable backup [-addTarget:{BackupTargetDisk}]
[-removeTarget:{BackupTargetDisk}]
[-schedule: TimeToRunBackup]
[-include: VolumesToInclude]
[-allCritical]
[-quiet]
■ START BACKUP Starts a one-time backup by using the specified parameters. If no parameters are passed and scheduled backups are enabled, the backup uses the settings for scheduled backups.
wbadmin start backup [-backupTarget:{TargetVolume |
TargetNetworkShare}]
[-include: VolumesToInclude]
[-allCritical]
[-noVerify]
[-user: username]
[-password: password]
[-inheritAcclass="underline" InheritAcl]
[-vssFull]
[-quiet]
■ STOP JOB Stops the currently running backup or recovery job. Stopped jobs cannot be restarted from where they were stopped.
wbadmin stop job [-quiet]
Using recovery management commands
You can recover your computers and data by using the following commands and command-line syntaxes:
■ START RECOVERY Initiates a recovery of volumes, applications, or files by using the specified parameters:
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]
■ START SYSTEMSTATEBACKUP Starts a system state backup by using the
options specified:
wbadmin start systemstateBackup -backupTarget:{VolumeName}
[-quiet]
■ START SYSTEMSTATERECOVERY Starts a system state recovery by using the specified parameters:
wbadmin start systemstateRecovery -version: VersionIdentifier
— showSummary
[-backupTarget:{VolumeName | NetworkSharePath}]
[-machine: BackupMachineName]
[-recoveryTarget: TargetPathForRecovery]
[-authSysvol]
[-quiet]
Performing server backups
As part of your planning for each server you intend to back up, you should consider which volumes you want to back up and whether backups will include system-state recovery data, application data, or both. Although you can manually back up to shared volumes and DVD media, you need a separate, dedicated hard disk for running scheduled backups. After you configure a disk for scheduled backups, the backup utilities automatically manage the disk usage and automatically reuse the space of older backups when creating new backups. After you schedule backups, you need to check periodically to ensure that backups are being performed as expected and that the backup schedule meets current needs.
When you create or schedule backups, you need to specify the volumes you want to include, and this affects the ways you can recover your servers and your data. You have the following options:
■ Full server (all volumes with application data) Back up all volumes with application data if you want to be able to fully recover a server, along with its system state and application data. Because you are backing up all files, the system state, and application data, you should be able to fully restore your server by using only the Windows backup tools.