Dell EMC Data Domain and CommVault Integration Guide · October 2016 Rev 3 IG Update . ... Perform a test backup, verify that the job finishes successfully, and verify that data can

A Dell EMC Data Domain Integration Guide

Dell EMC Data Domain and CommVault Integration Guide February 2018

2 Dell EMC Data Domain and CommVault Integration Guide

Revisions

Date Description

February 2018 Rev 4 IG Update

October 2016 Rev 3 IG Update

The information in this publication is provided “as is.” Dell Inc. makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any software described in this publication requires an applicable software license. Copyright © 2018 Dell Inc. or its subsidiaries. All Rights Reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA [2/20/2018] [Data Domain Integration Guide] Dell believes the information in this document is accurate as of its publication date. The information is subject to change without notice.


Table of Contents CHAPTER 1……………………………………………………………………………..5 Overview .................................................................................................................................... 5 About This Integration Guide ..................................................................................................... 5 Related Documentation ............................................................................................................. 5

CommVault Documentation ....................................................................................................... 5 Configuration Overview ............................................................................................................. 6

Prerequisites ............................................................................................................................. 6 Configuration Checklist .............................................................................................................. 6 Data Domain System Configuration Overview .......................................................................... 7

Next Steps ................................................................................................................................. 7 CHAPTER 2……………………………………………………………………………....8 CommVault 10.0 with CIFS, NFS, and VTL ........................................................................... ..8 Configuration .......................................................................................................................... ..8

Enabling Basic CIFS Access on the Data Domain System ................................................... ..8 Enabling Basic NFS Access on the Data Domain System .................................................... ..9 Configuring VTL ..................................................................................................................... 10

Creating CIFS Devices in CommVault ................................................................................... 21 Creating NFS Devices in CommVault .................................................................................... 27 Backups .................................................................................................................................. 34

Performing a Windows or Linux Backup ................................................................................. 34 Performing an NAS Client Backup .......................................................................................... 46

Performing Restores ............................................................................................................... 47 CHAPTER 3……………………………………………………………………………..51 CommVault 11.0 with CIFS, NFS, and VTL ........................................................................... 51 Configuration .......................................................................................................................... 51


Enabling Basic CIFS Access on the Data Domain System ................................................... 51 Enabling Basic NFS Access on the Data Domain System .................................................... 52 Configuring VTL ..................................................................................................................... 53

Creating CIFS Devices in CommVault ................................................................................... 63 Creating NFS Devices in CommVault ................................................................................... ..68 Backups ................................................................................................................................. ..75

Performing a Windows or Linux/UNIX Backup ...................................................................... ..75 Performing an NAS Client Backup ......................................................................................... ..85

Performing Restores .............................................................................................................. ..86 CHAPTER 4…………………………………………………………………………….90 Data Domain Replication and restore from replication .......................................................... ..90 Configuration ......................................................................................................................... ..90 CIFS restore .......................................................................................................................... ..90 NFS restore ........................................................................................................................... ..90 CHAPTER5…………………………...…..……………………………………………91 Data Domain Cloud Tier ........................................................................................................ ..91 Configuring CommVault for Cloud Tier Devices .................................................................... ..92 Backing up files to DDR ......................................................................................................... ..92 Cloud Configuration on DDR ................................................................................................. ..92 Moving files from Cloud Tier to Active Tier ............................................................................ ..93 Restore of Data...................................................................................................................... ..95


CHAPTER 1

Overview

This chapter provides an overview of the integration of the CommVault software with EMC Data Domain systems.

About This Integration Guide

This integration guide explains how to configure a CommVault backup and restore application with an EMC Data Domain system. This chapter provides an overview of the integration and describes configuration prerequisites that apply to all versions of the software. The remaining chapters focus on a single version of the software. Use this document together with the documentation.

This document assumes that the software is already installed.

Related Documentation Hard copies of this document may be out of date. Always check for the current version of this document on the Support Documentation Website.

The Documentation page at https://support.emc.com/products/9012_Data-Domain/Documentation/ provides access to documents that are related to use of Data Domain products:

CommVault Documentation

Follow this link to access the CommVault 10 documentation: http://documentation.CommVault.com/CommVault/v10/article.

Follow this link to access the CommVault 11 documentation: http://documentation.CommVault.com/CommVault/v11/article.

https://support.emc.com/products/9012_Data-Domain/Documentation/

http://documentation.commvault.com/commvault/v10/article

http://documentation.commvault.com/commvault/v11/article


Configuration Overview

This section gives an overview of how to configure a CommVault server to work with the Data Domain system.

Prerequisites

System Prerequisites • A Data Domain system running Data Domain OS version 5.2 or later

• A second optional Data Domain system if replication is desired

• One CommVault server

• One server with CommVault MediaAgent installed and configured MediaAgent can also be installed on the server. • Backup sources: NDMP servers, Windows file servers, and UNIX file servers

Software Prerequisites:

• Install the CommVault software, with its own prerequisites checked and configured, including SQL Server, the Windows Domain Controller, and other prerequisites.

• Install the backup agent for Windows (or UNIX) on all of the systems that you want to back up.

Required Licenses: • Data Domain VTL licenses, if you want to back up to a VTL or an NDMP tape server

• CommVault licenses, as required

Configuration Checklist

This checklist summarizes the detailed procedures later in this document.

Procedure 1. Prepare and configure the Data Domain backup target subdirectories and shares for CIFS or NFS access under /backup. Create a folder under /backup to store CommVault backup data, such as /backup/cvbackupdata. Alternatively, create an MTree and a share for CIFS or NFS access. 2. Create the CommVault shared magnetic libraries, which are connected via CIFS or NFS to the appropriate CommVault MediaAgent. 3. Create a storage policy for Client systems to use under Policies. When using the Create Storage Policy Wizard, be sure to select <proper name> as the policy type.


