Dell EMC Data Domain and Veritas Backup Exec 2014 and ...

1 Dell EMC Data Domain and Veritas Backup Exec 2014 and later CIFS and VTL Integration Guide | docu48700 | version 2

Dell EMC Data Domain and Veritas Backup Exec 2014 and later CIFS and VTL Integration Guide February 2018

2 Dell EMC Data Domain and Veritas Backup Exec 2014 and later CIFS and VTL Integration Guide | docu48700 |

version 2

Revisions

Date Description

February 2018 Updated IG with new content

October 2016 Initial release

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 © February 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] [docu48700] Dell believes the information in this document is accurate as of its publication date. The information is subject to change without notice.


version 2

Table of Contents 1 About this document ............................................................................................................................................ 4

1.1 Audience .................................................................................................................................................... 4

1.2 Related Documents .................................................................................................................................... 4

2 Configuration overview ......................................................................................................................................... 5

2.1 Tape Marker Settings .................................................................................................................................. 5

2.2 Compression and encryption ...................................................................................................................... 5

2.3 Prerequisites .............................................................................................................................................. 5

3 Data Domain configuration................................................................................................................................... 6

4 CIFS Prerequisites ............................................................................................................................................... 7

5 Backup Exec configuration — CIFS .................................................................................................................. 8

6 Backup Exec configuration — VTL .................................................................................................................. 10

6.1 Installing Symantec tape device drivers ................................................................................................ 10

6.2 Configure the robotic library partitions ................................................................................................... 14

6.3 Backup and Restore Example ................................................................................................................. 18

6.3.1 Backup ..................................................................................................................................................... 18

6.3.2 Restore ................................................................................................................................................... 21

7 Advanced Topics ............................................................................................................................................... 24

7.1 Replication ............................................................................................................................................... 24

7.2 Data Domain Cloud Tier .......................................................................................................................... 25

7.2.1 Backup ..................................................................................................................................................... 27

7.2.2 Data movement to cloud .......................................................................................................................... 30

7.2.3 Restore (Direct Restore, only ECS cloud) ............................................................................................... 31

7.2.4 Recall ....................................................................................................................................................... 36

7.2.5 Restore..................................................................................................................................................... 36


version 2

1 About this document This document explains how to configure the EMC® Data Domain® system as a backup storage target for Veritas™ Backup Exec™ using CIFS and VTL protocols.

1.1 Audience

This guide is intended for customers, technical field consultants, and engineers who have familiarity with Backup Exec and Data Domain operations.

1.2 Related Documents

Documentation for the Data Domain system is available at https://support.emc.com/products/9012_Data-Domain/Documentation. Documentation for Backup Exec is available at www.veritas.com/support.

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

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

http://www.veritas.com/support


version 2

2 Configuration overview To configure a Data Domain system to be a backup storage target for Backup Exec:

1. Validate the physical connectivity, which can include the Fibre Channel protocol and the Ethernet protocol.

2. Discover, configure, and verify the VTL and CIFS connectivity by using the Backup Exec Configuration Storage Wizard.

3. Perform a test backup.

4. Perform a test restore.

2.1 Tape Marker Settings Tape marker settings are not required.

2.2 Compression and encryption When backing up to tape (VTL), use the job defaults of Compression: Hardware and Encryption: None.

When backing up to a CIFS share, use the job defaults of Compression: None and Encryption: None.

These settings allow for the best performance.

2.3 Prerequisites Integrating Backup Exec with Data Domain requires:

• Data Domain system

• Veritas Backup Exec 2014 or later


version 2

3 Data Domain configuration Before you begin, make sure that the Data Domain system is installed and operating without errors.


version 2

4 CIFS Prerequisites To use the Data Domain system with Backup Exec, your CIFS configuration must meet these requirements:

• A Backup Exec client system must have CIFS access to the Data Domain CIFS shares using the Data Domain GUI or commands.

