spectrum protect tivoli storage manager 7.1.2 technical introduction tricia jiang hardware snapshot...

Spectrum ProtectTivoli Storage Manager 7.1.2 Technical IntroductionTricia Jiang

Hardware Snapshot Protect for Spectrum ProtectFlashCopy Manager 4.1.2 Technical IntroductionCyrus Niltchian April 2015

© 2015 IBM Corporation2

Tivoli Storage Manager 7.1.2 Announce 4/14 eGA 4/17/15

TSM Client: Client - Ubuntu support on Intel x86 (API Support)

TDP for Vmware: Client - DP for VMware - vSphere 6 support DP for VMware - Enhanced snapshot management (snapshot retry) DP for VMware – Better integration with VMware Site Recovery Manager (SRM) Client - DP for VMware - Database-level recovery and IMR from virtual machines hosting Microsoft Exchange

HSM for Windows: Alternate Data Stream Support

Flashcopy Manager: TSM SUR Front End - addition of FCM to the bundle FCM GPFS File System support (GA) FCM 3PAR adaptor (Rocket) FCM for VMware - vSphere 6.0 (Toleration) FCM Config wizard 3rd party adapters FCM Exchange & FCM for Windows; various usability & performance enhancement FCM MR Exchange archive mailboxes & Exchange public folders


Continuous Delivery Model

As we join the IBM Spectrum Storage™ family, the Tivoli Storage Manager family (which includes Tivoli Storage FlashCopy Manager) is becoming more agile without losing what we are known for: our quality and stability.

Starting with TSM 7.1 and FCM 4.1, we will be delivering both new functions and maintenance updates in our fix pack deliverables for the current release. The maintenance approach for prior releases remains unaffected.

What you can expect going forward: - Predictable maintenance cycles - Timely enhancements, targeted to occur up to once per quarter - Frequent communication and feedback requests to help us drive innovation

http://www-01.ibm.com/support/docview.wss?uid=swg21700499

http://www-03.ibm.com/systems/storage/spectrum/

https://www.ibm.com/developerworks/rfe

https://www-304.ibm.com/software/support/trial/cst/forms/nomination.wss?id=6048

https://www-304.ibm.com/software/support/trial/cst/forms/nomination.wss?id=6048


7.1.1.x TSM server + 7.1.2 TSM client

TSM server component is not updated in this release

The release is called TSM SUR 7.1.2 - The TSM client is updated to 7.1.2- The TSM server component is 7.1.1.x

• The server will be updated in the next release

Make sure there isn't confusion with business partners or customers thinking they experienced a failed install when the server version remains at 7.1.1.x


Tivoli Storage Manager 7.1.2 Announce 4/14 eGA 4/17/15TSM Client: Client - Ubuntu support on Intel x86 (API Support)

TDP for Vmware: DP for VMware - Enhanced snapshot management (snapshot retry) DP for VMware – Better integration with VMware Site Recovery Manager (SRM) Client - DP for VMware - vSphere 6 support Client - DP for VMware - Database-level recovery and IMR from virtual machines hosting Microsoft Exchange


Flashcopy Manager: TSM SUR Front End - addition of FCM to the bundle FCM - GPFS File System support (GA) FCM - 3PAR adaptor (Rocket) FCM for VMware - vSphere 6.0 (Toleration) FCM - Config wizard 3rd party adapters FCM Exchange & FCM for Windows; various usability & performance enhancement FCM MR Exchange archive mailboxes & Exchange public folders


Ubuntu support on Intel x86: TSM B/A & API Support Ubuntu is an open source, Linux, software platform

- Runs everywhere from smartphones, tablets and PCs, to the server and the cloud

The TSM API client and TSM Backup Archive client will be supported on Ubuntu Supported Ubuntu version: 14.04 x86_64 Supported API client function: equal to other x86_64 platforms Supported Backup Archive client function: equal to other x86_64 platforms Not Supported:

Ubuntu GPFS Snapshot image LAN-free data movement Any functions currently not offered in the Linux package

• JBB, file-level snapshot support, etc

