White Papers
Table Of Contents
- 1 Installing and configuring the DR Series system for use with CommVault Simpana
- 2 Configuring CIFS and NFS containers for CommVault Simpana
- 2.1 Creating containers in the DR Series system
- 2.2 Adding the target container(s) to CommVault Simpana
- 2.2 Setting up a single system environment (DR Series system as NFS disk library)
- 2.3 Setting up a replicated system environment
- 2.4 Using the continuous data replicator to replicate client data to a DR Series container
- 3 Configuring VTL for CommVault Simpana
- 4 Setting up the DR Series system cleaner
- 5 Monitoring deduplication, compression, and performance
- A VTL configuration guidelines
- A.1 Managing VTL protocol accounts and credentials
- A.2 VTL default account summary table
- A.3 Managing VTL media and space use
- A.3.1 General performance guidelines for DMA configuration
- A.3.2 Physical space sizing and planning
- A.3.3 Logical VTL geometry and media sizing
- A.3.4 Media retention and grouping
- A.3.5 VTL media count guidelines
- A.3.6 Adding the VTL media to the container
- A.3.7 Updating CommVault to identify newly added VTL media
- A.3.8 Space reclamation
- B Glossary
88 Setting Up the Dell™ DR Series System as a CIFS or VTL Backup Target on CommVault Simpana |
April 2015
5. Calculate the data footprint during the retention period for change rate data sets
based on a 10-1 deduplication ratio
6. Calculate the ratios within the retention period for each of the data sets
7. Determine the lowest ratio data set to be retired within the retention period and
create media of size that closest matches this data footprint so that when a
retention period is met the most amount of media is recycled to invoke data
reclamation alignment and optimizing media consumption.
IMPORTANT NOTE: If other containers are being configured to host CIFS/ NFS / RDA or
OST, these must also be factored into the planning and management of space.
A.3.3 Logical VTL geometry and media sizing
The logical size of the VTL including media size and media count should be made such so
as to accommodate the existing data footprint targeted for protection. The calculation for
such should include the initial footprint, change rate and retention period. It should also
take in account the size of both full and incremental data sets. Using the smallest iteration
of the data sets to dictate the logical size of the VTL media affords users the ability to retire
media in smaller increments which results in high levels of use and also provides the users
the ability to conduct operations across smaller objects which results in higher levels of
flexibility such as when a restore is needed during backup operations.
We can review a typical full weekly plus incremental daily example to demonstrate one
method of conducting this calculation. In our example the total logical foot print for the
customer environment is 20TB and with a 10% change within a weekly recovery point
objective period for a complete weeks’ worth of protection we calculate that we will
require 22TB of total logical media to retain the data footprint for the given environment
for one week. In order to allow for disparities we also include a 10% increase to allow for
flexibility in the deployment and use of the VTL which results in a 24.2TB total virtual
media requirement for a single weekly retention period.
Important Note: Media can always be added as needed. Media cannot however be
deleted so care must be taken in order to avoid creating too many media items.
In the previous example at the end of the 5 week cycle the 1
st
week retires and frees up
media to be reused or recycled which once processed will allow the DR to reclaim the
physical space associated with the virtual media. Since the smallest data set footprint
resulting from the change rate is 2TB in each incremental iteration we create our media at
800GB increments and add as we grow. For this example the initial Virtual Tape Library
would be created with 152 (
121TB divided by 800GB
) pieces of media at 800GB for each
piece media.