• The Data Domain system must use the Active Directory or the Workgroup authentication mode.

• The Data Domain system must have a valid CIFS user account. The valid user account must have the following minimum permissions: • If the account is part of a Domain or Active Directory, the account must have the

Domain\Backup Operator and the Local Administrator permissions.

• If the account is in a workgroup, the account must have the Backup Operation group permission.


version 2

5 Backup Exec configuration — CIFS 1. From the Backup Exec Administration console, click Storage > Configure

Storage Wizards.

2. Click Disk-based storage.

3. Type the UNC path to specify the share on the Data Domain system. In the following example, the disk storage device points to the share “bue” on the Data Domain system dd2500-30.

Figure 1: Network share on the Data Domain system

4. Complete the wizard to finish the basic CIFS configuration.

5. Right-click the new device and then select Details. Alternatively, double-click the new device.

6. Change the Block size and the Buffer Size to 512 KB or higher to improve data compression. Change the Maximum file size to 50 GB to reduce the number of files that will be created over time.


version 2

Figure 2: Block size and Buffer size options


version 2

6 Backup Exec configuration — VTL It is recommended that you use either the DDVTL or RESTORER L180 emulation. Otherwise the Backup Exec unlimited VTL license will not be usable.

6.1 Installing Symantec tape device drivers

Note: You do not need to install Symantec tape device drivers if Backup Exec runs on Windows Server 2012 and later. Symantec kernel-mode drivers and tapeinst.exe are no longer installed if Backup Exec runs on Windows Server 2012 or later. If the Backup Exec server runs on Windows Server 2012 or later, the Configure Storage wizard option Install tape device drivers is not available.

1. From the Backup Exec Administration console, click Storage > Configuration Storage Wizard.

2. Click Tape storage.

Figure 3: Configuration Storage Wizard

3. Click Next.

4. Click Install tape device drivers.


version 2

Figure 4: Install Symantec Tape Device Drivers

5. Click Next to continue with driver installation.

Figure 5: Symantec Device Driver Installation

6. Click Next to begin device driver installation.


version 2

Figure 6: Symantec Device Driver Installer

7. Click Next. 8. Click Use Symantec tape drivers for all supported tape devices.


version 2

Figure 7: Symantec Tape Driver Options

9. Click Next to install the drivers.


version 2

Figure 8: Installing Symantec Device Drivers

10. After the installation finishes, restart the Backup Exec server.

6.2 Configure the robotic library partitions Before you begin: as appropriate, configure the tape device drivers and restart the Backup Exec server.

1. Click Configuration Storage Wizard.

2. Click Tape storage.


Figure 9: Configure Tape Storage

3. Click Configure robotic library partitions.

4. Click Next. The robotic library is detected.


Figure 10: Robotic Library is Detected and Configured

5. Select the library that you want to configure, and then click Next to review the partition configuration.


Figure 11: Robotic Library is Detected and Configured

6. Click Next to complete the configuration of the robotic library partitions.

Figure 12: Robotic Library is Successfully Configured


version 2

6.3 Backup and Restore Example 6.3.1 Backup

1. Click Backup and Restore > One-Time Backup > One-Time Backup to Tape Wizard.

Figure 14: One-Time Backup Wizard

2. Under the host name on the left side, click Edit to specify the backup path. Click OK.

19 Dell EMC Data Domain and Veritas Backup Exec 2014 and later CIFS and VTL Integration Guide | docu48700 | version

2

Figure 15: Example of Backup Selections

3. On the right side, click Edit to specify the Robotic library. Click OK.

Figure 16: Example of Backup Device and Media

20 Dell EMC Data Domain and Veritas Backup Exec 2014 and later CIFS and VTL Integration Guide | docu48700 | version

2

4. Click Verify to open the Options for One-Time Backup screen.