TSM client is available in debian packaging format GSKIT: gskcrypt64_8.0-50.40.linux.x86_64.deb; gskssl64_8.0-50.40.linux.x86_64.deb API: tivsm-api64.amd64.deb; tivsm-apicit.amd64.deb BA: tivsm-ba.amd64.deb; tivsm-bacit.amd64.deb; tivsm-bahdw.amd64.deb; tivsm-jbb.amd64.deb



TSM Client: Client - Ubuntu support on Intel x86 (API SUpport)

TSM for VE Client - DP for VMware - vSphere 6 support DP for VMware - Enhanced snapshot management (snapshot retry) DP for VMware – Better integration with VMware Site Recovery Manager (SRM) Client - DP for VMware - Database-level recovery and IMR from virtual machines hosting Microsoft Exchange




• TSM 7.1.2 supported vSphere levels (7.1.2 added in green)

– Vsphere 5.1, 5.5, 6.0

• TSM 7.1.1 dropped support for vSphere 5.0

• TSM 7.1.2 Data Mover supported platforms (7.1.2 added in green, 7.1.2 dropped in red)

– Windows Server 2008 R2

• TSM 7.1.1 dropped support for Windows 2008

– Windows Server 2012, 2012 R2

– RHEL 5.9, 6.2, 6.3, 6.4, 6.6, 7.0

– SLES 11.2, 11.3, 12 See TSM VE Hardware and Software technote for the official support list

• Note: All TSM for VE components need to be upgraded to the same fixpack level– All components at 7.1.2.x would include the VE GUI, Recovery Agent, and Data Mover (which include TSM APIs)– TSM for VE integrated install on Windows will upgrade all of these components together

• Note: Data Movers BELOW v7.1.2, will not be able to perform a restore of a VM backed up with TSM 7.1.2

• TSM for VE: DP for VMware - vSphere 6 support


vVol (virtual volumes) TSM 7.1.2 currently does not support vVols

If a backup is attempted with a VM using a vVol datastore the backup will fail

ANS2713E The virtual machine 'vmname' is in an invalid connection state 'vvol_unsupported'. As a result, it cannot be backed up.

TSM for VE: DP for VMware – vSphere 6 vVol


• VMotion enables the live migration of running vms from one physical server to another • Zero downtime• Continuous service availability• Complete transaction integrity• Transparent to users

• Earlier versions of Vmware’s vSphere, vMotion• Required similar network configuration between ESXi hosts• Required the same vSwitch level• No vMotion between the vSphere distributed Switches, limited within the dvswitch• TSM for VE did support earlier version vMotion within the same vCenter

• VMware introduced Long Distance vMotion in vSphere 6.0 • vMotion is allowed across vSwitches, Virtual Data centers and vCenter Servers

• TSM for VE with long distance vMotion• Can affect virtual machine backups• If a VM is moved to another node, its backups will be covered by another TSM node • After the move a full backup will be needed

• Long Distance vMotion across vCenters will be documented in a technote

TSM for VE: DP for VMware – Long Distance vMotion


Small percentage (1 – 2% or more) of VMs previously failed to backup

Unable to take a VMware quiesced snapshot

Snapshot failure due to

Volume Copy Shadow Service (VSS) in guest interaction

High I/O load to datastore

New INCLUDE.VMSNAPSHOTATTEMPTS option

Application quiescing (VSS) and filesystem quiescing can be bypassed

Creates a 'crash-consistent' backup instead of no backup

Only applies when TSM VE is taking the VMware snapshot

Doesn’t apply to FCM VE or FCM VE offloads to TSM, when FCM supplies snapshot used by TSM

TSM for VE: Enhanced vSphere Snapshot Management


TSM for VE: Enhanced vSphere Snapshot Management Change in default behavior when INCLUDE.VMSNAPSHOTATTEMPTS is not specified

Previous TSM releases: One quiesced snapshot attempt

TSM 7.1.2: 2 quiesced snapshot attempts

0 non-quiesced snapshot attempts

New option to configure type and number of snapshot attempts

INCLUDE.VMSNAPSHOTATTEMPTS <vmname> <num_with_quiescing> <num_without_quiescing>

If 0 snapshots of both types specified then the option is invalid

If > 10 snapshots of one type is specified then the option is invalid

INCLUDE.VMSNAPSHOTATTEMPTS in Knowledge Center

Examples:

