Transcription
EMC Avamar Data Migration EnablerVersion 19.64User Guide302-004-296REV 04Copyright 2016-2021 Dell Inc. or its subsidiaries. All rights reserved.Published April 2021Revised September 23, 2021Dell 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.“ DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KINDWITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OFMERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATIONREQUIRES AN APPLICABLE SOFTWARE LICENSE.Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published inthe USA.Dell CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381 www.dell.com
Table of ContentsTABLES . 4PREFACE . 5CHAPTER 1 . 9ADME INTRODUCTION . 9AVAMAR DATA MIGRATION ENABLER OVERVIEW . 11The data migration process . 11Avamar system and client plug-in support with ADMe . 11CAPABILITIES AND LIMITATIONS . 12Capabilities . 12Limitations . 12ARCHITECTURAL OVERVIEW . 13DATA MIGRATION METHODS . 13Rehydration method . 13PAX Archive Method. 16ADME ADMINISTRATION WEB-UI . 17ADME CLI INTERACTIVE MENU UI . 17CHAPTER 2 . 18INSTALLING AND GETTING STARTED WITH ADME . 18INSTALLING THE ADME SOFTWARE . 19Installation Procedure . 19GETTING STARTED WITH ADME . 21Environment files . 21Client group definitions . 21Job policy definitions . 21Configuration workflow. 22CHAPTER 3 . 23CONFIGURING AND USING THE ADME SOFTWARE . 23LAUNCHING THE ADME WEB-UI . 24Web-UI Service Status . 24CONFIGURING ENVIRONMENT FILES . 24Creating Environment Files . 24Editing Environment Files . 26Deleting Environment Files . 26Viewing Environment Files Summary Report . 26CLIENT GROUP CONFIGURATION . 27Client Group Naming Convention. 27Client Group Limitations . 27Creating Client Groups . 28Adding clients to an existing client group . 30Deleting clients from a client group . 30Disabling clients in a client group . 30Deleting a client group . 31Calculating the aggregate size of a client group . 31CONFIGURING AND USING JOB POLICIES . 31Creating Standard job policies . 31Editing standard job policies . 35
Creating Batch job policies . 36Starting job policies on demand. 36Scheduling job policies . 37Removing job schedules . 38Modifying job schedules . 38RECOVERY PROCEDURES. 42APPENDIX-A . 46CONFIGURING TAPE APPLICATIONS . 46SUPPORTED EXPORT APPLICATIONS . 47AUTO-SCHEDULING DIRECTLY FROM NETWORKER . 48APPENDIX-B . 51STRUCTURED STAGING PATHS. 51STRUCTURED STAGING PATHS . 52APPENDIX-C . 54ADME COMMAND LINE INTERACTIVE MENU SYSTEM . 54ADME CLI INTERACTIVE MENU SYSTEM . 55APPENDIX-D . 57ENVIRONMENT FILE & CLIENT CONFIGURATION . 57FILE DEFINITIONS. 57ENVIRONMENT FILE CONTENTS . 58APPENDIX-E . 69COMMAND LINE INTERFACE SYNTAX . 69ADME COMMAND LINE OPTIONS . 70ADME SYNTAX . 70APPENDIX-F . 82NETWORKER POLICY SETUP WITH ADME. 82NetWorker backup commands. 80 . 82Using the save command . . . 82 . 82Using the savefs command . 82 . 82Using nsrworkflow command . 84 . 82Server initiated limitations. 88 . 82Conclusion. 89 . 82NETWORKER BACKUP COMMANDS . 83Using the save command . 84Using the savefs command . 84Using nsrworkflow command . 86SERVER INITIATED LIMITATIONS . 90CONCLUSION . 91APPENDIX-G . 92TROUBLESHOOTING AND BEST PRACTICES . 92TROUBLESHOOTING & BEST PRACTICE . 93APPENDIX-H . 98ADME ERROR/WARNING/INFO MESSAGES . 98ADME INFORMATIONAL MESSAGES. ERROR! BOOKMARK NOT DEFINED.ADME WARNING MESSAGES . 102ADME ERROR MESSAGES . 104
TABLES1234Revision history. 7Typographical conventions.8Environment file attributes and descriptions.62NetWorker backup commands and their corresponding ADMe arguments. 84
PREFACEAs part of an effort to improve the product lines, revisions of the software and hardware areperiodically released. Therefore, some functions that are described in this document mightnot be supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.Contact the technical support professional when a product does not function correctly ordoes not function as described in this document.NoteThis document was accurate at publication time. To find the latest version of this document,go to Online Support (https://support.EMC.com).PurposeThis guide describes how to use the Avamar Data Migration Enabler (ADMe).AudienceThe information in this guide is primarily intended for system administrators who areresponsible for maintaining servers and clients on a network, as well as operators whomonitor daily backups and storage devices.Revision historyThe following table presents the revision history of this document.Table 1 Revision historyRevisionDateDescription01January 30, 2018GA release of Avamar 7.5.102April 9, 2021Not tied to any Avamar release03June 23, 2021Not tied to any Avamar releaseRelated documentationThe following publications provide additional information: Avamar Compatibility and Interoperability Matrix Avamar ReleaseNotes All Avamar client and plug-in user guidesSpecial notice conventions used in this document Theseconventions are used for special notices.DANGERIndicates a hazardous situation which, if not avoided, results in death or serious injury.WARNINGIndicates a hazardous situation which, if not avoided, could result in death or seriousinjury.
CAUTIONIndicates a hazardous situation which, if not avoided, could result in minor or moderateinjury.NOTICEAddresses practices that are not related to personal injury.NotePresents information that is important, but not hazard-related.Typographical conventionsThese type style conventions are used in this document.Table 2 Typographical conventionsBoldUsed for names of interface elements, such as names of windows, dialogboxes, buttons, fields, tab names, key names, and menu paths (what theuser specifically selects or clicks)ItalicUsed for full titles of publications that are referenced in textMonospaceUsed for: System codeSystem output, such as an error message or scriptPathnames, filenames, prompts, and syntax Commands andoptions Monospace italicUsed for variablesMonospace boldUsed for user input[]Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means “or”{}Braces enclose content that the user must specify, such as x or y or z.Ellipses indicate nonessential information that is omitted from theexamplePREFACEWhere to get helpThe Avamar support page provides access to licensing information, product documentation,advisories, and downloads, as well as how-to and troubleshooting information. Thisinformation may resolve a product issue before contacting Customer Support.To access the Avamar support page:1. Go to https://support.DELL.com/products
2. Type a product name in the Find a Product by Name box.3. Select the product from the list that appears.4. Click the arrow next to the Find a Product by Name box.5. (Optional) Add the product to the My Products list by clicking Add to My Saved Productsin the upper right corner of the Support by Product page.DocumentationThe Avamar product documentation provides a comprehensive set of feature overview,operational task, and technical reference information. To supplement the information inproduct administration and user guides, review the following documents: Release notes provide an overview of new features and known limitations for a release. Technical notes provide technical details about specific product features, including stepby-step tasks, where necessary. White papers provide an in-depth technical perspective of a product or products asapplied to critical business issues or requirements.KnowledgebaseThe Knowledgebase contains applicable solutions that you can search for either by solutionnumber (for example, esgxxxxxx) or by keyword.To search the Knowledgebase:1. Click Search at the top of the page.2. Type either the solution number or keywords in the search box.3. (Optional) Limit the search to specific products by typing a product name in the Scope byproduct box and then selecting the product from the list that appears.4. Select Knowledgebase from the Scope by resource list.5. (Optional) Specify advanced options by clicking Advanced options and specifying valuesin the available fields.6. Click Search.Online communitiesGo to Community Network at http://community.dell.com/community for peer contacts,conversations, and content on product support and solutions. Interactively engage onlinewith customers, partners, and certified professionals for all products.Live chatTo engage Customer Support by using live interactive chat, click Join Live Chat on the ServiceCenter panel of the Avamar support page.Service RequestsFor in-depth help from Customer Support, submit a service request by clicking Create ServiceRequests on the Service Center panel of the Avamar support page.
NoteTo open a service request, you must have a valid support agreement. Contact a salesrepresentative for details about obtaining a valid support agreement or with questionsabout an account.To review an open service request, click the Service Center link on the Service Centerpanel, and then click View and manage service requests.Enhancing supportIt is recommended to enable ConnectEMC and Email Home on all Avamar systems: ConnectEMC automatically generates service requests for high priority events. Email Home sends configuration, capacity, and general system information to CustomerSupport.Comments and suggestionsComments and suggestions help to continue to improve the accuracy, organization, andoverall quality of the user publications. Send comments and suggestions about thisdocument to DPAD.Doc.Feedback@dell.com.Please include the following information: Product name and version Document name, part number, and revision (for example,01) Page numbers Other details to help address documentation issues
CHAPTER 1ADMe IntroductionAvamar Data Migration Enabler overview. 99
Capabilities and limitations.10Architectural Overview.11Data migration methods.11ADMe Administration Web-UI.15ADMe CLI interactive menu UI.1510
Avamar Data Migration Enabler overviewAvamar Data Migration Enabler (ADMe) is a software tool used to migrate Avamar backupdata to a different storage medium, such as tape, cloud storage, a target Avamar with differentstorage type or stand alone hard drives such as external USB or NAS units.ADMe relies on simple concepts whereby selected backup data gets rehydrated to a server,where it can be staged to various disk storage types then optionally exported to tape from thestaging area using a standard tape backup product such as NetWorker. Recovery of migratedfiles can be retrieved from the storage used or restored from tape via the tape backupapplication's native recovery tools.The data migration processADMe automates the migration process via user-defined migration policies. They control thebackup selection process then perform a redirected recovery of them from Avamar to astructured directory tree on the defined staging disk area.Optionally, export to a tape backup application can be automatically invoked against apredefined tape policy within the tape backup application. Once the staged data is written totape, the tape backup application is responsible for assigning appropriate retention periodsand catalog mechanism to allow for browsable file-level recoveries. Tape recoveries can bedirected to the ADMe staging server or any compatible client available to the tape backupapplication.Using this same migration approach, ADMe can also be used to export the staged Avamarbackups to another Avamar system which uses Data Domain for its back-end storage. Thisallows backups stored in Avamar GSAN-based storage node to be migrated to a targetAvamar/Data Domain system. The resulting migrations are browsable using the target Avamarrecovery browser to perform file level recoveries.If the Avamar backups are staged to cloud based or object storage, data will be in a rehydratedformat which can be recovered using the cloud storage provider's UI mechanisms. If the cloudenabled storage is accessed through a gateway which supports data deduplication, therehydrated data can be stored in deduplicated format in the cloud.Avamar system and client plug-in support with ADMeADMe supports all Avamar system types including single or multi-node systems, AvamarVirtual Edition, replication sources and targets, IDPA and Avamar with Data Domain.ADMe migration software supports the following features: Avamar filesystem plug-in on all supported filesystems Avamar plug-ins for virtual machines in both VMware and Hyper-V environments NDMP plug-in Supported database application plug-ins such as the Microsoft Exchange, SQL andOracle plug-insAn Avamar PAX archival format is available allowing the migrated data to be stored in a nativeAvamar format which must be re-imported to an Avamar GSAN storage afterwards to make itusable. There are several limitations on the use of the Avamar archival format; Limitations ofthe PAX archive method on page 16 addresses these limitations.While different tape backup applications can be used with the ADMe workflow, onlyNetworker provides the full chain-of-custody details associated with an end-to-end migration.11
Capabilities and limitationsThe following capabilities and limitations apply to the ADMe migration tool:Capabilities Enables exporting Avamar backup data to tape or cloud storage for long-term retention,lowering overall cost of the storage consumed within Avamar directly. Creates transportable media such as tape or standalone USB or NAS hard drives foroffsite storage. Leverages existing tape backup application functionality and associated infrastructure. A variety of compatible servers and operating systems can be used as staging servers. Supports multiple export use cases at the same time, for example, to tape and cloudstorage. Single point of management for Avamar data migration. No dependencies on Avamar or ADMe when recovering from tape or cloud, with theexpectation of Oracle and PAX file archives where Avamar would be required. Tape backups can be cataloged and browsable for file-level recovery. Supports migrating backups to public or private cloud storage. Supports multiple staging servers concurrently, including more than one thread perstaging server if configured. Supports all Avamar system types. Provides a web-based graphical interface, as well as a CLI based menu driven interface. Provides email notifications for significant migration activity. Event and job policy logs capture status of all significant migration activity. Provides non-incremental and incremental staging strategies. Supports most Avamar plug-in types. Provides a wide choice of backup selection filters for automatically selecting backups formigration. Provides an audit mechanism for tracking critical path components and chain-of-custody. Able to migrate GSAN/Hybrid/DD based backups from one Avamar system to anotherAvamar server using Data Domain as the target system backend storage, ensuringmigrated backups are stored on the Data Domain.LimitationsConsider the following ADMe limitations: Migrations can take a significant amount of time depending on the data size and filecounts involved; therefore, while your backup software may perform frequentbackups (such as daily), it is not practical to migrate daily backups with ADMe. When exporting migrated backups to physical tape, a robotic tape library is required aspart of the tape backup application infrastructure. When migrating backups to cloud storage, the upload bandwidth and latency to thecloud provider directly impacts the migration throughput. ADMe offers limited benefit in reducing Avamar capacity therefore should not be reliedon or used for this purpose.
ADMe automates the migration process via user-defined migration policies. They control the backup selection process then perform a redirected recovery of them from Avamar to a structured directory tree on the defined staging disk area. Optionally, export to a tape backup application can be automatically invoked against a
