When backups targeted to NetVault SmartDisk are retired, the data is removed from the backup database; however, the unique Chunks are not automatically removed from the Chunk Store. The NetVault SmartDisk Garbage Collection process is designed to remove orphaned Chunks from the Chunk Store and reclaim disk space. To do so, Garbage Collection maintains reference counts of added and deleted Chunks, and it deletes or rewrites partially used Chunk pages.
Garbage Collection cannot run at the same time as deduplication, because deduplication needs to write to the Chunk Store. During the configured Garbage Collection window, data waiting for deduplication is queued until Garbage Collection has completed. By default, the Garbage Collection window is from 18:00 through 06:00 on every night; however, you can revise this setting — for more information, see Configuring NetVault SmartDisk. Outside the Garbage Collection window, Garbage Collection is only started if no data is being deduplicated or is queued for deduplication. If data becomes available for deduplication outside the Garbage Collection window and Garbage Collection is active, Garbage Collection is stopped and deduplication proceeds.
The first step in defining your NetVault SmartDisk Deployment Strategy is determining which data to deduplicate. Not all data benefits from deduplication; therefore, it is important to determine which data is targeted to use the NetVault SmartDisk Deduplication Option to reduce its storage footprint.
• |
• |
© ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center