The Data Domain system automatically verifies the data integrity, so enabling Backup Exec data verification is typically not necessary. For small backups, you can select the option to enable Backup Exec data verification. For large backups, it is recommended that you select Do not verify data for this job. Enabling Backup Exec data verification for large backups might adversely affect the Data Domain system garbage collection process.

Figure 17: Example of Backup Options

5. Click OK to accept the One-Time Backup options.

6. On the Backup Properties screen, click OK to start the one-time backup job.

7. Click the Job Monitor tab to watch the job progress.

Figure 18: Successful Backups


version 2

6.3.2 Restore Before you begin, perform a backup by using the One-Time Backup to Tape wizard.

1. Click the Backup and Restore tab.

2. Click Jobs, and select the completed backup job.

3. Click Restore backup sets created by this job > Files, folders, or volumes. Click Next.

Figure 19: Backup and Restore Option

5. Select the file and folder backups from a backup set, and click Next.

6. Click the files and folders that you want to restore.


version 2

Figure 20: Example of Select Files and Directories

7. Continue with the Restore Wizard to define your restore options.


version 2

Figure 21: Example of Restore options

8. Complete the wizard to start the restore process.


7 Advanced Topics

7.1 Replication

For more information about setting up replication with CIFS and VTL, see the Data Domain Operating System Administration Guide. The following steps describe a restore from a Data Domain replica for Disk-based Storage option. This procedure does not break replication.

1. Replicate the source directory to the secondary Data Domain system. For example, replicate /data/col1/source to /data/col1/target on the secondary system.

2. From the secondary system, use FastCopy to copy the target directory to another directory. For example “filesys fastcopy /data/col1/target /data/col1/fastcopy”.

3. Delete the Changer.cfg and Folder.cfg files in the /data/col1/fastcopy directory. Otherwise, Backup Exec detects that the original path is in use.

4. From Backup Exec, use the Backup-to-Disk wizard to create a new backup to disk folder that uses /data/col1/fastcopy on the secondary Data Domain system.

5. Run an inventory on the fastcopy directory.

6. Double-click the device folder, and then select Backup Sets. You should see the backup sets that were replicated.


8. Run the Restore wizard to configure and start a restore job. The restore should execute and successfully complete.


7.2 Data Domain Cloud Tier DD Cloud Tier is a Data Domain System feature for moving data from the active tier to low-cost, high-capacity object storage in the public, private, or hybrid cloud for long-term retention. DD Cloud Tier is best suited for long-term storage of infrequently accessed data that is being held for compliance, regulatory, and governance reasons. The ideal data for DD Cloud Tier is data that is past its normal recovery window.

Backup Exec allows users to backup datasets to data domain active tier location (i.e. mtree) and from there, files are moved to cloud with data-movement command, based on the data-movement policy configured on the Data Domain system.

Figure 23: Overview of DD Cloud Tier Solution

Configure cloud tier as described in the Data Domain Operating System Administration Guide

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

For supported cloud platforms, refer to “Data Domain Cloud Tier Compatibility Matrix”.

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

Important Note:

Backup Exec creates two backup metadata files when we create a backup to disk storage device which store information about the backup-to-disk files.

• Changer.cfg • Folder.cfg

Backup Exec recommends not to edit or delete these metadata files.

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

https://support.emc.com/docu86790_Data-Domain-Cloud-Tier-Compatibility-Matrix.pdf?language=en_US


Since Backup exec needs access to these configuration files, user has to ensure that these metadata files are not moved to cloud

In such an event where these backup metadata files are moved to the cloud, this could result in storage device going offline and subsequent failure of backup and restore jobs

You may need to recall these files back to the active tier to continue with normal operations

It is observed that every time a backup job runs, backup metadata file “Changer.cfg” is updated, so “Changer.cfg” automatically remains in active tier if at least 1 backup job is executed every 14 days

For the “Folder.cfg” please ensure that it remains on the active tier and not moved to cloud by setting the modified time for this metadata file to some future date. For example 10 years from now

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

Perform a test backup – Backing up files to Data Domain

