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 the data targeted for NetVault SmartDisk is a combination of nondeduplicated and deduplicated data, you can create multiple NetVault SmartDisk Instances: one for nondeduplicated data and one for deduplicated data. In this case, the Nondeduplicated Instance is licensed as NetVault SmartDisk Capacity and the Deduplicated Instance is licensed as NetVault SmartDisk Capacity with Deduplication Option.
NetVault SmartDisk is licensed by front-end terabytes (TBs). A front-end TB is the aggregate amount of data that you want NetVault SmartDisk to protect from all source or client machines that are targeting a single NetVault SmartDisk Instance. A front-end TB is measured by the amount of storage capacity occupied on the source storage by files that are to be backed up; this measurement is based on the capacity consumed before data reduction that might be achieved by using the optional NetVault SmartDisk Deduplication Option. Front-end source data can include OS-related data, file system data, database data, application data, and so on.
NetVault SmartDisk Licensed Capacity is not based on the following:
• |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center