4. Install the CommVault Backup iDataAgents. Be aware of the CommVault licensing requirements. 5. Add and configure the CommVault backup subclients.

For most backup agents, there is default subclient.

6. Define the backup job rules.

7. Perform a test backup, verify that the job finishes successfully, and verify that data can be restored.

Data Domain System Configuration Overview

The Data Domain system is presented to the CommVault server as a CIFS or NFS storage target depending on the media agent platform. For CIFS, the first consideration to address is what level of CIFS sharing is desired for the Data Domain storage. By default, the entire Data Domain directory structure (\\datadomain\backup) can be shared via CIFS to all or selected hosts. Alternatively, subfolders or an Mtree can be created for explicit CIFS sharing. The choice will depend on the specific use case for the customer environment.

Next Steps

If you use CommVault 10, continue with the next chapter, CommVault 10.0 with CIFS, NFS, and VTL and NDMP Tape Server. If you use CommVault 11, skip ahead to CommVault 11.0 with CIFS, NFS, and VTL and NDMP Tape Server.


CHAPTER 2

CommVault 10.0 with CIFS, NFS, and VTL Configuration

For the following section, we will assume the following naming conventions (you may need to use the FQDN in your environment):

• The Data Domain system is named datadomain.

• MediaAgent Servers are named ARES (for CIFS) and APOLLO (for NFS).

Enabling Basic CIFS Access on the Data Domain System

Procedure 1. Log on to the Data Domain system as sysadmin or as a user with sysadmin privilege.

2. Determine whether CIFS is enabled:

sysadmin@datadomain# cifs status CIFS is enabled and running.

3. Determine the CIFS access level currently defined by running the DD OS command cifs share show. The output in the example below shows the access for the Data Domain share /backup is open to all hosts

sysadmin@datadomain# cifs share show Shares information for: all shares

--------------- share backup --------------- enabled: yes maxconn: 0 path: /backup

4. If the /backup path is not included, or the client list does not include the proper server, add the appropriate server access.

Use the following DD OS command to allow access to MediaAgent host. In the example, access to /backup is open to all servers including MediaAgent host ARES.

sysadmin@datadomain# cifs share modify backup clients ARES Share

"backup" is modified for new connections.

Share "backup" is modified for new connections.

A * as the client name allows access to all servers to the specified path on the Data Domain system.


5. Verify the results sysadmin@datadomain# cifs share show Shares information for: all shares

--------------- share backup --------------- clients: ARES enabled: yes maxconn: 0 path: /backup

You should now be able to map to the Data Domain share through usual Windows CIFS methods.

6. Repeat Step 3 thru 5 for all MediaAgent servers to open access to the appropriate Data Domain share.

Enabling Basic NFS Access on the Data Domain System


2. Determine whether NFS is enabled.

sysadmin@datadomain# nfs status The NFS system is currently active and running. Total number of NFS requests handled = 1734102.

3. Determine the NFS access level currently defined by running the DD OS command nfs show clients. The output in the example below shows the access for the Data Domain share /backup is open to all hosts as shown with ‘*’.

sysadmin@datadomain# nfs show clients

path client options

/backup---------- ---------------- ---------------------------------------- * (rw,no_root_squash,no_all_squash,secure)

---------- ---------------- ---------------------------------------- 4. If the /backup path is not included, or the client list does not include the proper server, add the appropriate server access.

Use the following DD OS command to allow access to MediaAgent host. In the example, access to /backup is open to APOLLO as the client name which is a MediaAgent server:

sysadmin@datadomain# nfs add /backup APOLLO NFS export for "/backup" added.

A * as a client name allows all servers access to the specified path on the Data Domain system.


5. Verify the results. sysadmin@datadomain# nfs show clients

options path client ---------- --------------------- ----------------------------------------

/backup * (rw,no_root_squash,no_all_squash,secure)

/backup APOLLO (rw,no_root_squash,no_all_squash,secure)

---------- --------------------- ----------------------------------------

Configuring VTL

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 MediaAgent servers on the CommServe. Valid MediaAgent servers appear under Storage Resources > MediaAgents on the CommCell Console. To configure a Data Domain system as a VTL target device for data protection operations, perform the procedures listed below. See the following sections for details.

Procedure 1. Establish the FC connection, install drivers, and verify the connection on the CommVault MediaAgent server. 2. Create a VTL group on the Data Domain system.

3. Verify the Fibre Channel configuration for the VTL.

4. Configure the new VTL on the CommVault MediaAgent server.

Establish the Fibre Channel Connection, Install Drivers, and Verify the Connection on the CommVault MediaAgent Server

Procedure 1. Physically connect and configure a Fibre Channel (FC) connection between the Data Domain system and the CommVault MediaAgent server. 2. Check that the correct changer driver and tape device driver are installed and loaded on the CommVault MediaAgent server.


For the required changer and tape device drivers, see the Compatibility Guide, Data Domain Operating System, for your version of DD OS. Also check the CommVault compatibility documentation for information about supported driver versions. Log in to the command line interface (CLI) on the Data Domain system as sysadmin and enter the vtl initiator show command.

sysadmin@datadomain# vtl initiator show WWNN WWPN Initiator Group Status

Port

---------------- ------ ----------------------- ---------------- ------------------------

ibmx3650-2 Online 20:00:00:24:ff:22:07:66

initiator-1 21:00:00:24:ff:22:07:66 1a

------ ----------------------- ---------------- ------------------------

----------------

Symbolic Port Name

Initiator Address Method

---------------------------------------------------------------------- ------------- --------- --------------

