This Hardware Compatibility List (HCL) document contains information for all editions of Backup Exec 21. All hardware must be present on this HCL for support, unless a section clearly states that the devices listed are not the only devices supported (such as the Disk Target section). If your tape drive, tape library, or virtual tape library is not properly detected, please update your system using the latest Update (previously called a Feature Pack) before calling Support. Updating the drivers frequently resolves device related issues. This update can be found on our support site. https://www.veritas.com/support/en_US/15047.html Please see these links for information about how and where to obtain updates https://www.veritas.com/content/support/en_US/article.100019916 and https://www.veritas.com/support/en_US/article.100041552

Backup Exec support policy is that all of the vendors involved (both hardware and software) must support all the pieces involved. For example, the Host Bus Adapter must be supported by the hardware vendor and the operating system vendor in order for Veritas to provide support. Always consult the hardware manufacturer’s support list and the operating system vendor’s support list when troubleshooting or planning a data protection installation. All entries were believed to be fully supported by all parties involved when they were added to this Veritas list, but if a vendor drops their support after this list was published, Veritas support will be on a reasonable-effort basis.

Hardware is selected and prioritized for certification based on market research and input from the field, including customer feedback. If a customer would like to have their hardware considered for inclusion on this HCL, simply submit the request via an email mailto:[email protected] . Requests will be reviewed by the appropriate Veritas Product Management team members for possible certification, with final decisions based on the overall fit with the product, target market, and frequency of request.

Some notes about drivers: Veritas Kernel-mode Tape drivers and tapeinst.exe are no longer installed if Backup Exec 21 is installed on Windows Server 2012 or later. There are no devices on this Backup Exec 21 Hardware Compatibility List (HCL) that require Veritas Kernel-mode drivers. USB tape devices still require a Microsoft or vendor Kernel-mode driver, in addition to the Veritas User-mode driver. Users of very old, unsupported, tape devices should investigate and test before using Windows Server 2012 or later to determine the functionality as kernel-mode drivers may be required. All supported tape devices are now accessed by Veritas User-mode drivers. Most tape devices have been accessed by User-mode drivers for multiple previous versions of Backup Exec.

User-mode drivers are not visible in the Windows Device Manager. When no Kernel-mode drivers are installed, the Windows Device Manager may show the tape drive with a yellow exclamation mark. This is acceptable and does NOT prevent the device from being used with Backup Exec and the User-mode drivers. Kernel-mode drivers from Microsoft or the tape hardware vendor are generally acceptable to be installed. Backup Exec will continue to access the tape devices via User-mode drivers.

Tapeinst.exe is the program that installs Veritas Kernel-mode tape class drivers. When using Windows Server 2008 R2 or earlier, tapeinst.exe can be invoked manually or via the “Install Tape Device Drivers” wizard (under the “Configure Storage” menu). When using Windows Server 2012 or later, the ability to run the “Install Tape Device Drivers” wizard (under the Configure Storage menu) is no longer present and is not needed.

Some notes about tape drive block sizes: Please be sure to consult this technote when using tape drive block sizes above the 64KB default size. https://www.veritas.com/content/support/en_US/article.100019307

Alternative Configurations: Our Licensed Software is designed to interoperate with many types of systems, applications, and hardware. Sometimes a customer may choose to use our Licensed Software in an “Alternative Configuration” , namely, an environment that has not been validated, approved or verified to operate with our Licensed Software or which does not support such Licensed Software or only supports limited functionality. In most cases, we do not support Alternative Configurations, and we have no obligation to provide Support Services to Licensed Software in an Alternative Configuration. Veritas makes no warranty with respect to use of Licensed Software in an Alternative Configuration and any such use is at your own risk. A “Supported Configuration” might be converted into an Alternative Configuration where a vendor modifies one of its components that is part of the original Supported Configuration. As a consequence, your Licensed Software would then be operating in an Alternative Configuration. If you experience a problem with the Licensed Software in an Alternative Configuration or if your issue deals with script that was not developed by Veritas or an authorized consulting partner, then we may ask you to reproduce the problem in a Supported Configuration environment. Please note we have no obligation to attempt to resolve problems that cannot be replicated in a Supported Configuration. However, if the problem can be replicated in a Supported Configuration, we will investigate the problem in that Supported Configuration and attempt to resolve it. If the problem cannot be replicated in a Supported Configuration, then we may elect not to work on that problem.

Configuring a tape device with a virtual machine is considered an “Alternative Configuration”. For more details on the configuration of virtual machines with tape devices, see the following related articles:

https://www.veritas.com/support/en_US/article.100023671 Support for Backup Exec in virtual and IaaS environments

https://www.veritas.com/support/en_US/article.100001998 Can Backup Exec Media Servers be installed on a Guest virtual machine running on an ESX server?

https://www.veritas.com/support/en_US/article.100020969 How to properly configure a VMWare ESX virtual machine to use tape devices which are connected to the host server via SCSI Passthrough.

Go to Top of “Document”

Backup Exec Documentation

Newly-Supported Devices

The following new devices have been added to this HCL. See the device in its respective section, via bookmarks, for more details.

Veritas Update (previously LiveUpdate) will obtain the latest updates for your BE version.

Your device may require that you download and install an Update (previously called a Feature Pack), but it is RECOMMENDED that the latest patches are always used. If a new Update is utilized, it is required that Simplified Disaster Recovery (SDR) users regenerate the SDR boot media.

New Backup-to-cloud | S3 Cloud connector:

1. Tencent Cloud Object Storage – All locales

New NDMP Option components:

1. Dell EMC PowerScale with OneFS v9.0

The PowerScale line was previously known as the Isilon Scale-Out NAS line.

Added 2020-09-15:

New Backup-to-Disk | OpenStorage appliances:

1. Data Domain Appliance series and DDVE with DDOS plugins v7.2 and v7.3

Added 2020-09-07:

New Backup-to-cloud | S3 Cloud connector:

1. Google Cloud – Salt Lake City (US-West3) and Las Vegas (US-West4)

2. Amazon – Africa (Cape Town) and Europe (Milan)

New Backup-to-cloud | OpenStorage:

1. Hewlett Packard Enterprise Cloud Volumes

New NDMP Option components:

1. Dell EMC PowerStore T-series

For details about Backup Exec 21 Update 1 (aka 21.1), please see https://www.veritas.com/content/support/en_US/doc/59226813-141939443-0/index or https://www.veritas.com/content/support/en_US/downloads/detail.REL741973 Released September 07, 2020

