Emc Data Domain Networker Implementation Student Guide 26461u

EMC© Data Domain DD OS 5.1 Implementation with EMC NetWorker Student Guide Version: A.1 December, 2011

Backup Recovery Systems Division EMC© Data Domain 2421 Mission College Boulevard Santa Clara, CA 95054 866-WE-DEDUPE 408-980-4800 www.datadomain.com

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION 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. Using, copying, and distributing EMC software described in this publication requires an applicable software license. EMC2, EMC, Data Domain, Global Compression™, SISL™, the EMC logo, and where information lives are ed trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. © Copyright 2009-2011 EMC Corporation. All rights reserved. Published in the USA.

Welcome to EMC Data Domain Implementation with EMC NetWorker course. Welcome to EMC Data Domain Implementation with EMC NetWorker Copyright © 1996, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.   THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.”  EMC CORPORATION 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 EMC software described in this publication requires an applicable software license. EMC2, EMC, Data Domain, RSA, EMC Centera, EMC ControlCenter, EMC LifeLine, EMC OnCourse, EMC Proven, EMC Snap, EMC SourceOne, EMC Storage , Acartus, Access Logix, AdvantEdge, AlphaStor, ApplicationXtender, ArchiveXtender, Atmos, Authentica, Authentic Problems, Automated Resource Manager, AutoStart, AutoSwap, AVALONidm, Avamar, Captiva, Catalog Solution, C‐Clip, Celerra, Celerra Replicator, Centera, CenterStage, CentraStar, ClaimPack, ClaimsEditor, CLARiiON, ClientPak, Codebook Correlation Technology, Common Information Model, Configuration Intelligence, Configuresoft, Connectrix, CopyCross, CopyPoint, Dantz, DatabaseXtender, Direct Matrix Architecture, DiskXtender, DiskXtender 2000, Document Sciences, Documentum, elnput, E‐Lab, EmailXaminer, E ilX d E i i EmailXtender, Enginuity, eRoom, Event Explorer, FarPoint, First, FLARE, FormWare, Geosynchrony, Global File R E E l F P i Fi P FLARE F W G h Gl b l Fil Virtualization, Graphic Visualization, Greenplum, HighRoad, HomeBase, InfoMover, Infoscape, Infra, InputAccel, InputAccel Express, Invista, Ionix, ISIS, Max Retriever, MediaStor, MirrorView, Navisphere, NetWorker, nLayers, OnAlert, OpenScale, PixTools, Powerlink, PowerPath, PowerSnap, QuickScan, Rainfinity, RepliCare, RepliStor, ResourcePak, Retrospect, RSA, the RSA logo, SafeLine, SAN Advisor, SAN Copy, SAN Manager, Smarts, SnapImage, SnapSure, SnapView, SRDF, StorageScope, Mate, SymmAPI, SymmEnabler, Symmetrix, Symmetrix DMX, Symmetrix VMAX, TimeFinder, UltraFlex, UltraPoint, UltraScale, Unisphere, VMAX, Vblock, Viewlets, Virtual Matrix, Virtual Matrix Architecture, Virtual Provisioning, VisualSAN, VisualSRM, Voyence, VPLEX, VSAM‐Assist, WebXtender, xPression, xPresso, YottaYotta, the EMC logo, and where information lives, are ed trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners. © Copyright 2011 EMC Corporation. All rights reserved. Published in the USA. Revision Date: December, 2011 Revision Number: MR-7WN-DDNWINT.5.1.0

Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.

1

Upon completion of this course, you will be able to: completion of this course you will be able to: Understand fundamental concepts of Data Domain implementation with application software. Perform Data Domain implementation with EMC NetWorker. You will be also able to perform

implementation of the Data Domain Boost option with NetWorker. In addition, you will learn how to prepare for and perform advanced procedures such as performance tuning, troubleshooting, and ongoing implementation of best practices.


EMC Data Domain Implementation -

2

This course provides Implementation Engineers with the skills necessary to integrate a Data This course provides Implementation Engineers with the skills necessary to integrate a Data Domain system with common application software found in backup and recovery environments.   The course is intended for implementation engineers, s,  personnel, and others providing services and  for the integration Data Domain systems. To understand the content and successfully complete this course, a student must have a suitable knowledgebase and skill set. The student should have completed the following e‐ it bl k l d b d kill t Th t d t h ld h l t d th f ll i learning courses: EMC Data Domain Technology and Systems Introduction EMC Data Domain System istration EMC Data Domain System Installation Note: This course should be used in conjunction with Implementation shadowing. The student This course should be used in conjunction with Implementation shadowing The student should also spend time on Data Domain equipment performing these procedures to reinforce the objectives of this e‐learning course.



3

This module covers a number of key concepts involved This module covers a number of key concepts involved in the implementation of EMC Data Domain in the implementation of EMC Data Domain systems with application software.


4

After completing this module, you will be able to: completing this module you will be able to: • Describe the full range of implementations covered in this course, across a variety of software products, protocols, and architectures •Describe data flow in these environments •Describe file system‐based, or NAS, versus VTL, or SAN environments •Describe the basic implementation workflow •Describe a set of requirements that apply to all CIFS servers •Describe the role played by the DD Boost option in a number of these implementations



5

This lesson covers the topics shown This lesson covers the topics shown.


6

This slide presents a general overview This slide presents a general overview of implementation architectures that combine backup of implementation architectures that combine backup software solutions – listed down the left side of the table – with a NAS, or network‐attached storage environment, or a SAN or storage area network environment.  These environments utilize one or more of the protocols  listed along the top, and might also include the DD Boost option. The Data Domain system integrates into any of these configurations, as indicated by the checkmarks.  The green checkmarks indicate the most common configurations.  Take a moment to review before proceeding. p g



7

Here’ss a brief review of basic terminology associated with the backup environment. Here a brief review of basic terminology associated with the backup environment In all configurations, there are clients that need to be backed up, a server that manages these backups, a server that writes to and reads from backup targets, and the backup targets themselves. In some environments, the backup management and read/write functions are performed on a single server. Networking connectivity can be via Ethernet LAN or Fibre Channel SAN.