initiator-1 QLE2562 FW:v5.04.04 DVR:v9.1.9.27 auto ------------- ------------------------------------------------------------------------------- --------------

If the Storage Area Network (SAN) connection is configured correctly, the initiator on the CommVault MediaAgent server appears with the status of Online. The example shows initiators that have been configured with aliases on a Data Domain system.

For DDOS 5.7 and newer versions ‘vtl initiator’ command is deprecated and one need to use scsitarget command in place as follow.

sysadmin@dd# scsitarget initiator show detailed

Initiator: Pinnacles_S2_HBA3 System Address: 50:06:01:63:47:20:51:a5 Group: NDMP_1 Service: VTL Address Method: auto Transport: FibreChannel


FC WWPN: 50:06:01:63:47:20:51:a5 FC WWNN: 50:06:01:60:c7:20:51:a5 FC Symbolic Port Name: EMC Celerra DM02:03 APM001430195692007

Initiator: Pinnacles_S3_HBA3 System Address: 50:06:01:6b:47:20:51:a5 Group: NDMP_2 Service: VTL Address Method: auto Transport: FibreChannel FC WWPN: 50:06:01:6b:47:20:51:a5 FC WWNN: 50:06:01:60:c7:20:51:a5

FC Symbolic Port Name: EMC Celerra DM03:03 APM001430195692007

Initiator Status Endpoint ----------------- ------ ------------- Pinnacles_S2_HBA3 Online endpoint-fc-0 Pinnacles_S3_HBA3 Online endpoint-fc-0 ----------------- ------ ------------- sysadmin@dd#

Create a VTL Group on the Data Domain System

You can create a VTL group at the DD OS command line or with the web interface. Refer to the "Virtual Tape Library" chapter of the EMC Data Domain Operating System Administration Guide for more information about the VTL feature, including the creation of virtual tape drives, virtual tape media, and virtual changers.

Procedure

1. On the Data Domain system, create an access group.

2. Add the VTL and the initiator to the access group.

3. Confirm the VTL configuration with the command vtl group show groupname.

sysadmin@dd670-41# vtl group show ibmx3650-2

Group: ibmx3650-2 Initiators:

Initiator WWPN

Initiator Alias


--------------- ----------------------- initiator-1 21:00:00:24:ff:22:07:66

--------------- ----------------------- Devices:

Primary Ports Secondary Ports In-use Ports Device Name

------------- ------------- --------------- ------------ VTL1 changer all all all VTL1 drive 1 all all all VTL1 drive 2 all all all VTL1 drive 3 all all all VTL1 drive 4 all all all VTL1 drive 5 all all all VTL1 drive 6 all all all VTL1 drive 7 all all all VTL1 drive 8 all all all VTL1 drive 9 all all all

VTL1 drive 10 all all all

------------- ------------- --------------- ------------

. 4. Check that the marker type is set to auto: sysadmin@dd670-41# filesys option show Option Value

Local-------------------------------compressiontype -------- lz

Marker-type auto app-optimized-compression none Report-replica-as-writable disabled Current global compression type 9 Staging reserve disabled

------------------------------- --------

Verify the Fibre Channel Configuration for the VTL

Before discovering the new VTL device within the CommVault MediaAgent server, follow the steps below to ensure that the operating system and HBA driver discover the VTL devices.

Procedure 1. On the Fibre Channel switch, check that the target Data Domain system Fibre Channel port and the initiator (CommVault MediaAgent server Fibre Channel HBA port) are both zoned properly.


2. If the zoning is correct but you still cannot see the VTL target devices, ensure that both the Data Domain VTL HBA and the CommVault MediaAgent HBA are online in the switch name server.

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

4. At the operating system level, check that the changer and tape drives are discovered properly. For example, use Device Manager on a Windows system.

Configure the New VTL on the CommVault MediaAgent Server

This section describes the steps to configure a new Data Domain VTL within a CommVault MediaAgent.

Procedure 1. On MediaAgents, install the tape device drivers that the CommVault compatibility documentation recommends. 2. In the CommVault console, select Storage > Library and Drive Configuration.

3. From the Select MediaAgents window, select the MediaAgent that connects to the Data Domain VTL library and click OK.

In this example, the MediaAgent is ibmx3650-2.

4. Right click Libraries and select Detect/Config Devices. The Detect

Library dialog box appears.


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. The example shows one VTL library.


6. Right-click the device and select Configure.


7. Select Library and all drives and click OK.


8. After you create the library, right click the newly added library and choose Properties. The Library

Properties dialog box appears.


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.

9. Close the Library and Drive Configuration window.

In the Commcell console browser, the new library appears under MediaAgent ibmx3650-2 and Libraries. Also, a storage policy for this library appears under Storage Policies.



Creating CIFS Devices in CommVault

Before you begin Complete the procedure in Enabling Basic CIFS Access on the Data Domain System. You can use a Data Domain system as a CIFS backup target by creating a Shared Disk Device Library in with storage used from the Data Domain system over the CIFS connection.

Procedure

1. In the Express Administrative console, select Storage > Library and Drive Configuration.


2. When prompted, add the Windows MediaAgent in the Select MediaAgents dialog box. The Library

and Drive Configuration dialog box appears.


3. Right click Libraries and select Add > Disk Library. The Add Disk


4. Type the alias for the library name, select Automatically create storage policy for new data paths box, and click OK.

The Shared Mount Path (ARES_CIFS_Library) dialog box appears.


5. Type the base folder name, enter the user name of the user who has access to the CIFS share on the Data Domain system in the Connect As box, enter the password, enter the path to the CIFS share on the Data Domain system, and click OK.


The new library is added.




Creating NFS Devices in

