Using IBM FlashCopy Manager 4.1 to Protect VMware Environments

FlashCopy for VMware Overview

What is IBM Tivoli Storage FlashCopy Manager? Course title What is IBM Tivoli Storage FlashCopy Manager? IBM Tivoli FlashCopy Manager (FCM) provides application-aware data protection using various snapshot technologies Three components: FlashCopy Manager for Windows FlashCopy Manager for UNIX FlashCopy Manager for VMware Can operate stand-alone or integrated with Tivoli Storage Manager (TSM) Snapshots stored locally on storage device (e.g. XIV, SVC, 3rd party) Snapshots stored on TSM (for longer term retention and redundancy) © Copyright IBM Corporation 2014

Local Snapshot Versions FCM Solution Overview FlashCopy Manager Snapshot backup to TSM server Transfer outboard of application server to minimize impact to application Copies on TSM server provide long-term retention and disaster recovery Very fast restore from the snapshot Support for multiple, persistent snapshots Persistent snapshots retained locally Policy-based management of local, persistent snapshots Retention policies may be different for local snapshots and copies on TSM server Automatic reuse of local snapshot storage as older snapshot versions expire Application Local Snapshot Versions Application Data Snapshot Backup Snapshot Restore IBM DB2 Oracle SAP MS-SQL MS-Exchange VMware Filesystems Custom Applications For Various Storage With Optional TSM Backup Integration SVC V7000 V5000 XIV DS8000 N-Series NetApp EMC* HDS* Other** * Via Rocket adapter or ** VSS Integration

FlashCopy Manager for VMware – Features at a glance Off-host (proxy based) hardware snapshot backups with VMFS datastore granularity Scheduled or ad-hoc execution No need to deploy OS specific agents to each VM Optional offloaded backup to TSM with VM granularity Supporting block level incremental forever backups with VMware Changed Block Tracking Instant restore of a VMFS datastore Restore of individual VMs from a) from a Hardware snapshot of a VMFS datastore b) from oflloaded TSM backup to original or alternative VMFS datastore under original name or new one Restore of individual files Mount of a backup to a guest VM for individual drive / files access Restore of individual virtual disk (vmdk files) Volume Restore using Recovery Agent User interface vCenter client integration (plug-in web GUI) Command Line Interface (on proxy node) Reporting and Monitoring summary view with drill down for details backup & restore stats Policy based management of local snapshot backups

FCM for VMware – Supported Storage Types Course title FCM for VMware – Supported Storage Types IBM Storwize V3700/V5000 VMware ESX / ESXi Server Virtual Machines NetApp IBM Storwize V7000 Unified VM VM VM FCM IBM XIV Spectrum Accelerate IBM Storwize V7000 Datastore 1 (vmfs) c.vmdk d.vmdk c.vmdk d.vmdk Datastore 2 (nfs) Hypervisor CPU Memory Network Internal Disk IBM DS8000 SAN / LAN IBM FlashSystem V9000 / A9000 FC SAN NAS iSCSI IBM SVC / Spectrum Virtualize Using Rocket Adapter: EMC VMAX, EMC VNX, EMC XtremeIO, HDS, HP 3PAR, Huawei OceanStor © Copyright IBM Corporation 2014

FlashCopy for VMware Installation

FlashCopy Manager for VMware 2 VMware ESX / ESXi Server Storage Hierarchy TSM Server (optional) 5 Virtual Machines VM Auxiliary ESX / ESXi Server 5 Virtual Machines VM VE FCM Hypervisor 1 vStorage Backup Server Common UI integrated with vCenter Client Auxiliary ESX Host for mounting datastore snapshots Supported Snapshot capable storage device Optional integration with Tivoli Storage Manager via TSM for VE VMDKs Hypervisor 3 Datastore Datastore Datastore Snapshot Backup Snapshot Restore 4 Local Snapshot Versions

FlashCopy Manager Proxy Host Requirements RedHat or SUSE Linux physical or virtualized proxy host FCM for VMware can be installed in coexistance with other software products If a VM is used, this VM must not be stored on a datastore being backed up by FlashCopy Manager Network connection (IPv4 or IPv6) to vCenter server No SAN attachment required

