Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

vRanger 7.8 - Integration Guide for NetVault SmartDisk

Getting started Understanding NetVault SmartDisk Planning your NetVault SmartDisk deployment Installing vRanger Installing NetVault SmartDisk Configuring NetVault SmartDisk Monitoring NetVault SmartDisk About us

Defining a NetVault SmartDisk Storage Pool strategy

Previous Next


Planning your NetVault SmartDisk deployment > Defining a NetVault SmartDisk Storage Pool strategy

Understanding space allocation for NetVault SmartDisk Storage Pools

Previous Next


Planning your NetVault SmartDisk deployment > Defining a NetVault SmartDisk Storage Pool strategy > Understanding space allocation for NetVault SmartDisk Storage Pools

When configuring a NetVault SmartDisk Storage Pool, you can identify it as a favorite for specific roles (favour), and you can indicate that it should never be used for specific roles (deny).
Using the volume-size parameter, you can set aside a portion of the volume so that it cannot be used for NetVault SmartDisk. After the volume is full with NetVault SmartDisk or non-NetVault SmartDisk data, NetVault SmartDisk does not store anything else on the volume until space is made available.
NetVault SmartDisk uses storage space in each volume up to a threshold amount that includes space directly set aside using the volume-size parameter, and the Last Resort Threshold (LRT) amount set by NetVault SmartDisk internally.
NetVault SmartDisk first uses a volume for its intended role, for example, Chunk Store or Staging Store, but it also uses it for other purposes if necessary. Even if you supply a threshold, NetVault SmartDisk implements an LRT that stops NetVault SmartDisk from using a volume after there is less than a certain amount of space available and thus prevents the disk from becoming full. The LRT is calculated to include both a fixed amount of space (1 GB) and the space that would be required to make Garbage Collection possible, that is, the gc_reserve_bytes parameter. This process means that the figure varies in size depending on the amount of data held in the Chunk Store; typically, you can expect the gc_reserve_bytes parameter to be at least 1.7 GB.
If the LRT is large enough, NetVault SmartDisk properly allocates space when multiple Staging Store and Chunk Store processes are both writing to a volume that becomes too full. NetVault SmartDisk maintains an overall idea of how much space is used both by the Staging Store and the Chunk Store. This allows it to enforce the licensed amount of capacity and to enforce the LRT and the volume-size limits.
User thresholds and the NetVault SmartDisk LRT do not affect licensing. Licensing measures the amount of data accepted for protection by the NetVault SmartDisk Instance, regardless of whether the data has been deduplicated.

Understanding the optimal performance strategy

Previous Next



Content Index: Should be small and reside in a Storage Pool made of fault-tolerant disks with good random-access performance.
Staging Store: Should reside in a Storage Pool made of fault-tolerant disks with good streaming performance.
Chunk Index: Should reside in a Storage Pool made of fault-tolerant disks with good random-access performance.
Chunk Store: Should reside in a Storage Pool made of fault-tolerant disks.
On Windows® platforms, you can disable the New Technology File System (NTFS) Last Access Update feature, which can reduce disk accesses and increase performance. For instructions on disabling this feature, see the documentation for your specific operating system.

Installing vRanger

Previous Next



Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating