BPG Data Domain Commvault

CommVault Simpana 8.
0
Application Introduction
EMC Data Domain, Inc.

2421 Mission College Boulevard, Santa Clara, CA 95054
866-WE-DDUPE; 408-980-4800
Version 1.0, Revision B
December 14, 2011
Copyright 2009-2011 EMC Data Domain, Inc. All rights reserved.
Data Domain, the Data Domain logo and Global Compression are trademarks or registered
trademarks of Data Domain, Inc. All other trademarks used or mentioned herein belong to their
respective owners.
Data Domain products are protected by one or more of the following patents issued to Data
Domain. U.S. Patents 6,928,526; 7,007,141; 7,065,619; 7,143,251; 7,305,532; 7,373,464; 7,424,498;
7,434,015 and other patents and patents pending in USA and other countries.
Disclaimer: The information contained in this publication is subject to change without notice.
Data Domain, Inc. makes no warranty of any kind with regard to this manual, including, but not
limited to, the implied warranties of merchantability and fitness for a particular purpose. Data
Domain, Inc. shall not be liable for errors contained herein or for incidental or consequential
damages in connection with the furnishing, performance, or use of this manual.
The instructions provided in this document by Data Domain are for customer convenience and
are not warranted or supported by Data Domain, Inc. Data Domain expects users to integrate
third-party software and arrays as needed, but Data Domain is not responsible for the usability
of the third-party software or the arrays after installation.
2
CommVault Simpana 8.0 Software
Application Introduction
This document provides information needed to integrate a Data Domain system as a

backup target for the CommVault Simpana software.
This document covers the topics shown in the following table.
Related Documentation Page6

Access to Integration-Related Documents at Data Domain Page6
Product Introduction Page8
Product Installation Page9
Concepts and Terms Page9
Software Configuration Introduction Page12
Access to the CommVault Simpana CommCell Console Page12
Client Computer Data Backup Job Description Page14
Storage Policy Description Page13
Licenses Page15
Data Domain CIFS Configuration Page16
CommVault Simpana Configuration Page17
Prerequisites Page18
Simpana Static Shared Magnetic Library Configuration Page18
Simpana Backup Configuration Page23
Configuring CommVault Simpana for Optimal Compression Page31
Data Expiration and Space Reclamation Page35
Backup and Restore Operations Page40
VTL Configuration Page43
Simpana Tape Drive and Media Management Page50
Create a VTL Storage Policy Page52
NDMP Configuration Page53
Simpana Troubleshooting Page61
Advanced Topics Page64
3
Configuring Simpana Multistream Backups Page64
Static Shared Magnetic Library Configuration for Replica Restores in FS Mode Page75
Configuring Restores from a Replica Data Domain System Page77
Write Aux Copies to Tape with a Replica Data Domain System as the Source Page83
If desired, you can go directly to the following procedures.

View Data Domain application integration documents Page6
To access the CommCell Console from a Windows host Page13
To view Data Domain system installed licenses Page15
To review CommVault Simpana installed licenses Page15
Configure a shared disk device for the Media Agent Page18
Create a Shared Magnetic Library for the new Shared Disk Device Page21
Create a backup storage policy Page23
Create a backup schedule policy Page25
Create a backup set Page25
Create a subclient Page26
Increase the Chunk Size and Block Size Page31
Verify that multiplexing is disabled Page34
To manually start a job pruning process Page35
To have the Data Domain system reclaim space manually Page37
To start a backup operation Page40
To start a restore operation Page41
Establish the FC connection, install drivers, and verify the connection on the Page43
CommVault Media Agent server
Create a VTL group on the Data Domain system Page44
Verify the Fiber Channel configuration for the VTL Page46
Configure the new VTL on the CommVault Media Agent server Page46
To discover new media that have been imported from the Data Domain vault Page50
To import new media from the I/E ports Page51
To export media from a library slot to the I/E ports Page51
Add the NAS device as an NDMP client Page54
Discover and Configure Libraries and Tape Drives Page56
Create an NAS NDMP Storage Policy Page58
Configure Subclients Page58
4 CommVault Simpana 8.0 Software Application Introduction

Configuring an NDMP Remote Server (NRS) Backup Destination Page59
To view log files Page61
To check that the Simpana processes and services are running (UNIX) Page61
To check that the Simpana processes and services are running (Windows) Page62
Handling a pending backup job on a Windows media agent Page62
Configuring multistream backups of static shared magnetic libraries Page65
Configuring multistream backups of a VTL Page68
Configuring multistream backups of an NAS device Page69
Configure replication on a Data Domain system Page70
Restore from a Data Domain system replica in a VTL Page71
Import volumes into a new VTL on a secondary Data Domain system from a Page72
replica
Restore from a secondary Data Domain system VTL Page72
Create a network shared device Page77
Create a shared magnetic library device and mount paths Page81
Perform a test restore from the replica Page82
Creating an Aux Copy Page83
5
Related Documentation
The Data Domain and CommVault Simpana documents referred to in this guide
provide additional information you need to configure and integrate the Data Domain
system and the backup software. To view the CommVault Simpana documentation,
visit http://documentation.commvault.com. To view the Data Domain documentation,
see the instructions in this section.
Access to Integration-Related Documents at Data Domain

The Documentation page at https://my.datadomain.com/documentation provides
access to documents that are related to use of this application with Data Domain
products:
User guides referred to in this document, under Product Documentation.
The latest version of this document, along with other integration-related
documents, under Integration Documentation.
Compatibility Matrices, including the following:
DD OS 4.6 Application Compatibility List
DD OS 4.6 Fibre Channel Switch and Director Compatibility List
DD OS 4.6 Storage Array Compatibility List
In the Compatibility Matrices, you can find information including:
Data Domain hardware product numbers
Data Domain operating system (DDOS) versions
CommVault Simpana server and client operating system versions
CommVault Simpana software versions
Previous versions of the software were named CommVault Galaxy.
Hardware driver versions
View Data Domain application integration documents

1. Log into the support portal at: https://my.datadomain.com/documentation.
2. To view user documents, click Product Documentation and then perform the
following steps:
a. Select the Data Domain model from the Platform list and click View.
b. On the row for the correct Data Domain operating system (DD OS) version,
click View under Documentation.
c. Click the desired title.

3. To view CommVault Simpana integration-related documents, perform the

following steps:
a. Click Integration Documentation.
b. Select CommVault from the Vendor menu.
c. Select the desired title from the list and click View.
4. To view compatibility matrices, perform the following steps.
a. Click Compatibility Matrices.
b. Select the desired title from product menu and click View.
7
Product Introduction
CommVault Simpana software is a data protection suite for large-scale
enterprises. Simpana provides backup, recovery, archive, and disaster recovery
options to protect enterprises against data loss. The Simpana software suite is a
modular application that lets the administrator pick specific client agents that
support their organizations data types, such as Microsoft Exchange and Sun
Solaris files.
The first Simpana system installed must be configured as a CommServe.
A CommServe defines a backup domain called a CommCell that manages member
Media Agents, Clients, and data protection storage resources. A CommVault Media
Agent server is any system, including the CommServe, that has the iDataMediaAgent
installed. The CommServe contains a SQL database that keeps track of the various
agents and data protection metadata, such as the media index.
Note: This document does not describe the Simpana Archive product for nearline
storage.
Note: In this document, the term UNIX refers to any UNIX or UNIX-based operating
system such as Linux, HP-UX, or Solaris.
Note: The illustrations and procedures in this manual come from Commvault
Simpana 8. The illustrations and procedures for previous versions, known as
CommVault Galaxy, are similar.

Product Installation
At least one Windows server is required for CommVault Simpana installation. This
system must contain the CommServe that defines the CommCell. To install the
software on a Windows system:
1. Launch the setup.exe file on the installation media.
2. Select Install Simpana on this Computer for a local installation.
On UNIX or Linux systems, separate media is required. Use the cvpkgadd script that
is included on the media to install the software.
For details on how to install CommVault software and options, refer to the
documentation available at http://www.commvault.com.
Concepts and Terms

The following Data Domain and CommVault-specific concepts and terms are used in
this document.
Table 1: Terms
Term Definition
Auxiliary Copy An Aux Copy is defined within a Storage Policy and is one example of a
Aux Copy secondary copy of a primary backup data set independent of the original
copy. The auxiliary copy operation can be useful for creating additional
standby copies of data.
Backup Set A group of subclients. There is a default backup set created with most
iDataAgents that backs up all data associated with an iDataAgent.
Block Size Media Agents can write to media using different block sizes, if the
Operating System associated with the Media Agent in which the library is
configured supports a higher block size. The system can write block sizes
up to 256 KB and can automatically read block sizes up to 512 KB.
Chunk Size A chunk is the unit of data that the Media Agent software uses to store data
on magnetic media, such as a magnetic library.
For sequential access media such as tape, a chunk is defined as the data
between two file markers.
The default chunk size for file system iDataAgent data is 4 GB.
The default chunk size for data associated with databases is 16 GB.
For Random access media each chunk is a file on the disk. The default
chunk size is 2 GB.
Client Computer Any computer host that has one or more iDataAgents installed.
9
Table 1: Terms (Continued)