8

The NetWorker environment shown here The NetWorker environment shown here adds the concept of the NetWorker Data Zone, adds the concept of the NetWorker Data Zone encoming these networked devices. The NetWorker Clients generate the backup data, while a NetWorker Server manages the backup traffic. Specifically, the NetWorker Server s the backup and stores tracking and configuration information.   NetWorker Storage Nodes write data to and read data from backup targets. Another way to define a NetWorker A h d fi N W k data zone is to say that d i h it is the set of hosts managed by a i i h fh db single NetWorker server. This includes all hosts with backup devices controlled by the NetWorker server and all hosts who send their backup data to those devices. NetWorker clients may be backed up by multiple NetWorker servers and therefore may belong to multiple data zones.  NetWorker servers and storage nodes may belong to only one data zone.   In large NetWorker environments, storage nodes serve as an aggregation point for a large number of clients. The clients send their data to the storage node with which they are associated, and the f li h li d h i d h d i h hi h h i d d h storage node backs up the data to the storage.


9

The basic flow of data in a backup and recovery environment runs as follows. The basic flow of data in a backup and recovery environment runs as follows The full range of systems that might require their data to be backed up can include LAN clients, Windows and UNIX Servers, databases and VMWare servers. The backup traffic gets routed through the servers that write to storage – in this example, a Tape Library.  In this case, tapes are rotated out of the tape library and are shipped via trucks to an offsite location. The tapes are stored so the data can be recovered in case of a disaster at the primary site primary site. The metadata associated with the backup is stored with the backup server managing the environment. The metadata is instrumental to the backup system’s ability to quickly locate and restore data.

With tape library storage systems, data is sometimes stored on staging disks called the primary disk pool. It is then migrated to the physical tape library or primary tape pool. The primary tape pool is copied and moved offsite (called the copy tape pool) As a result up to primary tape pool is copied and moved offsite (called the copy tape pool). As a result, up to three copies of the data must be tracked in some situations:  the primary disk pool, the primary tape pool, and the copy tape pool.


10

A Data Domain system integrates as the primary storage destination for deduplicated A Data Domain system integrates as the primary storage destination for deduplicated and and compressed backups.  In this example, Data Domain system A (DDS A) is the primary destination for backups at the headquarters while Data Domain system B (DDS B) is the primary destination for backups at the offsite location. Data can be replicated from the headquarters location to the offsite location via the WAN, preserving a copy at a different location.  The Data Domain system B can

also act as the primary target for backups for clients located at the secondary site. By implementing Data Domain systems, the tape library configuration becomes optional.   Company policies or the need for regulatory compliance both determine the degree to which tapes can be entirely or partially replaced at a site.  Some sites may also choose to use Data Domain replication to partially or completely eliminate the transportation of tapes by truck for vaulting.


11

By replacing some or all of a company By replacing some or all of a company'ss reliance on tape backups with deduplicated reliance on tape backups with deduplicated storage of data storage of data on disk, customers can reduce cost, complexity, and the risks associated with tape.

The key advantages of implementing the Data Domain system are: 1. Reduction in the overall size and scope of the backup and recovery infrastructure. 2. Elimination or reduction of the time and resources needed to create, transport, and reclaim physical tape. 3. Reduction of the number of copies that need to be tracked, thereby reducing backup server database sizes while increasing performance. 4.

Increased speed of disaster recovery.


12



13

Data Domain systems  two integration methods, either in a NAS or Data Domain systems two integration methods either in a NAS or Network Attached Storage environment, via network file system mounts, or as a standalone Virtual Tape Library (VTL), in a SAN or Storage Area Network configuration. FFor network file system access in a NAS environment, the backup software t k fil t i NAS i t th b k ft addresses the Data Domain system via native NFS mounts or CIFS shares. The Backup software addresses the usable space exactly as it would a standard file system mount point such as NTFS, JFS, UFS, and so forth. In a VTL or SAN environment, typically, prior investments have usually been in tape – either physical or virtual. s who know how to manage, monitor, and configure SAN environments can adopt the Data Domain system as a Virtual Tape Library more easily. Data Domain systems can run in a mixed mode capacity, providing both interface methods concurrently to one or many servers. This flexibility   affords a great number of integration scenarios.   Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.

14

In the case of NetWorker, s already using NetWorker In the case of NetWorker s already using NetWorker Advanced File Type Devices (AFTDs) can adopt the Data Domain system as a file system without significant infrastructure or mindset change. The NetWorker AFTDs accept concurrent streams, writing them into separate files in the directory structure of the AFTD. For VTL implementations, use the NetWorker Device Manager drivers to interface with the VTL Library changer with little policy change.


15

This table shows trade-offs between the Data Domain system configured as a File System versus a VTL. Please take a few moments to become familiar with them.


16

This table continues with additional trade-offs between the Data Domain system configured as a File System versus a VTL. Please take a few moments to become familiar with them.


17



18

Data Domain implementations all follow a similar workflow Data Domain implementations all follow a similar workflow. To successfully integrate the Data Domain system into a backup environment, first perform the basic installation and configuration tasks shown in the diagram.   In the first step, make certain that all installations have occurred, including installation of all application software as necessary throughout the environment, and installation and initial configuration of the Data Domain system for proper network access by client systems and backup servers. servers Steps two and three are typically performed by Implementation Engineers. In the second step, configure the Data Domain system with the correct networking, and create a backup . Third, configure the backup server with the necessary credentials or other settings as necessary, and create a share on the Data Domain system.


19

Once the communication between the backup environment and the Data Domain system is Once the communication between the backup environment and the Data Domain system is established, you ister and operate the Data Domain system and backup servers in order to validate the implementation.  These steps are typically performed by Implementation Engineers. First, perform istrative tasks on the backup system’s istrative console in order to create a backup job. Next, you run and monitor the backup job in the backup system’s istrative console. You can also perform operations to perform backup recovery for a client system.   And finally, you can validate and analyze the backups within the Data Domain Enterprise Manager, where you can view statistics and reports.


20

The workflow for a VTL implementation varies with the basic steps shown here The workflow for a VTL implementation varies, with the basic steps shown here.   In most environments, FC zoning and HBA card installation and configuration will have been previously completed. Steps 3 through 5 are typically performed by implementation engineers, and cover configuration of the data domain system, device discovery and configuration on the backup system’s istrative console, followed by performance of normal backup istration and operation.


21



22

The Data The Data Domain Boost option is available for the software applications and protocols shown in the Domain Boost option is available for the software applications and protocols shown in the highlighted area.


EMC Data Domain Implementation - 23

What are the advantages of implementing the DD Boost option? What are the advantages of implementing the DD Boost option? DD Boost provides the advantages of improved throughput, backup server managed file replication and backup server replica awareness. How is this possible and why is this important in a backup, recovery and archive environment?


24

Let'ss discuss these advantages in detail. Let discuss these advantages in detail How does DD Boost improve throughput? Improved throughput of “retaining”  data (backups)  is accomplished with the Open Storage Technology (0ST) protocol and the Data Domain Distributed Segment Processing (DSP). OST when compared with CIFS and NFS protocols has a faster throughput. Distributed Segment Processing offloads part of the Deduplication process to the Backup Server (if enabled) to further improve offloads part of the Deduplication process to the Backup Server (if enabled) to further improve performance.


25

Why is Backup Server managed file replication beneficial? Why is Backup Server managed file replication beneficial? Without DD Boost, replication is initiated and managed by the Data Domain system.  The Backup server is not aware of the data written on the replica Data Domain system (B).   With DD Boost, the Backup server can now initiate and manage file replication.


26

Why is Backup Server awareness of the replica Data Domain system beneficial? Why is Backup Server awareness of the replica Data Domain system beneficial? Because DD Boost allows for the Backup server to be aware of the replica Data Domain system, it can directly restore and recover from the replica Data Domain system.  Prior to DD Boost, the backup server could not control or manage the replica data. This made restoring the data from a replica a manual process.

In summary, NetWorker and Data Domain are so tightly wound together through DD Boost In summary NetWorker and Data Domain are so tightly wound together through DD Boost that s see them as a single solution. Working entirely from the NetWorker console, s can create all backup routines, set up cloning tasks, and determine which pieces of data to send from site to site, without the need to go to multiple places to see that backups and replication have completed successfully. As a result, management time for data protection is reduced significantly.


27

This module covered the topics shown This module covered the topics shown.



This module covers various options and procedures for EMC Data Domain implementation with This module covers various options and procedures for EMC Data Domain implementation with EMC NetWorker.


29

After completion of this module you will be able to: After completion of this module, you will be able to: 

Implement the Data Domain system as a file system with NetWorker



Validate NetWorker backup and recovery



Implement DD Boost with Networker



Implement the Data Domain system as a VTL with NetWorker



Implement best practices with NetWorker best practices with NetWorker





31

To successfully integrate the Data Domain system with the backup environment, you will perform To successfully integrate the Data Domain system with the backup environment you will perform installation and configuration steps as shown. Proper installation and configuration are essential for proper communication.


32

All backup application software All backup application software should have previously been installed.  If necessary, complete all should have previously been installed If necessary complete all installations according to the manufacturers instructions.


33

Next,  that the CIFS configuration of the Data Domain system meets the basic Next that the CIFS configuration of the Data Domain system meets the basic requirements allowing proper access. For example, backup systems should be able to map a network drive to the Data Domain system backup directory.


34

The requirements are: The requirements are: • The Data Domain system must use either the Active Directory or Workgroup authentication mode. • The Data Domain system must have a valid CIFS   with the following minimum permissions: If the is part of a Domain or Active Directory, it must have at least, Domain • If the  is part of a Domain or Active Directory, it must have at least, Domain Backup Operator plus Local  permissions • If the  is in a workgroup, it must have at least, Backup Operation group permissions


35

The goal is to add a backup  to the Data Domain system, and map a CIFS share.  The details of both configurations g p y p g will be used in the istration of NetWorker. To get started, on the Data Domain system, after logging into the Enterprise Manager as sys, go to the System Settings tab. Click the Local s tab. To create a new , click the Create button and add the  information. For this exercise, the backup  information is: : : abc123 Pri ilege Privilege: Type and then retype the : abc123 Retype the  for verification: abc123 Choose  from the Privilege drop down menu. Choose the  option. Click OK to complete the configuration. You have added the backup  .  Take note of these new  credentials. They will be added to the services logon credentials on the NetWorker Server. g Now you will map a CIFS share on the Data Domain system, to be used in NetWorker backup istration. This directory will be the target for backups. From the task bar at the bottom of the screen, select the B:\\ drive. Click in the window. We've opened the right‐click context menu for you.   Choose New > Folder.   Choose Folder to create a new folder. Name the folder by typing: CIFS h f ld b i From the task bar at the bottom of the screen, select the Enterprise Manager. After viewing the system information in the Enterprise Manager, go to File System > CIFS. Under the Shares tab, click the Create button.



In the Create Share window, in the Share Name field, type: yp CIFSshare In the Directory Path field, type: /data/col1/backup/CIFS Under the Client section, click the green + sign. In the Client window, under the Client field, grant access to all clients by typing an asterisk (*) and pressing Enter. Ensure the Max connections is set to Unlimited and Allow Browsing and Writable are enabled. Click OK. In the Shares tab, ensure only CIFSshare is selected.   To Map a network drive to CIFSshare, from the task bar at the bottom of the screen, select the Computer window. Choose Map Network Drive from the Tools menu. Choose Map Network Drive. Choose T: from the Drive menu.   Choose T: In the Folder field, type the path to the CIFS share.  For this exercise, type: \\\\10.127.15.52\\CIFSshare In the Connect As window, log in with the sys credentials: name: sys : abc123 Type the  (abc123). Press Enter. Click Finish. Th The mapped CIFS share backup location opens in its own window. d CIFS h b k l ti i it i d Congratulations, you have configured the Data Domain system with a backup  and CIFS share.