Before you begin Follow the procedure in Enabling Basic NFS Access on the Data Domain System.

To use a Data Domain system as an NFS backup target, create a Shared Disk Device Library in with storage used from the Data Domain system over the NFS connection. This requires that a MediaAgent be running on the UNIX or Linux system. The examples in this section use Linux.

Procedure 1. On the Linux MediaAgent, create a mount point and mount the /backup share from the Data Domain system.

# mkdir /backup # mount datadomain:/data/col1/backup /backup

2. In the Express Administrative console, select Storage > Library and Drive Configuration.

3. When prompted, add the UNIX or Linux MediaAgent in the Select MediaAgents dialog box and click OK. The Library and Drive Configuration dialog box appears.


4. Click Start > Add > Choose Disk Library The Add Disk




The Shared Mount Path(apollo_nfs_library) dialog box appears.


6. Type the base folder name that you want, select Local Path, and click … to browse for the Linux MediaAgent.

The Browse for Folder dialog box appears.


7. Choose backup and click OK.

The browser window closes and /backup is shown in the Folder box. In this example, we chose /nfs/dd27_source_repl_Folder1/backup.


8. Click OK.

The Library and Drive Configuration window appears, showing the new library.




Backups

Before performing a backup, check the following items:

• Check that the backup source and destination are correctly defined in the subclient. The backup source is defined as content in subclient property and backup destination is defined as storage policy in the Subclient Properties dialog box.

• Enough media are available in the scratch group under the target tape library, or enough free space is available under the target disk library.

• The library and drive are in the Ready state.

Performing a Windows or Linux Backup

The procedures for performing backups in Windows and Linux are similar. This example uses Windows.

Procedure 1. In the CommCell Console, expand the Windows client in the CommCell Browser, right click defaultBackupSet and choose All Tasks > New Subclient to create a new subclient.


2. In the Subclient Properties dialog box General tab, enter as the Subclient name.


3. In the Content tab, click Browse, select the folders to be backed up (for example, C:\Simpana), and click Add. Repeat this step for each folder and then click Close.

4. In the Storage Device tab, Data Storage Policy tab, choose the policy where backup data is to be written, such as DD_CIFS_Library.

See the next sections for details.


5. Select Data Protection and Archiving and click Next.


6. Enter a storage policy name and click Next.


7. Select the library that you created earlier and click Next.

8. Select the MediaAgent that you configured earlier and click Next.


9. Review your choices and click Finish to complete the Create Storage Policy wizard.


10. In the Storage Device tab, Data Transfer Option tab, set Software Compression to Off.


11. Click OK to close the Subclient Properties window. The Backup

Schedule dialog box opens.

12. Choose a schedule option and click OK.

• To use an existing backup schedule for this subclient, select Associate to schedule policy and choose a policy from the list.

• To create a new schedule, select Schedule.

• If you do not want to schedule this backup, select Do Not Schedule.

The subclient appears in the defaultBackupSet tab of the CommCellBrowser.


13. To run a backup, right click a subclient name and choose Backup.

The Backup Options for Subclient window appears.


14. Choose options under Select Backup Type and Job Initiation and click OK. The backup

job starts as seen in the Job Controller.

Job progress can be seen in the Job Controller window and job events can be monitored in the Event Viewer window.


15. To see detailed job status, right click the job entry and choose Detail.

The Backup Job Details for Job ID window appears.


Results If the job finishes successfully, the status will change to Completed. For other status results, look at the Errors field and logs in the Event Viewer window. To view the detailed job log, right-click the job entry and choose View Logs.

Performing an NAS Client Backup Procedure 1. In the CommCell Console, expand the NAS client in CommCell Browser, right click defaultBackupSet, and choose All Tasks > New Subclient to create a new subclient.

2. In the General tab of the Subclient Properties window, enter fs1 as the Subclient name.

3. In the Content tab, under Backup Content Path, select the file system, enter the path of the folder to be backed up in that file system (/fs1/dir in the example), and click Add. Repeat this step for each folder. 4. Refer to Performing a Windows or Linux Backup and continue from step 4.


Performing Restores

The procedures for performing restores with Windows, Linux, and NAS clients are similar. This example uses Windows.

Procedure 1. In the CommCell Console, expand the Windows client in the CommCell Browser, right click defaultBackupSet and choose All Tasks > Browse Backup Data.

The Browse Options dialog box appears.


You can view the latest data (consolidation of all backups) by choosing Browse the Latest Data, or you can browse backup data up to a time by choosing Specify Browse Time. You can also exclude backup data from before a specified time by clicking Advanced and setting the advanced options. 2. Click OK.

The backup data browser window opens for this client. This example shows the latest backup data for this client.


3. Explore the data, choose folders and files to be restored, and click Recover All Selected. The Restore

Options for All Selected Items dialog box appears.

4. Choose the required options. You can restore data to a different client by choosing a Destination client. You can restore data to a new location by deselecting Restore to same folder and specifying a destination path. Click OK when you finish choosing restore options.


The restore job starts.

5. Monitor the job in the Job Controller and Event Viewer windows. When the restore job finishes, the restored data will become available in the destination folder.


CHAPTER 3

CommVault 11.0 with CIFS, NFS, and VTL Configuration

For the following section, we will assume the following naming conventions (you may need to use the FQDN in your environment):

• The Data Domain system is named datadomain.

• MediaAgent Servers are named appeng25 (for CIFS) and appeng32 (for NFS).

Enabling Basic CIFS Access on the Data Domain System


2. Determine whether CIFS is enabled:

sysadmin@datadomain# cifs status CIFS is enabled.

3. Determine the CIFS access level currently defined by running the DD OS command cifs share show. The output in the example below shows the access for the Data Domain share backup is open to all hosts