Backup Exec 21.0 was released April 6, 2020 https://www.veritas.com/content/support/en_US/downloads/detail.REL991929

Select hardware by BE option or agent

The listed options and agents have hardware requirements. They are included here for the purpose of helping choose the appropriate hardware for the selected agent/option.

Advanced Disk-based Backup Option

The Advanced Disk-based Backup Option (ADBO, included with the Enterprise Server Option), as it relates to hardware devices in this HCL, can be seen in the VSS Providers for Offhost backup section.

Deduplication Option

The Deduplication Option support information is included with the Disk Targets sections. There are two basic options to choose from:
1. Backup Exec Deduplication Option Storage. To find tested devices, search by storage device vendor in the Disk Targets | Disk Storage section , then model, then look for a check [✔] in the “dedup” column for tested disk devices.
2. Deduplication Appliance – sometimes referred to as OpenStorage devices from our hardware/software partners. See the OST-Appliance section .

Simplified Disaster Recovery Option

The Simplified Disaster Recovery (SDR) Option is supported on tape libraries, tape drives, virtual tape libraries, and disk devices (present at system start time) unless otherwise mentioned in a footnote, or section header paragraph.

For compatibility information on physical tape libraries with SDR, please refer to the Tape Libraries with Drives Section of this document.

For compatibility information on virtual tape libraries (VTLs) with SDR, please refer to the Virtual Tape Libraries with Drives Section of this document.

For compatibility information on tape drives with SDR, please refer to the Tape Drives Section of this document.

NDMP Option

The storage devices supported by the NDMP option are included with the Tape Library / Virtual Tape Library sections. Please refer to the NDMP-specific notes in the “NDMP Platforms” section. These notes can be found as footnotes, per NDMP vendor / device combination. These notes apply to the “Virtual Tape Libraries with Drives” and “Tape Libraries with Drives Section” sections. Search by storage device vendor, then model, then look for a check [✔] in the NDMP column for support. Please note that the presence of a check means that Veritas will support the storage device and NDMP combination IF and ONLY IF the NDMP vendor also supports the library / drive combination. Please refer to the NDMP vendors’ documentation for storage device support.

For compatibility information on NDMP platforms supported, please refer to the NDMP Platforms Section of this document.

For compatibility information on physical tape libraries with NDMP, please refer to the Tape Libraries with Drives Section of this document.

For compatibility information on virtual tape libraries (VTLs) with NDMP, please refer to the Virtual Tape Libraries with Drives Section of this document.

Remote Media Agent for Linux

The Remote Media Agent for Linux (RMAL) support information is included with the Tape Library / Virtual Tape Library / Tape Drives sections. Search by storage device vendor, then model, then look for a check [✔] in the RMAL column for support.

For compatibility information on physical tape libraries with RMAL, please refer to the Tape Libraries with Drives Section of this document.

For compatibility information on virtual tape libraries (VTLs) with RMAL, please refer to the Virtual Tape Libraries with Drives Section of this document.

For compatibility information on tape drives with RMAL, please refer to the Tape Drives Section of this document.

Enterprise Server Option for use with SAN shared storage

The SAN Shared Storage Option is now available as part of the Enterprise Server Option in Backup Exec 2012, Backup Exec 2014, Backup Exec 15, Backup Exec 16 Backup Exec 20, & Backup Exec 21. All references to SSO on the HCL are now replaced with ESO due to the change. If you used the SAN Shared Storage Option in a previous version of Backup Exec, the SAN primary server will be upgraded to a Central Administration Server. SAN secondary servers will be upgraded to Managed Backup Exec Servers and will have the Managed Backup Exec Server option installed and the Unrestricted access to catalogs and backup sets for restore option selected.

The Enterprise Server Option (ESO) hardware support information is included with the Tape Library / Virtual Tape Library sections. Search by storage device vendor, then model, then look for a check [✔] in the ESO column for support.

For compatibility information on physical tape libraries with ESO, please refer to the Tape Libraries with Drives Section of this document.

For compatibility information on virtual tape libraries (VTLs) with ESO, please refer to the Virtual Tape Libraries with Drives Section of this document.

For compatibility information on storage area network (SAN) components with ESO, inlcuding fibre-channel and iSCSI components, please refer to the SAN Infrastructure components Section of this document.

Library Expansion Option

The Library Expansion Option (LEO) supported hardware configurations, including tape library and tape drive combinations, can be seen in the Tape Libraries with Drives section.

Virtual Tape Library Unlimited Drive Option

The Virtual Tape Library Unlimited Drive Option (VUDO) supported hardware configurations, including virtual tape library and virtual tape drive combinations, can be seen in the Virtual Tape Libraries with Drives section.

Often, a single VTL can be configured with a variable number of tape drives and tape libraries. VUDO allows for the variance in drives per physical VTL, not logical VTL. In other words, creating more than one logical VTL will require the need for multiple VUDO licenses.

Cloud Storage

Please see the “Best Practices for Using the Veritas Backup Exec Cloud Connector” at https://www.veritas.com/content/support/en_US/doc/72686287-140583204-0/v128967126-140583204

Backup Exec supports Cloud-based storage providers using a variety of technology methods, described below.

1) Azure Storage – This method uses the Backup Exec “Azure Cloud Connector” (a plugin included with Backup Exec). This target appears in Backup Exec with a Storage Type of “Cloud Storage”.

2) S3 Storage – This method uses the Backup Exec “S3 Cloud Connector” (a plugin included with Backup Exec). This target appears in Backup Exec with a Storage Type of “Cloud Storage”.

3) OST – This method uses a third-party Open Storage Technology plugin. This methods requires a Deduplication license in Backup Exec. This target appears in BE with a Storage Type of “OpenStorage”.

4) Disk Targets – This method uses third-party hardware or software to make the cloud appear as a “regular” disk volume to Windows and Backup Exec. This target appears in Backup Exec with a Storage Type of “Disk storage”.

5) VTL – This method uses third-party software to present the Cloud as if it was a VTL (Virtual Tape Library) to Windows and Backup Exec. A BE VUDO license is suggested. This target appears in Backup Exec with a Storage Type of “Robotic Library”.

Listed below are the supported and tested Cloud Storage solutions. Other Cloud Storage solutions may work, but it would be treated as an “Alternative Configuration”. See this article for more information https://www.veritas.com/support/en_US/article.100039077 Cloud solutions are selected and prioritized for certification based on market research and input from the field, including customer feedback. If a customer would like to have their cloud and/or hardware considered for inclusion on this HCL, simply submit the request via an email mailto:[email protected] . Requests will be reviewed by the appropriate Veritas Product Management team members for possible certification, with final decisions based on the overall fit with the product, target market, and frequency of request. Go to Top of “Cloud Storage”

Cloud Providers and Technology Methods

Azure Cloud

You can use the Azure Cloud Connector to back up data to Microsoft Azure cloud storage.

Microsoft

1. Hot-tier and cool-tier are supported.
2. Backup Exec supports Azure-Blob Storage type only.

S3 Storage

You can use the S3 Cloud Connector to back up data to a supported S3-compatible cloud storage.

The below section lists the S3-compatible cloud storage solutions that are currently supported by Backup Exec 21 and the BE 21 Update (if any) that are required for support.

Alibaba Cloud

1. To configure this cloud storage for use with Backup Exec, see the following article https://vox.veritas.com/t5/Backup-Exec/Backup-Exec-BE-workload-protection-with-Alibaba-Object-Storage/ba-p/858791

Amazon

1. To configure this cloud storage for use with Backup Exec, see the following article https://www.veritas.com/support/en_US/article.100038470
2. To get started with AWS S3, go to the following link http://aws.amazon.com/s3
3. Transfer Acceleration for AWS S3 is not currently supported in BE
4. Support for the Africa (Cape Town) or Europe (Milan) regions requires BE 21.1 (or higher). See https://www.veritas.com/content/support/en_US/doc/59226813-141939443-0/index

Chunghwa Telecom

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077

Cloudian

1. The Provider Name “Cloudian” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100038827.html

Dell EMC

1. The Provider Name “emc-ecs” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100038827.html

DOCKS by PingUs

1. The Provider Name “Cloudian” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100038827.html

Google

1. To configure this cloud storage for use with Backup Exec, see the following article https://www.veritas.com/support/en_US/article.100031532
2. Support for the US-West3 and US-West4 locations requires BE 21.1 (or higher). See https://www.veritas.com/content/support/en_US/doc/59226813-141939443-0/index

IBM

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077

Infoniqa

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077

RedHat

1. The Provider Name “rhceph” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100038827.html

Scality

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077

Tencent

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077
2. “COS Standard” is supported. “COS Standard_IA” and “Archive Storage” are not supported.

Telefonica

1. The Provider Name “Compatible-with-S3” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077

Veritas

1. The Provider Name “vtas-access” will be required for creating Cloud Instance using bemcli. For steps on using bemcli to create a new cloud instance, please see https://www.veritas.com/support/en_US/article.100039077
2. All Veritas Access versions and form-factors are supported, including Veritas built appliances and other appliances.

OST

Backup Exec OpenStorage (OST) Cloud Storage plug-ins enable Veritas data protection applications to access Cloud Storage Solutions. Either the storage vendor or Veritas provides a software plug-in, which is installed on each Backup Exec server that is connected to the cloud solution. If you do not see OST support for your desired Cloud Storage Solution provider / Backup Exec Server OS platform, please contact that Storage Server appliance vendor to request OST support for that platform. Please see the Backup Exec System Administrator’s Guide for more information on how to use OST. Go to Top of “OST”

Hewlett Packard Enterprise

1. For information on Cloud Volumes, go to https://demo.cloudvolumes.hpe.com/welcome/
2. See the HPE OST appliance section also

Quantum

1. For information on how to setup Q-Cloud Protect with Backup Exec, go to http://www.quantum.com/serviceandsupport/softwareanddocumentationdownloads/index.aspx select the appropriate DXi product, select the “Documentation” tab, in the best practices section select “DXi-Series and Best Practices Guide for Backup Exec from Symantec”. Once you enter the appropriate serial number, search for Appendix A.
2. DXi server model DXi8500 (3TB) or DXi6802 is required to support Data-at-Rest encryption.
3. See the Quantum OST appliance section also

Datish Systems OpenDedupe

1. For more information go to https://www.veritas.com/support/en_US/article.100042352
2. For more information go to http://opendedup.org
3. Installation demonstration videos are at https://youtu.be/VAa-K8WIXVo and https://youtu.be/Pf_xCj2FynI
4. Note: OpenDedupe devices must NOT be shared between BE server nodes, even in an MMS/CAS environment. Do not use the same cloud bucket for two different BE servers. OpenDedupe does not support device sharing at this time. Although BE may allow you to share the device, you must not share it. Corruption of the dedupe data is a likely result.
5. The OpenDedupe OST Plugin is not supported on a Backup Exec Remote Agent. The Opendedupe OST plugin must be used on a Backup Exec Server.
6. See the Datish Systems OST section also
7. An OpenDedupe upgrade demonstration video is at https://www.youtube.com/watch?v=YJFXLjswXbA or https://vox.veritas.com/t5/Backup-Exec/Video-How-to-Upgrade-OpenDedupe-from-a-previous-version-to-v3-6/m-p/852543

Disk Targets

The disk target software versions listed in this section are the minimum software levels that are supported. Where more than one software level is listed, this implies a newer version has been tested. The earlier software version is the minumum version required.

Cloud storage providers will be individually certified for use with Backup Exec, therefore, additional Cloud providers will be added as they are certified.

Amazon Web Services

1. The Gateway-Cached Volume is offered as a service and therefore specific software versions are not available. Please refer to release dates: http://aws.amazon.com/releasenotes/AWS-Storage-Gateway
2. Backup Exec Simplified Disaster Recovery (SDR) is not supported.
3. See the Amazon Disk Targets section also
4. Please refer to AWS documentation for hypervisor and host requirements: http://docs.aws.amazon.com/storagegateway/latest/userguide/Requirements.html

Microsoft StorSimple

1. Please refer to MS documentation: https://docs.microsoft.com/en-us/azure/storsimple/storsimple-configure-backup-target-using-backup-exec
2. Backup Exec Simplified Disaster Recovery (SDR) is not supported.
3. See the Microsoft Disk Targets section also

NetApp

1. Backup Exec Simplified Disaster Recovery (SDR) is not supported. Refer to the AltaVault docs for recovery instructions.
2. NetApp AltaVault Cloud Integrated Storage Deployment Guide 4.0.1: https://library.netapp.com/ecm/ecm_download_file/ECMP12510036
3. See the NetApp Disk Targets section also

