This is part 2 of a three-part conversation with Dr. Xin Wang, product manager for IBM Tivoli Storage Manager (TSM). In part 1, Xin discussed what she has learned about the challenges IT managers are facing leading to the backup redesign movement. Let’s continue the conversation:
The Line: So, first you mentioned that data is so big the old style of backup can’t keep up.
Xin: That’s right. For a long time, the primary method of capturing copies of data was to load a backup agent on a server, grab the copy and transfer it across some kind of network to a backup server for safe keeping. But data is getting too big for that. So today, we are helping clients redesign with a tool we call IBM Tivoli Storage FlashCopy Manager (FCM). The point of FCM is to bridge between the application that owns the data and the storage system that is housing the data so that IT managers can simply make snapshots where the data lives.
The Line: That may be new to some clients, but it seems things like FCM have been around for a while. What’s new?
Xin: You’re right. Snapshots have been around for a while and so has FCM. But the economic driver for redesigning backup environments so they use snapshots hasn’t been as strong as it is today.
The Line: Okay. How about the technical side? Snapshots are done differently on different storage devices. What storage infrastructures does FCM work with?
Xin: A lot is being made about the benefits of software defining your storage environment. One of the many benefits of that approach is that there is only one interface for snapshotting regardless of your choice in physical disk hardware. Move a workload from one kind of array to another, or even change vendors altogether, and your snapshot interface still stays the same. So:
- If an IT manager has chosen software-defined storage with IBM SmartCloud Virtual Storage Center then they can use FCM with pretty much any physical disk array they like.
If an IT manager chooses to continue working with native physical hardware, the support list is more specific.
- For applications running on Windows, FCM still supports most any physical disk.
- For applications running on Linux or Unix, FCM works with IBM and NetApp disk arrays.
- Soon we plan to offer an open application programming interface (API) that will enable plugins for other physical disk arrays from vendors like EMC and Hitachi.
The Line: Nice! So let’s move to your second point, that VMware is causing IT managers to redesign their backup environment.
Xin: VMware has caused IT managers to redesign a lot of things. So much so that a lot of IT managers I talk with have had to prioritize. In many cases, backup redesign has been one of those things that has been put off until now.
The Line: What do you mean “until now”?
Xin: Again, it’s about economics. The number of workloads and amount of data in these VMware estates is reaching critical mass. IT managers who have plodded along simply loading a backup agent in each guest machine are feeling pain. We are helping IT managers redesign with a tool custom built for VMware— IBM TSM for Virtual Environments (TSM for VE). TSM for VE is already nicely integrated with the VMware API for Data Protection (VADP), meaning its full set of snapshot features is available to IT managers without deploying agents in every VM guest. Soon we plan to add some new and really powerful integration.
- When restoring a virtual machine, the virtual machine disk (VMDK) will be instantly available for access the moment the restore starts. Verification can start right away, with no waiting around for data to be moved anywhere.
- There’s new integration with the vCloud API to back up, manage and recover a vApp in vCloud Director.
- When running workloads like Microsoft SQL Server or Exchange on VMware, there can be object or item level recovery without the need for an agent to back up the application VM.
- There’s a richer set of administrative and reporting capabilities in the vCenter plug-in.
- For FCM users, there is instant recovery of an entire VMware data store and coexistence with VMware Site Recovery Manager (SRM).
Check back soon for part 3 of the interview in which Xin finishes sharing her near term plans for TSM and adds some closing thoughts. If you have questions for Xin, please join the conversation by leaving a comment below.