In a previous lab, you created a backup on the Data Domain system with name In a previous lab, you created a backup  on the Data Domain system with name and  ab123.  The goal of this lab is to reconfigure Services on the NetWorker Server by adding these log on credentials  to allow for communication between the backup server and the Data Domain system. You will add these credentials to the following Networker Server services: ‐ Networker Backup and Recover Server ‐ Networker Remote Exec service To begin, click the Start menu. Click Run, then open the services.msc application. Type: services.msc then press Enter. Click OK. I th li t f In the list of services, click Networker Backup and Recover Server. i li k N t k B k dR S We've opened a right‐click menu for you.  Choose Properties. Select the Log On tab. Select This . Enter the credentials for the backup  you previously created on the Data Domain system: name: :abc123 Enter the :abc123, then press Enter.



by re‐entering the : abc123, then press Enter. y y g p , p Click OK. The system warns you that you must restart the services for the changes to take effect.  Click OK. Click OK again to complete the configuration. In the list of services, click Networker Remote Exec service. We've opened a right‐click menu for you.  Choose Properties. Select the Log On tab. Select the Log On tab. Select This . Enter the credentials for the backup  you previously created on the Data Domain system: name: :abc123 Enter the :abc123, then press Enter. by re‐entering by re entering the : abc123, then press Enter. the : abc123, then press Enter. Click OK. The system warns you that you must restart the services for the changes to take effect.  Click OK. Click OK again to complete the configuration. As the message stated, you must restart the services for the changes to take effect.   In the list of services, click Networker Remote Exec service. We've We ve opened a right opened a right‐click click menu for you.  Choose Restart. menu for you Choose Restart Congratulations, you've reconfigure Services on the NetWorker Server to allow for proper communication with the Data Domain system.



Once the communication between the backup environment and the Data Domain system is Once the communication between the backup environment and the Data Domain system is established, you will ister and operate the Data Domain system and backup servers in order to validate the implementation with the steps shown.


40

The goal of this lab is to perform istrative and operational tasks in the NetWorker istrative g p p Management Console. You will create an Advance File Type Device for the Data Domain system, configure, run, and validate a backup job, and perform and validate a restore. Begin by launching the NetWorker istrative Management Console from the shortcut located on the desktop. Enter the  credentials. name: : abc123 Enter the , abc123, then press Enter. Click OK. Click on DD01_win. We've opened a right‐click menu for you.  Choose istration to launch NetWorker . Create a new device.  First click Devices to view the tree. Select Devices under the Devices Tree Select Devices under the Devices Tree. We've opened a right‐click menu for you.  Choose New. For an Advanced File Type Device, replace the default “name” with the complete path of the directory for the device (either the NFS mount point or the CIFS share) In this example, specify the CIFS share you previously created on the Data Domain system:\\ddappliance1\data\col1\backup\CIFS This path is the target for backups for this device. Make sure theMedia Type is set to Make sure theMedia Type is set to “adv adv_file file” then click OK.   then click OK. Click Yes to Create the AFTD. After you create the Advance File Type Device, label and mount the AFTD device.  First, you specify the Volume label. Click the device in the Devices pane. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


We've We ve opened a right‐click menu for you.   opened a right‐click menu for you Choose Label… In this example, the Volume Label is the CIFS‐UNC absolute path.   Type the path into the field then press Enter: \\ddappliance1\data\col1\backup\CIFS Click OK. You have just created, labeled and mounted the AFTD device. Two AFTDs are created automatically. The first is a read‐write device. The second is a read only device, which is assigned the _AF_readonly suffix. Now you can create a backup job using the configuration wizard. Note that in this environment, the NetWorker Server also acts as the NetWorker Client. Cli k C fi Click Configuration at the top. i h Click Clients. We've opened a right‐click menu for you. To launch the wizard, choose Client Backup Configuration > New. Choose New. For simplicity purposes, you will choose most of the default settings except where indicated.  Once you become familiar with the Data Domain system and NetWorker configurations options, you can create policies that are specific to the environment, such as scheduling and grouping of save sets for particular data types. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


For the Client Name enter: Servers For the Client Name, enter: Servers then press Enter. Click Next. Select a folder to backup. In this example, select the Installs Directory, then click Next. Click Next. Accept the defaults here, and click Next to continue. Here you create a group called Server. Select Create a New Group. Under Group Name, enter: Servers then press Enter. Click Next. Here you specify the Data Domain system as the target for this backup and the source for restores. Select: Backup to the following storage nodes y y The Data Domain system is selected by default. Select: Recover from the following storage nodes The Data Domain system is selected by default. Click Next. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


The summary allows you to review the configurations you have created. The summary allows you to review the configurations you have created. Click Create. Click Finish. Now you can run and monitor the Backup Job you created. Browse to the Client you want to backup and start the backup. First, click Monitoring. In the Groups pane, Click Servers. We've opened a right‐click menu for you.   To run the backup, click Start. Click Yes. The backup is underway.  In the Groups pane, click Servers again. We've opened a right‐click menu for you.   To monitor the backup choose Show Details To monitor the backup, choose Show Details. Shown here is a detailed summary of the Backup job, including the client name, the save sets, and the start time. Click OK. You have just successfully monitored a backup job within NetWorker Console. You can validate that the Backup job successfully completed by browsing to the Data Domain CIFS share and viewing the files share and viewing the files. Go to the desktop by clicking the Show Desktop button in the task bar at the bottom. Click the Start button.