Term Definition
CommCell A single backup domain that contains:
A CommServe
One or more Media Agents
One or more iDataAgents that have defined backup sets and subclients
CommCell Console The management interface for the CommServe agents and clients that are
members of a CommCell. You access the Console either directly from the
desktop of the CommServe or through a system in the CommCell that has
the Console package installed.
Common Technology The set of base-level CommVault Simpana software components used to
Engine (CTE) administer client agents and storage media. The CTE includes the
CommServe Server, Media Agents, CommCell Console, Content Indexing
and Search, and CommCell DR.
CommServe The coordinator and administrator of the CommCell component. The
CommServe communicates with all agents in the CommCell to initiate data
protection, management and recovery operations. Similarly, the
CommServe communicates with Media Agents when the media subsystem
requires management. The CommServe server maintains a Microsoft SQL
database that contains all of the information that relates to the CommCell
configuration. In addition, the CommServe provides several tools to
administer and manage the CommCell components.
Data Domain system A standalone Data Domain storage appliance or gateway.
Data Path (Gridstor) The combination of a Media Agent, Library, Drive Pool, and Scratch Pool
used by the storage policy copy to perform a data protection operation.
Each storage policy copy has a default data path that gets used to perform
data protection operations. In addition, you can also define alternate data
paths in each of the storage policy copies to handle situations when one of
the data path elements fails.
DDFS Data Domain File System
DDSH Data Domain Shell, the command line interface for managing a Data
Domain system.
Global Compression The Data Domain deduplication engine
iDataAgent A computer with an agent whose data is backed up to a CommVault Media
Agent server and that has the appropriate client agent software installed.
Some examples of agents include:
Microsoft Windows File System iDataAgent for Windows file systems
NAS NDMP iDataAgent for NAS systems
Oracle iDataAgent for Oracle relational databases.
Local Compression Traditional zip compression applied to Data Domain data as it arrives on
the disk.

Table 1: Terms (Continued)

Term Definition
Media Agent Provides services to back up and recover the data for the CommVault
Simpana client computers in a CommCell. Storage devices, such as Data
Domain systems, can be connected to a Media Agent as a backup target
with CIFS, with NFS, or through a Virtual Tape Library (VTL).
Mount Path A location within a magnetic library where software can write backup data.
A mount path is analogous to a tape drive in a tape library. Mount paths are
for volumes that are network-based, such as a CIFS share or NFS volume.
Primary Copy The data protection operation that creates the first copy of a backed-up data
set. The system creates the primary copy automatically when a storage
policy gets created. All data protection operations that use a given storage
policy use the primary copy. Each copy definition contains retention
policies, data path definitions, media specific policy settings, and data
verification settings.
Secondary Copy An additional copy of a protected data set that gets used, for example, in
auxiliary copy operations or in other data protection operations that create
inline copies.
Shared Magnetic Library A virtual library associated with one or more mount paths. Magnetic
libraries enable direct disk access for faster and easier recovery of data. A
shared magnetic library allows multiple CommVault Media Agents access
to the same mount paths. The system supports multi-read and multi-restore
access to backed-up data. Shared Magnetic Libraries allow failover
capabilities between Media Agents and let you dedicate one Media Agent
to Auxiliary Copy operations.
Storage Policy Storage policies control how storage resources can be used.
There are two types of storage policies:
Data Protection and Archiving
CommServe DR
At least one primary copy, library storage resource, and Media Agent must
be assigned to each storage policy. A storage policy also controls retention
time, streams, and deduplication settings.
SubClient A SubClient is a single backup definition that specifies:
What to back up within a data set on the client
The iDataAgent type
The storage device to be used
You can define multiple SubClients for each iDataAgent and associated
backup set.
Virtual Tape Library Hard disk storage that gets presented to the backup software as tape
(VTL) libraries.
11
Software Configuration Introduction

You use the Simpana CommCell Console to configure:
Polices, such as Storage Policies and Schedule Policies
Storage Resources, such as Media Agents and Libraries
Clients, such as Client iDataAgents and Subclients
This section covers the following topics:
Access to the CommVault Simpana CommCell Console Page12
Client Computer Data Backup Job Description Page14
Storage Policy Description Page13
Access to the CommVault Simpana CommCell Console

You can launch the CommVault Simpana CommCell Console from any system that
has a CommCell Console component installed. Typically the CommCell Console
software gets installed on a management host that has access to all of the Simpana
CommCells, but you can install the CommCell Console software on any host in the
CommCell.
Figure1 shows an example of a CommCell Console window.
Figure 1: CommServe Console Window

To access the CommCell Console from a Windows host

1. Log on to the CommServe or to another host that has the CommCell Console
package installed.
2. Select Start > Programs > CommVault > Simpana > CommCell Console GUI.
The Connect to CommCell window appears.
3. Enter the username and password to access the CommCell that you select from
the drop-down list.
The CommCell Console (Figure1) appears.
Storage Policy Description

A storage policy manages storage resources that include copy definitions. There are
two types of storage policies:
Data Protection and Archiving
CommVault Simpana Disaster recovery
Each storage policy must include at least one copy definition. A copy definition
describes a data protection operation that includes information such as a retention
policy, data paths, and data verification settings for each associated subclient. You
define a storage policy on the Storage Device tab of the subclient (Figure7 on page
27). The first copy made from a storage policy is called a primary copy.
The CommVault Simpana software uses days and cycles to define the retention
period within a storage policy. A cycle is defined as a full backup to a full backup. For
example, if you want to retain data for four weeks with daily incremental backups
and weekly full backups, configure the retention period as three cycles and 30 days.
With this configuration, there would always be four full backups on the Data Domain
system.
13
Client Computer Data Backup Job Description

A client computer contains one or more iDataAgents for particular types of source
data, such as an Exchange database or a Solaris file system. Each client iDataAgent
contains one or more Backup Sets. A backup set can be thought of as a group of
subclients. Each subclient contains a backup job definition which has paths to source
data and a storage policy. A backup job can get launched from a backup set or a
specific subclient within a backup set either automatically on a schedule or on
demand.
Figure2 shows an example subclient.
Figure 2: Subclient configuration dialog box

Licenses
Licenses
You must purchase separate licenses from CommVault or Data Domain for advanced
features and most add-ons to both companies products. For example, replication is a
separately licensed feature for a Data Domain system, and Shared Magnetic Libraries
with Static Mount paths are a separately licensed feature for the CommVault
Simpana software.
To view Data Domain system installed licenses

1. Connect to the Data Domain Enterprise Manager.
For assistance, refer to the Data Domain Operating System User Guide or the Data
Domain Operating System Administration Guide.
2. Select Licenses.
To review CommVault Simpana installed licenses

To view licensed features in CommVault Simpana, use the CommCell Console to
navigate to the License Administration tool in the Control Panel.
1. From the CommCell Console, click Tools menu item. Select and click Control
Panel.
2. The Control Panel window appears with an icon for each task. Double click
License Administration to view and add licensees.
3. The License Administration window appears with four tabs. The License
Summary tab contains a brief report on the license information. The License
Details tab contains a detailed list of all installed licenses and their attributes. The
Update License tab allows the selection of a license file and a convert utility to
convert evaluation licenses to permanent licenses. There is also contact
information to purchase new licenses on the Purchasing tab.
15
Data Domain CIFS Configuration
Data Domain CIFS Configuration

To prepare a Data Domain system to be used as one or more Static Shared Magnetic
Libraries that utilize the CIFS protocol:
1. Create CommVault administrative user account with proper privileges.The
account should be the same as the service account used for CommVault
administration and have administrative rights.
# user add svc_simpana password mypassword priv admin
Note: Always use the CommVault administrative user account to log on and make
changes to the Data Domain system. Changes made by other accounts, regardless of
permissions, may cause read or write errors for the service account. Also be aware
that the Data Domain system might not be a member of a Windows domain.
2. Set the tape marker setting for Simpana and restart the file system.
The example shows how to set the marker type to auto. If the Data Domain
system will only be a target for Simpana backups, use the cv1 marker setting
instead.
Note: Only the auto marker setting is available with DD OS 5.0 and onward.
# filesys option set marker-type auto
Marker-type changed to "auto".
The filesystem must be restarted to effect this change.
# filesys disable
Please wait.......
The filesystem is now disabled.
# filesys enable
Please wait..........
The filesystem is now enabled.

CommVault Simpana Configuration
3. Verify that the marker setting is enabled.
# filesys option show

Option Value
------------------------------- --------
Local compression type lz
Marker-type auto
Report-replica-as-writable disabled
Current global compression type 9
Staging reserve disabled
The auto value for Marker-type shows that the marker setting got applied.
4. Set CIFS client access permissions for Simpana media agents.
# cifs add /backup client-list
To enable access to all client, set the client-list parameter to *.

5. Create folder(s) under /backup for Shared Disk Device backup target(s) and base
folders for mount paths. You can optionally define these folders as separate CIFS
shares by using the command cifs share create from DD OS.

This section explains how to configure the CommVault Simpana software with Data
Domain systems.
For details, please read the how-tos in the CommVault Simpana online
documentation. For information about Data Domain products, please refer to the
Data Domain OS User Guide.
A CommVault Media Agent server is any system that has the iDataMediaAgent
installed. Valid Media Agent servers appear under Storage Resources > Media
Agents on the CommCell Console.
This section covers the following topics:
Prerequisites Page18
Simpana Static Shared Magnetic Library Configuration Page18
Simpana Backup Configuration Page23
Configuring CommVault Simpana for Optimal Compression Page31
Data Expiration and Space Reclamation Page35
Backup and Restore Operations Page40
17
VTL Configuration Page43

