• |
Storage Service: The Quest NetVault SmartDisk Storage Service listens on a user-defined port for data flowing to and from NetVault SmartDisk. There is one Storage Server process per data stream. |
• |
Deduplicator: The Quest NetVault SmartDisk Deduplicator performs byte-level, variable-block software-based deduplication by breaking the data streams into unique Chunks. The Deduplicator uses the Chunk Store Daemon (CSD) to query the Chunk Index to determine if the Chunk is unique. When a Chunk is found in the Chunk Index, the Chunk Store Daemon stores the unique Chunk in the Chunk Store. There is one Deduplicator process per data stream. |
• |
Chunk Store Daemon: The Quest NetVault SmartDisk Chunk Store Daemon is the only process that writes to the Chunk Index and Chunk Store. There is only one CSD per NetVault SmartDisk Instance. The CSD also manages the Garbage Collection process. |
• |
percolatormonitor: The percolatormonitor is a privileged process that starts and monitors other NetVault SmartDisk Processes. |
• |
percolatorslave: The percolatorslave is responsible for communication routing. It routes messages between NetVault SmartDisk Processes on the local machine and between NetVault SmartDisk and other remote servers. |
• |
logd: The logd is the logging daemon that creates the NetVault SmartDisk logs and stores them in an internal database. It also sends them to the applicable system location, such as the Application log in the Windows Event Viewer. |
• |
resourcemanager: The resourcemanager manages the combined number and size of all trace files by periodically deleting inactive files, that is, those files that are not associated with any running processes, starting with the oldest files first. |
• |
superserver: The superserver is the high-level manager of all other processes. It coordinates operations, balances the load between file systems, and schedules deduplication and Garbage Collection. |
• |
winservicerunner: On Windows, the winservicerunner runs the Windows Service and starts the percolatormonitor. |
1 |
After the user initiates a nondeduplicated NetVault Backup backup that is targeted to a NetVault SmartDisk Instance, the NetVault Backup Client streams data on the user-defined port to Storage Service. |
2 |
3 |
The Storage Service updates the Content Index to indicate where the backup is stored in the Staging Store. |
4 |
The Storage Service updates the NetVault Backup Client to indicate that the backup stream has been successfully stored. |
5 |
1 |
After the user initiates a restore of a nondeduplicated NetVault Backup backup that is targeted to a NetVault SmartDisk Instance, the NetVault Backup Client requests data on the user-defined port from the Storage Service. |
2 |
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. |
3 |
The Storage Service retrieves the backup stream from the Staging Store and streams the data to the NetVault Backup Client. |
4 |
On completion of restoring the backup stream, the NetVault Backup Client updates the NetVault Backup Server with a Restore Completed job status. |
1 |
After the user initiates a deduplication-enabled NetVault Backup backup that is targeted to a NetVault SmartDisk Instance, the NetVault Backup Client streams data on the user-defined port to the Storage Service. |
2 |
3 |
The Storage Service updates the Content Index to indicate where the backup is stored in the Staging Store. |
4 |
The Storage Service updates the NetVault Backup Client to indicate that the backup stream has been successfully stored. |
5 |
During the user-defined deduplication window, backup data is retrieved from the Staging Store and sent to the Deduplicator. | ||
The Deduplicator performs byte-level, variable-block software-based deduplication by breaking data streams into unique Chunks and sending them to the Chunk Store Daemon. | ||
The Deduplicator creates a backup-specific Manifest, which is an ordered list of Chunks that make up the backup. | ||
The Chunk Store Daemon sends the unique Chunks to the Chunk Store for storage and updates the Chunk Index to indicate where each Chunk is stored in the Chunk Store. | ||
The Content Index is updated to indicate that the backup is stored in the Chunk Store. | ||
The backup data stream is removed from the Staging Store. |
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center