INCLUDE.VMSNAPSHOTATTEMPTS vmServer_Dept* 2 1 <--- 2 quiesced and 1 non-quiesced attempts

INCLUDE.VMSNAPSHOTATTEMPTS vmDB_Dept* 0 1 <--- 0 quiesced and 1 non-quiesced attempt

INCLUDE.VMSNAPSHOTATTEMPTS * 2 0 <--- default (2 quiesced and 0 non-quiesced attempts)

http://www-03preprod.ibm.com/support/knowledgecenter/SSGSG7_7.1.2/com.ibm.itsm.client.doc/r_opt_includevmsnapshotattempts.html

http://www-03preprod.ibm.com/support/knowledgecenter/SSGSG7_7.1.2/com.ibm.itsm.client.doc/r_opt_includevmsnapshotattempts.html


TSM for VE - DP for VMware Better Integration with VMware SRM VMware vCenter Site Recovery Manager (SRM) is a business continuity & disaster recovery solution that helps to plan,

test & run the recovery of VM between a protected vCenter Server site & a recovery vCenter Server site. • When a VM or template is added to a protection group, SRM creates a placeholder VM at the recovery site• Reserves a place for protected virtual machines in the inventory of the recovery site by creating a subset of VM files• SRM uses that subset of files as a placeholder to register a VM with vCenter Server on the recovery site • Placeholder in the recovery site inventory provides a visual indication to SRM admin that the VMs are protected

Previously: TSM for Ve would report a failure on every Site Recovery Manager (SRM) placeholder VM on a Recovery

site Could not obtain a snapshot even though backing up the source VM

Now: SRM Placeholder virtual machine- backup occuring on recovery site (new behavior)

• Located in the 'recovery site' with the fully functional vm at the 'primary site‘ which could be powered on or off• Virtual machine definition• No VMDKs and cannot be snapshoted

• Once the vm rolls over to the 'recovery site' it becomes a regular vm that TSM backups• TSM will identify as a 'placeholder' and skip this virtual machine

• SRM managed but protected vm is powered off – backup occuring on primary vCenter• Regular SRM protected vm, but it cannot be snapshoted because the snapshot task has been disabled• TSM backup will fail because the virtual machine cannot be snapshoted

• SRM managed and protected vm is powered on - backup occuring on primary vCenter• Regular virtual machine on primary vCenter that can be snapshoted• TSM backup supported


Example of SRM placeholder skipped in Recovery siteRecovery site Protected site

TSM for VE - DP for VMware Better integration with VMware SRM


Associates user-specific metadata information with virtual machines Requires the VM to be managed through vCenter The data is stored in the vCenter not with the virtual machine data Example: Custom Attribute called "Application Owner"

vSphere 6.0 Windows client can add/edit custom attributes vSphere CLI (Perl) vSphere PowerCLI (Powershell) Example: Set-CustomField -Entity (get-vm smallvm) -Name Location -Value

Austin

Backed up and restored by TSM 7.1.2 when the VMCHOST is set to a vCenter

Works with vSphere 6.0, vSphere 5.1 and 5.5

TSM for VE: VM Custom Attributes


TSM for VE– vSphere 6 New Attributes backed up

PCI Passthrough: VirtualPCIPassthrough

VMCI Device: VirtualMachineVMCIDevice

Graphics memory size: VirtualMachineVideoCard – graphicsMemorySizeinKB

Direct Path I/O: VirtualEthernetCard – uptCompatibilityEnabled

Message Bus Tunnel: VirtualMachineConfigSpec – messageBusTunnelEnabled

Raw Disk Mapping backing: VirtualDiskRawDiskMappingVer1BackingInfo


TSM for VE: DB-Level recovery & IMR from Microsoft Exchange

Previously, TSM for VE 7.1 with TDP for Exchange could do DB-Level and IMR restore- 2 step process: recovery agent mounts volume, then FCM reads data & can do IMR

Now, TSM for VE backing up Microsoft Exchange servers deployed in VMware ESXi vms can:- Restore individual Exchange Mailbox database from the vm backup- Recover Exchange user mailbox or mailbox-level items from the vm backup- Continue support of previously available options for db & user mailbox restore from vm backup

• Such as restore to alternate location, granular item level restore of user mailbox, etc- Stream line and EXPEDITE the Exchange DB and IMR restore process


