The NetVault SmartDisk Ingest Rate is the rate at which data can be streamed into NetVault SmartDisk. Because data streams into the NetVault SmartDisk Instance through a user-defined port, the network bandwidth limits the speed at which data can be streamed. To ensure that all backups targeted to a NetVault SmartDisk Instance can complete during the backup window, divide the required ingest rate by the Maximum Sustained Network Bandwidth to determine the number of required NetVault SmartDisk Instances. Use the following calculation to determine the number of NetVault SmartDisk Instances based on the NetVault SmartDisk Ingest Rate and Network Bandwidth:3.55 / 100 = .035Rounded Up to Next Whole Number = 1 NetVault SmartDisk Instance
The NetVault SmartDisk Deduplication Rate is the rate at which NetVault SmartDisk deduplicates data. If NetVault SmartDisk deduplication is configured to run during the backup, the NetVault SmartDisk Deduplication Rate must be greater than or equal to the Ingest Rate to ensure that the deduplication process completes before the next weekly backup window begins.
Use the following calculation to determine the number of NetVault SmartDisk Instances based on the Deduplication Rate and Ingest Rate:(((Size of Weekly Full Backups) + (Size of Daily Backups * Number of Daily Backups between Weekly Full Backups)) * 1024)(163840/518400)/50) = .0063Rounded Up to Next Whole Number = 1 NetVault SmartDisk Instance
The maximum result for the following three calculations determines the number of NetVault SmartDisk Instances that must be deployed:
The Total Required Disk Space is divided into the Staging Store and the Chunk Store. If you intend to use different file systems or disks for the Staging Store and the Chunk Store, it is important to know how much of the Total Required Disk Space is allocated to the Staging Store versus the Chunk Store. Use the following calculations to determine this amount.During the NetVault SmartDisk Deduplicated Backup process, backups are initially streamed to the Staging Store where they remain until the deduplication process is finished. The Staging Store must be large enough to hold all the backups while they await deduplication.If the deduplication window overlaps the backup window, deduplication and backups occur at the same time. Each backup starts deduplicating after the backup job is finished. Also, large backups are broken into 400 GB segments. Each segment starts to deduplicate after it is received, even if the backup stream is still being streamed to the Staging Store. Therefore, the Staging Store only requires space to hold some portion of the total backup size. If the Staging Store runs out of space, vRanger backups fail.