Система архивации данных windows server 2008 r2 удаление старых копий

A client uses Windows Server Backup to back up a small Hyper-V server running Windows Server 2008 R2. Today free space on the backup drive F: dropped below 100GB of 698GB, triggering a 15% monitoring threshold. Some quick notes on what I did.

Research

Review this Microsoft blog post:

Backup Version and Space Management in Windows Server Backup

List shadow copies:

wbadmin get versions -backupTarget:f:
vssadmin list shadows /for=f:

Delete Old Shadow Copies

Delete 5 oldest shadow copies on the target volume:

diskshadow
delete shadows oldest f:
delete shadows oldest f:
delete shadows oldest f:
delete shadows oldest f:
delete shadows oldest f:

That freed up about 4.5GB per shadow copy, so now 122GB free (17%), 175GB in shadow copies. I could delete more—there must be 20 left.

No System State Backups to Delete

Tried this command to delete system state backups:

wbadmin delete systemstatebackup -deleteOldest

Got this message:

Enumerating system state backups...
ERROR - No system state backups were found.
This command can be used to delete backups that only contain the system state.

So apparently that’s only needed if you’re doing separate system state backups. I do system state backups together with other backups.

Update November 17, 2012

About three hours after I did the above, free disk space fell under 15% again. By the next morning, it was 97.7GB free and 199GB in shadow copies. What? How did I drop from 122GB free to 97.7GB free in a matter of hours? I did delete the shadows while a backup was running, but should that matter? Does Windows Server Backup just use as much space as possible? I just deleted another five shadow copies, this time with no backup running, and I’m back to 126GB free and 171GB in shadow copies. We’ll see what happens.

Update November 19, 2012

Two days and two backups later, the F: drive is showing 115GB (16.5%) free and 187GB in shadow copies. Better.

Update January 17, 2013

2012 Essentials Issues and References

I’m having similar issues with Windows Server Backup (WSB) on Server Essentials 2012. I had a backup fail for lack of disk space, even though 61 backups were available. I had to manually delete old shadow copies to get the backup running again. More research and forum posts have turned up some additional information.

The Windows Server Backup Overview on TechNet says, “Windows Server Backup does not require user intervention to periodically delete older backups to free up disk space for newer backups—older backups are deleted automatically.” Unfortunately, that is not always the case.

Windows Server Backup automatic disk usage management, also on TechNet, explains how the auto-delete works, why it sometimes doesn’t delete enough, and why backups fail. Basically WSB always leaves 1/8 of the backup volume allocated to shadow copies, which is how it stores previous backups. If that doesn’t leave enough space for the backup (which, I’ve discovered, is not compressed), the backup fails.

Update February 26, 2013

Configure Shadow Copies

I’m trying a different approach for maintaining free space on a dedicated backup volume: Configure Shadow Copies.

1. In Disk Management, assign a drive letter to the backup drive. You probably did this already if you’ve been using wbadmin or vssadmin as described above.
2. In Windows Explorer, right-click on the drive and select Configure Shadow Copies.
3. In the Shadow Copies dialog, make sure the drive is highlighted. The Next Run Time should show Disabled.  Click on Settings.
4. Change Maximum Size from No limit to Use limit and set the value to leave about 15% of the drive free. For example, if a 100GB drive has become full using 40GB of shadow copy space, reduce the shadow copy space to a fixed 25GB to leave 15GB free.

I’ve had that set for a few days and it does seem to be maintaining 15% free space without my having to manually delete backups.

Caution I have not seen this method recommended anywhere so I can’t promise that it’s a safe approach to managing backup space. Use at your own risk!

Update April 14, 2016

To configure shadow copies on a desktop computer, you can select Control Panel > System, open System Protection, select the target drive, then click the Configure button. You’ll want to leave Restore Settings off for the backup target, but you can still adjust maximum Disk Space Usage for shadow copies on that drive.

This article mentions a couple more helpful vssadmin commands for doing the same thing. This should work on a desktop (if it’s a Pro version of Windows) or a server.

List shadow storage in use on all drives:

vssadmin list shadowstorage

Change shadow storage on one drive:

vssadmin resize shadowstorage /on=F: /for=F: /maxsize=25%

Windows

December 19, 2016December 19, 2016

1 Minute

Windows Server Backup is the built-in tool in Windows Server 2008/R2 that allows you to backup and restore files, folders, and critical system data such as the System State, entire volumes and even the full server itself.

After using it, Windows Server Backup will begin to display a log of recent backup and restore operations. This log allows the administrator to keep track of what backup and restore operations were taken on that server, and may be quite useful especially when having many people dealing with your servers.

While useful, sometimes one might want to delete or clear that list of log entries. Strangely, there’s no obvious place, button, command or checkbox you can use to clear that log.

After some digging, we found a workaround.

Clearing Windows Server Event Log

To clear the event log:

1. Open Event Viewer from the Administrative Tools folder.

2. Go to Applications and Services Logs.

3. Expand Microsoft > Windows > Backup.

4. Right click on the Operational Channel log and choose Save and Clear or just Clear in case you don’t want to save the existing log (we suggest you save the logs before clearing for any future reference).

Картинка с сайта: ismapl.wordpress.com

Картинка с сайта: ismapl.wordpress.com

Now, if you open Windows Server Backup, you’ll see that the log is empty.

Картинка с сайта: ismapl.wordpress.com

Clearing Windows Server Backup Status Catalog

Use this below command in PowerShell.

wbadmin delete catalog

Deletes the backup catalog on the local computer. Use this subcommand only if the backup catalog on this computer is corrupted and you have no backups stored at another location that you can use to restore the catalog.

Published
December 19, 2016December 19, 2016