Chat now with support
Chat mit Support

NetVault SmartDisk 11.4.5 - Installation Guide

Introducing NetVault SmartDisk Understanding NetVault SmartDisk architecture Planning your NetVault SmartDisk deployment Installing NetVault SmartDisk Licensing NetVault SmartDisk Completing the installation process Uninstalling NetVault SmartDisk Reinstalling NetVault SmartDisk Upgrading NetVault SmartDisk Troubleshooting

Deduplicated restore process

After the user initiates a restore of a deduplicated NetVault Backup backup that is targeted to a NetVault SmartDisk Instance, the NetVault Backup Client requests the data on the user-defined port from the Storage Service.
The Storage Service queries the Content Index to determine whether the backup is stored in the Staging Store for nondeduplicated backups or the Chunk Store for deduplicated backups.
The Storage Service queries the backup’s Manifest for the first or next batch of Chunk Names in the backup.
The Storage Service queries the Chunk Store Daemon for the location of the Chunks in the Chunk Store.
Using Chunk Names from the Manifest, the Chunk Store Daemon queries the Chunk Index for pointers to the Chunks in the Chunk Store.
The Chunk Store Daemon provides the Storage Service with the location of the Chunks in the Chunk Store.
The Storage Service retrieves the Chunks from the Chunk Store and streams the Chunk to the NetVault Backup Client.
Step 4 through Step 7 repeat for each batch of Chunk Names in the Manifest.
On completion of restoring all Chunk Names in Manifest, the NetVault Backup Client updates the NetVault Backup Server with a Restore Completed job status.

Garbage Collection process

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 must 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 every night. Because Garbage Collection has less impact on the speed at which new backups are staged than deduplication does, Quest recommends that you update the Garbage Collection windows to ensure that they match your backup windows. 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. For more information about scheduling Garbage Collection, see the Quest NetVault SmartDisk Administrator's Guide.

Quest also recommends scheduling regular Garbage Collection to avoid delays associated with collecting large amounts of data.

Planning your NetVault SmartDisk deployment

Deployment strategy: an overview

A NetVault SmartDisk deployment strategy includes multiple components, which you define before installing NetVault SmartDisk. To ensure a successful deployment, complete the following steps, which are described in detail in subsequent sections:

NetVault Backup is used as an example throughout this section; however, you can use any product that works with NetVault SmartDisk.

Before calculating the required NetVault SmartDisk Capacity, ensure that the backups being targeted to NetVault SmartDisk are compatible with NetVault SmartDisk. For more information, see the Quest NetVault Backup Compatibility Guide.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen