Goal of this slide: Emphasize that storage deployed in virtualized environments needs to be robust.Points:Server virtualization indeed allows dramatic levels of server consolidation, often in the range of 10:1. This gets over the old “silo” of one app = one server.A storage failure in a server now takes down 10 applications, not just one. (need more reliable storage)A dual-disk failure (or more commonly, a failure with a media error on rebuild) means that data sets of 10 apps have to be reloaded, not just one. (need something better than RAID 5)With 10X more data on a server, may not be able to make the backup window. (need faster backup)In addition, with the ever-increasing criticality of IT operations, disaster recovery continues to increase in priority. DR is very difficult in a DAS environment, but becomes practical with virtualized servers and storage-based DR.While server virtualization enhances server provisioning greatly, the result is fast server and slow storage provisioning, unless other means of storage provisioning are brought into the picture.
Goal of this slide: Illustrate the sequence of backup operationsPoints:The virtual administrator requests a backup of VM1 and VM2 Virtual Center communicates with the appropriate ESX server which will place VM1 and VM2 in “Hot Backup” modeRedo-Logs get created by VMware for these VMs and the VMDKs are now frozen and all writes happen on the Redo-Logs for these Virtual Machines.SnapManager for VI can now initiate Data ONTAP Snapshots via the ONTAP APIs and the Snapshot of the entire datastore where these Virtual Machines reside is taken.Once the ONTAP Snapshot is completed, SnapManager for VI informs VC to take these VMs from the “Hot-Backup” mode and the Redo-Logs are applied to their corresponding VMDK(s) and normal operation resume
Goal of this slide: Illustrate the SnapManager for VI DR Operations, which begin with a normal backup operation.Points:The virtual administrator requests a backup of VM1 and VM2Virtual Center communicates with the appropriate ESX server which will place VM1 and VM2 in “Hot Backup” modeRedo-Logs get created by VMware for these VMs and the VMDKs are now frozen and all writes happen on the Redo-Logs for these Virtual Machines.SnapManager for VI can now inititate ONTAP Snapshots via the ONTAP APIs and the Snapshot of the entire datastore where these Virtual Machines reside is taken, and a mention is made in the menu that SnapMirror will get invoked once the backup is completedOnce the ONTAP Snapshot is completed, SnapManager for VI informs VC to take these VMs from the “Hot-Backup” mode and the Redo-Logs are applied to their corresponding VMDK(s) and normal operation resumeSnapMirror is triggered and the newly created Snapshots are sent to their target
Restore Agent (RA) on guest VM to browse disks containing files to be restored Enables guest OS to:Scan for new storage (attached disks)Mount disk(s) to active file systemEnables requester to:See list of all backups for the source VM¹Mount a disk (VMDK) from a backup to the guest VMCopy selected files to appropriate locations w/i active file systemInstalled once, but only active during restore sessionsSelf-service restoreRestored file(s) are from destination or alternate VM backupsRequester can browse all source VM backups, select files from any disks, and restore them to any location within active file systemLimited self-service restoreNo network connectivity between destination VM and SMVI serverAdmin mounts disks from selected source VM backups to destination VMRequester can browse all mounted disks, select files from any disks, and restore them to any location within active file systemAdministrator-assisted restoreCompany policy prohibits self-service restoreAdmin goes through the self-service restore process for the requester and places files to be restored in accessible locationRequester copies files to be restored from accessible location to any location within the active file system
Goal of this slide: Leave them with the possibilities that apply directly to an overall virtualization deployment and can be provided by NetApp storagePoints:Self-explanatory points, all of which are addressed earlier in the presentation.This slide should address both audiences: (1) the customer who is still using DAS storage and has not yet adopted network-based storage, as well as (2) the customer who has adopted (or will be purchasing) networked storage but does not yet understand the NetApp advantages.
SnapManager for Virtual Infrastructure 2.0 A Guide for Deploying a 2,000 Seat Heterogeneous Environment on NetApp 3100 and 6000 Series Storage Controllers
2 Virtualization Increases Storage Demands After Virtualizing Servers Before Virtualizing Servers* Number of applications per server Number of physical servers Number of apps down on storage failure Data lost on dual-disk failure Backup data volume Meeting backup window Disaster recovery Provisioning 1 10+ 1 1x 1x Feasible Costly/complex Slow/complex 10+ 1 10+ 10x 10x Maybe not More complex Storage ! = servers * Typical configuration: DAS, RAID 5, tape backup 2
3 Instantaneous, Storage-Efficient Backup The Problem Tape is slow, complex Streaming backups take too long Recoveries are slow Recovery points are limited NetApp Snapshot™ Solution Backups built-in to the storage Instantaneous backup and recovery Low storage overhead Frequent, application consistent CPU Utilization CPU Utilization Storage Pool Fast, Affordable, and Simple Backup and Restores Traditional Backup Is NOT Practical 3
The Value of SMVI 4 Addresses highly dynamic, resource-intensive virtual environments without impacting performance or introducing administrative complexity Simplifies data protection management Optimizes resource utilization Improves RTO and RPO Leverages NetApp’sSnapShot and SnapRestore technologies Scales with your virtual infrastructure
SMVI Backup Operation 8 VM4 VMDK VM1 VMDK VM2 VMDK VM3 VMDK VM1 / VM2 REDO.LOG Primary Site SMVI initiates a backup SMVI triggers VMware snapshots of VMs vCenter creates consistent snapshots of VMs and captures active transactions in delta files SMVI triggers instant NetApp Snapshot SMVI triggers VMware snapshot removal vCenter removes consistent snapshots and reapplies the delta files VirtualServer Admin vCenter SMVI API ONTAP APIs
SMVI DR Process 9 VM4 VMDK VM1 VMDK VM2 VMDK VM1 VMDK VM2 VMDK VM3 VMDK Primary Site DR Site (VMware Agents) VirtualServer Admin vCenter VM2 VM1 SMVI API ONTAP APIs Storage Pool DR uses the same process as Snapshot backups Snapshots are replicated efficiently to DR system in the background
SMVI Single File Recover (SFR) 10 Can restore one or more files from a VM without having to restore the entire VM Three Types of Restores: Self Service Limited Self Service Administrator Requirements: Data Ontap 7.2.3 SMVI 2.0 VMware ESX 3.5 or later Restore Agent (RA) is installed on a guest VM to browse disks containing files to be restored The RA enables the requester to: See a list of backups Mount a disk from a backup Copy selected files RA enables Guest OS to scan for new storage and mount disks to active file system 55GB