FlashCopy Manager for VMware Configuration Wizard The FCM configuration wizard is integrated into the existing FCM VMware Web GUI / vCenter GUI plug-in Similar to the VE config wizard Allows initial configuration and later re-configuration at any time Reduced complexity by focussing on essential parameters only to cover the majority of typical environments Including multiple DEVICE_CLASSes Including HOST_NAME_MAPPING configuration Including remote mirroring support Many parameters are not exposed with default values being applied

FlashCopy Manager for VMware – Configuration Wizard A configuration wizard: Creates and modifies profile file Creates and modifies password file Configures necessary daemons to start on boot Not all configuration aspects are covered by new GUI based wizard Design goal: Keep it simple, focus on major scenarios and environments For advanced configurations console based wizard is still needed: Generic / 3rd party storage adapter configuration Specify USE_FOR <device class names> clauses for HOST_NAME_MAPPING Edit advanced mode parameters (-advanced option)

FlashCopy for VMware Operation

Full-VM Backup with FlashCopy Manager leveraging vStorage APIs 1. FCM initiates a software snapshot of virtual guest volumes (vSphere API) VM1 C: D: Linux Proxy Server (physical or virtual machine) /a VM2 FlashCopy Manager SAN ESX\ESXi Server VMFS Snaps VM1 vmdk vmdk vmdk TSM Server SAN Storage Subsystem 12 12

Full-VM Backup with FlashCopy Manager leveraging vStorage APIs 1. FCM initiates a software snapshot of virtual guest volumes (vSphere API) VM1 C: D: Linux Proxy Server (physical or virtual machine) 2. FCMdetermines which LUN(s) are associated with virtual machines /a VM2 FlashCopy Manager SAN ESX\ESXi Server VMFS LUN 1 LUN 2 Snaps VM1 vmdk vmdk vmdk TSM Server SAN Storage Subsystem 13 13

Full-VM Backup with FlashCopy Manager leveraging vStorage APIs 1. FCM initiates a software snapshot of virtual guest volumes (vSphere API) VM1 C: D: Linux Proxy Server (physical or virtual machine) 2. FCMdetermines which LUN(s) are associated with virtual machines /a VM2 3. FCM invokes hardware copy services to create a persistent snapshot copy of the LUN(s) hosting the .vmdk and software snapshot FlashCopy Manager SAN ESX\ESXi Server VMFS LUN 1 LUN 2 Snaps VM1 vmdk vmdk vmdk LUN 2’ LUN 1’ Snaps VM1 vmdk vmdk vmdk TSM Server SAN Storage Subsystem 14 14

Full-VM Backup with FlashCopy Manager leveraging vStorage APIs 1. FCM initiates a software snapshot of virtual guest volumes (vSphere API) VM1 C: D: Linux Proxy Server (physical or virtual machine) 2. FCMdetermines which LUN(s) are associated with virtual machines /a VM2 3. FCM invokes hardware copy services to create a persistent snapshot copy of the LUN(s) hosting the .vmdk and software snapshot FlashCopy Manager SAN ESX\ESXi Server VMFS LUN 1 LUN 2 4. Hardware snapshot is persisted for use as source for recovery operation, software snapshots are deleted. Snaps VM1 vmdk vmdk vmdk LUN 2’ LUN 1’ Snaps VM1 vmdk vmdk vmdk TSM Server SAN Storage Subsystem 15 15

Full-VM Backup with FlashCopy Manager leveraging vStorage APIs 1. FCM initiates a software snapshot of virtual guest volumes (vSphere API) VM1 C: D: Linux Proxy Server (physical or virtual machine) 2. FCMdetermines which LUN(s) are associated with virtual machines /a VM2 3. FCM invokes hardware copy services to create a persistent snapshot copy of the LUN(s) hosting the .vmdk and software snapshot FlashCopy Manager (+ TSM for VE) SAN ESX\ESXi Server VMFS LUN 1 LUN 2 4. Hardware snapshot is persisted for use as source for recovery operation, software snapshots are deleted. vmdk vmdk vmdk LUN 2’ LUN 1’ 5. FCM optionally creates additional copy of data on TSM server (Objects saved in common data format to enable individual file recovery using Recovery Agent Mount) Snaps VM1 vmdk vmdk vmdk TSM Server SAN Storage Subsystem 16 16

FCM (datastore) level backup considerations Not all VMs on a datastore need to be “included” in a backup. Excluded VMs Will be bypassed for VMware snapshot Will not be available for VM or more granular restore actions VM migration via Storage vMotion during the FCM backup process can invalidate the backup. FCM detects this, marks the backup of the migrated VM as invalid and issues an appropriate warning message If a VM selected for backup has virtual disks on multiple datastores, all required datastores are automatically included in the backup VM templates can be included in the Backup VMs within a vSphere vApp can be included in the Backup

Best Practice: Use FCM together with TSM for VE Benefits of Using FCM for VMware with TSM for VE Short lifespan of VMware snapshots Fast access to VMDKs for granular recovery Parallel restore of VMDKs Preserve all VM attributes Offload all I/O for backup to TSM Unified GUI showing all backup versions Virtual Proxy Backup Server Dedicated physical machine to handle TSM for VE data movement to TSM (assuming LAN-free data transfer not needed) Serves as auxiliary server for FCM datastore mounts Additional VE datamovers can be deployed as VMs as needed

FCM for VMware backup modes Description Pro Con SNAPSHOT_EXCL_MEM (Default) FCM triggers a VMWare snapshot excluding working memory for each VM before the actual HW snapshot. Filesystem level consistency VM stays online continuously - Takes additional time for VMWare snapshots (but less than when incl. memory) - Reboot after restore SNAPSHOT_INCL_MEM FCM triggers a VMWare snapshot including working memory for each VM before the actual HW snapshot. Filesystem level consistency+ VM can be resumed after restore Takes additional time for VMWare snapshots Not possible for VMs with independent disks (e.g. pRDMs) SUSPEND FCM triggers a suspend for each VM before the actual HW snapshot. Takes additional time for suspending VMs VM is offline for a while ASIS FCM performs HW snapshot right away Fast, not dependent on number of VMs VMs stay online continuously Crash consistency only Reboot after restore

Raw Device Mapping (RDM) Support vRDM pRDM Toleration Mode Fully Supported FlashCopy Manager Tivoli Storage Manager For Virtual Environments

VMWare support for backup/restore of VMs with Raw Device Mappings Types of RDMs: - pRDMs (physical) and vRDMs (virtual) FCM’s Support: FCM supports both in toleration mode FCM‘s Toleration Mode: - Clear indication that the virtual disk was skipped inserted in the OVF configuration file and in saved Object Info Disk structure - Disks treated exactly as if the user had excluded these disks from the backup How to protect them: - FCM inside the VM can be used to protect RDMs Examples of Applications and Databases that may use RDMs: Oracle, Informix, SQL Server, MYSQL DB2 on Linux MS Exchange

Support for Backup/Restore of VMs with RDM Disks Handle raw disk mappings: pRDM and vRDM vRDM Backup Supported today, works just like a regular disk pRDM Backup Clear indication that the virtual disk was skipped inserted in the OVF configuration file and in saved Object Info Disk structure pRDM disks treated exactly as if the user had excluded these disks from the backup Use options -vmprocessvmwithindependent=yes & vmprocessvmwithprdm=yes FCM inside the VM can be used to protect pRDMs VM1 LUN1 VM1’s Virtual disk C: VMDK SAN Snaps VM1 LUN2 D: Storage Disk Subsystem

Restore scenarios

Instant Recovery of complete Datastore IBM PULSE 2012 4/15/2018 4/15/2018 1:40 PM Instant Recovery of complete Datastore Guest Machines Host Machines (ESX, ESXi) VMFS VMDK NAS/local FCM f or VMware SAN Datastore Datastore Copy FlashCopy Manager can revert an entire datastore(s) via a snapshot restore “FlashBack” operation No file level copy of VMs is being performed VMs will be registered to vCenter after restore operation is complete to be made available for use User can view and optionally select dependent datastores to be included in the restore operation An Instant restore is a hardware-assisted revert FlashCopy/Snapshot from a valid FCM FlashCopy/Snapshot backup of one or more VMWare VMFS/NAS datastores. Unlike the traditional VM / vmdk based restore, the instant restore reverts the whole datastore via a snapshot restore/FlashBack operation instead of copying the VMs on file level. Since the Snapshot/FlashCopy technology of the storage device is used for the instant restore, also big datastores can be restored in minutes. e customer will be able to do: The user will be able to select a datastore that he wants to instant restore. FCM will do a flashback/snapshot restore of that datastore and thus bring back the VMFS/NAS Datastore and all of the contained files representing VMs at the backup point in time. The virtual machines that were part of the backup are registered in the vCenter after this operation so that the customer is able to work with them right away. The user will be able to identify all registered VMs in the vSphere environment that are affected and overwritten by the instant restore operation (GUI enhancement) The user will be able to check the dependencies of VMs contained in this datastore to other datastores. There will be an indication that for specific VM's the instant restore of other datastores is required as well to restore them consistently The user will be able to decide which ones of the dependent datastores the user wants to restore. Also the user will be able to identify all VMs that will be affected by the resulting instant restore operation. The user will be able to decide if the VMs should be turned on after the instant restore. What the customer will be able to do run at items: The user will be able to use his existing FCM backup schedules, even when the datastoreurl has been changed by an instant restore of the datastore. FCM will reconfigure the VMCLI backup schedules of the instant restored Datastore, so that the backup schedules will work after the instant restore of a changed backup. In the "Implementation Details" section it is described when the datastore url is changed. The user will be able to choose if the VMs which are not selected for restore will be deleted from the datastore directly after the instant restore or if he wants to keep this VMs and register them later manually What the customer will NOT be able to do: The user will not be able to do anything partial with a datastore. The datastore and all VM files within the datastore are the finest level of granularity that can be provided for instant restore. However, the choice which VM of the restored datastore should be part of the instant restore post processing, like register VMs and power on VMs, could be done on VM level. Improved RTO for full-VM restore PULSE2012_Steve Mills_template 24

VM level restore from storage snapshots Admin selects VM to restore FCM powers down the VM to be restored (if it is running) and mounts (and initiates a resignature) of the datastore snapshot. VM attributes are restored as they were at time of backup. When complete, the virtual machine is ready to be returned to service and the datastore backup is dismounted. Optional Alternate ESX Host SAN

File-Level Recovery from Hardware Snapshots (FCM Attach) Admin selects vdisk backup containing files to be restored and specifies the VM to which it should be attached FCM mounts a datastore snapshot backup and attaches the virtual disk backup to the target VM The VM Administrator mounts the volume on the attached vdisk and copies files from the backup to the target file system. The administrator dismounts the volume within the VM and the virtual disk is detached from the VM. FCM will also dismount the DataStore backup from the ESX host. SAN

FlashCopy for VMware Remote Mirroring Overview

FCM for Unix/Vmware Global/Metro/Remote Mirror Snapshots 07/26/12 FCM for Unix/Vmware Global/Metro/Remote Mirror Snapshots FlashCopy Manager allows application consistent copies from target of a remote mirror relationship on SVC, Storwize V7000, XIV and some 3rd party devices. * Only required for restore at DR Site * Only required when offloading backups into TSM 28

Remote Mirroring Support – FCM for VMware Remote mirroring support for FlashCopy Manager for VMware Mirroring Capabilities: Schedule snapshot backups for mirrored VMFS datastores whereby those are created on secondary site but triggered from primary site Restore (file-based and instant) those snapshot backups on secondary site (initiated on secondary site after fail over) Attach the snapshot backup to an ESX host on secondary site (initiated on secondary site after fail over) Schedule new (local) snapshot backups on secondary site after a fail over Restore and attach locally created snapshot backups on secondary site after a fail over All scenarios presume an existing remote mirroring relationship established on storage level for the volumes comprising the concerned datastores NOTE: The remote mirroring relationship is neither created nor managed by FCM

Typical FlashCopy Manager Remote Mirroring Setup Dedicated installation of FCM on each site FCM repository and Derby DB are replicated between sites Gives DR site similar capabilities to what already exists at the primary site Backup can be used for restores on secondary site in DR scenarios Supports SVC, Storwize V7000 and XIV remote mirroring capabilities Support through Rocket Software for non-IBM storage

VMware vSphere Site Recovery Manager Coexistence VMWare Site Recovery Manager (SRM) provides remote data mirroring capabilities between primary (protected) and secondary (recovery) site FlashCopy Manager for VMware can provide a secondary means of protection at the primary site For data stores that are protected using array-based replication, FlashCopy Manager can also protect data stores at secondary site To ensure immediate availability in the event of a failover operation, install Tivoli Storage FlashCopy Manager for VMware on a virtual machine that is protected by VMware SRM

Questions?