1 / 11

Use Case: Automated Snapshot Archiving using APIs

Use Case: Automated Snapshot Archiving using APIs. Jonathan Tourtellot Enterprise Infrastructure Architect. Agenda. The Customer Environment The Problem The Solution Script Demonstration / Questions. Customer Environment. Virtualized heterogeneous SAP environment

herman
Download Presentation

Use Case: Automated Snapshot Archiving using APIs

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. Use Case: Automated Snapshot Archiving using APIs Jonathan Tourtellot Enterprise Infrastructure Architect

  2. Agenda • The Customer Environment • The Problem • The Solution • Script Demonstration / Questions

  3. Customer Environment • Virtualized heterogeneous SAP environment • MetroCluster primary storage • Single-controller SnapVault destination • ~100 Linux and Windows virtualized OSes running Oracle database and SAP applications • Fibre Channel RDMs and Datastores

  4. Backup Requirements • Three backup types in environment • SMSAP Snapshots for SAP/Oracle databases, integration with backint • Linux and Windows VMs • VSC Snapshots for virtual machines • File system Snapshots for SAP-related NFS/CIFS volumes • All backups must be SnapVaulted • Due to size of environment, a centralized SnapVault monitoring/scheduling system is a must.

  5. The Problem • No SnapVault integration under Windows with Protection Manager • How to trigger SMSAP SnapVault relationships under Windows? • How to provide for a common SnapVault management interface?

  6. The Solution • NetApp Manageability SDK to the rescue! • Through heavy reuse of the perl code examples provided by the NetApp Manageability SDK, I was able to write, test, and implement a SnapVault control script to manage the entire replication environment in less than a week.

  7. Overview • A perl script, run from cron, that parses the config file and acts like a „protection manager lite“ to manage the SnapVault relationships • Central management • Logfile-based reporting

  8. Overview of the Config File concurrent=1 # throttle to limit the number of concurrent snapvault # updates archivename=sv_test # „snapvault snap sched“ to use on the destination user=scriptuser # For the API calls we need a user and password password=password # on the filers debug=yes # If yes, write out debug logs logpath=/home/user # Where to write the logfile logfile=log.out filer02-stor --> filer02 # Map between interface names and hostname snapsearchstring=smsap_ # The most recent source Snapshot name containing this string will be used tor the update. (optional) # The following lines, copied from „snapvault status“ define the relationships 10.68.9.230:/vol/sv_test_01/- filer02-stor:/vol/test_dest2/01 10.68.9.230:/vol/sv_test_02/- filer02-stor:/vol/test_dest2/02

  9. Demo / Q & A

More Related