Supported disk types (in guest vm hosting Exchange):

MS Exchange DB files must be on Windows disks of Type=“Basic” and Partition Style = “Master Boot Record (MBR)”

Disks of Type=“Dynamic” or Partition Style = “GUID Partition Table (GPT)” are NOT supported

ISCSI disks or Direct Storage attachment from any storage are NOT supported

Unsupported disks are skipped over during vm backup with this error: ANS2196W An incompatible disk configuration is detected for the following disk:

'Unknown disk E:\'. The individual database restore for the following database is

not supported:'Mailbox database 12345'\06c7fd00-622f-4575-a747-78a75fdde840'.

ANS2196W An incompatible disk configuration is detected for the following disk:

'Dynamic disk D:\'. The individual database restore for the following database is

not supported:'MyExchangeDB'\0454fd00-655f-4575-a747-234ddi556'.

Disk types supported for application protection


TSM for VE: DB-Level recovery & IMR Exchange – Install & Config

Install: On the data mover machine (Windows or Linux):

- TSM for VE 712 super installer - Install the Data Mover only option, which installs TSM for VE 712 automatically• Need tdp4vmw.lic license file for the backup function using ‘application protection

On the guest VM, hosting MS Exchange:- TSM for VE 712 super installer: Install Data Protection for VMware Instant Restore Only option, which automatically installs:

• TSM for VE Recovery Agent 712 – Need tdp4vmw.lic license file for invoking restore function• TSM B/A Client 712

- Install Data Protection for Exchange 412• Configure to TSM Server• Need excclient.lic license file –allows connection to TSM Server to obtain VM backups containing MS Exchange DB data

Configure: On the data mover machine:

• Add a virtual machine for application protection:1. Add to options file: include.vmtsmvss <vm_name>2. Setup VM guest connection: dsmc set password –type=vm vm_name vm_admin_ID vm_admin_pw 3. Run: dsmc backup vm vm_name -asnode=datacenter_node

On the guest VM :• Configure DP for Exchange using TSM Wizard, specify the datacenter node in the Nodes panel• Configure Recovery Agent cli to work with Recovery agent on guest vm• Run set access command on datamover machine that was used to do the backup


Microsoft Exchange Server – Database Restore from TDP

Now shows size


Microsoft Exchange Server – Individual Mailbox Restore (IMR)


Microsoft Exchange Server – Individual Item Restore


TSM Space Management (HSM on UNIX) Removing Admin GUI

Removing HSM Admin GUI from TSM for Space Management 7.1.2 package Deprecation and removal statement was published in TSM 7.1.1

Why removing GUI was only used to adjust the HSM file system management parameters GUI function had not been enhanced with new functions (CLI has) GUI had not changed since 5.3 GUI had no GPFS cluster integration GUI had no reporting or monitoring functions Our HSM customers use the CLI (dsmmigfs)

CLI is used by the HSM administrators (highly skilled Unix admins) CLI is needed and used for automation


HSM for Windows – Alternative Data Streams

Windows Alternate Data Streams (ADS) are also called Named Streams-Introduced into Windows NTFS FS starting in Windows NT 3.1 (1993)-Allows compatibility with the Macintosh Hierarchical File System (HFS)-Not solely used for MAC combatiblity

•Many applications use ADS to store information about the file in them•In Internet Explorer Favorites:

•When a Web site is added to 'Favorites‘, a .url file with the URL and description is created •If the Web site has an icon (favicon), the icon is saved as an ADS for the same URL file

MAC clients connecting to Windows servers are potential new HSM for Windows customers



Prior to 7.1.2 Alternate data streams were kept at the stub file in the file system (toleration support)

Problem:In a recovery situation ADS attached to a stub file are not fully protectedIf a stub is erroneously deleted from the fs, the ADS is lost

-The file has to be recovered either from the backup pool (stub restore)-Or the file has to be recovered from HSM archive

With 7.1.2 version:The protection for ADS is at the same level as for file security ACLs• ADS are recovered when a stub is restored from backup pool• Migrating ADS data together with file content data (PDS) to HSM archive is an optional feature of HSM• Retrieving ADS data together with file content data (PDS) from HSM archive is an optional feature of HSM



Install:• Un-install old version HSM for Windows client • Upgrade TSM Backup/Archive Client to version 7.1.2 • Install HSM for Windows client version 7.1.2• Restart the system

Configure with Wizard:- Default is ADS disabled

Can Exclude ADS for specific files, for instance might want to exclude zone identifiers

TSM Server Storage is used for ADS data

When ADS data are added or changed on a stub file, the next migration job will detect the changes and re-migrate the file



New Retrieve confirmation panels provide new options for ADS and overwrite data:



Case 1 : I don’t care about ADS data• Install new 7.1.2 HSM for Windows client• Configuring ADS option is not required

• Case 2: From now on I want to migrate ADS data to HSM archive• Install new 7.1.2 HSM for Windows client• Run the Configuration Wizard and set ADS option for migration to YES • Edit existing migration jobs and set ADS option for migration to YES• When creating new jobs ADS option for migration YES should be pre-selected• Edit Threshold Migration configuration for already configured volumes and set ADS option to YES• The ADS option for retrieval might be set to YES in the configurations wizard, or set as desired for the retrieve task

Case 3: I want all or part of the already stored files in HSM archive to be updated with the ADS data in the fs• Same tasks as CASE 2 • Re-run existing migration jobs to re-migrate stub files with ADS• Enough space resources and time have to be planned for this initial run depending on amount of stub files in file system• Limitation: Threshold Migration does not re-migrate stub files

© 2015 IBM Corporation

Efficiently protect and manage hybrid environments Efficiently protect and manage hybrid environments Next Generation Deduplication

Suite for Unified Recovery - Hardware snapshots

Hardware snapshots: Eliminates complex scripting and maximizes your hardware investment Application integration ensures consistency & recoverability Fully integrated Spectrum Protect solution

// Modernize data protectionIBM Spectrum Protect Suite for Unified Recovery

31


Fully integrated Spectrum Protect solution

Snapshots utilizing disk subsystems

Instant backup and restore capabilities

Application aware

Fast recovery of files, volumes and mailboxes

Instant restore for VMware datastores

Simplifies database cloning

Enables off-site copying

Leverage the power of hardware snapshots to modernize data protection

Note: Unix/Linux on non-IBM arrays require Rocket Adapter

Efficiently protect and manage hybrid environments Efficiently protect and manage hybrid environments// Modernize data protection

32

IBM Spectrum Protect Suite for Unified Recovery


Hardware Snapshot Addition

Hardware snapshots support is added to all TSM Suites

• Addition to the TSM Suites:- TSM Suite for Unified Recovery – Front End (TSM SUR-FE)- TSM Suite for Unified Recovery – Back End (TSM SUR) - TSM Suite for Unified Recovery Entry– Front End (TSM SURE-FE)- TSM Suite for Unified Recovery Entry– Back End (TSM SURE)

• One price (per TB) based on the size of the protected application/database now includes hardware snapshot support

- Front End: We license the capacity of the protected files/database/applications on the production servers on the source volumes- Back End: We license the capacity of the protected files/databases/applications including all snapshots on the target volumes plus all

versions in the TSM Server

• Addition is ‘retroactive’, therefore existing Suite customers can immediately deploy hardware snapshots.

• FCM Stand Alone and VSC entitlements will remain available and unchanged.

• FCM’s advanced hardware snapshot technology is now incorporated into the TSM Suites, therefore, FastBack is no longer needed as part of the TSM Suites and is withdrawn from all TSM Suites.

33

// Modernize data protection


Licensing Example Customer runs 1 MS SQL Server and 1 instance of Oracle on separate servers

on 2 attached arrays

MS SQL Server (500 GB in size) sits on 2 volumes (1 TB each) and the Oracle instance (3 TB in size) sits on 3 volumes (2 TB each)

Customer protects the Oracle database and the MS SQL Server database with 2 local snapshots each on disk

In case TSM is used, snapshots (full and uncompressed) are offloaded to TSM and 4 versions of both databases are kept in TSM

// Licensing for Hardware Snapshots

34


Scenario What is measured Capacity Required

FCM Stand Alone • Size of the source volumes protected (2 x 1 TB) + (3 x 2 TB) = 8 TB

TSM SUR-Front End

offloads snapshots into TSM

• Size of the database/application protected - size on source volumes

3 TB + 0.5 TB = 3.5 TB (≈4 TB)

3 TB size of Oracle0.5 TB size of MS SQL Server

does not offload snapshots into TSM

• Size of the database/application protected - size on source volumes

3 TB + 0.5 TB = 3.5 TB (≈4 TB)

3 TB size of Oracle0.5 TB size of MS SQL Server

TSM SUR-Back End

offloads snapshots into TSM

• Size of the database/application protected - size on source volumes multiplied by the number of snapshots in the array and - size of active/inactive objects in TSM Primary Storage Pools

(2 x 3.5 TB) + (4 x 3.5 TB) = 21 TB

2 local snapshots4 versions kept in TSM

does not offload snapshots into TSM

• Size of the database/application protected - size on source volumes multiplied by the number of snapshots in the array

2 x 3.5 TB = 7 TB

2 local snapshots

Table of Results // Licensing for Hardware Snapshots


Announcement of End of Marketing (June 2015) and End of Support

(April 2016) for the following FastBack products:

TSM FastBack – 5724-U93 TSM FastBack Center – 5724-V35 TSM FastBack for MS Exchange – 5724-U94 TSM FastBack for Bare Metal Recovery – 5724-U95 TSM FastBack for Storwize – 5639-FB1

For more information, see FAQ: https://w3-connections.ibm.com/files/app#/file/e0611ab1-a59d-47fd-bd66-8953eca27541

Note: FastBack for Workstations will continue being sold and supported.

FastBack // Transitioning Snapshot Technology

36

https://w3-connections.ibm.com/files/app

https://w3-connections.ibm.com/files/app


What Happens Now? Customer: “I Purchased FastBack Standalone.”

FastBack products that will get automatically migrated to Tivoli Storage Manager Entry product:- TSM FastBack- TSM FastBack Center- TSM FastBack for MS Exchange

TSM FastBack and TSM FastBack for MS Exchange migrate based on the PVU entitled amount. For each 420 PVU’s, customers will receive One TSM Entry license plus One additional TSM Entry license to account for TSM managing server.

TSM FastBack Center entitlement was on per managed server metric. TSM Entry is on the same metric. For each TSM FB Center entitlement, One TSM Entry license will be granted plus one TSM Entry license to account for TSM managing server.- For example, 1 Fastback center will convert to 2 TSM entry license, and 3 Fastback Center will convert to 4 TSM Entry

licenses.

FastBack // Transitioning Snapshot Technology

37


Leverage the power of hardware snapshots to modernize data protection

Efficiently protect and manage hybrid environments Efficiently protect and manage hybrid environments Next Generation Deduplication// Modernize data protection

Purpose-built administrative interfaces that tailor the experience to the needs of the persona or specialist that is using the interface

User experience for Exchange & SQL HW snapshots User experience for VMware HW snapshots

38

IBM Spectrum Protect Suite for Unified Recovery


Support for GPFS file systems

• Frequent, non-disruptive file set protection exploiting GPFS software snapshots (Spectrum Scale)

• Support for DB2 PureScale snapshots on GPFS (Spectrum Scale)• ‘Custom Application support’ for applications running on GPFS independent file sets

HP 3PAR support • Integrated application snapshot backup and restore capabilities on HP 3PAR storage arrays

Enhanced Configuration Wizard for VMware

• Configuration Wizard for VMware extended to automate connection to 3rd party storage arrays

VMware 6 • Hardware snapshots for VMware 6 environments (excluding VVOL support)

Restore archive mailboxes • Restore Exchange Server archive mailboxes (Also applies to DP for Mail)

Restore public folders • Restore Exchange Server public folders (Also applies to DP for Mail)

Hardware Snapshot enhancements

Efficiently protect and manage hybrid environments Efficiently protect and manage hybrid environments Next Generation Deduplication// Modernize data protectionIBM Spectrum ProtectHardware Snapshots

39


Thank You

spectrum protect tivoli storage manager 7.1.2 technical introduction tricia jiang hardware snapshot...

Documents

support dp

support client dp

vmware vsphere

client ubuntu support

vmware database

tsm sur

x tsm server

tsm ba api support ubuntu