Click Run. Click Run. Enter the path to the share.   For this exercise, enter: \\ddappliance1\data\col1\backup\CIFS Notice the files written to the Data Domain system. This validates that the backup job was successful. N Now you can restore files from a backup and validate this recovery. t fil f b k d lid t thi Switch to the dd01_win ‐ NetWorker  window by clicking it in the Windows task bar at the bottom. Click Configuration at the top to view the tree. Click Clients to view the configured systems. In the Clients pane, click the second dd01_win system in the list. We've opened a right‐click menu for you.  Choose Recover. dd01_win is selected by default as the Source Client.   Click OK. For this exercise, select the SysTools directory to restore. Select overwrite the existing file to replace the current file with the restore file. Click OK to start the restore Click OK to start the restore.   Note that this process can take several minutes.  We've shortened the time frame for this exercise. The recovery is now complete. Note the summary details at the end of the log. Congratulations, you've successfully istered and operated NetWorker configured with Data Domain for backup and recovery. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.




46

Picking up with steps 2 and 3 after the backup software has already been installed, the goal is to Picking up with steps 2 and 3 after the backup software has already been installed the goal is to establish communication between the Data Domain system and the Backup server in an NFS environment. In step 2, the Data Domain system must be configured for networking with NFS, and in step 3, the backup server must be configured for backups with NFS mounts.


47

Here s the high level task list for configuring the Data Domain system for Network connectivity and Here’s the high level task list for configuring the Data Domain system for Network connectivity and enabling the backup transport protocol for NFS. Take a moment to review before proceeding with the detailed steps.


48

To configure the Data Domain Networking and NFS Parameters, establish an SSH session to the To configure the Data Domain Networking and NFS Parameters establish an SSH session to the Data Domain system and run the  # config setup command. This will launch the installation wizard. Configure the Networking Parameters based on your environment. Note: If the Data Domain system is not on the network – for example, if it doesn’t have an IP address – you will have to directly connect to the Data Domain system via the serial console to manage the Data Domain system. Configure the Data Domain system NFS parameters. Configure the Backup server list by typing an asterisk. This allows for any host on the network to connect to the Data Domain system via NFS. To lock specific hosts, replace the asterisk with a specific hostname or an IP Address.  Next, you  access to the Data Domain backup and ddvar directories, through an NFS mount.


49

The goal is to create a mount on the Backup Server server and copy a test file to the Data Domain system. The diagram shows the high level task list flow: a. Create mount points (directories) b. Mount Data Domain directories on the new mount points c. Modify /etc/fstab to mount directories at every boot d. Create a backup directory on the NetBackup Server Once the NFS Mount procedure is completed, create and copy the file from the Server to the Data Domain backup directory to validate functionality. Note: The specific commands will differ depending on the platform you are running. running Always refer to documentation for the specific commands for each platform.


50

The detailed procedures are to: first, create mount points, or directories, using the The detailed procedures are to: first create mount points or directories using the commands shown.  Then, mount Data Domain directories on the new mount points.   Example commands and parameters are shown. Next, modify /etc/fstab to mount directories at every boot. Finally create a backup directory on the NetBackup Server. Note: The specific commands might differ depending on the platform you are running. Always refer to documentation for the specific commands for each platform.



Once the NFS Mount procedure is completed, create and copy the file from the Server to Once the NFS Mount procedure is completed create and copy the file from the Server to the Data Domain backup directory to validate functionality. Note: The specific commands will differ depending on the platform you are running. Always refer to documentation for the specific commands for each platform.



This lesson covers the topics shown shown.


53

To implement DD Boost in a Networker environment, do the following: To implement DD Boost in a Networker environment do the following: Step 1: Configure Data Domain systems (A and B) for DD Boost Note that these steps are configured on each of the Data Domain systems. Step 2: In the NetWorker Console: Configure Data Domain systems as Devices for DD Boost The following practice simulation will guide you through the specific steps.


54

C i Continue with the DD Boost Implementation by ing backup and clone functionality. i h h DD B I l i b if i b k d l f i li To do this: 3. On the Networker Console configure a Backup Client and Backup Clone 4. Monitor the activities for the backup and the clone operations. 5.  the files on Data Domain system A and B. y p 6. Finally, restore files from the Backup Clone.


55

In this lab, you prepare EMC NetWorker to perform backups to Data Domain Systems with DD ,y p p p p y Boost.  You should have already performed procedures to prepare the source and target Data Domain systems for DD Boost. Open the Networker Management Console with the   name and .   Normally this operation takes 2 ‐ 3 minutes. We've performed the operation for you, and the application is open as shown. Under Server Name in the list, select dd01_win (with Server Type NetWorker). We've opened a right‐click menu for you. Choose Launch Application. p g y pp In the NetWorker istration window, select the Devices tab at the top. Under the Devices tab, in left pane, select Data Domain Systems. We've opened a right‐click context menu for you in the right pane.  Select New Device Wizard to add the source Data Domain system as a device. In the Device Configuration Wizard, in the Select the Device Type screen, ensure Data Domain is selected. Cli k N t Click Next. In the Data Domain Preconfiguration Checklist screen, do not select an option. Click Next. In the Configuration Options screen, ensure that the Create a New Data Domain System option is selected. Type your source Data Domain System host name (dddev‐03). In the Data Domain OST name field type:
sys In the Data Domain OST name field type:


In the Select Folders to use as Devices screen, in the folder tree on the right, select In the Select Folders to use as Devices screen in the folder tree on the right select Boost_backup. Click Next. In the Configure Pool Information screen, ensure that: ‐Configure Media Pools for devices is selected ‐The Pool Type is Backup The Pool Type is Backup ‐Create and use a new Pool option is selected.   Under Create and use a new Pool, type: dddev‐03boostbackup Ensure the Label and Mount device after creation option is selected. Click Next. In the Select Storage Nodes screen, click Next. In the SNMP Monitoring Options screen, deselect Gather usage information and Receive SNMP trap events. Deselect Receive SNMP trap events. Click Next. In the Review Configuration Settings screen, review the information. click Configure. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