Simpana Tape Drive and Media Management Page50
Create a VTL Storage Policy Page52

Prerequisites
1. Install at least one Windows system to be a CommServe that manages a
CommCell.
2. Install at least one CommVault Media Agent.
Note: Note: The Media Agent can be located on the same computer system as the
CommServe component.
3. Add the Media Agent to the CommCell.
4. Configure the Data Domain system as described in Data Domain CIFS

Configuration on page 16.
5. Give the Media Agent access to a Data Domain CIFS share or folder.
Simpana Static Shared Magnetic Library Configuration

A Static Shared Magnetic Library is a network backup target that uses CIFS. The
benefit to using a shared magnetic library is that you can execute restores from any
media agent that has share privileges. The CommVault Media Agent server is any
server, including the CommServe, that has the iDataMediaAgent installed. Valid
Media Agent servers appear under Storage Resources > Media Agents on the
CommCell Console. The CommCell Console is used for all of the described tasks that
follow.
To configure Static Shared Magnetic Libraries for a Media Agent, perform the
procedures in this section.
Configure a shared disk device for the Media Agent

Note: Data Domain recommends that you always configure a Shared Disk Device.
1. From the CommCell Console, select Tools > Control Panel.
2. Double click Library and Drive Configuration.
The Select MediaAgents dialog box appears.
19
3. Select the media agents to configure, click Add >>, and then click OK.
The Library and Drive Configuration window appears.
Figure 3: Library and Drive Configuration window, Shared Disk Device tab
4. Right click Disk Devices and select Disk Device >Add.

The Add Sharing Folder dialog box appears.
5. Specify the network path and a valid user, and then click OK.
A typical network path is \\dd565-1\backup\cvtest. In an Active Directory

environment, the user must be a valid Active Directory user. In a Workgroup
environment, the user must be a local account on the Data Domain system.
The new Shared Disk Device will appear in an unconfigured state.
6. Right click the Network Sharing Device and select Configure.
The CommVault software authenticates to the Data Domain CIFS share. After a
few moments, the new Shared Disk Device will appear as configured. This step
saves the configuration; if you skip this step, the configuration gets discarded
when you exit.
7. Right click the new Shared Disk Device and select Properties.
8. Change the name of the new Shared Disk Device from the default name Device_1.
This completes the creation of a new Static Shared Disk Device
21
Create a Shared Magnetic Library for the new Shared Disk

Device
Note: A Shared Magnetic Library allows simultaneous library access by one or more
Media Agents. Data Domain highly recommends this option so that you can add
replication easily in the future. This lets storage be shared and frees restore
operations from relying on a single media agent. See Configure replication on a Data
Domain system on page 70.
1. Click the Libraries tab in the Library and Drive Configuration window.
2. Right click Libraries and select Add > Shared Magnetic Library.
The Add Magnetic Library dialog box appears.
3. Specify an alias, optionally select Automatically create storage policy for new
data paths, and then click OK.
The Shared Mount Path dialog box appears.
4. Select the disk device to associate as the mount path from the Disk Device field
and click OK.
Note: The Base Folder is where the mount path can store data. The Base Folder
needs to be created by the Media Agent and cannot exist on the Data Domain system.
The mount path gets added to the shared magnetic library and the new shared
magnetic library appears in the Library and Drive Configuration dialog box.
5. Optionally, add more Shared Mount Paths by following the previous two steps.
6. Close the Library and Drive Configuration window.
This completes the configuration of the Shared Magnetic Library.

Figure4 shows two properly configured Static Shared Magnetic Libraries.
Figure 4: Configured Shared Magnetic Libraries with a Data Domain Shared Disk Device
23
Simpana Backup Configuration

Creating a Simpana backup configuration involves these four main steps:
Create a backup storage policy
Create a backup schedule policy
Create a backup set
Create a subclient
You define a backup configuration on a subclient, but you can launch a backup job at
the backup set level to protect a group of subclients.
All Filesystem iDataAgents have a defaultBackupSet group for each client. Most
other iDataAgents follow this same pattern. The defaultBackupSet group contains a
default subclient that will backup all data on the client. To prepare Simpana for a
scheduled backup, follow the all of the steps below.
Note: Do not use multiplexing and avoid synthetic full backups when you use a Data
Domain system as a backup target.
Create a backup storage policy

This procedure creates a storage policy for a shared magnetic library.
Note: For a Data Domain VTL, be sure to also disable hardware compression when
you create the backup storage policy.
Disable any deduplication and compression options for the storage policy.
1. Right click Storage Policies in the CommCell Console window and select New
Storage Policy.
The Storage Policy Wizard appears.
2. Select Data Protection and Archiving on the first page of the wizard and click
Next.
3. Keep the default value of No for Legal Hold and click Next.
4. Add a storage policy name and click Next.
5. Enter a name for the Primary Copy and click Next.
6. Select a Library to associate with the primary copy and click Next.
The example screen shots use DataDomain_Shared_Mag_Library.

7. Select a Media Agent and click Next.
8. Set the number of Device Streams and define the primary copy aging rules, and
then click Next.

These rules define the retention policy. The default number of device streams is 1
and the default retention policy is infinite.
9. Disable deduplication for the primary copy. This is critical for obtaining optimal
compression results from the Data Domain system. See Figure5.
Figure 5: Deduplication Question in the Create Storage Policy Wizard

10. Click Next to continue through the wizard.
11. If the Data Domain system is configured as a VTL, the wizard asks about
hardware compression. Deselect the Hardware Compression setting for the
primary copy as shown Figure6 and click Next.
Figure 6: Hardware Compression Question in the Create Storage Policy Wizard

12. Review the information on the final page of the wizard and click Finish to create
the policy.
The new policy appears in the CommCell Browser window.
Caution: Before you launch the first full backup, increase the Chunk Size and Block
Size of the new Storage Policy primary copy. Otherwise, the changes do not take
effect and, for older versions of the CommVault Galaxy software, you cannot change
25
the parameters later. See Increase the Chunk Size and Block Size on page 31 for details
and minimum size recommendations.
Create a backup schedule policy

Create a Data Protection type Schedule Policy that contains a pattern of full or
incremental backups (or both), iDataAgents, and alerts. For example, if you want to
retain data for four weeks with daily incremental backups and weekly full backups,
configure the retention period as three cycles and 30 days. For help creating a backup
schedule policy, refer to the CommVault Simpana documentation.
Create a backup set

A backup set is a group with one or more subclients.
1. In the CommCell Browser tree, under Client Computers, locate the host that
contains the file system.
2. Right-click Filesystem under the host name and select All Tasks > Create New
Backup Set.
The Create New Backup Set dialog box appears.
3. Enter a Backup Set Name, select a Storage Policy, and click OK.

The Backup Schedule dialog box appears.
4. Do one of the following:
Select either Schedule or Do Not Schedule.

If you have already created a Schedule Policy, you can select it from the
Associate with Generic Schedule Policy list.
In the Associate with Generic Schedule Policy list, you can select System
Created.
The new Backup Set appears in the CommCell Browser dialog box under the
iDataAgent.
Create a subclient
Under Client Computers create a new subclient under the newly backup set for a
particular client.
1. In the CommCell Browser tree, under Client Computers, locate the host that
contains the file system.
2. Right click the backup set name and choose All Tasks > New Subclient.
The Subclient Properties dialog box appears.
27
Figure 7: Subclient Properties dialog box

3. Enter a Subclient name on the General Tab. Accept the defaults for all of the other
fields.
4. Select the Content Tab. This is where you select the source data from the client.
Click Browse to add folders and files. (If you know the exact path, you can select
Add Paths.)
After you click Browse, the Browsing content dialog box appears.
5. Select a source folder or file and click Add. Repeat this process for each file or
folder that you want to back up. Check the results in the Content Tab, Contents of
subclient dialog box.

6. When you finish selecting source files, click the Storage Device Tab of the
Subclient Properties dialog box.
7. Use the Data Storage Policy subtab to associate a Storage Policy with the
subclient.
In this example, BackupToDataDomain is selected. View the Data Paths by
clicking the Data Paths section.
29
8. In the Data Transfer Option subtab of the Subclient Properties dialog box, set
Software Compression to off. See Figure8.
Figure 8: Subclient Properties Dialog Box, Storage Device Tab

9. In the Deduplication subtab of the Subclient Properties dialog box, set

Deduplication to No Deduplication. See Figure9.
Figure 9: Subclient Properties Dialog Box, Storage Device Deduplication tab

10. Check the new subclient by clicking on the backup set name in the CommCell
Browser.
Note: You must disable all compression options under the Storage Device tab for
optimal Data Domain system global compression.
31
Figure10 shows an example of a properly configured subclient called ph5-test-

subclient.
Figure 10: CommCell Console Showing a Subclient
Configuring CommVault Simpana for Optimal Compression

This section explains how to optimize compression on a Data Domain system by
disabling the CommVault Simpana compression options for Storage Policies and for
the subclient.
Increase the Chunk Size and Block Size