Here, ECS Cloud is considered as example.

Configure CIFS storage as mentioned in the “Backup Exec configuration — CIFS” section in this guide

Once the storage is configured, you can now target backups to this Disk Storage

In this example, I have created a disk storage device on a CIFS network share on a Data Domain system


Figure 23: Disk Storage properties

Backup exec creates these files when disk storage device is created

Figure 24: Backup metadata files

7.2.1 Backup 1. Click Backup and Restore > One-Time Backup > One-Time Backup to Disk.


Figure 25: One-Time job properties

2. Under the host name on the left side, click Edit to specify the backup path. Click OK.

Figure 26: Backup job selection


3. On the right side, click Edit to specify the Disk storage. Click OK.

Figure 27: Backup job properties

4. Click OK to accept the One-Time Backup options.

5. On the Backup Properties screen, click OK to start the one-time backup job.


Once the backup job completes a B2D*.bkf file is created in the shared folder


Figure 28: CIFS share contents

7.2.2 Data movement to cloud

On the Data Domain

1. To view the file location, you can generate a file-location report #filesys report generate file-location path < >

Figure 29: File Report

2. To view the Data-movement policy #data-movement policy show

Figure 30: Data-movement policy

Once the files age-threshold reaches 14 days (since in this example the current age-threshold value is set to 14 days), the file will be eligible to be migrated to cloud tier on running the data-movement

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

Note: Data-movement can be either run manually or scheduled

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


3. Run data-movement to migrate the files from Active tier to Cloud tier.

Figure 31: Data-movement start

4. To monitor the progress, data-movement watch

Figure 32: Data-movement watch

5. Now, again run file report and ensure file is migrated to cloud. Note that the Location of file is now “ecs-be-u1” instead of “Active”.

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

Note: “ecs-be-u1” is configured as ECS cloud unit in data domain

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

6. However, observe that the backup metadata files “Folder.cfg” and “Changer.cfg” are on “Active”

Figure 33: File Report

7.2.3 Restore (Direct Restore, only ECS cloud) Restore from backed up file which has moved to cloud -----------------------------------------------------------------------------------------------------------------------------------

Note: Data Domain OS 6.1 and above with ECS 3.1 supports “direct restores” from cloud. This means restores would work without the need to recall the files to active. This is available only for ECS cloud vendor for non-integrated backup applications


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

Before you begin, perform a backup by using the One-Time Backup to Disk and move the B2D file to cloud




Figure 34: Backup and Restore Option

4. Select the file and folder backups from a backup set, and click Next.

5. Click the files and folders that you want to restore.


Figure 35: Restore Wizard > Select file/folders to restore



Figure 36: Restore options

7. Complete the wizard to start the restore process.


Figure 37: Job monitor

9. Job log of successful restore


Figure 38: Job log

10. Observe the file location, on Data Domain with #filesys report generate file-location path <>

Figure 39: Filesys Report after restore

Even after the restore the file is still in cloud-unit


7.2.4 Recall Here we “Recall” the file from cloud tier to Active tier and then restore

1. To restore back file(s) from cloud to active tier (DDR), file is first recalled with

# data-movement recall path <file_location>

Figure 40: data-movement recall

2. Data-movement progress can be monitored with #data-movement status

Figure 41: data-movement status

3. Recall migrates the file from cloud tier to Active tier

4. Run file report to ensure location is set to “active” # filesys report generate file-location path <mtree_path>

Figure 42: Filesys report after recall

7.2.5 Restore 1. Click the Backup and Restore tab.




Figure 43: Restore backup sets created by this job

Figure 44: Restore selection



Figure 45: Restore options

5. Complete the wizard to start the restore process. 6. Click the Job Monitor tab to watch the job progress.

Figure 46: Job monitor

7. Job log of successful restore


Figure 47: Restore Job Log

Date post:	11-Dec-2021
Category:	Documents
Upload:	others
View:	19 times
Download:	0 times