This operation usually takes two minutes. We This operation usually takes two minutes. We've ve shortened the duration for you. shortened the duration for you. In the Device Configuration Results screen, review the information. Click Finish. In the NetWorker istration window, in the left pane, click your source Data Domain System (dddev‐03). Review the information in the right pane.  You've completed preparation of the source system in EMC Networker EMC Networker. Now prepare EMC NetWorker to perform a backup clone of the target Data Domain system.  In the left pane, select the Data Domain system. In the right pane, we've opened a right‐click context menu for you.  Choose New Device Wizard. In the Device Configuration Wizard, in the Select the Device Type screen, make sure Data Domain is selected and click Next. In the Data Domain Configuration Checklist screen do not select an option In the Data Domain Configuration Checklist screen, do not select an option. Click Next. In the Configuration Options screen, select Create a New Data Domain System. Under Create a New Data Domain System, type your target Data Domain system host name (dddev‐ 04). In Data Domain OST name field type:
sys I D t D In Data Domain OST  field type: i OST P d fi ld t abc123 Click Next.



In the Select Folders to use as Devices screen, in the folder tree on the right, select Boost_clone. In the Select Folders to use as Devices screen, in the folder tree on the right, select Boost clone. Click Next. In the Configure Pool Information screen, ensure the Configure Media Pools for devices is checked, then under Pool Type, select Backup Clone. Under Create and use a new Pool,  type: dddev‐04backupclone E Ensure the Label and Mount device after creation is checked. Click Next. th L b l d M td i ft ti i h k d Cli k N t In the Select Storage Nodes screen, click Next. In the SNMP Monitoring Options screen, deselect Gather usage information and Receive SNMP trap events. Deselecte Receive SNMP trap events. Click Next. In the Review Configuration Settings screen, review the information. Click Configure. In the Check Results screen, review the information.
Click Finish. In the NetWorker istration window, in the left pane, click your target Data Domain System ((dddev‐04). ) Review the information in the right pane.   Congratulations, you completed preparation of the source and target Data Domain systems in EMC Networker.



In this lab you configure NetWorker to perform Backups with DD Boost.  You should have previously y g p p p y prepared the source and target Data Domain systems for DD Boost. Also, you should have prepared EMC NetWorker to work with the two Data Domain systems. In the NetWorker istration window, select the Configuration tab. In the Configuration tab, in the left pane, select Clients. In the right pane, we've opened a right‐click context menu for you.  Choose Client Backup Configuration > New. In the Client Backup Configuration window, in the Specify the Client Name screen, type the name of the Data Domain system in Client name field For this exercise type Data Domain system in Client name field.  For this exercise, type: dd01_win Click Next. In the Specify the Backup Configuration Type screen, click Next. In the Specify the Backup Options screen, ensure that Deduplication is set to None and  that Checkpoint Enabled is deselected. Choose the source DD Boost pool you created earlier form the Target Pool menu. Choose dddev03Boostbackup. Click Next. In the Select Files to Backup screen, in the tree on the right, Click the plus sign (+ ) to expand dd01_win. Un‐check dd01_win Click the plus sign (+ )  to expand C: Select the Troubleshooting folder. Click Next. Click Next. In the Select the Client Properties screen, click Next. In the Choose the Backup Group screen, select Create a new group. Under Create a new group, type the name of the group.  For this exercise, type: Boostgroup Click Next. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


In the Specify the Storage Node Options screen, click Next. In the Specify the Storage Node Options screen, click Next. In the Backup Configuration Summary screen, review the details. Click Create. In the Check Results screen, click Finish. In the NetWorker istration window, select the Media tab. In the left pane, ensure that Media Pools is selected. In the right pane, double‐click dddev‐03Boostbackup. In the Properties window, under the Data Source section, select Boostgroup, then click OK. Click OK. Click OK. Configure EMC NetWorker to perform a backup clone to the target Data Domain System. In the NetWorker istration window, click the Configuration tab. In the left pane, select Clones. We've opened a right‐click context menu for you in In the right pane. Choose New. In the Create Clone window ensure the General tab is selected Under the Name field type a name for the In the Create Clone window, ensure the General tab is selected. Under the Name field, type a name for the clone.  For this exercise, type: Boost_Clone From the Write clone data to pool drop‐down list, choose the target clone name.  For this exercise, choose: dddev04Backupclone Choose dddev04Backupclone. Select the Save Set Filters tab at the top of the window. Under Set Filters > Save Set Filter Options > Groups section, select Boostgroup. Click OK. In the Configuration tab, in left pane ensure that Clones is selected. In the right pane, review details for the clone you created. Congratulations, you configured EMC NetWorker to perform backups with DD Boost. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


In this lab you perform and  backups to Data Domain systems in a DD Boost environment  that is   y p y p y configured with EMC NetWorker. Under the NetWorker istration > Monitoring  > Groups section, click Boostgroup. We've opened a right‐click context menu for you.  Click Start. In the Question window, select Yes to initiate the backup job. We've opened the Boostgroup Details window for you, which you can access by right‐clicking the group and choosing Details.   The Boostgroup g p Details window allows you to monitor the backup job progress.  Note that the Status at the y pj p g top shows Succeeded, and the job is at 100% completion. Click OK. To review the logs, in the Log section click the floating window icon to break out and enlarge the log window. The Log window continuously updates, allowing you to review operations. After reviewing the logs, click the docking/minimize icon to minimize the window. Now you will perform a backup clone to the target Data Domain system. In the NetWorker istration window, under the Monitoring tab, select the Clones tab. Under the Clones section, click the Boost_Clone. We've opened a right‐click context menu for you.  Click Start. In the Question window, click Yes to initiate the backup clone job. Under the Clones section, click Boost Clone to refresh the details. Note the session details for the job under the All Sessions section.   To review the logs, under the Log section, click the floating window icon to maximize the enlarge the log To review the logs, under the Log section, click the floating window icon to maximize the enlarge the log window. After reviewing the logs, click the docking/minimize icon to minimize the window. space usage and file system stats on the Data Domain systems.   Click Enterprise Manager in the Windows task bar at the bottom to switch to the browser. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


