Wishlist 0 ¥0.00

Wbadmin start backup

Applies To: Windows Server 2008, Windows Server 2008 R2, Windows Vista

Creates a backup using specified parameters. If no parameters are specified and you have created a scheduled daily backup, this subcommand creates the backup by using the settings for the scheduled backup. If parameters are specified, it creates a Volume Shadow Copy Service (VSS) copy backup and will not update the history of the files that are being backed up.

To create a one-time backup 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
 
 

Syntax for Windows°Vista and Windows Server 2008:

 
 
wbadmin start backup
[-backupTarget:{<BackupTargetLocation> | <TargetNetworkShare>}]
[-include:<VolumesToInclude>]
[-allCritical]
[-noVerify]
[-user:<UserName>]
[-password:<Password>]
[-noinheritAcl]
[-vssFull]
[-quiet]

Syntax for Windows°7 and Windows Server 2008 R2:

 
 
Wbadmin start backup
[-backupTarget:{<BackupTargetLocation> | <TargetNetworkShare>}]
[-include:<ItemsToInclude>]
[-nonRecurseInclude:<ItemsToInclude>]
[-exclude:<ItemsToExclude>]
[-nonRecurseExclude:<ItemsToExclude>]
[-allCritical]
[-systemState]
[-noVerify]
[-user:<UserName>]
[-password:<Password>]
[-noInheritAcl]
[-vssFull | -vssCopy] 
[-quiet]
Parameters
 
 

 

Parameter Description

-backupTarget

Specifies the storage location for this backup. Requires a hard disk drive letter (f:), a volume GUID-based path in the format of \\?\Volume{GUID}, or a Universal Naming Convention (UNC) path to a remote shared folder (\\<servername>\<sharename>\). By default, the backup will be saved at: \\<servername>\<sharename>\WindowsImageBackup\<ComputerBackedUp>\.

ImportantImportant
If you save a backup to a remote shared folder, that backup will be overwritten if you use the same folder to back up the same computer again. In addition, if the backup operation fails, you may end up with no backup because the older backup will be overwritten, but the newer backup will not be usable. You can avoid this by creating subfolders in the remote shared folder to organize your backups. If you do this, the subfolders will need twice the space as the parent folder.

 

 

-include

For Windows°Vista and Windows Server 2008, specifies the comma-delimited list of volume drive letters, volume mount points, or GUID-based volume names to include in the backup. This parameter should be used only when the -backupTarget parameter is used.

For Windows°7 and Windows Server 2008 R2, specifies the comma-delimited list of items to include in the backup. You can include multiple files, folders, or volumes. Volume paths can be specified using volume drive letters, volume mount points, or GUID-based volume names. If you use a GUID-based volume name, it should be terminated with a backslash (\). You can use the wildcard character (*) in the file name when specifying a path to a file. Should be used only when the -backupTarget parameter is used.

-exclude

For Windows°7 and Windows Server 2008 R2, specifies the comma-delimited list of items to exclude from the backup. You can exclude files, folders, or volumes. Volume paths can be specified using volume drive letters, volume mount points, or GUID-based volume names. If you use a GUID-based volume name, it should be terminated with a backslash (\). You can use the wildcard character (*) in the file name when specifying a path to a file. Should be used only when the -backupTarget parameter is used.

-nonRecurseInclude

For Windows°7 and Windows Server 2008 R2, specifies the non-recursive, comma-delimited list of items to include in the backup. You can include multiple files, folders, or volumes. Volume paths can be specified using volume drive letters, volume mount points, or GUID-based volume names. If you use a GUID-based volume name, it should be terminated with a backslash (\). You can use the wildcard character (*) in the file name when specifying a path to a file. Should be used only when the -backupTarget parameter is used.

-nonRecurseExclude

For Windows°7 and Windows Server 2008 R2, specifies the non-recursive, comma-delimited list of items to exclude from the backup. You can exclude files, folders, or volumes. Volume paths can be specified using volume drive letters, volume mount points, or GUID-based volume names. If you use a GUID-based volume name, it should be terminated with a backslash (\). You can use the wildcard character (*) in the file name when specifying a path to a file. Should be used only when the -backupTarget parameter is used.