Riverbed

1. Backup Exec Simplified Disaster Recovery (SDR) is not supported. Refer to the SteelStore docs for recovery instructions.
2. SteelStore Solution Guide: http://media-cms.riverbed.com/documents/Solution+Guide+-+SteelStore+with+Backup+Exec+3.1.1.pdf
3. See the Riverbed Disk Targets section also

VTL

The Cloud Virtual Tape Library (VTL) device support information is listed below. Please Note:
1. Configure the virtual device with the unique inquiry string as listed in this document. Emulating other devices is not supported.
2. Tested iSCSI versions of virtual tape libraries are listed in the “iSCSI Solutions” section, under the “SAN Infrastructure components” bookmark. Please reference the limitations listed in that section.
Go to Top of “VTL”

Amazon Web Services

1. Please read through the Best Practice guide for the Gateway-VTL before deployment: https://www.veritas.com/support/en_US/article.100014745
2. The Storage Gateway is offered as a service and therefore specific software versions are not available. Please refer to release dates: http://aws.amazon.com/releasenotes/AWS-Storage-Gateway
3. For the AWS Storage Gateway-VTL user guide, please refer to: http://docs.aws.amazon.com/storagegateway/latest/userguide/gateway-vtl.html
4. Backup Exec Simplified Disaster Recovery (SDR) is not supported.
5. See the Amazon iSCSI VTL section also
6. Please refer to AWS documentation for hypervisor and host requirements: http://docs.aws.amazon.com/storagegateway/latest/userguide/Requirements.html
7. For information on the AWS Storage Gateway in EC2 please refer to the following documentation: https://aws.amazon.com/marketplace/pp/B00AZ4Q6MM
8. Import operations are limited to 64 tapes at a time. Please see https://www.veritas.com/support/en_US/article.100043731.html

Disk Targets

For this basic support, any device recognized and supported by the Windows platform should work with Backup Exec. Mapped network drives are not supported. UNC paths are supported. The disk devices listed in these two sections have been tested with Backup Exec as a result of a formal joint business agreement and OEM relationship, but are not intended to be a complete list of compatible devices.

For “basic” disk storage capabilities, Backup Exec does not exclude or block recognition for disk devices. Basic disk storage devices can be seen in the Disk Storage and Disk Cartridge sections. This information is organized by vendor and provides information on the storage devices tested, the Inquiry Strings (if applicable), the type of interface, media type, and any special notes on a per device basis.

If the desired device is not already listed in this section, customers are encouraged to run the B2D test tool to verify their desired device’s level of functionality. If Backup Exec is not already installed, the B2D test tool can be downloaded from https://www.veritas.com/content/support/en_US/article.100020569. Instructions for use are in that same technote. Backup Exec Technical Support will be unable to offer assistance if the device experiences failures during the B2Dtest and the customer should contact the hardware vendor for advice and assistance.

Devices running the Windows Unified Data Storage Server OS which provides iSCSI target functionality are supported per the Software Compatibility List. See http://www.backupexec.com/compatibility for supported operating system details.

Devices running the Windows Storage Server OS (sometimes referred to as a NAS) can be used as a Backup Exec Media Server if the operating system version is on the Software Compatibility List (SCL). Some examples are the Dell NX3200, the HPE StoreEasy series, and others. If the server meets the prerequisites for adding the Backup Exec Deduplication Option, then that server’s local disks can be used for deduplication by that Backup Exec Media Server. See http://www.backupexec.com/compatibility for supported operating system details.
If the server vendor supports the server as an iSCSI target, then it can be supported for remote deduplication storage from other Backup Exec Media Servers. Refer to the HCL Disk Storage section for tested systems, but other systems would be supported also. Please see the deduplication best practices document at https://www.veritas.com/content/support/en_US/doc/72686287-131623464-0/v70445236-131623464
A server running Windows Storage Server is NOT supported for OpenStorage (OST) target storage use, unless that server/appliance appears in the OST section of the HCL. A server running Windows Storage Server may be used with the Remote Agent for Windows Servers (RAWS) to send data to an OST appliance.

For more advanced disk capabilities, refer to the OST-Appliance section or VSS Providers for Offhost backup sections. The presence of the disk device in these advanced sections is required for support.

Granular Restore Technology (GRT) support, per deduplication type

Disk Storage

The disk devices listed in this section have been tested with Backup Exec, but are not intended to be a complete list of compatible devices.

To clarify: not all supportable disk device are listed in this section. There are simply too many variations to certify them all.

If the desired device is not already listed in this section, customers are encouraged to run the B2D test tool to verify their desired device’s level of functionality. If Backup Exec is not already installed, the B2D test tool can be downloaded from https://www.veritas.com/content/support/en_US/article.100020569. Instructions for use are in that same technote. Backup Exec Technical Support will be unable to offer assistance if the device experiences failures during the B2Dtest and the customer should contact the hardware vendor for advice and assistance. If you do run B2Dtest on a disk device not listed here, please submit the results to mailto:[email protected] . Go to Top of “Disk Storage”

Disk Device Legend

Amazon

1. This device includes Cloud features. Please see the Amazon Cloud Storage section for specifics.

BlueArc

Buffalo

Dell EMC

Dell EMC Data Domain

Drobo

Exablox

ExaGrid

Fujitsu

H3C

Hewlett Packard Enterprise

1. StoreOnce VSA is a virtual appliance. For device details and platform support refer to: https://www.hpe.com/h20195/v2/GetDocument.aspx?docname=c04328820

Hitachi

1. GRT is not recommended when the microcode version of HCO is 2.1

IBM

Imation

Infortrend

LaCie

Lenovo

Microsoft

1. This device includes Cloud features. Please see the Microsoft StorSimple section for specifics.

NEC

NetApp

1. Backup Exec Simplified Disaster Recovery (SDR) is not supported. Refer to the NetApp AltaVault docs for recovery instructions.
2. NetApp AltaVault Cloud Integrated Storage Deployment Guide 4.0.1: https://library.netapp.com/ecm/ecm_download_file/ECMP12510036
3. This device includes Cloud features. Please see the NetApp Cloud Storage section for specifics.

NETGEAR

Nexsan

Oracle

Overland Storage

Pure Storage

QNAP

Quantum

1. This device is a virtual appliance. Representative VMware-supported ESX4, ESXi4, or ESXi5 servers/storage were tested. Refer to http://downloads.quantum.com/dxiv1000/6-67611-01_DXi_V1000_QuickStartGuide_RevA.pdf