The Enterprise Manager was previously opened and logged into the source Data Domain system.   The Enterprise Manager was previously opened and logged into the source Data Domain system. Under the DD Boost tab, click the Storage Units tab. Review the Boost Backup storage unit details for the source system, dddev‐03.  This verifies that a backup via DD Boost was completed. Click the File Replication Stats tab. Note the statistics.  You see no inbound activity for this Data Domain system because it is the source for replication Note the outbound activity source for replication.  Note the outbound activity. Click the Statistics tab. Under the Statistics tab, you can find additional details.  Take a moment to review. Click the second Enterprise Manager tab at the top of the browser. On this tab, we previously logged into Enterprise Manager for the target Data Domain system (dddev‐04).  The Storage Units details are displayed.   Cli k th Fil R li ti St t t b Click the File Replication Stats tab. Under File Replication Stats, note the details.  Since this is the target Data Domain system, you see the inbound activity.  There is no outbound activity. Switch to the Windows view of the Boost_backup share by clicking it in the Windows task bar at the bottom of the screen. Note the files created by EMC NetWorker during the backup.   S it h t th B t l Switch to the Boost_clone share by clicking it in the Windows task bar at the bottom. h b li ki it i th Wi d t kb t th b tt Note the files created by EMC NetWorker during the backup clone operation.   Congratulations, you have successfully performed and verified backups from EMC NetWorker to Data Domain systems with a DD Boost configuration. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


The table shown compares the recommended NetWorker parameters for the Data Domain Device The table shown compares the recommended NetWorker parameters for the Data Domain Device TYPE used for DD Boost configurations and the Advanced File Type Device used for the NFS or CIFS configurations. Please take a few moments to review it.


64

This lessons covers the topics shown. This lessons covers the topics shown


65

To implement Data Domain as a VTL with NetWorker you perform the steps shown To implement Data Domain as a VTL with NetWorker, you perform the steps shown.


66

The goal of this lab is to configure the VTL feature with a library, pools and tapes, and then create a g g y, p p , VTL group on the Data Domain system. Begin by expanding the DD Network tree in the left pane, and selecting the Data Domain system. Select the dddev‐04 system. Under the Data Management tab, click the VTL tab to display its settings. Click the VTL Service tree to expand it. First you will create a VTL library. Choose Library > Create under the More Tasks menu. Choose Library > Create. Give the library a name. For this exercise, enter: VTL LIBRARY In the Number of drives field, enter: 10 In the Number of slots field, enter: 10 In the Number of CAPs field, enter: 2 Click the field under Changer Model Name. We've changed the Changer Model Name for you to RESTORER‐L‐180, which is the correct name for this exercise. Click Next to proceed.



The library creation is complete. Click OK. Now you can create a pool.   First, select Vault in the Virtual Tape Libraries tree to expand it. Choose Pool > Create under the More Tasks menu. Choose Pool > Create. Give the Pool a name.  For this exercise, enter: VTL Pool Click Next. The Pool has been created.   Click OK. Now you can add tapes.   First, select VTL Pool in the Virtual Tape Libraries tree. Choose Tapes > Create under the More Tasks menu Choose Tapes > Create under the More Tasks menu. Choose Tapes > Create. In the Number of Tapes field, enter: 10 Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


In the Starting Barcode field, enter: In the Starting Barcode field, enter: AAAA01L2 In the Tape Capacity field, enter: 10 Click Next. The tapes have been created.   Click Close. In the Virtual Tape Libraries tree, click to expand VTL Service > Libraries. Expand VTL LIBRARY. Select VTL LIBRARY. Under the More Tasks menu, choose Tapes > Import… Choose Tapes > Import Choose Tapes > Import… Choose VTL Pool from the Pool menu. Choose VTL Pool The tapes you previously created show up in the list. Select all of the tapes by clicking the checkbox at the top. Click Next. Click Next. The tapes have been successfully imported. Click Close.



In the Virtual Tape Libraries tree select Tapes under VTL LIBRARY > Drives In the Virtual Tape Libraries tree, select Tapes under VTL LIBRARY > Drives. The tapes appear correctly in the list on the right. Select VTL LIBRARY again. Now you can create a VTL group.   Select + Access Groups on the left to display its details. Under the More Tasks menu, choose Group > Create. Choose Group > Create. Give the group a name.  For this exercise, enter: VTLgroup Click Next. For this exercise, we will not add devices at this time. Click Next. The configuration summary is displayed here.   Click Finish to create the group. The new group has been created The new group has been created. Click OK. Congratulations, you have successfully configured the VTL feature with a library, pools and tapes, and then created a VTL group on the Data Domain system. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.


The goal of this lab is to  the discovery of the Data Domain system  and configure it as The goal of this lab is to the discovery of the Data Domain system and configure it as a VTL on the NetWorker Server. After opening the NetWorker instration console, begin by selecting Libraries in the tree on the left. Click in the empty pane under Libraries. We've We ve opened a right opened a right‐click click menu for you.  Choose Scan for Devices. menu for you. Choose Scan for Devices. With dd01_win selected, click Start Scan. The system is scanning to discover the Data Domain configuration. Click OK. Click the Monitoring button at the top to monitor the progress of the device discovery. Th l The log shows the progress, and its completion.   h h di l i Click Devices button at the top to view the discovered device. Expand Libraries in the tree on the left to view the VTL configuration. Click on the new library listed in the Libraries pane on the right. We've opened a right‐click menu for you.  Choose Configure Library. Make sure the checkboxes are selected, then click Start Configuration. Congratulations, you successfully configured the Data Domain system as a VTL on the NetWorker Server. Copyright © 2011 EMC Corporation. Do not copy - All Rights Reserved.






73

Upon completion of this module you will be able to: Upon completion of this module, you will be able to:

• • •

Find Resources on Advanced Topics Implement CIFS server Best Practices Troubleshoot Active Directory common issues



