1 / 20

ADM(e) Avamar Data Migration Enabler

ADM(e) Avamar Data Migration Enabler is a tool that automates recoveries from Avamar, allowing for backup to tape or cloud storage. It supports various staging platforms, tape applications, and Avamar node types.

woodworth
Download Presentation

ADM(e) Avamar Data Migration Enabler

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ADM(e)Avamar Data Migration Enabler Adam Kirkpatrick – March 12, 2014

  2. ADM(e)Avamar Tape Out • ADM(e) is an enabler automating recoveries from Avamar for any plug-in type to a staging disk area • ADM(e) can optionally backup the staging area to tape or it can be Cloud enabled to a storage provider such as ATMOS or AWS-SG etc. • ADM(e) supports fully re-hydrated or streamed PAX file approach • ADM(e) supports full and incremental staging strategies as well as for tape backups or Cloud synchronization • ADM(e) supports all major tape applications in a consistent manner • ADM(e) rehydrated recoveries result in a fully cataloged tape backup providing file level recoveries directly from tape with no dependencies on Avamar • Cloud recoveries are file granular with no dependencies on Avamar and the structured folders maintained by ADM(e) make file location simple using a standard FS browser

  3. Support Matrix’s ADM(e) Support Matrix (Rehydrate mode) Supported Staging Platforms Windows, Red Hat, SCO, SuSE, FreeBSD, Solaris, AIX, HPUX, MAC Supported Avamar Plug-In’s File System, Lotus Notes, SQL, Exchange 2003 & 2007 with legacy API, Exchange VSS, SharePoint VSS, Hyper-V VSS, NDMP-Celerra, (NDMP-NetApp & Isilon Avamar 7.1+) VMimage, Oracle, (SAP) Supported Tape Applications Networker, NetBackup, Backup Exec, Backup Exec 2012, ArcServ, HP Data Protector, TSM, (CommVault) Supported Cloud Providers ATMOS-via Geo Drive, Amazon S3 + 15 other cloud providers via CloudBerry Drive available at http://www.cloudberrylab.com/amazon-cloud-storage-online-hard-drive.aspx Supported Avamar Node Types Single & Multi-Node, Source or Replication Target, AVE, Networker De-Dup, VDP1 & VDPA2, ABE VDP – stages directly to a user defined data-store mounted on the VDP appliance VDPA – stages to a Windows staging server or for Linux directly to a user defined data-store mounted on the VDPA appliance

  4. Support Matrix’s ADM(e) Support Matrix (Archive streamed-pax-file) Supported Staging Platforms Linux Supported Avamar Plug-In’s All plug-ins Supported Tape Applications Networker, NetBackup, Backup Exec,Backup Exec 2012, Arcserv, HP Data Protector, TSM, (CommVault) Supported Cloud Providers ATMOS-via GeoDrive Supported Avamar Node Types Single & Multi-Node, Source or Replication Target, AVE, VDP1 & VDPA2 VDP – stages directly to a user defined data-store mounted on the VDP appliance VDPA – stages to a Windows staging server or for Linux directly to a user defined data-store mounted on the VDPA appliance

  5. ADM(e) Key Features • Single Point of Management & Control • No dependency on Avamar when recovering from tape (except for Oracle or PAX file archives) • Seamless support for various staging platform types • Seamless support for and number of concurrent sessions per ADM(e) instance assuming sufficient infrastructure • Any Avamar system type supported • Easy to use fully interactive menu driven user interface • Automated tape backup initiation and monitoring for all the major tape backup applications • Structured email alerts, event and batch logs capture status of all significant activity • Supports incremental and non-incremental staging strategies which carry over to tape backup back-up or cloud synchronization • Supports all Avamar Plug-In types • Checkpoint recovery mechanism • Extensive array of filters available to limit and control backup selections • Audit mechanism tracks critical path components to tape or cloud ensuring accurate location of files

  6. User Interface • Fully Interactive • All Functionality Available • Color Coded Displays • Easy Access to Logs • Online Help • Automated Upgrade Process ATO Rocks!

  7. Client Configuration Manager • Avamar domain display • Drill down to view clients in each domain • Value in [ ] brackets = the client count • Display ADM(e) client groups • Client Configuration File parse check & view • Display All clients in a single view • Refresh option for rediscovery of domains & clients

  8. Client Configuration Manager • Status view of all Avamar clients • Color scheme indicates client configuration status relative to ADM(e) • Green=configured, Red=configured but disabled, Blue=not-configured

  9. ADM(e)Batch Manager Dashboard Log view showing last completion status for Job-id #2

  10. ADM(e)Batch Manager Job History Report

  11. ATMOS: Use Case for Extended Retention • Relies on ATMOS GeoDrive – a free utility from EMC • GeoDrive provides cloud access from a Windows drive letter or a Linux mount point • ADM(e) redirected recoveries from Avamar are directed to a Geo Drive but has no knowledge the destination is cloud enabled • Local staging disk space is consumed initially until the files are synchronized into the cloud • Once synchronized the staged files are converted to stub files and the majority of the space is reclaimed providing in effect an almost infinite staging area

  12. ATMOS: Use Case for Extended Retention • ADM(e) incremental staging does not result in a recall of the previously staged files as the stubs contain the necessary metrics required to determine whether a file must be overwritten or not • Cloud synchronization process is 100% under the control of ATMOS • Stub files do not need to be protected as they are protected within ATMOS itself • Loss of a GeoDrive has no impact, you simply reregister another drive from the same host or any other host using the same ATMOS credentials, stub files are then automatically made available to it • Users can access their assigned GeoDrive from any host with appropriate ATMOS credentials , the staging server does not own a Geo Drive’s contents • ATMOS provides different layers of user access control to contents stored on a GeoDrive based on the ATMOS account being used

  13. Staged Data Hierarchy • ADM(e) establishes a user defined top level folder structure crucial in multi tenancy environments for data segregation • Non-Incremental provides a dated/time folder representing the original Avamar backup time and its associated BUID# Destination staging path includes Avamar source client name involved • ADM(e) establishes a user defined top level folder(s) structure crucial in multi tenancy environments for data segregation • ADM(e) Incremental provides a consistent path name to a clients data and includes an ADM(e)-Incinfo status file containing details on what was staged and its recovery completion status

  14. ATMOS: Synced GeoDrive Folder Original Avamar source client name staged by ADM(e) User defined top level folder(s) • Sample of staged data on a GeoDrive • A synchronized file leaves behind a stub file shown with its original name, size & timestamp but displayed with an X over its icon • To recover a file double-click or copy/paste • To recover a folder(s) use copy/paste to a new location • ADM(e) is responsible for laying down the files only • ATMOS/Geo Drive is responsible for the cloud synchronization process

  15. ATMOS GeoDrive UI • ATO responsible for laying down the files only • Geo Drive is the gateway to the cloud • Geo Drive presence is transparent to Avamar and ADM(e) • Synchronization stats are visible during the synchronization process • A log is provided documenting any files which failed to upload • A given host can have multiple enabled Geo Drives using a common or different ATMOS accounts facilitating concurrency and data segregation in multi tenancy environments • ADM(e)/ATMOS process is fully automated requiring minimal human intervention • A Geo Drives contents are fully protected by ATMOS therefore requires no local protection whether it be RAID or the need backup/protect the stub files.

  16. ADM(e) Job Initiation • ADM(e) CRON interface * • External Scheduler • Networker GUI • Interactively • Command line

  17. 1. Initiate an ADM(e) batch job directly from Networker Management Console 3. Completion status & run times will be reflected in NMC & ADM(e) Dashboard. Detailed job log available from ADM(e) dashboard Initiation From Networker GUI 2. It’s corresponding batch job goes active reflected by the date stamp displayed in cyan/white

  18. ADM(e) Sizing Tool

  19. Collateral & Code Download EMC Internal – ADM(e) Homepage http://ca-center.lss.emc.com/imsg/ProductPages/ATO.html EMC Community Network – Doc & Download https://community.emc.com/docs/DOC-7910 OneEmc – Implementation Service Briefs and WBS documentation http://one.emc.com/clearspace/docs/DOC-27473 or

More Related