{page-title}
The Server Backup Manager offers two cleanup methods that can be used to maintain Disk Safe size and performance. They work in similar ways, but have different considerations, and produce different results.
This quick guide is meant to help you decide which disk safe cleanup method is best for you.
h1. {color:windowtext}Vacuum{color}{color:windowtext} {color}
----
{color:windowtext}{*}Full Vacuum guide available{*}{color} {color:windowtext}*[here|ServerBackupManager:Vacuum Disk Safes]*{color}{color:windowtext}.{color}
{color:windowtext}{*}{+}What it does:+{*}{color}{color:windowtext} {color}
{color:windowtext}The Vacuum task removes free pages from the disk safe, by moving full and partially used pages to the front of the file, and truncating the file at the point free pages begin. It removes unused space and shrinks the Disk Safe file.{color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to use it:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Vacuum should only be used if a Disk Safe has grown to a large size, and freeing up disk space is the top concern. {color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to avoid it:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Vacuum should not be used to increase Disk Safe performance. Vacuuming a disk safe one or more times can increase fragmentation, and result in a performance reduction.{color}{color:windowtext} {color}
h1. Compaction
----
*Full Compaction guide available* *[here|ServerBackupManager:Compact Disk Safes]**.*{color:windowtext} {color}
{color:windowtext}{*}{+}What it does:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Compaction makes a copy of your Disk Safe which replaces the original. During the copy process, free pages are removed to reduce the Disk Safe footprint, and the blocks are re-ordered to help improve backup and restore performance.{color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to use it{+}{*}{color}{color:windowtext}{*}+ :+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Compaction is most effective on Disk Safes where backup and restore performance has gradually decreased over time. Disk Safes that have had hundreds or thousands of backups stored and merged out of them over time are good candidates for Compaction. {color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to avoid it :+{*}{color}{color:windowtext} {color}
* {color:windowtext}Compaction tasks are I/O intensive. Avoid compacting during peak backup hours when system resources are most needed to complete scheduled replication tasks. {color}{color:windowtext} {color}
* {color:windowtext}Compaction makes a full copy of the Disk Safe. Avoid using it on systems with low available free space. {color}
* Compaction can take many hours or even days to complete on larger Disk Safes. Do not expect instant results.
The Server Backup Manager offers two cleanup methods that can be used to maintain Disk Safe size and performance. They work in similar ways, but have different considerations, and produce different results.
This quick guide is meant to help you decide which disk safe cleanup method is best for you.
h1. {color:windowtext}Vacuum{color}{color:windowtext} {color}
----
{color:windowtext}{*}Full Vacuum guide available{*}{color} {color:windowtext}*[here|ServerBackupManager:Vacuum Disk Safes]*{color}{color:windowtext}.{color}
{color:windowtext}{*}{+}What it does:+{*}{color}{color:windowtext} {color}
{color:windowtext}The Vacuum task removes free pages from the disk safe, by moving full and partially used pages to the front of the file, and truncating the file at the point free pages begin. It removes unused space and shrinks the Disk Safe file.{color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to use it:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Vacuum should only be used if a Disk Safe has grown to a large size, and freeing up disk space is the top concern. {color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to avoid it:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Vacuum should not be used to increase Disk Safe performance. Vacuuming a disk safe one or more times can increase fragmentation, and result in a performance reduction.{color}{color:windowtext} {color}
h1. Compaction
----
*Full Compaction guide available* *[here|ServerBackupManager:Compact Disk Safes]**.*{color:windowtext} {color}
{color:windowtext}{*}{+}What it does:+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Compaction makes a copy of your Disk Safe which replaces the original. During the copy process, free pages are removed to reduce the Disk Safe footprint, and the blocks are re-ordered to help improve backup and restore performance.{color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to use it{+}{*}{color}{color:windowtext}{*}+ :+{*}{color}{color:windowtext}{*}+ +{*}{color}
{color:windowtext}Compaction is most effective on Disk Safes where backup and restore performance has gradually decreased over time. Disk Safes that have had hundreds or thousands of backups stored and merged out of them over time are good candidates for Compaction. {color}{color:windowtext} {color}
{color:windowtext} {color}
{color:windowtext}{*}{+}When to avoid it :+{*}{color}{color:windowtext} {color}
* {color:windowtext}Compaction tasks are I/O intensive. Avoid compacting during peak backup hours when system resources are most needed to complete scheduled replication tasks. {color}{color:windowtext} {color}
* {color:windowtext}Compaction makes a full copy of the Disk Safe. Avoid using it on systems with low available free space. {color}
* Compaction can take many hours or even days to complete on larger Disk Safes. Do not expect instant results.