For optimal Data Domain Magnetic Library performance and improved
compression, increase the chunk and block sizes immediately after creating a new
Storage Policy. These terms are defined in the Concepts and Terms section. The
chunk size can be applied globally to a Media Agent or locally to a specific data path.
The local data path settings will override the Media Agent setting. The block size can
only be applied to a data path.
Note: Set the chunk size for the Data Domain system by using a data path so that the
chunk size settings do not get changed globally for existing backup targets that are
being managed by a particular Media Agent.
1. From the CommCell Browser, click + next to Policies, and click + next to Storage
Policies.
2. Right click the new storage policy and select Properties.

A tab for this policy name appears to the right.

3. Right click Primary Copy and select Properties.
The Copy Properties: Primary Copy dialog box appears.

4. Click the Data Paths tab. See Figure11.
Figure 11: Copy Properties: Primary Copy dialog box

5. Select a path and click Properties.
33
The Data Path properties dialog box appears.
6. Increase the Chunk Size (MB) and Block Size (KB) settings as shown below.
Use a Chunk Size a value of 4096 kB.

Use a minimum Block Size a value of 256 kB.
7. Click OK and then, in the Copy Properties: Primary Copy dialog box click OK
again to save the settings.
8. Set the Data Path Properties for all of the storage policies that you created with
new data paths that reference the Data Domain system.
9. Perform a test full backup job after the values have been modified. Verify that the
size of the CHUNKMAP_TRAILER file is 256 kB after the full backup is complete.

Verify that multiplexing is disabled

Backup data multiplexing was designed to let multiple slow client data streams use a
tape device at an efficient data rate. Data multiplexing offers no benefits when
working with disk media. Moreover, multiplexing of data that is being written to
Data Domain systems yields poor compression results. In CommVault Simpana, you
must disable multiplexing for each copy in a Storage Policy that uses Data Domain as
a backup target.
1. Left click a Storage Policy name in the CommCell Browser to view the all of the
associated copies. There should be at least one primary copy present.
2. Right click the desired copy name and select Properties from the context menu.
3. The Copy Properties dialog box appears.
4. Click the Media tab and confirm that the Enable Multiplexing setting is not
selected, as shown in Figure12.
Figure 12: Multiplexing Disabled in the Copy Properties Dialog Box
35
Data Expiration and Space Reclamation

Data Domain systems use a scheduled cleaning operation to reclaim space for
expired data. By default, cleaning occurs on Tuesdays at 6:00am. To ensure that the
Data Domain system recognizes that Simpana backup data has expired, follow the
procedure below that matches your networking setup:
Shared Magnetic Libraries that use CIFS
VTL Devices that use Fibre Channel
Shared Magnetic Libraries that use CIFS

To mark data as expired, either schedule or manually start a job pruning process.
This updates the CommServe database with information about which data should
get expired.
By default, a data ageing and pruning process runs daily on the CommServe. On the
Data Domain system, there is a default weekly cleaning process. Data Domain
recommends that you let both of these automatic processes run.
To manually start a job pruning process

1. Right click the Storage Policy and choose View > Jobs.
The Job Filter for Storage Policy: dialog box opens.

2. Select the appropriate search parameters and click OK.
3. Select the jobs that you want to prune and click Prune Job.
4. In newer versions of the Simpana software, you must also select the media. Right
click the Media choose View > Media.
The Media used by Job ID dialog box (Figure13) appears.

5. Select the desired media and then Delete Contents from the media context menu
to prune. See Figure13.
Figure 13: Deleting Media Contents (Pruning) Manually

The selected job gets marked and becomes available for a Data Aging operation.
Note: Job pruning or content deletion will only remove the job permanently from the
CommServe database. This process will not delete the backup files from the Shared
Magnetic Library.
6. Schedule or manually start a Data Aging process on the CommServe after the
pruning operation finishes. This expires the backup data and prepares it for
deletion on the Data Domain system.
To run the Data Aging job manually:
a. Right click the CommServe name in the CommCell Browser (the upper node
in the tree) and select All Tasks > Data Aging.
b. Select Run Immediately for an unscheduled Data Aging process.
By default, Simpana data aging happens once per day at 12:00pm.

At the next scheduled cleaning cycle, the data will be deleted from the Data Domain
system and the space will become available for future backup jobs
37
VTL Devices that use Fibre Channel

For VTL devices, the backup administrator must format or long erase Data Domain
virtual tape media for the Data Domain system to recognize that the data is to be
deleted. Expired Simpana tape volumes will not be automatically deleted from the
Data Domain system. The default policy will have them recycled and placed in a
scratch pool for future use. Data Domain recommends that you schedule media
recycling to occur automatically. By default, new media in the library will be used
prior to existing recycled media.
Erasing media manually in Simpana is a two step process. First the tape media must
be removed as assigned media in the SQL database to mark the backup data as
expired. Second, the media with the newly expired data must be long erased.
To have the Data Domain system reclaim space manually

1. Right click the Storage Policy name under Storage Policies and select View > Jobs.
The Job Filter for Storage Policy dialog box appears.

2. Select the appropriate search criteria and click OK.
Jobs appear on the Job for Storage Policy tab in the CommCell console.
3. Right click the Job ID and select View Media from the context menu.
The Media Used by Job ID dialog box appears.

4. Right click a particular media and select Delete Contents. Read the warning
dialog box and click Yes to continue. See Figure14.
Figure 14: Delete Contents for Selected Media

The Enter Confirmation text dialog box appears.

5. Enter the text that the dialog box requests and click OK.
The Delete Contents and Move Media dialog box appears.

6. Select the Scratch/Overwrite Protect Media pool. By default the Default Scratch
media pool is selected
7. Click OK to delete the contents. The media gets moved from the Assigned Media
group to the selected Scratch media pool. Repeat these steps for each media that
you want to expire for the selected job.
8. Select the Default Scratch media group.
The media appears in the Default Scratch tab.

9. Right click the desired media and select Erase Media.
After a few moments, the media gets loaded into a free Data Domain virtual tape
drive and erased. See Figure15.
Figure 15: Erasing media in the Default Scratch media group
39
After a few moments, the tape icon changes under the Status window to indicate
that it is now ready to be recycled for use. See Figure16.
Figure 16: Virtual tape ready to be recycled

At the next scheduled cleaning cycle, the data will be deleted from the Data Domain
system and the space will become available for future backup jobs.

Backup and Restore Operations

After you configure a subclient with a new Storage Policy, Data Domain recommends
that you run a small test backup job followed by a test restore job. While those jobs
run, observe their progress and check for errors.
Note: To check a group of subclients simultaneously, perform a backup at the
Backup Set level.
To start a backup operation

1. Select the backup set in the CommCell browser.
2. A list of subclients appears on the right side of the CommCell Console window.
3. Right click the subclient and select Backup.
The Backup Options for Subclient dialog box appears.
Figure 17: Backup Options for a Test

4. Set the backup options and click OK.
In Figure17, a Full backup is selected to Run Immediately.

5. Right click the Job ID row under the Job Controller box within the CommCell
Console to view the backup job progress.
When the backup job finishes, the status appears in the Event Viewer box below the
Job Controller box.
41
To start a restore operation

1. Right click the client name under Client Computers in the CommCell Console
and select All Tasks > Browse & Recover.
The Browse Options dialog box appears.
2. Select the latest data, or specify the time window, and click OK.
3. A list of files that you can restore appears in the Client Tab on the CommCell
Console, as shown in Figure18.
Figure 18: Restorable Files for a Client

4. Select the appropriate files and click Recover All Selected.
The Restore Options for All Selected Items appear. For a test restore, the defaults
should be acceptable.
5. Optionally, to change the destination path, clear the Restore to Same Paths and
select the restore location.

6. Optionally, click Advanced to open the Advanced Restore Options tab. For a test
restore, the defaults should be acceptable.
7. Click OK to start the restore.
8. Click through the Warning dialog box about service pack compatibility if it
appears.
9. The restore job appears in the Job Controller tab. The progress can be tracked in
more detail by double clicking on the job id number to open the Restore Job
Details box. Click the View Events button for a detailed event view. The progress
shows 100% when the job completes.
Figure 19: Job Controller box
43
VTL Configuration
Virtual Tape Library (VTL) is a licensed feature that must have licenses registered on
both the Data Domain system and for one or more defined Media Agent servers on
the CommServe. Valid Media Agent servers appear under Storage Resources >
Media Agents on the CommCell Console.
To configure a Data Domain system as a VTL target device for Simpana data
protection operations, perform the procedures listed below:
Establish the FC connection, install drivers, and verify the connection on the
CommVault Media Agent server
Create a VTL group on the Data Domain system
Verify the Fiber Channel configuration for the VTL
Configure the new VTL on the CommVault Media Agent server
Establish the FC connection, install drivers, and verify the

connection on the CommVault Media Agent server
1. Physically connect and configure a Fibre Channel (FC) connection between the
Data Domain system and the CommVault Media Agent server.
2. Check that the correct changer driver and tape driver are installed and loaded on
the CommVault Media Agent server.
Note: For the required changer and tape drivers, see the VTL compatibility matrix
for the DD OS version at https://my.datadomain.com/documentation, under
Compatibility Matrices.

