vRanger 7.8.2 - Integration Guide for NetVault SmartDisk

Understanding the cost of restoring deduplicated data

Understanding the cost of restoring deduplicated data

While data deduplication reduces storage costs by reducing the storage footprint, there is a cost incurred during the restore processes. During the restoration of a deduplicated backup, NetVault SmartDisk has to reassemble the Chunks as it restores the data. This reassembly process, also called rehydration, lengthens the time to restore the data. Therefore, if the Recovery Time Objective (RTO) is important for a specific database, email, or file system, consider the trade-off between reducing storage costs and increasing RTO when you identify which data to deduplicate.

Deduplicating similar data together

Deduplicating similar data together

You can increase deduplication ratios by targeting backups from the same database, file system, or application to the same NetVault SmartDisk Instance. When a backup is deduplicated and a previous backup from the same database, file system, or application has already been deduplicated by the NetVault SmartDisk Instance, only the unique or new Chunks that did not exist in the previous backup have to be stored in the Chunk Store. If a previously deduplicated backup does not exist in the NetVault SmartDisk Instance, most of the backup is considered unique data; this issue increases the number of unique Chunks that have to be stored in the Chunk Store.

When targeting backups to NetVault SmartDisk Instances, deduplication ratios decline if backups are targeted to random NetVault SmartDisk Instances. Quest recommends that you target backups from the same database, file system, or application to the same NetVault SmartDisk Instance.

Determining the number of deduplicated NetVault SmartDisk Instances

Determining the number of deduplicated NetVault SmartDisk Instances

Three factors determine the number of NetVault SmartDisk Instances required. If any of these factors are true, you must deploy multiple NetVault SmartDisk Instances. To determine the total number of NetVault SmartDisk Instances required, perform the following calculations:

•	Unique Data Size > 15 TB for 64-bit OS and > 5 TB for 32-bit OS

•	Ingest Rate > Maximum Sustained Network Bandwidth

•	Deduplication Rate < Ingest Rate

The maximum result for the three calculations determines the number of NetVault SmartDisk Instances that must be deployed. For example, if the Unique Data Size calculation and the Deduplication Rate indicates that only one NetVault SmartDisk Instance is required, but the Ingest Rate calculation indicates that two NetVault SmartDisk Instances are required, you must deploy two NetVault SmartDisk Instances.

Unique Data Size > OS Bit Limit

Unique Data Size > OS Bit Limit

The Unique Data Size is the amount of unique data that is stored inside the NetVault SmartDisk Instance. An additional NetVault SmartDisk Instance must be deployed for every 15 TB of unique data on a 64-bit operating system (OS) and for every 5 TB of unique data on a 32-bit operating system. Use the following calculation to determine the number of NetVault SmartDisk Instances based on the Unique Data Size:

Size of Weekly Full Backups + ((Size of Weekly Full Backups * Weekly Change Rate)

* Weekly Full Backup Retention Period)

+ (Size of Daily Backups * (Number of Daily Backups between Weekly Full Backups

* Daily Backup Retention Period))

Example:

100 GB = Size of Weekly Full Backups

10% = Weekly Change Rate

12 = Weekly Full Backup Retention Period in Weeks

10 GB = Size of Daily Backups

4 = Daily Backup Retention Period in Weeks

6 = Number of Daily Backups between Full Backups

100 + ((100 * 0.1) * 12) + (10 * (6*4)) =

100 + ((10) * 12) + (10 * (24)) =

100 + (120) + (240) = 460 GB

•	If the operating system is 64-bit:

460/15360 =.029

Rounded Up to Next Whole Number = 1 NetVault SmartDisk Instance

•	If the operating system is 32-bit:

460/5120 =.089

Rounded Up to Next Whole Number = 1 NetVault SmartDisk Instance