Jump to content

Virtual tape library: Difference between revisions

From Wikipedia, the free encyclopedia
Content deleted Content added
mNo edit summary
Importing Wikidata short description: "Data storage virtualization technology" (Shortdesc helper)
(16 intermediate revisions by 10 users not shown)
Line 1: Line 1:
{{Short description|Data storage virtualization technology}}
A '''virtual tape library''' ('''VTL''') is a [[computer storage|data storage]] [[Storage virtualization|virtualization]] technology used typically for backup and recovery purposes. A VTL presents a storage component (usually hard disk storage) as [[tape library|tape libraries]] or [[tape drive]]s for use with existing backup software.
A '''virtual tape library''' ('''VTL''') is a [[computer storage|data storage]] [[Storage virtualization|virtualization]] technology used typically for backup and recovery purposes. A VTL presents a storage component (usually hard disk storage) as [[tape library|tape libraries]] or [[tape drive]]s for use with existing backup software.


Line 7: Line 8:
The shift to VTL also eliminates streaming problems that often impair efficiency in tape drives as disk technology does not rely on streaming and can write effectively regardless of data transfer speeds.
The shift to VTL also eliminates streaming problems that often impair efficiency in tape drives as disk technology does not rely on streaming and can write effectively regardless of data transfer speeds.


By backing up data to disks instead of tapes, VTL often increases performance of both backup and recovery operations. Restore processes are found to be faster than backup regardless of implementations. In some cases, the data stored on the VTL's disk array is exported to other media, such as physical tapes, for [[disaster recovery]] purposes (scheme called ''disk-to-disk-to-tape'', or ''D2D2T'').<ref>{{cite web|url=https://www.starwindsoftware.com/feature-virtual-tape-library|title=D2D2T}}</ref>
By backing up data to disks instead of tapes, VTL often increases performance of both backup and recovery operations. Restore processes are found to be faster than backup regardless of implementations. In some cases, the data stored on the VTL's disk array is exported to other media, such as physical tapes, for [[disaster recovery]] purposes (scheme called ''disk-to-disk-to-tape'', or ''D2D2T'').


Alternatively, most contemporary backup software products introduced also direct usage of the [[file system]] storage (especially [[network-attached storage]], accessed through [[Network File System (protocol)|NFS]] and [[CIFS]] protocols over [[Internet Protocol|IP]] networks) not requiring a tape library emulation at all. They also often offer a [[disk staging]] feature: moving the data from disk to a physical tape for a long-term storage.
Alternatively, most contemporary backup software products introduced also direct usage of the [[file system]] storage (especially [[network-attached storage]], accessed through [[Network File System (protocol)|NFS]] and [[CIFS]] protocols over [[Internet Protocol|IP]] networks) not requiring a tape library emulation at all. They also often offer a [[disk staging]] feature: moving the data from disk to a physical tape for a long-term storage.
Line 14: Line 15:


