Veeam Backup & Replication supports Linear Tape-Open tape libraries starting from generation 3 (LTO3) or later:
- Physical libraries, standalone drives and virtual tape libraries.
- Partitions of the physical or virtual tape libraries presented to the Veeam backup server.
Affecting 3rd Party Tape Solutions
Veeam Backup & Replication does not support sharing tape devices with 3rd party tape-recording software. If you plan to run both Veeam Backup & Replication and 3rd party tape-recording software (for example, in your evaluation lab), consider that Veeam Backup & Replication by default will periodically lock the drive to perform rescan, preventing other software from recording.
To share a tape device, configure a partition of the tape library that will be used only by Veeam Backup & Replication.
Mind the following limitations:
- Do not connect partitions presented to the 3rd party tape software to a Veeam tape server.
- Do not install any 3rd party tape-recording software or software components on Veeam tape server.
Driver Installation Mode
Veeam Backup & Replication supports both exclusive and non-exclusive driver installation.
If you use standalone tape drives, it is recommended to install drivers in non-exclusive mode.
Veeam Backup & Replication supports path failover for tape devices with multiple drives that manage multiple paths over multiple SANs.
Veeam Backup & Replication uses the MTF (Microsoft Tape Format) industry format to write data to tape.
Supported Connection Types
You can connect the tape device directly or remotely.
- Direct connection:
- Fibre Channel (FC)
- Serial Attached SCSI (SAS)
- Remote connection:
- Switched FC fabric
Data Block Size
Drives use hardware dependent block sizes to read/write the tape data. Generally, the drives support a range of block sizes and report this range to Veeam Backup & Replication.
If you use a tape library with multiple drives or a number of standalone drives, Veeam Backup & Replication uses a unified block size to write data to tapes. 256k data block size is used if all drives can support it. If any drive can support only a smaller block size, for example, 64k, then Veeam Backup & Replication uses the largest block supported by all drives. To understand block sizes supported by drives, Veeam Backup & Replication collects the block size ranges reported by each drive and compares them. Note that the reported range is additionally limited by storage controllers settings used in your infrastructure. You can check the resulting range of block sizes supported by Veeam Backup & Replication for a particular drive in the Drives properties. For details, see Working with Drives.
If you connect the tape devices via HBA, Veeam Backup & Replication uses the block size configured for the HBA.
The block size is unified for:
- All drives in one library (if the drives support different block sizes)
- All standalone drives connected to one tape server.
To read data from tape, Veeam Backup & Replication requires that the tape is written with the block size from the supported range (shown in the drive properties).
Mind the block size range when working with the following tapes:
- Tapes with Veeam backups written by another tape library,
- Tapes with Veeam backups written on another tape server,
- Tapes written with other data transfer configuration settings,
- Tapes written on a 3rd party device.
You can restore from tapes written with block size that match the block size range set for the tape device.
Unknown Medium Changers
Veeam supports medium changers that have no Microsoft Windows drivers available. Make sure that such device is recognized as an unknown medium changer in the Microsoft Device Manager list.
It is recommended that you use tape devices with original equipment manufacturer (OEM) drivers.
VMware does not support tape drives connected directly to ESX(i) 4.x and later. For more information, see VMware vSphere Release Notes.
For more details and recommendations on configuring vendor-supported tape drives and media changers on ESX/ESXi, refer to VMware documentation at http://kb.vmware.com/kb/1016407.