Wishlist 0 ¥0.00

[SOLVED] Windows Server Backup - Went from 100+ copies...to 1 copy available

    • Hi everyone,

      I'm using Windows Server Backup on a Windows Server 2012 R2 system that has been in production for half a year or so.  The server has around 60GB used, and the backup drive is a 160GB external drive that I had sitting around and put it in place until they can afford a larger external drive.  The setup has been working great, and just yesterday when I opened the Windows Server Backup utility, I noticed that all backups have been successful and there were well over 100 backups available.  The external hard drive was showing "in the red" for space available, about 15GB free or so if I remember right.  But that's fine, since I understand that Windows Server Backup should delete the oldest backup available.

      ...OR...you know, it deletes everything.  So I log in today, and what do you know?  60ish GB used on the external drive, so plenty of free space.  But only 1 copy available.  Is...like...am I missing something?  Is that how it's supposed to work when the drive gets full?  I was under the impression it would delete files from the oldest snapshot and create a new backup.  Or delete several old snapshots.

      Did something happen in a recent Windows update?  Any way to fix it?  In my little bit of searching before this, I found that some others have had experiences with at least Server 2008 where Windows Server Backup would all the sudden only keep 1 copy.  So I guess I'll know tomorrow whether or not that's happening to me; whether I see "1 copy available" again, or "2 copies available".

      Thanks in advance for any advice!

      • Edited by link470 Thursday, November 27, 2014 6:25 PM
      Sunday, November 16, 2014 10:50 PM
      Avatar of link470
       
      45 Points
       
 

Answers

    • Hi,

      The backup type is changed to Full from incremental automatically?

      I checked, and it hadn't done that.  The backup was still set to Normal [Full].

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing.

      This is what I'm thinking is the most likely cause.  I ended up stopping the backup schedule for the drive that was getting I/O errors in Event Viewer and releasing the old backup drive and pulling it.  Then I added a new external backup drive and created a new nightly schedule, and that's working great.  The backup completes very quickly and is a full backup every time, using VSS for block backups so the disk space isn't all eaten up [how it always was before this incident], and the drive is now carrying multiple backups again. 

      Something just got very confused when the last backup drive had I/O errors.

      The other thing I thought was interesting this time around is that I could no longer select VSS Copy Backup.  Only VSS Full backup was selected and I couldn't find an option anywhere to change it to VSS Copy Backup.  I'm assuming either VSS Copy was removed in 2012 R2 but not in 2012, or my backup settings I chose didn't allow for that option to be shown during the wizard.  Does anyone have any insight on this?

      Note: VSS Full is fine, and is working great.  But just curious, since one 2012 server I operate is set to VSS Copy, and the other is set to VSS Full.  Both appear to work the same and I understand how it really only effects the archive bit being set, but just curious why VSS Copy didn't present itself as an option.  I've also recently updated the third large 700ish MB update for Server 2012 R2/Windows 8.1, so maybe that changed something.

      Either way, resolved!  Backup appears to be fine.  But what I'm still really curious of is what caused the backup to start only holding 1 copy.

      • Marked as answer by link470 Thursday, November 27, 2014 6:07 PM
      • Edited by link470 Thursday, November 27, 2014 6:09 PM
      Thursday, November 27, 2014 6:06 PM
      Avatar of link470
       
      45 Points
       
 