==History==
==History==
The first VTL solution was an IBM Virtual Tape Server (VTS) introduced in 1997. It was targeted for a [[Mainframe computer|mainframe]] market, where many legacy applications tend to use a lot of very short tape volumes. It used [[ESCON]] interface, and acted as a disk cache for [[IBM 3494|3494]] tape library. A competitive offering from StorageTek (acquired in 2005 by SUN Microsystems, then subsequently by Oracle Corporation) was known as Virtual Storage Manager (VSM) which leveraged the market dominant STK Powderhorn library as a back store. Each product line has been enhanced to support larger disk buffer capacities, FICON, and more recently (c. 2010) "tapeless" disk-only environments.
The first VTL solution was introduced by Cybernetics in 1992 under the name HSTC (high speed tape cache).<ref>{{cite web|url=https://www.itjungle.com/2014/10/21/fhs102114-story03//|title=History of VTL/IBM}}</ref> Later, IBM released a Virtual Tape Server (VTS) introduced in 1997. It was targeted for a [[Mainframe computer|mainframe]] market, where many legacy applications tend to use a lot of very short tape volumes. It used the [[ESCON]] interface, and acted as a disk cache for the [[IBM 3494]] tape library. A competitive offering from StorageTek (acquired in 2005 by Sun Microsystems, then subsequently by Oracle Corporation) was known as Virtual Storage Manager (VSM) which leveraged the market dominant STK Powderhorn library as a back store. Each product line has been enhanced to support larger disk buffer capacities, FICON, and more recently (c. 2010) "tapeless" disk-only environments.


Other offerings in the mainframe space are also "tapeless". DLm has been developed by EMC Corporation, while [[Luminex Software, Inc.|Luminex]] has gained popularity and wide acceptance by teaming with Data Domain to provide the benefits of [[data deduplication]] behind its Channel Gateway platform. With the consequent reduction in off-site replication bandwidth afforded by deduplication, it is possible and practical for this form of virtual tape to reduce [[Recovery Point Objective]] /RPO and [[Recovery Time Objective]] /RTO to approaching zero (or instantaneous).
Other offerings in the mainframe space are also "tapeless". DLm has been developed by EMC Corporation, while [[Luminex Software, Inc.|Luminex]] has gained popularity and wide acceptance by teaming with Data Domain to provide the benefits of [[data deduplication]] behind its Channel Gateway platform. With the consequent reduction in off-site replication bandwidth afforded by deduplication, it is possible and practical for this form of virtual tape to reduce [[recovery point objective]] time and [[recovery time objective]] to near zero (or instantaneous).


Outside of [[Mainframe computer|mainframe]] environment, tape drives and libraries mostly featured [[SCSI]]. Likewise, VTLs were developed supporting popular SCSI transport protocols such as [[SCSI Parallel Interface|SPI]] (legacy systems), [[Fibre Channel]], and [[iSCSI]].
Outside of the [[Mainframe computer|mainframe]] environment, tape drives and libraries mostly featured [[SCSI]]. Likewise, VTLs were developed supporting popular SCSI transport protocols such as [[SCSI Parallel Interface|SPI]] (legacy systems), [[Fibre Channel]], and [[iSCSI]].


The [[FalconStor]] VTL is the foundation of nearly half of the products sold in the VTL market, according to an Enterprise Strategy Group analyst.<ref>{{cite web|url=http://www.infostor.com/index/articles/display/9694734941/s-articles/s-infostor/s-volume-13/s-issue_3/s-New_Analysis___Trends/s-VTLs__Going_beyond_data_de-dupe.html/|title=InfoStor ESG Report on FalconStor Virtual Tape Library}}</ref>
The [[FalconStor]] VTL is the foundation of nearly half of the products sold in the VTL market, according to an Enterprise Strategy Group analyst.<ref>{{cite web|url=http://www.infostor.com/index/articles/display/9694734941/s-articles/s-infostor/s-volume-13/s-issue_3/s-New_Analysis___Trends/s-VTLs__Going_beyond_data_de-dupe.html/|title=InfoStor ESG Report on FalconStor Virtual Tape Library}}</ref>


In mid-2010s VTLs got a rebirth thanks to hi-capacity "archive" drives from [[Seagate Technology|Seagate]] and [[HGST]] and more popular "tape in cloud" and Disk-to-Disk-to-Tape (often in cloud) scenarios. <ref>{{cite web|url=https://virtualizationreview.com/articles/2016/03/11/the-rise-fall-and-rise-of-virtual-tape-libraries.aspx/|title=The Rise, Fall, and Rise, of Virtual Tape Libraries}}</ref>
In mid-2010s VTLs got a rebirth thanks to hi-capacity "archive" drives from [[Seagate Technology|Seagate]] and [[HGST]] and more popular "tape in cloud" and Disk-to-Disk-to-Tape (often in cloud) scenarios. <ref>{{cite web|url=https://virtualizationreview.com/articles/2016/03/11/the-rise-fall-and-rise-of-virtual-tape-libraries.aspx/|title=The Rise, Fall, and Rise, of Virtual Tape Libraries}}</ref>

[[Amazon (company)|Amazon]] and [[StarWind Software]] in partnership with [[Veeam]], [[BackBlaze]] and [[Wasabi Technologies]] offer a so-called gateway products that facilitates backing up and archiving "on premises" data as virtual tapes stored in [[Amazon Web Services|AWS]], [[Microsoft]] [[Microsoft Azure|Azure]], [[Wasabi Technologies]] and [[BackBlaze]] public clouds.<ref>{{cite web |title=Integration of AWS Storage Gateway with Veeam – Backups and backup copy in Cloud |url=https://jorgedelacruz.uk/2017/09/06/veeam-integration-of-aws-storage-gateway-with-veeam-backups-and-backup-copy-in-cloud/ |website=orgedelacruz.uk |access-date=6 September 2017}}</ref> <ref>{{cite web |title=Setting Up a Veeam to StarWind Virtual Tape Library Configuration |url=https://blog.mpecsinc.com/2020/03/06/setting-up-a-veeam-to-starwind-virtual-tape-library-configuration/ |website=mpecsinc.com |access-date=3 March 2020}}</ref> <ref>{{cite web |title=Archive backups with Veeam and StarWind Virtual Tape Library |url=https://www.tech-coffee.net/archive-backups-with-veeam-and-starwind-virtual-tape-library/ |website=tech-coffee.net |access-date=20 April 2018}}</ref> The idea is to provide a seamless integration of a backup applications incompatible with the APIs object storages expose. Say, at the time [[Veeam]] couldn't do [[Amazon Web Services|AWS]] [[Amazon S3|S3]] and can't backup to the deep archive tier within [[Microsoft Azure|Azure]] still. <ref>{{cite web |title=Complete the Backup Lifecycle with Veeam’s SOBR Archive Tier |url=https://www.veeam.com/blog/v11-sobr-backup-lifecycyle.html |website=Veeam |access-date=4 March 2021}}</ref>


== See also ==
== See also ==
*[[Backup]]
*[[Backup]]
*[[Tape library]]
*[[Tape library]]
* [[Tape management system|Tape Management System]]
*[[Disk staging]] for an alternative approach
*[[Disk staging]] for an alternative approach
*[[Emulation (disambiguation)|Emulation]]
*[[Emulation (disambiguation)|Emulation]]

Revision as of 14:20, 27 April 2022

A virtual tape library (VTL) is a data storage virtualization technology used typically for backup and recovery purposes. A VTL presents a storage component (usually hard disk storage) as tape libraries or tape drives for use with existing backup software.

Virtualizing the disk storage as tape allows integration of VTLs with existing backup software and existing backup and recovery processes and policies. The benefits of such virtualization include storage consolidation and faster data restore processes. For most mainframe data centers, the storage capacity varies, however protecting its business and mission critical data is always vital.

Most current VTL solutions use SAS or SATA disk arrays as the primary storage component due to their relatively low cost. The use of array enclosures increases the scalability of the solution by allowing the addition of more disk drives and enclosures to increase the storage capacity.

The shift to VTL also eliminates streaming problems that often impair efficiency in tape drives as disk technology does not rely on streaming and can write effectively regardless of data transfer speeds.

By backing up data to disks instead of tapes, VTL often increases performance of both backup and recovery operations. Restore processes are found to be faster than backup regardless of implementations. In some cases, the data stored on the VTL's disk array is exported to other media, such as physical tapes, for disaster recovery purposes (scheme called disk-to-disk-to-tape, or D2D2T).

Alternatively, most contemporary backup software products introduced also direct usage of the file system storage (especially network-attached storage, accessed through NFS and CIFS protocols over IP networks) not requiring a tape library emulation at all. They also often offer a disk staging feature: moving the data from disk to a physical tape for a long-term storage.

While a virtual tape library is very fast, the disk storage within is not designed to be removable, and does not usually involve physically removable external disk drives to be used for data archiving in place of tape. Since the disk storage is always connected to power and data sources and is never physically electrically isolated, it is vulnerable to potential damage and corruption due to nearby building or power grid lightning strikes.

History

The first VTL solution was introduced by Cybernetics in 1992 under the name HSTC (high speed tape cache).[1] Later, IBM released a Virtual Tape Server (VTS) introduced in 1997. It was targeted for a mainframe market, where many legacy applications tend to use a lot of very short tape volumes. It used the ESCON interface, and acted as a disk cache for the IBM 3494 tape library. A competitive offering from StorageTek (acquired in 2005 by Sun Microsystems, then subsequently by Oracle Corporation) was known as Virtual Storage Manager (VSM) which leveraged the market dominant STK Powderhorn library as a back store. Each product line has been enhanced to support larger disk buffer capacities, FICON, and more recently (c. 2010) "tapeless" disk-only environments.

Other offerings in the mainframe space are also "tapeless". DLm has been developed by EMC Corporation, while Luminex has gained popularity and wide acceptance by teaming with Data Domain to provide the benefits of data deduplication behind its Channel Gateway platform. With the consequent reduction in off-site replication bandwidth afforded by deduplication, it is possible and practical for this form of virtual tape to reduce recovery point objective time and recovery time objective to near zero (or instantaneous).

Outside of the mainframe environment, tape drives and libraries mostly featured SCSI. Likewise, VTLs were developed supporting popular SCSI transport protocols such as SPI (legacy systems), Fibre Channel, and iSCSI.

The FalconStor VTL is the foundation of nearly half of the products sold in the VTL market, according to an Enterprise Strategy Group analyst.[2]

In mid-2010s VTLs got a rebirth thanks to hi-capacity "archive" drives from Seagate and HGST and more popular "tape in cloud" and Disk-to-Disk-to-Tape (often in cloud) scenarios. [3]

Amazon and StarWind Software in partnership with Veeam, BackBlaze and Wasabi Technologies offer a so-called gateway products that facilitates backing up and archiving "on premises" data as virtual tapes stored in AWS, Microsoft Azure, Wasabi Technologies and BackBlaze public clouds.[4] [5] [6] The idea is to provide a seamless integration of a backup applications incompatible with the APIs object storages expose. Say, at the time Veeam couldn't do AWS S3 and can't backup to the deep archive tier within Azure still. [7]

See also

References

  1. ^ "History of VTL/IBM".
  2. ^ "InfoStor ESG Report on FalconStor Virtual Tape Library".
  3. ^ "The Rise, Fall, and Rise, of Virtual Tape Libraries".
  4. ^ "Integration of AWS Storage Gateway with Veeam – Backups and backup copy in Cloud". orgedelacruz.uk. Retrieved 6 September 2017.
  5. ^ "Setting Up a Veeam to StarWind Virtual Tape Library Configuration". mpecsinc.com. Retrieved 3 March 2020.
  6. ^ "Archive backups with Veeam and StarWind Virtual Tape Library". tech-coffee.net. Retrieved 20 April 2018.
  7. ^ "Complete the Backup Lifecycle with Veeam's SOBR Archive Tier". Veeam. Retrieved 4 March 2021.