3. Log into the command line interface (CLI) on the Data Domain system as
sysadmin, and enter the vtl initiator show command as shown in the
following example.
# vtl initiator show
Initiator Group Status WWNN
WWPN Port
--------- ---------- ------- -----------------------
----------------------- ----
ph5_pt1 ph5_group Online 20:00:00:00:c9:6e:a7:28
10:00:00:00:c9:6e:a7:28 5a
Offline 20:00:00:00:c9:6e:a7:28
10:00:00:00:c9:6e:a7:28 5b
--------- ---------- ------- -----------------------
----------------------- ----
Initiator Symbolic Port Name
--------- ------------------
ph5_pt1
Figure 20: Initiators with Aliases on a Data Domain System

If the Storage Area Network (SAN) connection is configured correctly, the initiator on
the CommVault Media Agent server appears with the Online status. Figure20 shows
initiators that have been configured with aliases on a Data Domain system.
Create a VTL group on the Data Domain system

You can create a VTL group at the DD OS command line or via a web browser by
using the Data Domain Enterprise Manager. The example in this section uses DD OS.
Currently, the Data Domain VTL option supports an STK L180 changer and virtual
LTO-1, LTO-2 and LTO-3 drives. Refer to the Virtual Tape Library chapter of the Data
Domain Operating System User Guide for more information about the VTL feature,
including the creation of virtual tape drives, virtual tape media and virtual changers.
1. On the Data Domain system, create a VTL group.
2. Add the VTL and the initiator to the VTL group.
3. Confirm the VTL configuration with the command vtl group show groupname.
45
The results should be similar to the next example, which shows a valid VTL
group with one initiator, two changers, and five drives.
# vtl group show ph5_group

Group: ph5_group
Initiators:
Initiator Alias Initiator WWPN
--------------- -----------------------
ph5_pt1 10:00:00:00:c9:6e:a7:28
--------------- -----------------------
Devices:
Device Name LUN Primary Ports Secondary Ports In-use Ports
------------ --- ------------- --------------- ------------
vlt3 changer 3 all all all
vlt3 drive 1 4 all all all
vtl2 changer 0 all all all
vtl2 drive 1 1 all all all
vtl2 drive 2 2 all all all
------------ --- ------------- --------------- ------------
4. Check that the tape marker type is set to auto or CV1:
# filesys option show

Option Value
------------------------------- --------
Local compression type lz
Marker-type auto
Report-replica-as-writable disabled
Current global compression type 9
Staging reserve disabled
------------------------------- --------
Note: Only the auto marker setting is available with DD OS 5.0 and onward.

Verify the Fiber Channel configuration for the VTL

Before discovering the new VTL device within the CommVault Media Agent server,
follow the steps below to ensure that the operating system and HBA drivers discover
the VTL device.
1. At the operating system level, check that the changer and tape drives are
discovered properly.
2. Use the FC HBA management tool to ensure that the LUNs for both the changer
and the tape drives are discovered and mapped properly.
Data Domain recommends that you configure the HBA driver for target-
persistent binding.
3. On the Fibre Channel switch, check that the target Data Domain system and the
initiator (CommVault Media Agent server) are both zoned properly.
4. If the zoning is correct but you still cannot see the VTL target devices, ensure that
both the Data Domain VTL HBA and CommVault Media Agent HBA are online
in the switch name server.
Configure the new VTL on the CommVault Media Agent

server
This section describes the tasks to configure a new Data Domain VTL within a
CommVault Media Agent that has LTO-2 drives.
1. For Windows systems, install the IBM tape drivers as well as the STK library
driver. See the VTL compatibility matrix on the Data Domain Support web site for
the correct driver versions.
For Unix or Linux Media Agents, use the supplied CommVault drivers.
2. In the CommVault console, select Tools > Control Panel and double-click Library
and Drive Configuration.
3. From the Select Media Agents window, select the Media Agent that connects to
the Data Domain VTL library.
47
4. (Some systems) For Media Agent servers that do not use DDS, right click
Libraries and select Detect/Config Devices.
The Detect Library dialog box appears.
Figure 21: Detect Library dialog box

5. Deselect Automatically Create DDS Drivepools and click OK.

Auto detection should now start. All of the drives that the CommVault software
recognizes appear in the Log window. Figure22 shows an example with two VTL
libraries.
Figure 22: Log window

6. If a prompt in the Log window asks for the media type, select the appropriate
type. For example, if LTO-1 drives are used in the VTL device, select ULTRIUM.
7. After you create the library, right click the library in the Library and Drive
Configuration window choose Configure.
The Configure dialog box appears.
8. Select Library and all drives, and click OK.
49
9. If a confirmation dialog box asks if there a barcode reader, click Yes.
The Discover Media Options dialog box appears.
10. Select the default media type. For LTO-2 drives, select ULTRIUM V2. For LTO-3
drives, select ULTRIUM V3.
The new Library appears as configured. Figure23 shows two libraries that have
been added. Note that one is in a configured state and the other is not configured.
Figure 23: Example of Configured and Unconfigured Libraries

Note: If you close the Library and Drive Configuration window without configuring
a library, the unconfigured library disappears from the Libraries tab list. Configure
all of the libraries before closing the window.
This completes the VTL configuration procedure.

Simpana Tape Drive and Media Management

Tape drives are managed either individually or through a Master Pool for each
robotic changer. Media are managed by using the Media by Location, Media by
Groups, Slots, and I/E ports items under the Library name in the Storage Resources
branch of the CommCell Browser. See Figure24.
When you select a group, the media in that group appear in the upper right window
of the CommCell Console. From the media list, right click a particular tape volume to
view the status and perform various media management tasks.
Figure 24: Tape Drive and Media Management

New blank media appear in the Default Scratch group by default. Tape media with
live data appear under Assigned Media. New tape media are made ready for use
automatically after the CommVault software discovers the Data Domain VTL and
you configure the VTL in the Library and Tape Configuration tool.
To discover new media that have been imported from the

Data Domain vault
Right click the VTL name and select Discover Media.
51
To import new media from the I/E ports

Right click the VTL name and select Import Media.
If you enabled the Auto-Discover option for the library, the newly imported
media automatically get discovered and formatted for immediate use.
To view media in the I/E ports, click I/E ports in the CommCell Browser. The I/
E Ports list appears on the upper right side of the CommCell console. See
Figure25.
Figure 25: I/E Ports List
To export media from a library slot to the I/E ports

1. Right click the VTL name and select Export Media.
The Export Media Wizard dialog box appears.

2. Answer the Vault Tracker question and click Next to continue.
3. Select the desired media and click Finish.
4. Click Exports in Progress to view the results. See Figure26.
Figure 26: Exports in Progress List

Create a VTL Storage Policy

After you add the VTL to the CommVault Simpana configuration, you must create a
storage policy to utilize the VTL for backups. See Create a backup storage policy on
page 23.
Note: Be sure to disable hardware compression for the primary copy.
53
NDMP Configuration
NDMP Configuration
You can find detailed procedures with specific NAS device login and setup
information in the CommVault Books Online NAS NDMP Library and Drive
Configuration chapter.
Network Attached Storage (NAS) devices or filers get backed up to a Data Domain
target as backup clients with the NDMP protocol. The NAS device must have NDMP
enabled. Separate licenses are required for each NAS device type. For example,
separate licenses are required for NetApp and EMC NAS devices. Please read the
CommVault Books Online documentation for NAS-device-specific installation and
configuration details.
To perform data protection and recovery operations, the NAS NDMP agents require
a user account with which to log on to the filer and access the data. The user account
depends upon the filer being accessed. To configure an NAS device as an NDMP
client to be backed up to a Data Domain system through CommVault, follow the
procedures in this section.
You can set up the Data Domain system in two ways:
As a local backup destination: a Data Domain VTL gets connected to the NAS
filer either directly attached or through a SAN. No separate iDataAgent is
required for NAS devices. The required NDMP components are included in the
Windows Media Agent.
As an NDMP Remote Server (NRS) backup destination: a library gets connected
to a Media Agent and configured as a non-NDMP device. The Simpana library
type may either be a VTL or Magnetic. NRS is a separate package that must be
installed on the Media Agent from the DVD media. On Windows systems only,
you can install NRS at the same time as the Media Agent. For UNIX systems, you
must install NRS separately and then reboot the Media Agent server.
The procedures in this section show examples that use a NetApp filer NAS device
and a Data Domain system attached as a local backup destination.
This section contains the following procedures:
Add the NAS device as an NDMP client Page54
Discover and Configure Libraries and Tape Drives Page56
Create an NAS NDMP Storage Policy Page58
Configure Subclients Page58
Configuring an NDMP Remote Server (NRS) Backup Destination Page59

NDMP Configuration
Add the NAS device as an NDMP client

1. In the CommCell Console, right click Client Computers and select New Client.
The Add New Client dialog box appears.
Figure 27: Add New Client dialog box

2. Select NAS Client and click OK. See Figure27.
The Add NDMP Server Dialog Box appears.

3. Enter the NDMP hostname and NDMP login information. Once this information
is entered, click Detect.
The Add NDMP Server window re-appears.
55
NDMP Configuration
4. Note the entries in the Supported Features section and click OK. See Figure28.
Figure 28: Add NDMP Server dialog box