--------------- share backup --------------- path: /data/col1/backup maxconn: 0 clients: * enabled: yes

Shares displayed: 1 sysadmin@datadomain#

4. If the /data/col1/backup path is not included, or the client list does not include the proper server, add the appropriate server access.

Use the following DD OS command to allow access to MediaAgent host. In the example, access to /data/col1/backup is open to all servers including MediaAgent host appeng25.

sysadmin@datadomain# cifs share modify backup clients appeng25 Share

"backup" is modified for new connections.


A * as the client name allows access to all servers to the specified path on the Data Domain system.

5. Verify the results


--------------- share backup --------------- path: /data/col1/backup maxconn: 0 clients: appeng25 enabled: yes

Shares displayed: 1 sysadmin@datadomain#

6. Repeat Step 3 thru 5 for all MediaAgent servers to open access to the appropriate Data Domain share.

Enabling Basic NFS Access on the Data Domain System


2. Determine whether NFS is enabled.

sysadmin@datadomain# nfs status The NFS system is currently active and running. Total number of NFS requests handled = 1734102.

3. Determine the NFS access level currently defined by running the DD OS command nfs show clients. The output in the example below shows the access for the Data Domain share /backup is open to all hosts as shown with ‘*’.

sysadmin@datadomain# nfs show clients path client options ----------------- ------ ---------------------------------------- /data/col1/backup * (sec=sys,rw,no_root_squash,no_all_squash,secure,nolog) ----------------- ------- ---------------------------------------- 4. If the /data/col1/backup path is not included, or the client list does not include the proper server, add the appropriate server access.

Use the following DD OS command to allow access to MediaAgent host. In the example, access to /backup is open to APOLLO as the client name which is a MediaAgent server:

sysadmin@datadomain# nfs add /data/col1/backup appeng32 NFS export for

"/data/col1/backup" added.


A * as a client name allows all servers access to the specified path on the Data Domain system.

5. Verify the results. sysadmin@datadomain# nfs show clients Path Client Options

/data/col1/backup----------------- -------- ------------------------------------------------------ * (sec=sys,rw,no_root_squash,no_all_squash,secure,nolog)

/data/col1/backup appeng32 (sec=sys,rw,root_squash,no_all_squash,secure,nolog)

----------------- -------- ------------------------------------------------------

Configuring VTL

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 MediaAgent servers on the CommServe. Valid MediaAgent servers appear under Storage Resources > MediaAgents on the CommCell Console. To configure a Data Domain system as a VTL target device for data protection operations, perform the procedures listed below. See the following sections for details.

Procedure 1. Establish the FC connection, install drivers, and verify the connection on the CommVault MediaAgent server. 2. Create a VTL group on the Data Domain system.

3. Verify the Fibre Channel configuration for the VTL.

4. Configure the new VTL on the CommVault MediaAgent server.

Establish the Fibre Channel Connection, Install Drivers, and Verify the Connection on the CommVault MediaAgent Server

Procedure 1. Physically connect and configure a Fibre Channel (FC) connection between the Data Domain system and the CommVault MediaAgent server. 2. Check that the correct changer driver and tape device driver are installed and loaded on the CommVault MediaAgent server.


For the required changer and tape device drivers, see the Compatibility Guide, Data Domain Operating System, for your version of DD OS. Also check the CommVault compatibility documentation for information about supported driver versions.

3. Log in to the command line interface (CLI) on the Data Domain system as sysadmin and enter the scsitarget initiator show command.

sysadmin@datadomain# scsitarget initiator show detailed

Initiator: appeng25-port2

System Address: 21:00:00:0e:1e:30:63:39

Group: appeng25

Service:

Address Method: auto

Transport: FibreChannel

FC WWPN: 21:00:00:0e:1e:30:63:39

FC WWNN: 20:00:00:0e:1e:30:63:39

FC Symbolic Port Name: QLE2672 FW:v8.00.00 DVR:v9.1.11.24

Initiator Endpoint

------------------- -------------

appeng25-port2 endpoint-fc-0


------------------- -------------

sysadmin@datadomain#

If the Storage Area Network (SAN) connection is configured correctly, the initiator on the CommVault MediaAgent server appears with the status of Online. The example 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 with the web interface. Refer to the "Virtual Tape Library" chapter of the EMC Data Domain Operating System Administration Guide for more information about the VTL feature, including the creation of virtual tape drives, virtual tape media, and virtual changers.

Procedure

1. On the Data Domain system, create an access group.

2. Add the VTL and the initiator to the access group.

3. Confirm the VTL configuration with the command vtl group show groupname. sysadmin@datadomain# vtl group show appeng25

Group: appeng25

Initiators: Initiator WWPN

Initiator Alias

appeng25----------------port2

----------------------- 21:00:00:0e:1e:30:63:39

--------------- -----------------------


Devices:

LUN

Primary

Ports

Secondary

Ports

In-use Ports Device Name

simpana---------------changer

------------- --------------- ------------ all all all

simpana drive 1 all all all simpana drive 2 all all all simpana drive 3 all all all simpana drive 4 all all all

4. Check that the marker type is set to auto: sysadmin@datadomain# filesys option show Option Value ------------------------------- -------- Local compression type lz Marker-type auto app-optimized-compression none randomio enabled anchoring-algorithm variable Report-replica-as-writable disabled warning-space-usage 80 critical-space-usage 90 Current global compression type 9 Staging reserve disabled ------------------------------- --------

Verify the Fibre Channel Configuration for the VTL

Before discovering the new VTL device within the CommVault MediaAgent server, follow the steps below to ensure that the operating system and HBA driver discover the VTL devices.

Procedure