Quest

Riverbed

1. Backup Exec Simplified Disaster Recovery (SDR) is not supported. Refer to the SteelStore docs for recovery instructions.
2. SteelStore Solution Guide: http://media-cms.riverbed.com/documents/Solution+Guide+-+SteelStore+with+Backup+Exec+3.1.1.pdf
3. This device includes Cloud features. Please see the Riverbed Cloud Storage section for specifics.

Synology

Tandberg

Disk Cartridge

The disk devices listed in this section have been tested with Backup Exec, but are not intended to be a complete list of compatible devices.

To clarify: not all supportable disk device are listed in this section. There are simply too many variations to certify them all.

Note: Granular Restore Technology (GRT) is not supported on disk cartridge devices if the backup spans media.

Note: USB 3.0 devices are supported (when available from the vendor).

Note: To view the disk inquiry string: Open Computer Management, Go to Device Manager | Disk drives, Double click on the RDX drive, Click on the Details tab, For the Property drop-down, select ‘Hardware Ids’, View the inquiry string in the Value section Go to Top of “Disk Cartridge”

Disk Device Legend

Go to Top of “Disk Cartridge”

actidata

Go to Top of “Disk Cartridge”

BDT

Go to Top of “Disk Cartridge”

Dell EMC

Go to Top of “Disk Cartridge”

Hewlett Packard Enterprise

1. Requires the use of the HPE RDX utility from http://www.hp.com/support/rdx for proper eject functionality.

Go to Top of “Disk Cartridge”

IBM

Go to Top of “Disk Cartridge”

Imation

Go to Top of “Disk Cartridge”

Lenovo

Go to Top of “Disk Cartridge”

ProStor

Go to Top of “Disk Cartridge”

Quantum

Go to Top of “Disk Cartridge”

Tandberg

Go to Top of “Disk Targets”

OST-Appliance

OpenStorage Servers are intelligent storage devices that interface to Backup Exec Servers and Remote Agents for Windows (with Direct Access) via the Veritas OpenStorage (OST) API. The vendor supplying the Storage Server appliance provides a software Plug-in, which is installed on each Backup Exec Server and Remote Agent for Windows (with Direct Access) that is attached to the OpenStorage Server.

OST functionality is available on supported Windows Backup Exec 21 Backup Exec Server and Remote Agent for Windows platforms.

Please see the Backup Exec System Administrator’s Guide for more information on how to use OST.

Attention: OpenStorage (OST) appliance users: Backup Exec 21 may require a new OST plug-in from your appliance vendor.
Please contact your vendor for access to this new plug-in. If needed, the required Backup Exec 21 plug-in details will be listed as a footnote in the “Storage Server Family” column, per vendor.

In the tables below, “Basic Duplication” refers to server-side or client-side deduplication.