-allCritical

Specifies that all critical volumes (volumes that contain operating system's state) be included in the backups. This parameter is useful if you are creating a backup for bare metal recovery. It should be used only when -backupTarget is specified, otherwise the command will fail. Can be used with the -include option.

TipTip
The target volume for a critical-volume backup can be a local drive, but it cannot be any of the volumes that are included in the backup.

 

 

-systemState

For Windows°7 and Windows Server 2008 R2, creates a backup that includes the system state in addition to any other items that you specified with the -include parameter. The system state contains boot files (Boot.ini, NDTLDR, NTDetect.com), the Windows Registry including COM settings, the SYSVOL (Group Policies and Logon Scripts), the Active Directory and NTDS.DIT on Domain Controllers and, if the certificates service is installed, the Certificate Store. If your server has the Web server role installed, the IIS Metadirectory will be included. If the server is part of a cluster, Cluster Service information will also be included.

-noVerify

Specifies that backups saved to removable media (such as a DVD) are not verified for errors. If you do not use this parameter, backups saved to removable media are verified for errors.

-user

If the backup is saved to a remote shared folder, specifies the user name with write permission to the folder.

-password

Specifies the password for the user name that is provided by the parameter -user.

-noInheritAcl

Applies the access control list (ACL) permissions that correspond to the credentials provided by the -user and -password parameters to \\<servername>\<sharename>\WindowsImageBackup\<ComputerBackedUp>\ (the folder that contains the backup). To access the backup later, you must use these credentials or be a member of the Administrators group or the Backup Operators group on the computer with the shared folder. If -noInheritAcl is not used, the ACL permissions from the remote shared folder are applied to the <ComputerBackedUp> folder by default so that anyone with access to the remote shared folder can access the backup.

-vssFull

Performs a full back up using the Volume Shadow Copy Service (VSS). All files are backed up, each file's history is updated to reflect that it was backed up, and the logs of previous backups may be truncated. If this parameter is not used wbadmin start backup makes a copy backup, but the history of files being backed up is not updated.

CautionCaution
Do not use this parameter if you are using a product other than Windows Server Backup to back up applications that are on the volumes included in the current backup. Doing so can potentially break the incremental, differential, or other type of backups that the other backup product is creating because the history that they are relying on to determine how much data to backup might be missing and they might perform a full backup unnecessarily.

 

 

-vssCopy

For Windows 7 andWindows Server 2008 R2, performs a copy backup using VSS. All files are backed up but the history of the files being backup up is not updated so you preserve the all the information on which files where changed, deleted, and so on, as well as any application log files. Using this type of backup does not affect the sequence of incremental and differential backups that might happen independent of this copy backup. This is the default value.

WarningWarning
A copy backup cannot be used for incremental or differential backups or restores.

 

 

-quiet

Runs the subcommand with no prompts to the user.

Examples
 
 

The following examples show how the wbadmin start backup command can be used in different backup scenarios:

Scenario #1

  • Create a backup of volumes e:, d:\mountpoint, and \\?\Volume{cc566d14-4410-11d9-9d93-806e6f6e6963}

  • Save the backup to volume f:

 
 
wbadmin start backup -backupTarget:f: -include:e:,d:\mountpoint,\\?\Volume{cc566d14-44a0-11d9-9d93-806e6f6e6963}\

Scenario #2

  • Perform a one-time backup of f:\folder1 and h:\folder2 to volume d:.

  • Backup the system state

  • Make a copy backup so that the normally scheduled differential backup is not impacted.

 
 
wbadmin start backup –backupTarget:d: -include:g\folder1,h:\folder2 –systemstate -vsscopy

Scenario #3

  • Perform a one-time backup of d:\folder1 that should be backed up non-recursively.

  • Backup the folder to the network location \\backupshare\backup1

  • Restrict access to the backup to members of the Administrators or Backup Operators group.

 
 
wbadmin start backup –backupTarget: \\backupshare\backup1 -noinheritacl -nonrecurseinclude:d:\folder1

What is the difference between VSS Full Backup and VSS Copy Backup in Windows Server 2008?

We sometimes get people asking about the difference between VSS Full Backup and VSS Copy Backup in Windows Server 2008.

 

Basically, for certain applications (such as Exchange), VSS Copy Backup preserves logs and VSS Full Backup truncate logs. Yes, we know, this explanation is not very enlightening per se…

 

The point is that some applications create log files. For example, Exchange server creates a transaction log file. If you are using only Windows Server Backup to protect the applications, you can use any option to backup the data. However, if you are using a third party backup application, you should not use VSS Full Backup because it will delete the logs at the end of the backup. If the third party backup application relies on those logs to take incremental backups, it would take full backups all the time – a less than optimal situation…

 

So, when you do a VSS full backup, you create backup of all the files – but after that, the backup application may truncate logs on the file system.

 

On the other hand, when you do a VSS copy backup, all files are backed up and you preserve the all the applications files including log files on the live system. That means, you do preserve information on which files where changed, deleted, etc, and this will not affect the sequence of incremental and differential that might happen independent of the copy backup. Therefore, a copy backup cannot be used as a starting point for incremental/differential backups/restores.

 

Just a final technical note: The backup type (full, copy, incremental) can be specified by a VSS-based backup application at the beginning of the backup session, using the IVssBackupComponents::SetBackupState. In response to that, any application that implements a VSS writer can choose to truncate the logs in the OnBackupComplete VSS event. This is one of the last events that a VSS-based backup application (such as DPM) sends to all affected writer at the end of the backup session.

Windows Server Backup

删除Windows Server Backup控制台上操作历史记录

首先在命令行状态运行Wbadmin delete catalog删除记录,然后打开事件查看器,打开BACKUP事件,清除所有事件,再打开Windows Server Backup控制台就没有备份还原历史记录了。最后可以删除备份文件夹了。

删除Windows Server Backup创建的含有其他文件的备份副本

参考网址:http://bbs.51cto.com/thread-1032029-1.html

经过微软确认,Windows Server 2008 R2的wbadmin的删除功能,确实只能用于纯system state备份的删除。如果包含其他backup,则不能用这个命令删除。换句话说,使用-allCritical参数备份的,wbadmin不能删除。

每次运行Windows Server Backup备份,程序除了创建WindowsImageBackup目录下的备份文件并产生一个快照ID外,由于是通过VSS程序,所以还会在System Volume Information目录下创建一个卷影副本文件,且二者的ID号相同。

diskshadow删除的是卷影副本,备份副本并没有删除。简单的说,通过diskshadow删除的只是目标卷下System Volume Information目录下的卷影副本文件,而备份文件夹WindowsImageBackup下的文件,diskshadow是不会删除的。

删除记录或卷影副本后,WindowsImageBackup目录下的备份文件可以手动删除。

微软官方资料:http://blogs.technet.com/b/filecab/archive/2009/06/22/backup-version-and-space-management-in-windows-server-backup.aspx

相关命令

vssadmin list shadows
diskshadow
delete shadows all
exit
wbadmin delete catalog
wbadmin start backup -allCritical -backuptarget:e:
wbadmin get versions
wbadmin delete systemstatebackup -keepversion:0

注:2012 的 wbadmin 删除属性多了一个 -backup 参数,用这个参数可以删除备份。

删除windows server backup备份

C:\>Wbadmin delete catalog
wbadmin 1.0 - 备份命令行工具
(C) 版权所有 2004 Microsoft Corp.
您确定要删除备份编录吗? 如果删除该编录,
将需要创建一组新的备份。
[Y] 是 [N] 否 y
已成功删除备份编录。

About Us

Since 1996, our company has been focusing on domain name registration, web hosting, server hosting, website construction, e-commerce and other Internet services, and constantly practicing the concept of "providing enterprise-level solutions and providing personalized service support". As a Dell Authorized Solution Provider, we also provide hardware product solutions associated with the company's services.
 

Contact Us

Address: No. 2, Jingwu Road, Zhengzhou City, Henan Province

Phone: 0086-371-63520088 

QQ:76257322

Website: 800188.com

E-mail: This email address is being protected from spambots. You need JavaScript enabled to view it.