The NAS device appears with an NAS NDMP iDataAgent under Client
Computers in the CommCell Browser section of the CommCell Console. Note
that a defaultBackupSet and default Subclient also get created automatically.
They both get configured after you discover and configure the VTL devices and
create a Storage Policy.
This completes adding the NDMP NAS client.

NDMP Configuration
Discover and Configure Libraries and Tape Drives

Discovering and configuring Data Domain tape devices for an NDMP device is very
similar to the process discussed in CommVault Simpana Configuration section. There
are two methods, automatic detection and manual detection. This section shows how
to configure a locally-attached NetApp filer NAS device automatically. For
information on verifying tape drives and media changers, refer to your vendor
documentation.
1. Configure the Data Domain device as Static Shared Magnetic Library or VTL as
described in Simpana Static Shared Magnetic Library Configuration on page 18 or
VTL Configuration on page 43.
2. In the CommCell Console, select Tools > Control Panel and double-click Library
and Drive Configuration .
3. When prompted, add the Media Agents in the Select Media Agents dialog box.
The Library and Drive Configuration dialog box appears.

4. Right click Libraries and select Detect/Config Devices from the context menu.
The Detect Library dialog box appears.
5. Select the NDMP Devices and the Media Agent to control the library.
6. Select the Exhaustive Detection option to automatically map the drives in the
library. Tape media attempt to be mounted in each selected drive to properly
discover the drive and library mapping.
7. Click Yes on the Confirm Exhaustive Detection dialog box after reading the
warning that appears.
57
NDMP Configuration
The Select NDMP Servers to Detect dialog box opens.
8. Move the devices to the Selected NDMP Servers list and click OK.
9. If the Confirm dialog box appears, read the warning and click Yes.
After a few moments, the Processing window opens to show the status of the
detection process. When the detection process finishes, the Log window appears
to show the detected VTL libraries.
10. Click Close after confirming that the proper devices were discovered.
The Library and Drive Configuration window re-appears. The new library
appears in an unconfigured state and must be configured.
11. Right click the new library and choose Configure.
Note: The detected library and configuration information will not get saved if you
close the Library and Drive Configuration window before configuring the library.
The Configuration window appears.
12. Select Yes for Has Barcode reader.
13. Select Yes for Should the media be automatically discovered.
14. Check the Data Paths tab to verify that the configuration is correct.
The Data Domain VTL library and drives are now detected and configured properly.

NDMP Configuration
Create an NAS NDMP Storage Policy

