This Content Component encountered an error
This Content Component encountered an error
This Content Component encountered an error

From disaster recovery to capacity optimization and dedupe, the next phase of VTLs promises major change.

When virtual tape libraries (VTLs) emerged several years ago, they improved how backup applications wrote data to disk. Tape-centric backup applications understood how to communicate with and manage tape devices, and then write data in tape format. VTL vendors that launched those initial solutions were focused mostly on developing the emulations for popular Fibre Channel (FC) tape libraries; proving compatibility with leading backup apps; ensuring that the VTL wasn't a single point of failure in the backup process; and figuring out how to get virtual tape copies easily offsite for disaster recovery (DR) purposes. VTL vendors masked any complexity by packaging their solution as a purpose-built appliance and partnering with disk vendors to deliver turnkey solutions.

Disk-based backup continues to evolve as adoption increases and new requirements are uncovered. Here's a snapshot of user adoption from Enterprise Strategy Group (ESG): Among organizations employing backup to disk, 32% use VTL technology. VTL adoption is greatest among enterprise-class organizations with more than 1,000 employees. Specifically, 45% of enterprise-class organizations surveyed have implemented VTL solutions and another 33% plan to implement the technology within 24 months vs. 21% of small- and medium-sized businesses that have implemented VTLs and 31% that plan to.

As VTLs have moved from early adopters to mainstream users, the stakes have changed. Ease of deployment and use, improved backup performance and reduced physical tape media management issues are basic requirements today. VTL vendors now need to accommodate the more advanced needs of mainstream users and adapt to the changing climate.


Climate change
There are a number of factors contributing to the changing VTL climate. First, the base technology is more mature. VTL vendors have been able to exercise their products in a variety of environments and collect valuable feedback from customers. Second, today's VTL buyer is better educated not only about VTL technology but their own data protection requirements. This next generation of VTL buyers (that's you) is more careful about vetting vendor claims. For example, what type of scalability is required to achieve advertised throughput estimates? And are deduplication ratios realistic?

Another angle is the advancement of backup solutions. Most, if not all, of the traditional backup vendors have embraced disk-to-disk (D2D) backup and a new crop of backup solutions built specifically for D2D backup has emerged. Today, backup vendors are keenly aware of user needs for addressing backup window problems with better backup performance, improving recovery time objectives with rapid recovery techniques, and reducing the capacity of data transferred and stored with capacity optimization technologies.

Because many of the newer backup solutions address these primary concerns, how have VTL vendors responded? It turns out they're introducing a crop of new features to win over the pragmatic buyer (you again), which is great news for IT organizations.

Gen2 VTL requirements
ESG surveyed VTL users about the types of features they would like to see in their current VTL solution. Data deduplication and improvements in VTL management topped the list, followed closely by improved scalability, and better recoverability and performance. Some users, struggling with methods for getting data offsite for DR purposes, prioritized DR features and support for physical tape on the VTL back end. Lastly, support for protocols--such as FICON and ESCON for mainframe support, and Ethernet for iSCSI support--rounded out the list.

These users are concerned with overall functionality. VTL vendors are beginning to factor this into their development roadmaps. For example, implementing replication between VTLs has become a standard feature for most solutions. VTL buyers are interested in how that capability maps to current processes and existing environments. Can the replication occur to more than one location? Is it possible to encrypt the data while in flight? Is scheduling (at off-peak times) or bandwidth throttling available? What techniques are offered to reduce the capacity of data transferred?

Here are some of the Gen2 features VTL users are interested in.

Capacity and performance scalability. The ability to scale storage capacity and performance are high-priority requirements that go hand in hand. Some early VTL solutions had design bottlenecks where the VTL architectures didn't fully take into account how backup applications work or what performance limits they would hit. Often, the existing backup processes or jobs would have to change just to take the pressure off VTL solutions. Gen2 VTLs must have the ability to seamlessly increase throughput performance as backup window pressure and recovery objectives dictate. The same holds true for capacity limits, and how easy it is to deploy additional disk capacity in the environment.


Capacity optimization. As organizations back up more workloads to disk and retain data on disk for longer periods of time, capacity optimization capabilities such as compression and data deduplication become more critical. Gen2 VTLs will need to have these features packaged in a way that addresses functional requirements. That includes deduplicating data across multiple VTL heads, turning deduplication off depending on the workload, and deduplicating data in real-time (inline processing) or batch mode (post-processing) to address performance concerns.

Central management. Organizations that have implemented multiple VTLs (due to scale limitations or by design) created an unexpected management issue: VTL sprawl. Central management of policies and a consolidated view of multiple VTLs can alleviate the management burden, and are important features in the next phase of VTL products.

DR. Another burden of adopting a D2D strategy is safeguarding data in the event of a local outage or disaster. Best practices call for a copy of backup media to be stored offsite. Those first VTL vendors either implemented a "tape export" command to generate a physical duplicate of a virtual tape or directly managed the physical tape library to create duplicate media outside of the backup window. Neither approach satisfied the requirement that the backup app maintain full knowledge and control of duplicates. The alternative was to initiate a virtual-to-physical tape copy through the backup app, which meant the backup application was burdened with additional processing and the data was dragged over the network unnecessarily. Gen2 VTLs are leveraging more efficient methods for creating physical media for offsite storage. Taking advantage of backup vendors' APIs, such as Symantec Veritas NetBackup's OpenStorage programming interface, allows VTLs to initiate duplication to tape or a secondary location, while ensuring that the media catalog is synchronized. DR preparedness is also being addressed via local-to-remote VTL-to-VTL replication. Gen2 VTLs take this basic feature a step further by allowing users the flexibility to decide which workloads require site-to-site replication; supporting multiple replication topologies, such as 1:1, and many-to-one ratios; as well as supporting bi-directional replication.

iSCSI support. Improvements in iSCSI performance, wider deployment of 10Gb Ethernet networks and increased support for iSCSI from storage vendors may drive more demand for Ethernet interface support. Users who want to leverage an IP SAN instead of, or in addition to, FC will look for VTLs that support iSCSI connectivity.

We know that organizations of all sizes are under pressure to have secondary data available and quickly accessible in downtime situations. Not doing so can be costly--if not devastating--to organizations. VTLs have emerged as a means to this end for a segment of the market. VTL vendors are responding to these challenges as evidenced by the excitement around their incorporation of data deduplication features. For users, it means scouting out vendors that are improving on these capabilities so you can be prepared to take advantage of the benefits being offered by the next generation of VTL products.

This was last published in September 2008
This Content Component encountered an error
This Content Component encountered an error
This Content Component encountered an error