1. On the Fibre Channel switch, check that the target Data Domain system Fibre Channel port and the initiator (CommVault MediaAgent server Fibre Channel HBA port) are both zoned properly. 2. If the zoning is correct but you still cannot see the VTL target devices, ensure that both the Data Domain VTL HBA and the CommVault MediaAgent HBA are online in the switch name server.

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


4. At the operating system level, check that the changer and tape drives are discovered properly. For example, use Device Manager on a Windows system.

Configure the New VTL on the CommVault MediaAgent Server

This section describes the steps to configure a new Data Domain VTL within a CommVault MediaAgent.

Procedure 1. On MediaAgents, install the tape device drivers that the CommVault compatibility documentation recommends. 2. In the CommVault console, select Storage > Expert Storage Configuration.

3. From the Select MediaAgents window, select the MediaAgent that connects to the Data Domain VTL library and click Add and then OK. Click OK again in information window.

In this example, the MediaAgent is appeng25.

4. Right click Libraries and select Detect/Config Devices. The Detect



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. The example shows one VTL library. Click OK and then Close to close Log window.

6. Right-click the device and select Properties.


7. Check Automatically create storage policy for new data paths and click OK.


8. Right-click the device and select Configure.

9. Select Library and all drives and click OK.


10. If asked, On Confirm window click Yes.

11. On Discover Media Options choose correct media type and click Yes.


12. Close Expert Storage Configuration window by clicking Start and Exit. If you exit without configuring newly detected library then it is not saved.

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.

13. After you create the library, right click the newly added library and choose Properties. The Library

Properties dialog box appears.


14. In the Commcell console browser, the new library appears under MediaAgent appeng25 and Libraries. Also, a storage policy for this library appears under Storage Policies.

Creating CIFS Devices in CommVault

Before you begin Complete the procedure in Enabling Basic CIFS Access on the Data Domain System.

You can use a Data Domain system as a CIFS backup target by creating a Shared Disk Device Library in with storage used from the Data Domain system over the CIFS connection.

Procedure 1. In the Express Administrative console, select Storage > Expert Storage Configuration.


2. When prompted, add the Windows MediaAgent in the Select MediaAgents dialog box. The Expert

Storage Configuration dialog box appears.


3. Right click Libraries and select Add > Disk Library. The Add Disk




The Shared Mount Path (Appeng25_CIFS_Library) dialog box appears.

5. Type the base folder name, enter the user name of the user who has access to the CIFS share on the Data Domain system in the Connect As box, enter the password, enter the path to the CIFS share on the Data Domain system, and click OK.


The new library is added.



Creating NFS Devices in CommVault

Before you begin Follow the procedure in Enabling Basic NFS Access on the Data Domain System.

To use a Data Domain system as an NFS backup target, create a Shared Disk Device Library in with storage used from the Data Domain system over the NFS connection. This requires that a MediaAgent be running on the UNIX or Linux system. The examples in this section use Solaris (UNIX).

Procedure


1. On the Solaris MediaAgent, create a mount point and mount the /backup share from the Data Domain system. # mkdir /backup # mount datadomain:/backup /backup # mkdir /backup/nfs

2. In the Express Administrative console, select Storage > Expert Storage Configuration.

3. When prompted, add the UNIX or Linux MediaAgent in the Select MediaAgents dialog box and click OK. The Expert Storage Configuration dialog box appears.


4. Click Start > Add > Choose Disk Library The Add Disk




The Shared Mount Path(appeng32_nfs_library) dialog box appears.

6. Type the base folder name that you want, select Local Path, and click … to browse for the Linux MediaAgent.

The Browse for Folder dialog box appears.


7. Choose backup and click OK.

The browser window closes and /backup is shown in the Folder box. Here we choose path /backup/nfs.


8. Click OK.

The Expert Storage Configuration window appears, showing the new library.




Backups

Before performing a backup, check the following items:

• Check that the backup source and destination are correctly defined in the subclient. The backup source is defined as content in subclient property and backup destination is defined as storage policy in the Subclient Properties dialog box.

• Enough media are available in the scratch group under the target tape library, or enough free space is available under the target disk library.

• The library and drive are in the Ready state.

Performing a Windows or Linux/UNIX Backup

The procedures for performing backups in Windows and Linux/UNIX are similar. This example uses Windows.

Procedure

1. In the CommCell Console, expand the Windows client in the CommCell Browser, right click defaultBackupSet and choose All Tasks > New Subclient to create a new subclient.

2. In the Subclient Properties dialog box General tab, enter as the Subclient name.


3. In the Content tab, click Browse, select the folders to be backed up (for example, C:\can_data\blah), and

click Add. Repeat this step for each folder and then click Close.


4. In the Storage Device tab, Data Storage Policy tab, choose the policy where backup data is to be written, such as Appeng25_CIFS_Library.


5. In the Storage Device tab, Data Transfer Option tab, set Software Compression to Off.


6. In the Storage Device tab, Deduplication tab, uncheck Enable Deduplication.


7. Click OK to close the Subclient Properties window. The Backup

Schedule dialog box opens.

8. Choose a schedule option and click OK.

• To use an existing backup schedule for this subclient, select Associate to schedule policy and choose a policy from the list.

• To create a new schedule, select Schedule.

• If you do not want to schedule this backup, select Do Not Schedule.


The demo subclient appears in the defaultBackupSet tab of the CommCellBrowser.

9. To run a backup, right click a subclient name and choose Backup.


The Backup Options for Subclient window appears.


10. Choose options under Select Backup Type and Job Initiation and click OK. The backup

job starts as seen in the Job Controller.

Job progress can be seen in the Job Controller window and job events can be monitored in the Event Viewer

