Vacuum Disk Safes

!DiskSafe_Compaction.png|width=300!



{note:title=Notice}
Because the vacuum routines are I/O intensive, only one vacuum task should be executed at one time.
{note}

h3. {color:#000000}{*}About Vacuuming{*}{color}

The Disk Safe has a fixed size of 32 KB pages. The pages are indexed using B-Trees and each page is packed with block-level deltas. As you merge old recovery points, some deltas can be discarded.

Deltas can be discarded when merging an old recovery point into a newer one when any one of the following conditions are met:

1. The file system (e.g., NTFS or Ext4) is no longer using the block (you will likely have deleted some files and the associated blocks may not all have been re-used by the O/S).

2. The block has become overwritten (you changed a file).

3. You have re-sized your file system to make it smaller, and the blocks are simply no longer used.

When you merge old or unwanted recovery points, it is normal for the on-disk size of the Disk Safe files to not change or get smaller. Normally, this is not an issue and you can let the Disk Safe manage its on-disk footprint, automatically reusing the freed storage for new block-level deltas.

If you delete a device or disk volume from the Disk Safe, its space is automatically deleted because each disk has its own block-level delta store ({{.db}} file). When you delete a disk from the Disk Safe, this file is deleted.

h4. When to Vacuum

If one of the following events occur and you need to save as much disk space as possible, then you may want to consider vacuuming your Disk Safe:

1. You deleted a large number of recovery points. For example, you used to keep the last 100 Recovery Points but now only keep 5.

2. You greatly reduced the amount of files or data you are replicating. Maybe you protected the whole {{C:}} previously, and you now have changed your policy so that you exclude {{C:\Windows}} and another large directory, and the old Recovery Points still containing the folders you excluded have been merged away. Another example is that your {{D:}} drive had 100 GB of files on it but now only contains 10 GB.

When any of these events occur, there may be a lot of empty, unused space in the Disk Safe {{.db}} files. You can use the "vacuum" action on Disk Safes to shrink the on-disk footprint of the Disk Safe {{.db}} files.

When you run a vacuum, the Disk Safe is taken offline, meaning the Disk Safe cannot be used by policies or for restores. The vacuum attempts to shrink the Disk Safe {{.db}} files as much as possible by relocating empty pages to the end of the file and full or partially filled pages to the front of the file. At the end, the file is truncated by the number of empty pages that existed in the {{.db}} file.

h4. How to Vacuum Disk Safes

Follow the instructions below to vacuum a Disk Safe in Server Backup.

1. Click *Settings* and then *Disk Safes* in the Main Menu to access the _Disk Safes_ screen.

2. On the _Disk Safes_ screen, find the Disk Safe you need, click the corresponding _Actions_ icon, and select *Vacuum*. !VacuumDiskSafe-Resized.png|border=1!


3. A warning window displays. Confirm your request to vacuum the selected Disk Safe by clicking the *Vacuum* button.
!VacuumWarning.png|border=1!

4. The Vacuum process begins. The _Details for Vacuum_ window displays with the vacuum process summary. !VacuumSummary.png|border=1!


The following tabs can also be accessed in the _Details for Vacuum_ window:
* *Alerts*. Displays vacuum alerts. 
* *Logs*. Displays the log messages for the vacuum task. You can also download the log messages on this tab using the *Download Log Messages* button.
* *Task*. Displays additional vacuum task details, such as the task ID, date and time, etc.
{info:title=Tip}The Task results can be sent via email as a Report. See [ServerBackupManager:Reports].
{info}

{excerpt:hidden=true}
Instructions on how to vacuum a Disk Safe in Server Backup Manager.{excerpt}