CommVault Simpana 8.0 Application Introduction

(1)

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

Application Introduction

(2)

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.

(3)

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.

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.

(7)

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.

(8)

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 organization’s 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.

(9)

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 Aux Copy

An Aux Copy is defined within a Storage Policy and is one example of a 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.

(10)

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

Engine (CTE) The set of base-level CommVault Simpana software components used to 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)

(11)

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

(VTL) Hard disk storage that gets presented to the backup software as tape libraries.

Table 1: Terms (Continued)

(12)

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

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.

Figure 1 shows an example of a CommCell Console window.

Access to the CommVault Simpana CommCell Console Page 12

Client Computer Data Backup Job Description Page 14

Storage Policy Description Page 13

(13)

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 (Figure 1) 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 (Figure 7 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.

(14)

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.

Figure 2 shows an example subclient.

Figure 2: Subclient configuration dialog box

(15)

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.

(16)

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.

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.

# user add svc_simpana password mypassword priv admin

# 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.

(17)

3. Verify that the marker setting is enabled.

The auto value for Marker-type shows that the marker setting got applied.

4. Set CIFS client access permissions for Simpana media agents.

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.

CommVault Simpana Configuration

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:

# 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

# cifs add /backup client-list

Prerequisites Page 18

Simpana Static Shared Magnetic Library Configuration Page 18

Simpana Backup Configuration Page 23

Configuring CommVault Simpana for Optimal Compression Page 31

Data Expiration and Space Reclamation Page 35

Backup and Restore Operations Page 40

(18)

VTL Configuration Page 43

Simpana Tape Drive and Media Management Page 50

Create a VTL Storage Policy Page 52

(19)

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.

(20)

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.

(21)

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

(22)

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.

(23)

Figure 4 shows two properly configured Static Shared Magnetic Libraries.

Figure 4: Configured Shared Magnetic Libraries with a Data Domain Shared Disk Device

(24)

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.

(25)

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 Figure 5.

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 Figure 6 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

(26)

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.

(27)

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.

(28)

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.

(29)

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.

(30)

8. In the Data Transfer Option subtab of the Subclient Properties dialog box, set Software Compression to off. See Figure 8.

Figure 8: Subclient Properties Dialog Box, Storage Device Tab

(31)

9. In the Deduplication subtab of the Subclient Properties dialog box, set Deduplication to No Deduplication. See Figure 9.

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.

(32)

Figure 10 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.

(33)

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 Figure 11.

Figure 11: Copy Properties: Primary Copy dialog box 5. Select a path and click Properties.

(34)

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.

(35)

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 Figure 12.

Figure 12: Multiplexing Disabled in the Copy Properties Dialog Box

(36)

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 (Figure 13) appears.

(37)

5. Select the desired media and then Delete Contents from the media context menu to prune. See Figure 13.

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

(38)

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 Figure 14.

Figure 14: Delete Contents for Selected Media

(39)

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 Figure 15.

Figure 15: Erasing media in the Default Scratch media group

(40)

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 Figure 16.

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.

(41)

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 Figure 17, 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.

(42)

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 Figure 18.

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

(43)

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

(44)

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.

(45)

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.

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. Figure 20 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.

# 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

(46)

The results should be similar to the next example, which shows a valid VTL group with one initiator, two changers, and five drives.

4. Check that the tape marker type is set to auto or CV1:

Note: Only the auto marker setting is available with DD OS 5.0 and onward.

# 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 vlt3 drive 2 5 all all all vlt3 drive 3 6 all all all vtl2 changer 0 all all all vtl2 drive 1 1 all all all vtl2 drive 2 2 all all all --- --- --- --- ---

# 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 --- ---

(47)

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.

(48)

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.

(49)

Auto detection should now start. All of the drives that the CommVault software recognizes appear in the Log window. Figure 22 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.

(50)

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. Figure 23 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.

(51)

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 Figure 24.

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.

(52)

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 Figure 25.

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 Figure 26.

Figure 26:

(53)

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.

(54)

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 Page 54

Discover and Configure Libraries and Tape Drives Page 56

Create an NAS NDMP Storage Policy Page 58

Configure Subclients Page 58

Configuring an NDMP Remote Server (NRS) Backup Destination Page 59

(55)

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 Figure 27.

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.

(56)

4. Note the entries in the Supported Features section and click OK. See Figure 28.

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.

(57)

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.

CommVault Simpana 8.0 Application Introduction

Application Introduction

CommVault Simpana 8.0 Software

Application Introduction

Related Documentation

Access to Integration-Related Documents at Data Domain

View Data Domain application integration documents

Product Introduction

Product Installation

Concepts and Terms

Software Configuration Introduction

Access to the CommVault Simpana CommCell Console

To access the CommCell Console from a Windows host

Storage Policy Description

Client Computer Data Backup Job Description

Licenses

To view Data Domain system installed licenses

To review CommVault Simpana installed licenses

Data Domain CIFS Configuration

CommVault Simpana Configuration

Prerequisites

Simpana Static Shared Magnetic Library Configuration

Configure a shared disk device for the Media Agent

Create a Shared Magnetic Library for the new Shared Disk

Device

Simpana Backup Configuration

Create a backup storage policy

Create a backup schedule policy

Create a backup set

Create a subclient

Configuring CommVault Simpana for Optimal Compression

Increase the Chunk Size and Block Size

Verify that multiplexing is disabled

Data Expiration and Space Reclamation

Shared Magnetic Libraries that use CIFS

To manually start a job pruning process

VTL Devices that use Fibre Channel

To have the Data Domain system reclaim space manually

Backup and Restore Operations

To start a backup operation

To start a restore operation

VTL Configuration

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

Simpana Tape Drive and Media Management

To discover new media that have been imported from the

Data Domain vault

To import new media from the I/E ports

To export media from a library slot to the I/E ports

Create a VTL Storage Policy

NDMP Configuration

Add the NAS device as an NDMP client

Discover and Configure Libraries and Tape Drives