window. 11. To see detailed job status, right click the job entry and choose Detail.


The Backup Job Details for Job ID window appears.


Results If the job finishes successfully, the status will change to Completed. For other status results, look at the Errors field and logs in the Event Viewer window. To view the detailed job log, right-click the job entry and choose View Logs.

Performing an NAS Client Backup Procedure 1. In the CommCell Console, expand the NAS client in CommCell Browser, right click defaultBackupSet, and choose All Tasks > New Subclient to create a new subclient.

2. In the General tab of the Subclient Properties window, enter fs1 as the Subclient name.

3. In the Content tab, under Backup Content Path, select the file system, enter the path of the folder to be backed up in that file system (/fs1/dir in the example), and click Add. Repeat this step for each folder. 4. Refer to Performing a Windows or Linux Backup and continue from step 4.


Performing Restores

The procedures for performing restores with Windows, Linux/UNIX, and NAS clients are similar. This example uses Windows. Procedure

1. In the CommCell Console, expand the Windows client in the CommCell Browser, right click defaultBackupSet and choose All Tasks > Browse and Restore.

The Browse Options dialog box appears.


You can view the latest data (consolidation of all backups) by choosing Browse the Latest Data, or you can browse backup data up to a time by choosing Specify Browse Time. You can also exclude backup data from before a specified time by clicking Advanced and setting the advanced options. 2. Click View Content.

The backup data browser window opens for this client. This example shows the latest backup data for this client.


3. Explore the data, choose folders and files to be restored, and click Recover All Selected. The Restore

Options for All Selected Items dialog box appears.

4. Choose the required options. You can restore data to a different client by choosing a Destination client. You can restore data to a new location by deselecting Restore to same folder and specifying a destination path. Click OK when you finish choosing restore options.


The restore job starts.

5. Monitor the job in the Job Controller and Event Viewer windows. When the restore job finishes, the restored data will become available in the destination folder.


CHAPTER 4

Data Domain Replication and restore from replication

Configuration Configure the replication from source DDR mtree, where backup images are stored, to destination DDR. In case of issues with source backup copy, restore from replication copy of backup can be done using following process. Before use of following process make sure that replication is fully synchronized.

CIFS restore

- In server go to Expert Storage configuration wizard. - Choose media agent, under 'Shared Disk Device' tab right click path, choose 'Properties', and replace

source DDR share path with destination DDR share path. Also check 'Read only'. - Now any restore will restore data from replication copy.

NFS restore

- On Unix/Linux media agent, unmount source DDR mtree and mount replication DDR mtree as read only at same mount point.

- Now any restore will restore data from replication copy. NOTE

- There is no need to break replication pair and make target mtree read/write. Read only is fine for restore.

- At this point backup cannot be run as device is read only.


CHAPTER 5

Data Domain Cloud Tier

The Data Domain Cloud Tier (DD Cloud Tier) is a long term data retention solution that enables the movement of data from an Data Domain Active Tier (DD Active Tier) device to a DD Cloud Tier device, and then to an external Cloud Provider. The CommVault integration with the DD Cloud Tier provides a Data Protection Administrator with the ability to perform the following functions:

• Ability to move data from a DD Active Tier device to DD Cloud Tier device. • Recover data to a client from the cloud, including FLR/GLR recoveries.

CommVault supports multiple cloud services. Please refer compatibility guide for the same. http://compatibilityguide.emc.com:8080/CompGuideApp/getDataDomainCloudTierCompGuidePage.do

Overview of the DD Cloud Tier solution:

Note:

To know about Cloud Tier Requirements, Configuring DD Cloud Tier Devices and Cloud data movement schedules, refer to “Data Domain OS 6.1 Administration Guide”.

http://compatibilityguide.emc.com:8080/CompGuideApp/getDataDomainCloudTierCompGuidePage.do

https://support.emc.com/docu85190_Data-Domain-Operating-System-6.1-Administration-Guide.pdf?language=en_US


Configuring CommVault for Cloud Tier devices CommVault allows users to move their backup datasets to data domain active tier location (i.e.mtree) and from there, files are moved to cloud using DDR “data-movement” commands.

Backing up files to DDR:

Note: To know how to take backup on DDR refer “Backups” section under “CHAPTER 3”

Cloud Configuration on DDR: Note: CommVault is supported with multiple cloud vendors, and the example below is for ECS

a. Create an ECS Cloud Profile. Here “ECS” is the profile name. sysadmin@dd7200-26# cloud profile add ECS

Enter provider name (aws|azure|virtustream|ecs|s3_flexible): ecs Enter the access key: Enter the secret key: Enter the endpoint: http://load-vm1.chaos.local:9020 Do you want to enter proxy details? (yes|no) [no]: no Cloud profile 'ECS' added successfully sysadmin@dd7200-26#

b. Create a Cloud Unit. Here “ecs-unit1” is the cloud unit name. sysadmin@dd7200-26# cloud unit list Name Profile Status --------- ------- ------ ecs-unit1 ECS Active --------- ------- ------ sysadmin@dd7200-26#

c. Once the backup is done Datadomain, run file report. # filesys report generate file-location path <mtree path> sysadmin@dd7200-26# filesys report generate file-location path /data/col1/ltr1 -------------------------------- ---------------------- ---------------------- --------------------------- File Name Location(Unit Name) Size Placement Time -------------------------------- ---------------------- ---------------------- --------------------------- /data/col1/ltr1/DEVICE_LABEL Active 38 Tue Dec 12 03:21:44 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MountPathConfigs Active 257 Tue Dec 12 03:21:50 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MOUNTPATH_LABEL Active 2.00 KiB Tue Dec 12 03:21:50 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/MEDIA_LABEL Active 64.00 KiB Tue Dec 12 03:36:11 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_188 Active 1.00 GiB Tue Dec 12 03:36:12 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_188 Active 64.00 KiB Tue Dec 12