After you add the NAS device to the CommVault Simpana configuration, you need to
create a storage policy to use the NAS backups (unless a policy already exists.
See Create a backup storage policy on page 23. Be sure to disable all deduplication and
compression options for the primary copy when you create the storage policy.
Configure Subclients
After you have defined the new NAS device client and storage policies are defined,
configure the subclients to execute backup and restore jobs.
1. At a minimum, configure the General, Content and Storage Device tabs to
prepare a subclient for a backup and restore job. The default subclient under the
defaultBackupSet has all files on the NAS filer selected for backup by default.
2. Ensure that all deduplication and compression options are disabled.
3. For details, see Create a backup set on page 25 and Create a subclient on page 26.
Figure 29: Subclient Properties dialog box
59
NDMP Configuration
Configuring an NDMP Remote Server (NRS) Backup

Destination
Note: For local backup destinations, skip this procedure.
The CommVault Simpana NDMP Remote Server (NRS) lets you use a Data Domain
system as an NDMP target device when it is attached to a non-NAS device Media
Agent. The Data Domain target may either be a Shared Magnetic Library or a VTL.
1. To verify that the Simpana NRS is properly installed, right click the Media Agent
name in the CommCell Browser and choose Properties.
The MediaAgent Properties dialog box appears.
Figure 30: MediaAgent Properties dialog box

2. Click the General tab to view the status. Under Host Information, NDMP Remote
Server should be listed as Installed. See Figure30.
You can use any Data Domain libraries that are attached to the Media Agent with
the appropriate configured Storage Policies as backup targets with the NDMP
Remote Server option.
3. If a Storage Policy does not exist, create a new one that has a library attached to
the local Media Agent .

NDMP Configuration
4. Configure the NAS NDMP IDataAgent Subclient General, Content and Storage
Device tabs to enable NRS backup and restore of NAS Device data. See Figure31.
Figure 31: Subclient Properties dialog box, Content tab

Note: The Data Storage Policy subtab of the Storage Device tab will show blank
Storage Policy selections on the Storage Policy drop down list box if the NRS option is
not installed properly on the Media Agent .
After the NAS device Subclient configuration is complete, the NDMP Remote Server
is ready for backup and restore requests.
61
Simpana Troubleshooting
This section explains how to troubleshoot problems with CommVault Simpana. This
section contains the following procedures:
To view log files Page61
To check that the Simpana processes and services are running (UNIX) Page61
To check that the Simpana processes and services are running (Windows) Page62
Handling a pending backup job on a Windows media agent Page62
To view log files

In Simpana, you can view the logs under the installation directory of any
CommServe, Media Agent or Client system.
On a Windows system, if you choose the default locations during the installation,
the logs are under
C:\Program Files\CommVault\Simpana\Log Files
On UNIX servers, the log files are under /var/log/simpana/Log_Files

The log files are in ASCII text format. On Windows, you can use Notepad or
WordPad to view log files. On UNIX or Linux systems, use the cat or more
command.
To check that the Simpana processes and services are

running (UNIX)
1. Log in as root
2. Enter the ps -ef command.
3. Make sure the UNIX processes needed for Simpana are running, as shown in the
following example output.
# ps -ef | grep simpana

root 2019 1 0 Mar 25 ? 0:29 /opt/simpana/Base/EvMgrC
root 2018 1 0 Mar 25 ? 5:01 /opt/simpana/Base/cvd
root 2020 1 0 Mar 25 ? 6:19 /opt/simpana/MediaAgent/CvMountd
4. If the system is a Media Agent, select MediaAgents > Media Agent name in the
CommCell Browser and check that the Status is Ready.

To check that the Simpana processes and services are

running (Windows)
1. Select the Service Control Manager Tool from the Start Menu.
2. To see more detail, check the service status by using the standard Windows
Services manager.
3. If the system is a Media Agent, select MediaAgents > Media Agent name in the
CommCell Browser and check that the Status is Ready.
Handling a pending backup job on a Windows media agent

If the status of a backup in progress changes from Running to Pending in the Job
Controller window for a Windows Media Agent on the CommCell Console, ensure
that the Fragmentation setting is set to the default.
1. Open the Backup Job Details window to the Progress Tab.
2. Check the Reason for job delay for messages.
3. If the message is
Error Code: [62:1225] Description: Actual size of chunk on the disk does not
match size of chunk stored in CommServe Database
do the following:
63
a. Select the Mount Path for the Media Agent and open the Mount Path
Properties window. See Figure32.
Figure 32: Mount Path Properties dialog box

b. Select the Allocation Policy Tab.
c. Change Fragmentation to Minimize Fragmentation by allocating write

blocks of 128 MB and click OK.
This restores the default setting.
d. Right click the Pending Job and select Resume.
The job status should change from Pending to Running.

Advanced Topics
Advanced Topics
This section contains the following advanced topics and procedures:
Configuring Simpana Multistream Backups Page64
Static Shared Magnetic Library Configuration for Replica Restores in FS Mode Page75
Configuring Restores from a Replica Data Domain System Page77
Write Aux Copies to Tape with a Replica Data Domain System as the Source Page83
Configuring Simpana Multistream Backups

By default Simpana backups are configured for a single concurrent stream. While this
is ok in many cases, a single concurrent stream may limit the total performance and
critical backup jobs may not finish within the backup window. Data Domain systems
can handle multiple streams at once and it is recommended to tune the number of
Simpana streams to gain maximum performance. There are a number of factors that
contribute to an optimal setting. These include the number of clients, Media Agents,
Data Domain model and Data Domain OS release as well as specific environmental
factors.
It is highly recommended to read the CommVault Books Online and the Data
Domain User Guide to understand stream concepts and what the maximum total,
read and write stream counts should be. The backup environment should also be
evaluated to ensure bottlenecks arent accidently created somewhere else. Avoid
multiplexing for compression reasons.
65
Advanced Topics
Configuring multistream backups of static shared magnetic

libraries
Follow this procedure to configure a Simpana for 5 concurrent backup streams that
get stored in a static shared magnetic library.
1. Increase the number of Subclient Data Readers:
a. Open the Subclient Properties dialog box to the General tab.
b. Set the number of Data Readers to 5. The default is 2.
c. Select Allow multiple data readers within a drive or mount point and click
OK.
2. Modify the Magnetic Library Writer values:
a. Right click a Shared Magnetic Library name and choose Properties.
The Library Properties dialog box appears.

Advanced Topics
b. In the Mount Paths tab, check the Mount Path allocation policy. Either select
Maximum Allowed Writers or set Allocate No. of Writers to 5, and click OK.
3. Modify the Magnetic Library Mount Path Writer values:
a. Right click a Mount Path from the list on the right side of the CommVault
window and choose Properties.
b. In the Allocation Policy tab, select Allocate No. of Writers, set the value to 5,
and click OK.
c. Repeat Step a and Step b for each mount path in the library.
4. Modify the Storage Policy Streams to increase the number of streams for the
policy. By default, most versions of the Simpana software limit the number of
streams to 1.
a. Right click a Storage Policy and choose Properties.
67
Advanced Topics
b. In the General Tab, set Device Streams to 5 and click OK.
Note: The number of streams configured in the Storage Policy should be equal to or
greater than the number of Data Readers specified in your Subclient Properties.
5. Start a backup of the subclient and check the stream count in the Streams tab of
the Backup Job Details window
6. Verify that the number of streams is correct. See Figure33.
Figure 33: Backup Job Details Showing Five Streams

Advanced Topics
Configuring multistream backups of a VTL

Typically you would configure one stream per drive on the Data Domain system.
This example shows how to configure the Simpana software for two concurrent
streams for a two-drive Data Domain VTL.
Note: If the Data Domain system has more than two drives, Data Domain
recommends that you configure one stream per VTL drive and avoid multiplexing.
1. Modify the number of Subclient Data Readers
a. Open the Subclient Properties - General Tab. Set the number of Data Readers
to a value of 2. The default setting is 2.
b. The Allow Multiple Data Readers needs to be enabled as it is off by default. It
is enabled by viewing the Subclient Properties - General Tab and selecting
Allow multiple data readers within a drive or mount point. Click OK to save both
settings and close the window
2. Modify the Storage Policy Streams. This setting caps the number of allowed
streams for a particular policy. The default setting is 1. This may vary depending
on the Simpana version.
a. Right click a Storage Policy and select Properties.
b. Select the General Tab to view the Device Streams setting under No. Of
Copies entry.
c. The General Tab appears. Change the Device Streams: value to 2. Click OK to
save the setting
3. Initiate a backup of a desired Subclient and view the stream count in the Streams
tab of the Backup Job Details window to verify that the number of streams are as
desired. In this case, we desired 2 streams, 1 per VTL drive. See Figure34 for an
illustration.
Figure 34:
69
Advanced Topics
Configuring multistream backups of an NAS device

Multistream backups of an NAS Device that utilizes NDMP are only possible for an
NAS client that either :
Has subclients for which multiple data content paths are defined.
Specifies a content path of "/" and has more than one volume or root file system.
NAS subclients that do not meet either of those requirements cannot use multiple
data streams.
Note: If the Storage Policy uses a VTL, Data Domain recommends against using
multistream backups. See Verify that multiplexing is disabled on page 34 for an
explanation.
To configure multistream backups with two content paths:
1. Open the Subclient Properties dialog box to the Content tab.
2. Use the Add Paths command to specify multiple content paths. In Figure35, there
are two content paths.
Figure 35: Subclient with Two Paths Defined

3. In the General tab, set the Number of Data Readers to specify the maximum
number of concurrent backups. The default is 1.
4. In the Storage Device tab, assign a Storage Policy that contains as many streams
(or more streams) than the value you specified for Number of Data Readers.
5. Run a backup and check the Streams tab in the Backup Job Details window to
confirm the desired number of concurrent backups.

Advanced Topics
Configure replication on a Data Domain system

1. Log on to the Data Domain Enterprise Manager or the DD OS command line.
2. Do one of the following:
In the Enterprise Manager, select License.

In the CLI, run the license show command.
3. Verify that you have a replication license .
4. Configure replication as described in the Data Domain Operating System

Administration Guide.
Figure36 shows an example of a tape pool replication on a Data Domain system. In
the example, the source (primary Data Domain system) is dd400, and the destination
(the target Data Domain system) is thekid.
Figure 36: Tape Pool Replication Example
71
Advanced Topics
Restore from a Data Domain system replica in a VTL

To restore backups from a Data Domain replica when using a VTL, the required tape
media must be exported from the Data Domain source in both the Simpana media
agent and the replica Data Domain system.
1. Check that the tape media are all replicated to the Data Domain replica by
running either the replication sync or replication status command.
2. Use the replication sync command to verify the last time the two Data
Domain system were synchronized.
3. Import the tape media from the Data Domain vault into the Data Domain replica
VTL.
Note: The overall process of export and import is very similar to the process used
with a physical tape library. With a physical tape library, tape media gets ejected and
then inserted into another physical tape library that has the same LTO tape drive
model. On the Data Domain system, exporting tape media into the Vault is similar to
ejecting tape media out of a physical tape library.
4. Verify the status of replication by checking the Sync-ed-as-of-time.
#replication status all

CTX: 1
Mode: destination
Destination: pool://mysystem.local/nw-copy
Enabled: yes
Local filesystem status: enabled
Connection: connected since Tue Nov 11 12:44:37
State: normal
Error: no error
Synced-as-of time: Wed Nov 12 12:07
Current throttle: unlimited
In the example, the Synced-as-of time shows the last time that the two Data Domain
systems were synchronized.

Advanced Topics
Import volumes into a new VTL on a secondary Data Domain

system from a replica
On the command line of the secondary Data Domain system, run the VTL import
command with the following syntax:
#vtl import stk1 barcode DQT014L2 count 10 element slot
address 25
... imported 10 tape(s)...
The example shows that 10 replicated VTL tape volumes from a secondary Data
Domain system have been imported into a new tape library named stk1. Address 25
is the first slot number in the range of slots.
Restore from a secondary Data Domain system VTL

1. On the secondary Data Domain system, use the vtl import command to move
the tapes from the Data Domain vault to the library. See the Data Domain
Operating System Administration Guide for the procedures.
2. In the CommCell console, right click the tape volume from the Media In Library
Tab and select Export. See Figure37.
Figure 37: Export Tapes Example

3. On the Data Domain system, do one of the following to verify that the tape media
location has changed from Slot to Vault.
73
Advanced Topics
On the command line, enter the vtl tape show command with the following
syntax:
# vtl tape show vault barcode AAA001L1
Processing tapes....
Barcode Pool Location Type Size Used (%) Comp ModTime
-------- ---- -------- ----- ------ ----------------- -----
AAA001L1 nw vault LTO-1 50 GiB 10.0 GiB (20.01%) 1046x 2008/
11/11
14:10:35
-------- ---- -------- ----- ------ ----------------- -----
VTL Tape Summary
----------------
Total number of tapes: 1
Total pools: 1
Total size of tapes: 50 GiB
Total space used by tapes: 10.0 GiB
Average Compression: 1046.2x
4. If the tape media are not in the Data Domain vault, move the tape media from the
slot to the vault.
5. On the Data Domain system replica, create a new VTL with the same type of tape
drive that is currently being used in the Data Domain System source. See VTL
Configuration on page 43 for details.
6. On the Data Domain system replica, import the tape media into the VTL library.
On the Simpana Media Agent server, the tape media gets detected after a few
minutes.

Advanced Topics
7. In the CommCell Console, verify that the replica tape media has been imported.
Figure38 shows a successful detection by Simpana of the tape media imported
from the Data Domain replica.
Figure 38: Imported Tape Media

8. On the subclient, restore the desired data from the imported tape by right clicking
the client computer and choosing All Tasks > Browse & Recover.
Note: There are no special requirements to do the restore. See Backup and Restore
Operations on page 40.
75
Advanced Topics
Static Shared Magnetic Library Configuration for Replica

Restores in FS Mode
Data Domain leverages the Simpana Shared Disk feature for replication control. Use
the Library and Drive Configuration tool to configure a source read/write Data
Domain system and a secondary read-only destination Data Domain system as a
single Network Shared Device. In the Simpana documentation, this approach is
called the Media Agent Replication solution.
Requirements
The hardware requirements are:
Two Simpana Media Agents
Two Data Domain systems, one the read/write source and the other a read-only
replica.
The license requirements are:
MediaAgent, Continuous Data Replicator (CDR), and Magnetic Libraries licenses
for the Simpana software.
A Replication license for the Data Domain system.
In the examples that follow, both of the Media Agents are in the same CommCell and
all of the systems are members of the same Microsoft Active Directory domain.

Advanced Topics
CIFS Restore from a Replica Process Summary

Here is a summary of the process for recovery from a replica when using a CIFS
magnetic library (refer toFigure39):
1. MA1 gets backed up to the locally attached Data Domain system.
2. The backup data gets replicated by using either Data Domain directory or
collection replication from the source Data Domain system to the replica Data
Domain system.
3. A restore occurs from replicated data that MA2 can access while connected to the
Data Domain replica
Figure 39: Directory Replication Configuration Example

When configuring for replication restores, keep the following points in mind:
Always configure the read/write mount path within Simpana first. If the Media
Agent that accesses the primary disk (the read/write accessible mount path) is
not configured first, expired backups do not get pruned from the disk and the
Data Domain system cannot reclaim space.
Do not add a data path to any storage policy copy if the data path points to the
read-only mount paths. Backups would fail without write permission. Read-only
operations do not require a data path.
During de-configuration, do not de-configure the read/write data path first.
Delete the read-only data path before removing the read/write data path.
If the Media Agent with read/write access is offline, expired backups cannot be
pruned from the read-only Media Agent.
77
Advanced Topics
Configuring Restores from a Replica Data Domain System

The following procedure describes how the Data Domain systems and Simpana
Media Agents must be configured on the CommCell console so that the first Media
Agent read write device points to the Data Domain system originator, and the second
Media Agent points to the Data Domain system replica.
To configure restores, the replica directory structure must be identical to the
source Data Domain system. For example:
ddrsource/backup/test > ddrtarget/backup/test
If you are using a Windows workgroup, set up the CommVault service user
account on each local system to match a user account on the local Data Domain
system.
This configuration ensures that, when Media Agent MA1 backs up the data, it writes
the data to the local read/write device. When a second Media AGent requests a
restore, , MA2 Simpana restores from the replica read-only folder.
To configure the systems, set up a Static Shared Magnetic Library that uses a
Network Shared Device by following these procedures:
Create a network shared device
Create a shared magnetic library device and mount paths
Create a network shared device

1. From the Simpana Control Panel, open the Library and Drive Configuration
dialog box.
2. Select the two target Media Agents to configure.
3. Click Add and then click OK.
The Media Agent attached to the Data Domain system to which the primary copy
is written is the read/write shared disk.
The second Media Agent, which will access the replica Data Domain system for
restores, will have read-only access to the Network Shared Device.
The Galaxy Library and Drive Configuration dialog box appears.
4. Click the Shared Disk Device tab.

Advanced Topics
5. Right click Disk Devices and choose Disk Device > Add to create the disk
resource for the primary (read/write) copy.
The Add Sharing Folder dialog box appears.
Figure 40: Add Sharing Folder dialog box

6. Select the read/write Media Agent that is used for backups from the clients. To
match the example in Figure39, you would enter MA1.
7. In the Add Sharing Folder dialog box:
a. For a CIFS Shared Disk Device, fill out the Network Path information.
b. Enter the user name that the Media Agent uses to access the network path, the
password for that user, and the UNC path for the folder, and then click OK.
In an Active Directory environment, specify an Active Directory user. For a
Workgroup environment, specify a local account on the restorer.
In Figure42, the Folder path is \\dd565-1\backup\rep.
Note: For a UNIX and NFS-based configuration where the Media Agents are running
on UNIX or Linux servers, enter the information in the Unix Sharing Folder section
near the top of the window.
The Library and Drive Configuration Window appears.
79
Advanced Topics
8. Right click the network sharing device that you created and choose Add Replica
Sharing Folder. This adds the second Media Agent and a path to the replica Data
Domain system. Add the path to the replica copy of the magnetic library.
The Add Sharing Folder window appears. Note that by default, the second Media
Agent with read-only access appears in the Media Agent drop down box.
9. Fill in the Network Path section as before, enter the appropriate user account and
password, and click OK. The folder must already exist on the replica destination. Here is
an example, \\dd410-4\backup\rep. See Figure41 for an illustration.
Note: The replica directory structure must be identical to the source Data Domain
system. For example: ddrsource/backup/test > ddrtarget/backup/test.
Figure 41: Entering the Path to the Replica Copy

Advanced Topics
10. In the Library and Drive Configuration window that appears, select
NetworkSharingDevice#.
a. Right click and select Configure. This saves the previous settings.
b. Click Yes in the Confirm Configure dialog box.
11. Rename the device by right clicking the Network Share Device and selecting
Properties.
12. Enter the new name and click OK.
This completes the creation of the Network Share Device. Figure42 shows a properly
configured network shared device in the Library and Drive Configuration dialog box.
Figure 42: Network Share Device for Replication
81
Advanced Topics
Create a shared magnetic library device and mount paths

1. From the Library and Drive Configuration window, select either Libraries or Data
Paths.
Note: The following example uses the Data Paths tab.
2. Right click Data Paths, select Add, and select Shared Magnetic Library to create
the appropriate library. See Figure43.
Figure 43: Adding a Shared Magnetic Library

The Add Magnetic Library dialog box appears.
3. Specify an Alias Name
4. Deselect the Confirm that Automatically create storage policy for new data paths
option if necessary, and click OK.
The Shared Mount Path Window appears
5. In the Disk Device drop down list box, select the Network Shared Device that you
created to associate with the mount paths.
6. In the Base Folder list that appears in the Shared Mount Path window, enter a
unique name for which the new mount path will store data.

Advanced Topics
This completes the mount path setup. See Figure44 for an illustration of how the
final configuration would appear in the Library and Drive Configuration
Window.
Figure 44: Shared Magnetic Library with Single Mount Path

7. Create a new Storage Policy. See Create a backup storage policy on page 23.
8. Prepare a subclient for replicated backups. See Create a subclient on page 26.
Perform a test restore from the replica

To check that the user authentication is working properly and that you can recover
data from the replica, follow these steps:
1. Perform a backup to the source Data Domain system
2. On the Data Domain system, configure and perform a directory replication

operation. See the Data Domain Operating System Administration Guide for
information about configuring a directory and about collection replication.
3. Perform a test restore by using the read-only Media Agent from the replica
system. See To start a restore operation on page 41.
83
Advanced Topics
Write Aux Copies to Tape with a Replica Data Domain System

as the Source
An Auxiliary Copy (Aux Copy) operation lets you create secondary copies of data
associated with one or more data protection operations, independent of the original
copy. An Aux Copy is tied to a Storage Policy for which a primary copy is already
defined.
The procedures in this section show how to create an Aux Copy from a replica Data
Domain system at a location that has a tape system attached to a Media Agent. This
example assumes that a Storage Policy has been defined that includes the replica
Data Domain system. For information about Auxiliary Copies, visit the CommVault
Simpana Books online.
Creating an Aux Copy

1. Select a Storage Policy that contains the Data Domain replica as backup target.
1. Right click the policy name and choose All Tasks > Create New Copy.
The Copy Properties dialog box appears.

2. On the General Tab, refer to Figure45 and enter the following information:
a. Under Copy Information, enter the Copy Name.
b. Under Default Destination, enter the Library, Media Agent, Drive Pool, and
Scratch Pool.
c. (Optional) Data Domain recommends that you enable the Combine source
data streams option with a value 1 or 2 on the General or Media tab. This
helps the Simpana software avoid wasting tape media.

Advanced Topics
Figure 45: Copy Properties dialog box, General tab

3. Click the Retention Tab and specify the retention settings for this copy.
4. Accept the default settings in the other tabs and click OK to save the
configuration.
The Auxiliary Copy Schedule dialog box appears.
5. Select a schedule option and click OK.
This completes the Aux Copy setup.
85
Advanced Topics

BPG Data Domain Commvault

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

BPG Data Domain Commvault

Enviado por

Direitos autorais:

Formatos disponíveis

CommVault Simpana 8.

EMC Data Domain, Inc.

This document provides information needed to integrate a Data Domain system as a

Related Documentation Page6

If desired, you can go directly to the following procedures.

4 CommVault Simpana 8.0 Software Application Introduction

Access to Integration-Related Documents at Data Domain

View Data Domain application integration documents

6 CommVault Simpana 8.0 Software Application Introduction

3. To view CommVault Simpana integration-related documents, perform the

b. Select CommVault from the Vendor menu.

4. To view compatibility matrices, perform the following steps.

a. Click Compatibility Matrices.

8 CommVault Simpana 8.0 Software Application Introduction

2. Select Install Simpana on this Computer for a local installation.

Concepts and Terms

Table 1: Terms (Continued)

10 CommVault Simpana 8.0 Software Application Introduction

Table 1: Terms (Continued)

Software Configuration Introduction

Access to the CommVault Simpana CommCell Console

Figure 1: CommServe Console Window

12 CommVault Simpana 8.0 Software Application Introduction

To access the CommCell Console from a Windows host

The Connect to CommCell window appears.

Storage Policy Description

Client Computer Data Backup Job Description

Figure 2: Subclient configuration dialog box

14 CommVault Simpana 8.0 Software Application Introduction

To view Data Domain system installed licenses

To review CommVault Simpana installed licenses

Data Domain CIFS Configuration

16 CommVault Simpana 8.0 Software Application Introduction

3. Verify that the marker setting is enabled.

# filesys option show

# cifs add /backup client-list

To enable access to all client, set the client-list parameter to *.

CommVault Simpana Configuration

VTL Configuration Page43

18 CommVault Simpana 8.0 Software Application Introduction

4. Configure the Data Domain system as described in Data Domain CIFS

Simpana Static Shared Magnetic Library Configuration

Configure a shared disk device for the Media Agent

2. Double click Library and Drive Configuration.

The Select MediaAgents dialog box appears.

The Library and Drive Configuration window appears.

4. Right click Disk Devices and select Disk Device >Add.

20 CommVault Simpana 8.0 Software Application Introduction

The Add Sharing Folder dialog box appears.

A typical network path is \\dd565-1\backup\cvtest. In an Active Directory

This completes the creation of a new Static Shared Disk Device

Create a Shared Magnetic Library for the new Shared Disk

The Add Magnetic Library dialog box appears.

6. Close the Library and Drive Configuration window.

This completes the configuration of the Shared Magnetic Library.

22 CommVault Simpana 8.0 Software Application Introduction

Figure4 shows two properly configured Static Shared Magnetic Libraries.

Simpana Backup Configuration

Create a backup schedule policy

Create a backup set

Create a backup storage policy

4. Add a storage policy name and click Next.

5. Enter a name for the Primary Copy and click Next.