All replies

    • Hi,

      As it has been a while, whether new backup copies are created these days?

      As you said Windows Server Backup should not delete all backup at a time even it is for releasing disk space - it will not delete more than 1/8 space and if it has to, it will provide an error "no enough space" instead of just deleting all backups.

      Since you mentioned Windows Update, have you checked if any new update is installed just before the issue occurs?


      If you have any feedback on our support, please send to This email address is being protected from spambots. You need JavaScript enabled to view it..

      Thursday, November 20, 2014 5:54 AM
      Avatar of MedicalS
      (MSFT CSG)
      64,325 Points
      Moderator
 
    • Hi,

      As it has been a while, whether new backup copies are created these days?

      I've been monitoring the server in question, and the backups are still only maintaining 1 copy.  I did notice though that the "Advanced option:" in Windows Server Backup schedule settings shows up as "VSS Full Backup", instead of "VSS Copy Backup" which other Windows Server 2012 servers [not R2] are using.  VSS Full seems to only store 1 copy, and the backups take an incredibly long time to run.  What used to take 1 hour now takes more like 18 hours.

      As you said Windows Server Backup should not delete all backup at a time even it is for releasing disk space - it will not delete more than 1/8 space and if it has to, it will provide an error "no enough space" instead of just deleting all backups.

      That's what I thought, glad to know that isn't the usual behavior I'm experiencing.  I did have a look in the event viewer as well and noticed that there was I/O errors on the external drive.  So I'm wondering if that's contributing to why the backup is running so incredibly slow, and also what may have caused Windows Server Backup to delete all the previous backups.

      Since you mentioned Windows Update, have you checked if any new update is installed just before the issue occurs?

      No new updates were installed before.  The last updates would have been the October patch Tuesday, where all updates were successfully installed.  Windows Server Backup was fine after that until right up before I ran these past updates in November.  So I can't see that directly being the cause, at least not immediately taking effect. 

      My bets right now are with the external hard drive possibly failing.

      Thursday, November 20, 2014 10:34 PM
      Avatar of link470
       
      45 Points
       
 
    • Hi,

      The backup type is changed to Full from incremental automatically?

      Full Backup will take a long time - actually the first backup of an incremental backup schedule is a full backup which will also take a long time. The rest ones will be incremental so they will be finished much quicker.

      In this situation can you change the backup type to incremental again?

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing. 


      If you have any feedback on our support, please send to This email address is being protected from spambots. You need JavaScript enabled to view it..

      Thursday, November 27, 2014 6:19 AM
      Avatar of MedicalS
      (MSFT CSG)
      64,325 Points
      Moderator
 
    • Hi,

      The backup type is changed to Full from incremental automatically?

      I checked, and it hadn't done that.  The backup was still set to Normal [Full].

      And if it is caused by a corrupted hard disk, you can try to do a check disk on it first and you may need to get a disk analysis tool from the hard disk manufacturer for accurate testing.

      This is what I'm thinking is the most likely cause.  I ended up stopping the backup schedule for the drive that was getting I/O errors in Event Viewer and releasing the old backup drive and pulling it.  Then I added a new external backup drive and created a new nightly schedule, and that's working great.  The backup completes very quickly and is a full backup every time, using VSS for block backups so the disk space isn't all eaten up [how it always was before this incident], and the drive is now carrying multiple backups again. 

      Something just got very confused when the last backup drive had I/O errors.

      The other thing I thought was interesting this time around is that I could no longer select VSS Copy Backup.  Only VSS Full backup was selected and I couldn't find an option anywhere to change it to VSS Copy Backup.  I'm assuming either VSS Copy was removed in 2012 R2 but not in 2012, or my backup settings I chose didn't allow for that option to be shown during the wizard.  Does anyone have any insight on this?

      Note: VSS Full is fine, and is working great.  But just curious, since one 2012 server I operate is set to VSS Copy, and the other is set to VSS Full.  Both appear to work the same and I understand how it really only effects the archive bit being set, but just curious why VSS Copy didn't present itself as an option.  I've also recently updated the third large 700ish MB update for Server 2012 R2/Windows 8.1, so maybe that changed something.

      Either way, resolved!  Backup appears to be fine.  But what I'm still really curious of is what caused the backup to start only holding 1 copy.

      • Marked as answer by link470 Thursday, November 27, 2014 6:07 PM
      • Edited by link470 Thursday, November 27, 2014 6:09 PM
      Thursday, November 27, 2014 6:06 PM
      Avatar of link470
       
      45 Points
       
 
    • Hello,

      it took us a few weeks and lots of trial and error to figure this out.

      Despite backing up every day successfully only the previous day was restorable on one of our servers (2012) and the windows server backup GUI showed only 1 copy on the ISCSI drive. Recreating the backup from scratch (and prior deleting all shadow copies) did not help.

      It turned out the assigned space for the volume shadow service for the specific drive (drive properties) was set way too low. After increasing that amount the backup has created several copies and we could now restore more than just a single day.

      Best regards,
      complingua

      • Edited by complingua Thursday, April 13, 2017 10:43 AM
      Thursday, April 13, 2017 9:58 AM
      Avatar of complingua
      (Partner)
      0 Points
       
 
    • Similar issue here.

      A disk error caused the back up to fail several times.  Solved the disk error issue, but was only getting 1 copy available (yesterdays).

      Turns out the Advanced back up settings had been changed from VSS Copy to Full.  Restored this to VSS copy and we had the multiday copies available after that.

      rossh

      Saturday, May 06, 2017 5:57 AM
      Avatar of rossh_hm
       
      5 Points
       
 
 
 
 
 