To dig deeper into the many facets of implementation with application software, click the To dig deeper into the many facets of implementation with application software click the ing Materials tab to  application‐specific documentation.  The documentation is current as of this publication. You can also check for any recently added or updated documentation by visiting the my.datadomain.com  portal, or the white paper locations at the URLs shown.





76

Multiplexing interleaves backup streams, writing a little of save set 1, then a little of save set 2, and Multiplexing interleaves backup streams writing a little of save set 1 then a little of save set 2 and so on, so that none of the clients sending save sets need to wait for the other clients to finish. The interleaving of save sets has a significant impact on deduplication efficiency when the Data Domain device is used as a virtual tape library (VTL). Multiplexed streams hinder the deduplication process from efficiently identifying blocks of common data because of the additional header information added to the data with parallelism. In order to realize the full benefit of deduplication, EMC recommends multiplexing be turned off when using the Data Domain appliance as a VTL with NetWorker by setting both target sessions and max sessions on each virtual tape drive to a value of 1. Note that the use of parallelism is not an issue if the Data Domain system is used as a NAS target by creating an Advanced File Type Device (AFTD) on CIFS or NFS shares because each save set is stored as a separate file regardless of parallelism settings. The older File Type Device (FTD) stores save sets as multiplexed however, and is affected.


77

This table shows some of the Best Practices when implementing the Data Domain system as a file This table shows some of the Best Practices when implementing the Data Domain system as a file system to NetWorker.  Please take a few moments to become familiar with them.


78

This table shows additional Best Practices when implementing the Data Domain system as a file This table shows additional Best Practices when implementing the Data Domain system as a file system to NetWorker.  Please take a few moments to become familiar with them.


79

This table shows some of the Best Practices when Implementing the Data Domain system as a VTL to NetWorker. Please take a few moments to become familiar with them.


80



81

Certain internal activities on a Data Domain system can take longer than the default CIFS timeout Certain internal activities on a Data Domain system can take longer than the default CIFS timeout on the servers. This can lead to an error message during a backup. To avoid a premature timeout, change the SESSTIMEOUT value from the default 45 seconds to 3600 seconds. To do so:

a. b. c. d. e.

Open REGEDIT and navigate to the path shown. In the parameters folder add a new String Value Set the Value name to SESSTIMEOUT And the Value data to 3600


82

With respect to CIFS performance, performance it is necessary to tune the T/IP parameters on each server. Modify the Windows Registry for the following: •

Send and Receive Window

•

T Window Size

The modification parameters change slightly, depending upon whether the backup server is Windows 2000/2003 or Windows NT.



The specific procedure for tuning of T/IP parameters on Windows 2000/2003 backup servers are shown here. Please a take a moment to review before proceeding. For full details,  the CIFS and Data Domain Systems Tech Note from the ing materials tab.



Please a take a moment to review before proceeding proceeding.



The specific procedure for tuning of T/IP parameters on Windows NT backup servers are shown here. Please a take a moment to review before proceeding. For full details,  the CIFS and Data Domain Systems Tech Note from the ing materials tab.



Please a take a moment to review before proceeding proceeding.



There are several requirements for CIFS environments configured There are several requirements for CIFS environments configured for Active Directory.  For full for Active Directory For full details,  the CIFS and Data Domain Systems Tech Note from the ing materials tab. The following slides describe basic troubleshooting guidelines.



In an active directory environment the most common issues can be separated into two categories: In an active directory environment, the most common issues can be separated into two categories: 1.

ing the Domain, where the Data Domain system has trouble ing the Active Directory domain and

2.

Client Access, where the Media server is unable to access the Data Domain system to perform a backup


89

To troubleshoot “ing ing the Domain Domain” issues, issues check physical and transport connectivity between the two components, mainly T connectivity. On the Data Domain system, check to make sure the time on the Data Domain system is within 5 minutes of the Active Directory Server. Also, check to make sure that the backup specified on the Data Domain system is a valid on the Active Directory Domain with at minimum “Operator” privileges. The command # CIFS Troubleshooting list-s can help with narrowing down any issues.


90

To troubleshoot “Client Client Access Access” issues, issues again check physical and transport connectivity between the two components, mainly T connectivity. On the Data Domain system, check to make sure the Media server host is allowed as a Backup Client.

Also check to make sure that there are no stale Kerberos Tickets.


91




To learn about EMC Data Domain products and solutions solutions, consult the following resources. resources For product information, including overviews, data and specification sheets, and white papers, visit the link shown at EMC’s website. For product documentation, knowledge base articles, and additional white papers, visit my.datadomain.com. This site requires a . To find and enroll in follow-on training covering a wide range of topics including system i t ll ti and installation d maintenance, i t integration i t ti and d implementation, i l t ti istration d i i t ti and d troubleshooting, visit EMC Education Services, using the link shown. Search for Data Domain to view a complete list of offerings.


This course covered the topics shown This course covered the topics shown. This concludes the training. Proceed to the course assessment on the next slide.



Emc Data Domain Networker Implementation Student Guide 26461u

Overview 26281t

More details 6y5l6z

Related Documents 3h463d

Emc Data Domain Networker Implementation Student Guide 26461u

Data Domain Student Guide 1d571q

Data Domain Student Guide 1d571q

Emc Data Domain Overview 6h691x

Emc Networker Vmware Integration Guide 5k242j

Dell Emc Data Domain Dd3300 Data Protection.pdf 6x2j3z

More Documents from "Mansoor" 21203r

Cv10 Implementation And Maintenance Studentguide 1p3f3o

Emc Data Domain Networker Implementation Student Guide 26461u

Ldap Interview Questions _ Redhat Panacia ce2z

Two Dimensional Problems In Cartesian Coordinate System And Polar System 19503q

Backing Up And Recovering Clusters With Emc Networker 514a6m

Cv10 Core Fundamentals Course Student Guide_indexcache Portion Is Very Wrong 405k5u