Where support is shown for Windows Server 2008, Windows Server 2012, Windows Server 2016, or Windows Server 2019, please reference the Software Compatibility List ( http://www.backupexec.com/compatibility ) for supported operating system versions.

Go to Top of “OST-Appliance”

Datish Systems (OpenDedup)

1. Note: OpenDedupe devices must NOT be shared between BE server nodes, even in an MMS/CAS environment. Do not use the same cloud bucket for two different BE servers. OpenDedupe does not support device sharing at this time. Although BE may allow you to share the device, you must not share it. Corruption of the dedupe data is a likely result.
2. Plugin version 2.1.3.0 is required.
3. SDFS Cloud File System 3.4.10.1 is required.
4. The OpenDedupe OST Plugin is not supported on a Backup Exec Remote Agent. The Opendedupe OST plugin must be used on a Backup Exec Server.

Go to Top of “OST-Appliance”

Dell EMC Data Domain

1. Refer to the following technote regarding a possible issue with Optimized Duplication (OpDup) not working correctly. https://www.veritas.com/content/support/en_US/article.100048397
2. See the Backup Exec sections in the DataDomain OST Admin guide for installation and configuration details. (Data Domain Support account and access to the plug-in releases is required)
3. Use the 7.0 Plug-In with Data Domain OS 7.1. Data Domain did not release a new Plug-In for 7.1.

Go to Top of “OST-Appliance”

ExaGrid

1. Browse to the Help->Online Library in the ExaGrid administrative interface and view/download Using Symantec Backup Exec™ with an ExaGrid System.
2. ExaGrid OS version 4.6.4 P12 (or higher) is required.
3. For more information, see here: http://www.exagrid.com/backup_applications/Symantec_VERITAS_Backup_Exec.asp

Go to Top of “OST-Appliance”

Fujitsu

1. For more information, see http://support.ts.fujitsu.com/Download/ Then, fill in the following values in the “Driver and Downloads” section: select “Storage solutions”, then select “ETERNUS CS/CentricStor”, then select “ETERNUS CS800”

Go to Top of “OST-Appliance”

H3C

1. Refer to the following technote for FC configuration information. https://www.veritas.com/support/en_US/article.100041993

Go to Top of “OST-Appliance”

Hewlett Packard Enterprise

1. The HPE v4.1 and v4.2 OST plugins do not support client-side deduplication for systems running the Backup Exec remote agent. This will be addressed by HPE in a future release of the plugin. For now, deduplication from the remote system must be done via server-side.
2. Version 3.14 code is the minimum required for the StoreOnce 3100, 3520, 3540, 5100, or 5500 devices. The code is not backwards compatible with earlier versions of StoreOnce hardware. For more information, please contact Hewlett Packard Enterprise.
3. Refer to the following technote for FC configuration information. https://www.veritas.com/support/en_US/article.100041993
4. There is a capacity reporting issue with early versions of the 4.2 plugin. Please upgrade to 4.2.1.2532 (or greater) or consult HPE about bugs 123275 & 124555
5. StoreOnce VSA is a virtual appliance. For device details and platform support refer to: https://www.hpe.com/h20195/v2/GetDocument.aspx?docname=c04328820

Go to Top of “OST-Appliance”

Quantum

1. For more information, see http://www.quantum.com/ServiceandSupport/SoftwareandDocumentationDownloads/OSTClientPlugIn/Index.aspx
2. Quantum DXi OST plugins, version 10.0.0 and above, support 64 bit systems only.
3. The Quantum hostname and storage server name needs to be different to avoid connection issues.
4. This device is a virtual appliance. Representative VMware-supported ESX4, ESXi4, or ESXi5 servers/storage were tested. Refer to http://downloads.quantum.com/dxiv1000/6-67611-01_DXi_V1000_QuickStartGuide_RevA.pdf

Go to Top of “OST-Appliance”

Quest

1. Dell EMC has separated/sold the DR appliance division into Quest. Customers should migrate to running newer Quest branded software on the appliance and using the Quest branded plugin. Download Quest stuff from https://support.quest.com/download-product-select
2. For 4.0: The Quest packaged 4.x plug-in installer should be used to install the required OST plugin. The Quest packaged 4.0.2 (or newer) plug-in installer now installs two plugin files, one named for Dell and one named for Quest. When configuring storage within Backup Exec 21, and if your DR appliance is running 4.0.2 (or newer), please select the “Quest” provider. The Backup Exec adamm.log will document which plugin is being used in the line “OST Server: DELL:DR4300-HPVxxxx” versus “OST Server: QUEST:DR4300-HPVxxxx”. There are no performance differences between the different named plugins. There are no changes to the container on the Quest DR appliance side. The container may be using either the Symantec or the Veritas OST access protocol. In other words: The Dell-named libstspiDellMT.dll works & is supported by Backup Exec 21. The preferred Quest-named libstspiocaMT.dll works & is supported in Backup Exec 21.
3. Please see the Quest Migration Guide for changing Dell containers to Quest containers https://support.quest.com/download/downloads?id=6084223
4. Plug-in version 4.1.0.327 (or higher) is required for NEW Backup Exec 21 installations. Older (supported) versions of the plugin (3.2 & 4.0) are acceptable when Backup Exec is upgraded in-place to Backup Exec 21.
5. The 3.2 PLUGINS work with BE 21, but the 3.2 INSTALLER does NOT work with BE 21.
6. Plug-in version 4.1.0.327 (or higher) is required for NEW Backup Exec 21 installations. Older (supported) versions of the plugin (4.1) are acceptable when Backup Exec is upgraded in-place to Backup Exec 21.
7. QoreStor is supported on Linux, ESX & Hyper-V platforms.
8. The Quest packaged 4.x plug-in installer should be used to install the required OST plugin. The Quest packaged 4.0.2 (or newer) plug-in installer now installs two plugin files, one named for Dell and one named for Quest. When configuring storage within Backup Exec 21, please select the “Quest” provider. The Backup Exec adamm.log will document which plugin is being used in the line “OST Server: DELL:hostname:container” versus “OST Server: QUEST:hostname:container”. There are no performance differences between the different named plugins. There are no changes to the container on the Quest QoreStor side. The container may be using either the Symantec or the Veritas OST access protocol. In other words: The Dell-named libstspiDellMT.dll works & is supported by Backup Exec 21. The preferred Quest-named libstspiocaMT.dll works & is supported in Backup Exec 21.

Go to Top of “Disk Targets”

VSS Providers for Offhost backup

This list of tested Volume Shadow Copy Service (VSS) components represents what has been tested in Veritas labs, or in Veritas-supervised partner labs. To ensure compatibility, Veritas, the device manufacturers, and the operating system vendor must support the combination of VSS components. Note: The Backup Exec Advanced Disk Based Backup Option, now part of the Enterprise Server Option, is required for VSS. See the Administrator’s Guide for more details on usage of the VSS provider.

Please Note:

1. The provider version and array firmware listed in this section are the minimum levels that are supported. Where more than one entry level is listed in these “Minimum” columns, this implies a newer version has been tested. The earlier versions are the minimum versions required. The hardware vendor may specify rules for pairing of the provider and firmware versions.

2. The Array Firmware listed in this section are the minimum levels that are supported.

3. The Advanced Open File job options are not supported for use with Dynamic Disk Snapshots. Go to Top of “VSS Providers for Offhost backup”

Dell EMC

1. Only basic disks are supported, per the VSS provider.
2. For the older provider (CLARiiON VSS Provider), only Snapshots are supported. Clones are not supported. The newer provider (Solutions Enabler with VSS Provider) does not have this limitation.
3. The MD3000/MD3000i does not support concurrent multi-volume snapshot (includes Mount Points).

Go to Top of “VSS Providers for Offhost backup”

Fujitsu

1. Only basic disks are supported, per the VSS provider.
2. Series S2 platforms require a v2.x provider.
3. The ETERNUS DX60 S2 requires a v1.x provider.

Go to Top of “VSS Providers for Offhost backup”

Hewlett Packard Enterprise

1. Only basic disks are supported, per the VSS provider.
2. The minimum VSS provider for Windows 2008 is 5.01.00.02.

Go to Top of “VSS Providers for Offhost backup”

Hitachi

1. Only basic disks are supported, per the VSS provider.

Go to Top of “VSS Providers for Offhost backup”

IBM

1. Only basic disks are supported, per the VSS provider.
2. Only Snapshots are supported. Clones are not currently supported.
3. In order to use the ADBO VSS feature, the IBM “Flash Copy” Premium Feature must be purchased.

Go to Top of “VSS Providers for Offhost backup”

Imation

Go to Top of “VSS Providers for Offhost backup”

LeftHand Networks

Go to Top of “VSS Providers for Offhost backup”

LSI Logic

1. Only basic disks are supported, per the VSS provider.

Go to Top of “VSS Providers for Offhost backup”

NEC

1. Only Replication Control (full copy method) is supported.

Go to Top of “VSS Providers for Offhost backup”

Oracle

1. Only basic disks are supported, per the VSS provider.
2. Requires Sun ‘Data Snapshot’ Software

Go to Top of “VSS Providers for Offhost backup”

SGI

1. Only basic disks are supported, per the VSS provider.
2. Requires SGI ‘SnapCopy’ Software

Go to Top of “VSS Providers for Offhost backup”

StorageTek

1. Only basic disks are supported, per the VSS provider.

Go to Top of “VSS Providers for Offhost backup”

Sun

1. Only basic disks are supported, per the VSS provider.
2. Requires Sun ‘Data Snapshot’ Software

Go to Top of “VSS Providers for Offhost backup”

Xiotech

Go to Top of “VSS Providers for Offhost backup”

Xyratex

Go to Top of “Document”

Virtual Tape Libraries with Drives

The virtual tape device support information is listed below. This information is organized by vendor and provides information on the level of software tested, inquiry string (vendor ID + product ID), and any other important notes about the hardware and its compatibility.

Please Note:

1. The virtual tape device software listed in this section are the minimum software levels that are supported. Where more than one software level is listed, this implies a newer version has been tested. The earlier software version is the minimum version required.

2. Configure the virtual device with the unique inquiry string as listed in this document. Emulating other devices is not supported.

3. For each virtual library only the virtual tape drives that are listed are supported. This information can be found with each virtual section. Other virtual tape drive types are not supported even if the real device is supported with Backup Exec.

4. Do not fill up the disk space on a virtual device. Doing so may cause unpredictable behavior of the device. The device vendor will then have to recover from any errors that result from a full disk.

5. When moving virtual volumes to physical media it works best if the virtual device has a volume size that is dynamic. Make sure that the virtual volume is slightly smaller than the physical volume. When you migrate the data to physical media you will need to ensure that there is enough space on the physical device in order to accommodate the virtual volume size.

6. It is highly recommended that Backup Exec move virtual volumes to physical media so that the data can be restored directly from physical media rather than needing to utilize the virtual device as an intermediary restoration point. If the virtual tape library moves virtual volumes to physical media Backup Exec is not aware of the physical media and may not be able to recover that data directly from that physical media.

7. When a virtual volume becomes overwriteable, the virtual device is not aware that the data is no longer needed. When Backup Exec overwrites that virtual volume the virtual library is aware that the rest of the data is not needed and it can free up the disk space. Because of this, the virtual device may appear to be much closer to capacity than it really is.

8. Tested iSCSI versions of virtual tape libraries are listed in the “iSCSI Solutions” section, under the “SAN Infrastructure components” bookmark. Please reference the limitations listed in that section.

9. The software versions documented here are obtained from the library interface (web or physical) and may not match the firmware version logged in the adamm.log.

10. All VTLs shared with the Linux server(s) must be approved for both RMAL and ESO. Zoning or LUN masking are possible methods of preventing Linux servers from seeing a VTL not approved for RMAL. Go to Top of “Virtual Tape Libraries with Drives”

Virtual Tape Library/Drive Legend

Virtual Tape Library/Drive Legend | Dell EMC | Dell EMC Data Domain | FalconStor | Fujitsu | H3C | Hewlett Packard Enterprise | IBM | NetApp | Overland Storage | Quantum | Quest | SEPATON | Virtual Tape Library Families Go to Top of “Virtual Tape Libraries with Drives”

Dell EMC

Go to Top of “Virtual Tape Libraries with Drives”

Dell EMC Data Domain

1. Both the “D_DOMAINRESTORER_L180” and “EMC^^^^^DDVTL” library inquiry strings are supported when using DDOS 5.5 (or higher).
2. VTLs are not shareable between servers. Each VTL must be configured with LUN masking so that it can only be seen by 1 server to prevent interference.

Go to Top of “Virtual Tape Libraries with Drives”

FalconStor

Go to Top of “Virtual Tape Libraries with Drives”

Fujitsu

1. Capacity and compression reporting is not currently supported for this device.
2. The ETERNUS line was previously known as the CentricStor.
3. Backup Exec supports Fujitsu’s Path-to-Tape (PTT) feature available on this VTL. PTT enables Backup Exec duplication jobs to move data directly from virtual tape to physical tape while off-loading the actual copying of data from the Backup Exec server to the VTL. This is referred to as “DirectCopy to tape” in the Backup Exec Administrator’s Guide.
4. The default port for Backup Exec remote agents may conflict with the NDMP port used for the Path-to-Tape feature. Refer to the following technote to change the default port: https://www.veritas.com/content/support/en_US/article.100016014
5. This VTL also supports the following emulated tape drives: HPE Ultrium 1-SCSI, HPE Ultrium 2-SCSI, HPE Ultrium 3-SCSI, HPE Ultrium 4-SCSI, HPE Ultrium 5-SCSI, IBM ULTRIUM-TD1, IBM ULTRIUM-TD2, IBM ULTRIUM-TD3, IBM ULTRIUM-TD4, and the IBM ULTRIUM-TD5. Older device software versions may not support newer emulated drive generations.

Go to Top of “Virtual Tape Libraries with Drives”

H3C

1. This VTL also supports HPE LTO2, LTO3, LTO4, and LTO5 tape drive emulation. These combinations are also supported.

Go to Top of “Virtual Tape Libraries with Drives”

Hewlett Packard Enterprise

1. This VTL also supports HPE LTO2, LTO3, LTO4, and LTO5 tape drive emulation. These combinations are also supported.
2. Version 3.14 code is the minimum required for the StoreOnce 3520, 3540, 5100, & 5500 devices. The code is not backwards compatible with earlier versions of StoreOnce hardware. For more information, please contact Hewlett Packard Enterprise.
3. This VTL also supports HPE LTO3 and HPE LTO2 tape drive emulation. These combinations are also supported.

Go to Top of “Virtual Tape Libraries with Drives”

IBM

1. Capacity and compression reporting is not currently supported for this device.
2. Minimum firmware level of 2.2.3.16 is required.

Go to Top of “Virtual Tape Libraries with Drives”

NetApp

Go to Top of “Virtual Tape Libraries with Drives”

Overland Storage

Go to Top of “Virtual Tape Libraries with Drives”

Quantum

1. This VTL also supports the following emulated tape drives: HP Ultrium 2-SCSI, HP Ultrium 3-SCSI, HP Ultrium 4-SCSI, HP Ultrium 5-SCSI, IBM ULTRIUM-TD2, IBM ULTRIUM-TD3, IBM ULTRIUM-TD4, and the IBM ULTRIUM-TD5.
2. Backup Exec supports Quantum’s Path-to-Tape (PTT) feature available on this VTL. PTT enables Backup Exec duplication jobs to move data directly from virtual tape to physical tape while off-loading the actual copying of data from the Backup Exec server to the VTL. This is referred to as “DirectCopy to tape” in the Backup Exec Administrator’s Guide.
3. The default port for Backup Exec remote agents may conflict with the NDMP port used for the Path-to-Tape feature. Refer to the following technote to change the default port: https://www.veritas.com/content/support/en_US/article.100016014
4. In order to support 2TB capacity expansions for the DXi6700, Quantum DXi Software 2.0.1 (or higher) is required. Please contact Quantum Service [email protected]
5. This VTL also supports the following emulated tape drives: HPE Ultrium 1-SCSI, HPE Ultrium 2-SCSI, HPE Ultrium 3-SCSI, HPE Ultrium 4-SCSI, IBM ULTRIUM-TD1, IBM ULTRIUM-TD2, IBM ULTRIUM-TD3, IBM ULTRIUM-TD4, Quantum LTO-2, Quantum LTO-3, Quantum SDLT 600, and the Quantum DLT-S4.

Go to Top of “Virtual Tape Libraries with Drives”

Quest

1. Each VTL may only be assigned to a single server (no sharing).
2. Minimum DR software of 4.0.2 is required for the Quest inquiry string.
3. Please see the Quest Migration Guide for changing Dell containers to Quest containers https://support.quest.com/download/downloads?id=6084223

Go to Top of “Virtual Tape Libraries with Drives”

SEPATON

Go to Top of “Virtual Tape Libraries with Drives”

Virtual Tape Library Families

When a hardware family of devices is listed, refer to this section for a definition of family members. Generally speaking, the family name and members are defined by the hardware manufacturer, and share common operational traits. In some cases, a specific member of the family may not be supported in the same fashion as the other members. When this occurs, a footnote in the hardware category section will indentify this limitation. Go to Top of “Virtual Tape Library Families”

Dell EMC

Go to Top of “Virtual Tape Library Families”

Dell EMC Data Domain

Go to Top of “Virtual Tape Library Families”

Fujitsu

Go to Top of “Virtual Tape Library Families”

Hewlett Packard Enterprise

Go to Top of “Virtual Tape Library Families”

IBM

Go to Top of “Virtual Tape Library Families”

NetApp

Go to Top of “Virtual Tape Library Families”

Quantum

Go to Top of “Virtual Tape Library Families”

Quest

Go to Top of “Virtual Tape Library Families”

SEPATON

Go to Top of “Document”

Tape Drives

The tape drive support information is listed below. This information is organized by vendor and provides information on the tape drives tested, the supported Inquiry Strings, the type of interface, media type, and any special notes on a per device basis.

Please Note:

1. To ensure support, a device must be supported by Veritas and the device manufacturer.

2. Unless otherwise noted, Veritas tape class drivers were used when testing Windows-supported devices.

3. At times the manufacturer may refer to their devices by product name, which differs from the model name.

4. WORM is supported only on tape drives with a footnote indicating WORM support and a possible minimum firmware or software level. These footnotes are documented in this stand-alone tape drive section. To determine if WORM is supported in an automation environment. (i.e. physical tape libraries), please refer to the tape drive manufacturers stand-alone drive section and check for a footnote. If WORM is supported in the manufacturers drive section, then it is supported in all automation, unless documented otherwise in the automation section.

5. Hardware encryption is supported only on tape drives with a footnote indicating hardware encryption support and a possible minimum firmware or software level. These footnotes are documented in this stand-alone tape drive section. To determine if hardware encryption is supported in an automation environment. (i.e. physical tape libraries), please refer to the tape drive manufacturers stand-alone drive section and check for a footnote. If hardware encryption is supported in the manufacturers drive section, then it is supported in all automation, unless documented otherwise in the automation section.

6. The “ULTRIUM-TD” and the “ULT3580-TD” inquiry strings are interchangeable (both are supported), unless otherwise indicated. The “ULTRIUM-HH” and the “ULT3580-HH” inquiry strings are interchangeable (both are supported), unless otherwise indicated.

7. Unless specifically stated in technote article https://www.veritas.com/content/support/en_US/article.100021088 , tape libraries or tape drives attached to a RAID controller are not supported.

8. The HPE One Button Disaster Recovery (OBDR) feature is no longer supported with Backup Exec.

9. The LTO ‘Encrypt Only’ feature is currently not supported with any robotic library or tape drive. This new LTO feature is being investigated by Veritas.

10. Backup Exec supports LTO-7 Type M media (also known as M8 cartridges) in the following manner. These are LTO-7 cartridges that have been formatted to a new LTO-8 standard and their native capacity increased from 6TB to 9TB.

• M8 cartridges are only supported with LTO-8 tape drives, either stand-alone tape drives or in an M8 supported tape library.

• M8 cartridges pre-formatted by the media vendor are supported.

• M8 cartridges manually formatted using hardware vendors’ software tools or tape library firmware features (automatic or manual) are supported.

• Backup Exec does NOT have the ability to convert LTO-7 cartridges to M8 format.

• Backup Exec requires version 20 Update 1 (aka 20.1) (or higher) to support hardware encryption on M8 media.

• Backup Exec requires version 20 Update 1 (aka 20.1) (or higher) to provide pre-configured bar code rules and pre-defined media type for M8 cartridges.

• Customers should use caution when re-labeling the bar code on used LTO-7 cartridges as an LTO-7 cartridge with good data could be accidentally erased in a tape library with firmware that automatically re-initializes tapes with M8 bar codes.

• For details on M8 (formatting methods, technical information, supported barcodes, etc.) please consult the tape hardware documentation or vendor.

• For details on M8 please see https://www.lto.org/technology/typem/ Go to Top of “Tape Drives”

Tape Drive Legend

Tape Drive Legend | actidata | Dell EMC | Hewlett Packard Enterprise | IBM | Imation | Oracle | Quantum | StorageTek | Sun | Tandberg | UNITEX Go to Top of “Tape Drives”

actidata

Go to Top of “Tape Drives”

Dell EMC

1. This is a rack mounted enclosure for Dell EMC certified tape drives and should not be confused with actual Dell EMC tape drives.
2. WORM tape is supported with this drive.
3. T10 Hardware Encryption is supported.

Go to Top of “Tape Drives”

Hewlett Packard Enterprise

1. WORM tape is supported with this drive.
2. For all USB tape drives, the vendor’s device driver must be loaded prior to starting Backup Exec.
3. T10 Hardware Encryption is supported.
4. Half-Height drive configuration.
5. Supported in the HPE BladeSystem c-Class chassis.

Go to Top of “Tape Drives”

IBM

1. WORM tape is supported with this drive.
2. T10 Hardware Encryption is supported.
3. Capacity and compression reporting is not currently supported for this device.
4. WORM tape is not supported with this drive.
5. WORM tape is supported with initial firmware level 5480

Go to Top of “Tape Drives”

Imation

1. WORM tape is supported with this drive.
2. T10 Hardware Encryption is supported.

Go to Top of “Tape Drives”

Oracle

1. WORM tape is supported with this drive.

Go to Top of “Tape Drives”

Quantum