对win2008服务器备份功能的介绍——Backup Version and Space Management in Windows Server Backup

This article answers following questions related to Windows Server Backup in Windows Server 2008 and Windows Server 2008 R2:

Q1. How does Windows Server Backup store backups and maintain backup versions?
Q2. How do I query backup stored versions on a backup storage location?
Q3. How do I delete non system state backups created using Windows Server Backup?
Q4. How do I delete system state backups created using Windows Server Backup?

Overview

  • Windows Server Backup is the built-in backup solution in Windows Server 2008 and Windows Server 2008 R2. Using Windows Server Backup, an administrator can schedule periodic backups of a server and also create backups on demand. For details on using Windows Server Backup, please see the Installed Help for Windows Server 2008 (http://technet.microsoft.com/en-us/library/cc770757(WS.10).aspx) and for Windows Server 2008 R2 (http://technet.microsoft.com/en-us/library/cc770757.aspx).
  • Windows Server Backup in Windows Server 2008 allows administrators to back up entire volumes. More flexibility is available in Windows Server 2008 R2 where administrators can pick and choose individual files and folders to be included in a backup. The technology used by Windows Server Backup to perform a backup differs based on the nature of the backup:
    • If you back up an entire volume, Windows Server Backup creates a block-level backup that reads directly from the volume by passing the file system.
    • If you back up just specific files and folders, Windows Server Backup reads individual files going through the file system.
  • Windows Server Backup stores backups at the following path: <BackupStorageLocation>WindowsImageBackup<ComputerName>. A back up operation performs following steps:
  1. Windows Server Backup reads data from source volumes and then creates a .vhd file per source volume on the backup storage location and writes the backup metadata.
  2. Windows Server Backup stores backup versions in volume shadow copies. After the data write is complete, Windows Server Backup creates a shadow copy of the volume where the backup is stored using Volume Shadow Copy Service (VSS). This shadow copy retains the state of the storage volume as a “backup version” or “point-in-time” of the backup and must restore using this backup version. VSS is the underlying Microsoft technology required for maintaining backup versions. (For more information about VSS, see http://technet.microsoft.com/en-us/library/cc785914.aspx.)
  3. After creating the shadow copy, Windows Server Backup updates the backup catalog which is stored on both the system volume of the server that is being backed up and the backup storage folder with the following information:
    • The backup time − The local system time of the server when the backup operation started.
    • The shadow copy identifier (Shadow Copy ID) − Used by Windows Server Backup to associate the backup version to the correct shadow copy.
    • Version identifier − Used by Windows Server Backup to uniquely identify a backup version. Users using command line tools (Wbadmin and the Windows PowerShell cmdlets for Windows Server Backup) will specify the version identifier as a parameter to the command to work with a backup version.
  • If the backup storage location is full, Windows Server Backup automatically deletes the oldest backup version to make space for the current backup. Since each backup is stored inside a shadow copy, deleting a backup version is accomplished by simply deleting the corresponding shadow copy. However, space for a system state backup in Windows Server 2008 is not automatically managed by Windows Server Backup. See the section “How to Delete System State Backups” below for managing system state backups in Windows Server 2008.
  • Windows Server Backup can store only one backup version on a network share (remote shared folder). You can store backups from multiple computers to a network share. A backup from a computer to a network share will be saved at: \<RemoteServer><SharedFolderPath>WindowsImageBackup<ComputerBackedUp>. To delete the backup on network share, you need to delete the <ComputerBackedUp> directory from network share.
  • Windows Server Backup uses the .vhd format for writing backups. The current virtual hard disk specification limits the size of a virtual hard disk to be 2040 GB, which can fit a volume of size 2040 GB – 2 MB, (i.e., 2088958 MB). Windows Server Backup in Windows Server 2008 also limits the maximum source volume size to be 2088958 MB. In Windows Server 2008 R2, if you are not backing up a full volume and, instead, creating a backup of selected files/folders, your source volume size can be more than 2088958 MB, provided your actual data size is less than equal to 2088958 MB. If you are creating a full volume backup, the maximum source volume size limit continues to be 2088958 MB.

How to Query Backup Versions

To see the backup versions present in a particular computer, use the Wbadmin get versions command. Note that, to use the Wbadmin command, you must be a member of the Administrators group or Backup Operators group and must open an elevated instance Cmd.exe (click Start, right-click Command Prompt, and then click Run as administrator). For detailed Wbadmin command documentation, see: http://technet.microsoft.com/en-us/library/cc754015.aspx.

Sample output of Wbadmin get versions command:

wbadmin 1.0 – Backup command-line tool

(C) Copyright 2004 Microsoft Corp.

 

Backup time: 3/12/2009 10:55 AM

Backup target: Fixed Disk labeled New Volume(I:)

Version identifier: 03/12/2009-05:25

Can recover: Volume(s), File(s)

Snapshot ID: {f5e946da-5cc7-44c3-a747-9f1079e639b0}

 

Snapshot ID in the above output is new in Windows Server 2008 R2. Snapshot ID is same as Shadow Copy ID. It corresponds to a specific backup version and can be used to delete that backup version.

 

To view all backup versions on a particular backup storage location, type:

Wbadmin get versions -backupTarget:<BackupStorageLocation:>

 

For example, if you want to view all the backup versions on the backup storage location K:, type:

Wbadmin get versions –backupTarget:K:

 

In the output of Wbadmin get versions command, Backup time is the local system time and Version Identifier is the GMT time at the time the backup was created. If you change your system time zone, the value for Backup time will also change. Note that Version Identifier is a unique identifier for a given backup version and remains constant for a backup.

 

How to Delete Non-System State Backups

Windows Server Backup deletes a backup by just deleting the corresponding shadow copy and updating the backup catalog. You can perform the same steps manually to delete backups on demand. However, the backup catalog update cannot be done manually and it will happen instead during the next backup. In short, to delete a backup version manually, you need to delete the corresponding shadow copy from the backup storage location.

To delete a shadow copy, follow these general steps:

  1. Identify the backup version you want to delete by querying the backup versions on your backup storage location.
  2. Determine the shadow copy ID of the version you want to delete.
  3. Delete the shadow copy.

 

Identify the backup version:

To list all the shadow copies on a volume, use the Vssadmin command. (For the complete syntax for Vssadmin, see: http://technet.microsoft.com/en-us/library/cc754968(WS.10).aspx.) The following command line lists all shadow copies on a specified backup storage location:

Vssadmin list shadows /for=<BackupTarget>

For example, to list the shadow copies on the location Y, type:

Vssadmin list shadows /for=Y:

Determine the shadow copy ID:

On Windows Server 2008 R2, the shadow copy ID is same as Snapshot ID given in the output of querying backups. On Windows Server 2008, you can find your backup’s shadow copy ID by looking at output of Vssadmin list shadows /for=<Backup Target>. Match the shadow copy creation time with your backup’s Backup time value.

 

Delete the Shadow Copy for the specific Shadow Copy ID:

  1. To open a command prompt with elevated privileges, click Start, right-click Command Prompt, and then click Run as administrator.

三款免费实用的本地文件夹同步/备份软件推荐 (SyncToy/FreeFileSync/Compare Advance)

Microsoft SyncToy

SyncToy 是由 微软 推出的一款免费的文件夹同步工具。虽然名字中有一个 Toy,但是大家可千万不要误以为它的功能弱爆了。实际上,我感觉这款软件还真是摆脱了微软大多数软件给人复杂和臃肿的印象,通过很简单的操作便能够完成复杂的操作,免去了大量重复的手动复制、移动操作。

 

SyncToy 支持三种同步模式:

 

  • synchronize :在这个模式下,SyncToy会使得两个文件夹完全一致,无论在哪一个文件夹中操作,对应的操作相当于都在另一个文件夹中执行了一次。(也就是我们所说的“同步”)。
  • echo:echo模式的效果是,使得在左边文件夹中新增加的和被改变的内容会被备份到右边的文件夹中。在左侧被重命名的文件以及被删除了的文件,将也会在右侧的文件夹中删除。(这种模式与synchronize 很像,差别就在于这里只会从左边同步到右边,右边的操作对左边的文件夹无效~)。
  • Contribute :也就是我们常说的“增量备份”,相当于在echo的基础上,把所有的删除操作都屏蔽掉了,只要在左边文件夹中存在过的文件都会在右侧文件夹中存在。

相信上面这三种模式已经能够满足大多数人的需求了。对于 Microsoft SyncToy,一句话:简单+实用。

FreeFileSync

一听 FreeFileSync 这个名字就知道这又是一款免费的文件同步软件了(并且也是开源的哦)。而且这款软件也非常绿色,虽然需要下载安装包,但是在安装的时候可以选择便携模式安装。程序运行之后,(虽然界面有些丑陋……)选择两个文件夹,首先进行的是比较操作,可以非常直观地看出文件夹之间的差异(可以 选择根据 文件内容 来判定而不是文件名)。而且我倒是觉得通过文件内容判定不同的话,这个软件还可以用来对两个不同版本的项目中,哪些代码文件做了修改之类的进行对比分析。

 

除了 SyncToy 中提到的那三种同步的模式以外,FreeFileSync 还提供了自定义功能,可以用户根据自己的需要更加灵活地自定义操作,赞~

 

Compare Advance

其实 Compare Advance 官方对它的定义更加倾向于文件夹对比工具而不是文件夹同步,利用Compare Advance可以非常方便地找出两个文件夹中哪些文件是哪些文件是A(或者B)文件夹特有的,哪些是共有的,哪些是不同的,生成的信息图以及数据非常详细。对于一些需要做大量文件分析的工作的人来说,这个可是利器呀~

 

 

当然,既然分析得都如此彻底了,那么进行同步操作也无非就是一个命令的事情, Compare Advance 的同步功能也很强大,按 Ctrl + Y 就可以在分析之后调出同步面板,在这里也可以设置同步的模式,也很方便。

写在后面:

虽然现在使用各种云端网盘备份文件已经很方便了,但是在一些不能上网的场合,或是一些敏感的不放心摆到互联网上去的文件(这些文件中很多又是重要的),还是在本地多建立备份会比较好,而那样的话,上面介绍的这几个软件就很适合你了~好了,说了这么多相信你心中也有了比较中意的那款软件了吧:) Enjoy吧!

用Macallan Mail Solution配置邮件服务器

 

基本上我们只需要操作2个页也就足够了,分别是:User Settings和Domains Names.

在Domains Names内输入域名,也就是邮箱的@符号右边的那一撮东西。比如“用户名@sina.com”,那域名就是sina.com了。我是偷懒,直接把主机IP当域名。。。

域名的操作界面:

 

改好域名接下来就是STMP和用户名了。进入User Settings页面。

这里分了4个用户组,熟悉WINDOWS权限的朋友应该了解这些是什么意思。基本上就是用户的权限高低区别了。因为是内部邮箱,所以也不用太讲究,我选择在ANTISPAM里创建用户和STMP。

User Settings页面如下:

 

这里也没什么操作内容,选中你要创建用户的组,然后点屏幕下方的按钮就能创建响应的项目。

这里我就创建个SMTP和邮箱用户就行了。

SMTP么就是邮箱里的发送邮件服务器,这里我继续用主机Ip。。。。

用户名就是邮箱名@左边的东西啦。比如This email address is being protected from spambots. You need JavaScript enabled to view it..0.1中,xylon就是用户名了。想设置密码的时候,在创建好的用户名左侧有个+号键,点开,在钥匙形状的那一栏填上密码就行了。

好了,现在基本上邮箱设置完了。我这里是用FOXMAIL的。设置如下:

用户邮箱:This email address is being protected from spambots. You need JavaScript enabled to view it..0.1

stmp:192.168.0.1

pop3:192.168.0.1

然后验证一下能否通信,全部通过之后就能正常使用啦。

 

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.