03:36:54 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_190 Active 64.00 KiB Tue Dec 12 03:37:11 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_190 Active 64.00 KiB Tue Dec 12 03:37:11 2017 ------------------------------------------------------------------------------------------------------------------------- sysadmin@dd7200-26# Ensure that backup dataset is moved to DDR Active tier. Moving files from Active Tier to Cloud Tier:

1. To check any data-movement policy is set on DDR by running below command. # data-movement policy show

Note: In the below example, default age-threshold of “14” days is maintained.

2. Set data-movement policy age-threshold to 14 to specific mtree. sysadmin@dd7200-26# data-movement policy set age-threshold 14 to-tier cloud cloud-unit ecs-unit1 mtrees /data/col1/ltr1 The data-movement age-threshold policy is set to "14" days for the following Mtree(s): /data/col1/ltr1 sysadmin@dd7200-26#

3. Verify age-threshold is set successfully.

sysadmin@dd7200-26# data-movement policy show Mtree Target(Tier/Unit Name) Policy Value --------------- ---------------------- ------------- ------ /data/col1/ltr1 Cloud/ecs-unit1 age-threshold 14 days --------------- ---------------------- ------------- ------ sysadmin@dd7200-26#

4. Run data movement command in order to move from Active Tier to cloud Tier. # data-movement start mtrees <mtree path>

sysadmin@dd7200-26# data-movement start mtrees /data/col1/ltr1 Data-movement started. Run "data-movement watch" to monitor progress. Sysadmin@dd7200-26#

5. Run “data-movement watch” command to watch the status of data-movement.

sysadmin@dd7200-26# data-movement watch Data-movement: 97% complete; time: 0:02:20 Moved (post-comp): 168.77 MiB, (pre-comp): 1.00 GiB, Files inspected: 8, Files eligible: 8, Files moved: 8, Files failed: 0


Data-movement was started on Dec 12 2017 04:02 and completed on Dec 12 2017 04:05 Moved (post-comp): 168.77 MiB, (pre-comp): 1.00 GiB, Files inspected: 8, Files eligible: 8, Files moved: 8, Files failed: 0 sysadmin@dd7200-26#

6. Now, again run file report and ensure file is now available on cloud. Note that the location of file is now “ecs-unit1” instead of “active” # filesys report generate file-location path <mtree path>

sysadmin@dd7200-26# filesys report generate file-location path /data/col1/ltr1 -------------------------------- ---------------------- ---------------------- --------------------------- File Name Location(Unit Name) Size Placement Time -------------------------------- ---------------------- ---------------------- --------------------------- /data/col1/ltr1/DEVICE_LABEL ecs-unit1 38 Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MountPathConfigs ecs-unit1 257 Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MOUNTPATH_LABEL ecs-unit1 2.00 KiB Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/MEDIA_LABEL ecs-unit1 64.00 KiB Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_188 ecs-unit1 1.00 GiB Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_188 ecs-unit1 64.00 KiB Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_190 ecs-unit1 64.00 KiB Tue Dec 12 04:04:01 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_190 ecs-unit1 64.00 KiB Tue Dec 12 04:04:01 2017 ------------------------------------------------------------------------------------------------------------------------- sysadmin@dd7200-26#

7. Now, to restore back file(s) from cloud (ECS) to active tier (DDR), file should be recalled and run file report to ensure location is set to “active”

# data-movement recall path <file location> sysadmin@dd7200-26# data-movement recall path /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_188 Recall initiated for "/data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_188". Run the status command to monitor its progress. sysadmin@dd7200-26#

8. Check “data-movement” status. # data-movement status

sysadmin@dd7200-26# data-movement status Data-movement to cloud tier: ----------------------------


Data-movement was started on Dec 12 2017 04:02 and completed on Dec 12 2017 04:05 Moved (post-comp): 168.77 MiB, (pre-comp): 1.00 GiB, Files inspected: 8, Files eligible: 8, Files moved: 8, Files failed: 0 Data-movement recall: --------------------- No recall operations found. sysadmin@dd7200-26#

9. Generate report for file location. # filesys report generate file-location path <mtree path>

sysadmin@dd7200-26# filesys report generate file-location path /data/col1/ltr1 -------------------------------- ---------------------- ---------------------- --------------------------- File Name Location(Unit Name) Size Placement Time -------------------------------- ---------------------- ---------------------- --------------------------- /data/col1/ltr1/DEVICE_LABEL Active 38 Tue Dec 12 04:28:48 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MountPathConfigs Active 257 Tue Dec 12 04:30:27 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/MOUNTPATH_LABEL Active 2.00 KiB Tue Dec 12 04:30:41 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/MEDIA_LABEL Active 64.00 KiB Tue Dec 12 04:30:52 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_188 Active 1.00 GiB Tue Dec 12 04:32:18 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_188 Active 64.00 KiB Tue Dec 12 04:31:15 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNK_190 Active 64.00 KiB Tue Dec 12 04:31:28 2017 /data/col1/ltr1/Folder1/CV_MAGNETIC/V_46/CHUNKMAP_TRAILER_190 Active 64.00 KiB Tue Dec 12 04:31:39 2017 ------------------------------------------------------------------------------------------------------------------------- sysadmin@dd7200-26#

Restore of Data:

Note: To know how to restore of data from DDR refer “Performing Restores” section under “CHAPTER 3”

Documents

Dell EMC Data Domain and CommVault Integration Guide · October 2016 Rev 3 IG Update . ... Perform a test backup, verify that the job finishes successfully, and verify that data can