This document lists the available operating systems, platforms, and applications specifically supported by Veritas to be compatible with Backup Exec ™ 21.

The following guidelines regarding this Software Compatibility List (SCL) should be understood:

• Veritas support of 3rd party manufacturer products:
Veritas will cooperate with 3rd party vendors and attempt to assist in the diagnosis of problems found between the 3rd party products and Veritas products. Veritas Technical Support, for the combination of Veritas and 3rd party products listed in this document, is conditional on the 3rd party product being supported by the original manufacturer or vendor. If the original vendor has ceased providing support for a version of their product, Veritas also will no longer be able to provide support on that product in combination with our products.

• Minor update version support:
The contents of this document including 3rd party applications, databases, operating systems, in combination with Veritas products represent what has been tested in Veritas labs, or in Veritas-supervised partner labs, but is not intended to be a complete list of supported products and versions. Manufacturers of these products may frequently release minor version updates to their products as maintenance during their product’s normal life cycle. (e.g. version 1.x.x.x) that may not be explicitly listed in this document. In these situations where the base or major version of the product is listed as supported in this document but the minor maintenance update is not, Veritas will provide “reasonable effort” support on these versions until specific testing of them has completed.

• Not every combination of software and hardware has been tested:
Veritas provides reasonable effort to qualify Backup Exec with as many different operating systems, service packs, hardware platforms, database application service packs, and other applications as possible. However, due to the number of combinations, it is not possible to test all combinations for compatibility. If a particular service pack or version is not listed as specifically supported by Veritas, it may work fine but it has not been explicitly tested by Veritas with Backup Exec and may not be eligible for support.

• 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. Veritas does 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 Veritas has no obligation to investigate or attempt to resolve the problem.

• What’s New
This document reflects updates for Backup Exec 21.1
For details about Backup Exec 21.1, see: https://www.veritas.com/content/support/en_US/downloads/detail.REL741973

Support for Cloud File Share
• Azure File Share
• AWS FSx for Windows File Server

Agent for Windows Compatibility
• Windows 10 – Service Pack 2004
• Windows Server Semi-Annual Channel- Windows Server 2004

Agent for Linux
• Red Hat 6.10
• Red Hat 8.2
• Oracle Linux 8.2
• Ubuntu 19.10
• Ubuntu 20.04
• Debian 10 Update 4
• Debian 10 Update 5
• Debian 9 Update 9
• Debian 9 Update 10
• Debian 9 Update 11
• Debian 9 Update 12
• Debian 9 Update 13

Remote Media Agent for Linux
• Red Hat 6.10
• Red Hat 8.2

Agent for VMware Compatibility
• vSphere 7 Update 1

Agent for Applications and Databases
• Microsoft SharePoint Server 2019
• Oracle 18c

Cluster Support
• Added support for Microsoft SQL AG

•Refer to Retiring Soon section for items planned for end-of-life.

Introduction | Getting Started | Backup Exec Server Operating System Compatibility | Agent Operating System Compatibility | Agent for Applications and Databases Compatibility | Agent for VMware and Hyper-V Compatibility | Cloud File Share Compatibility | Backup Exec Upgrade Compatibility | Backup Exec Feature Specific Compatibility | 3rd Party Software Compatibility | End-of-Life information

Getting Started

Backup Exec Documentation

Supported languages for the Backup Exec

• Backup Exec supports only the following languages. No other combination of Backup Exec and operating system language configurations are tested or qualified.

Minimum System Requirements

Certifications

Backup Exec Server Operating System Compatibility

Go to Top of “Backup Exec Server Operating System Compatibility”

Windows Operating System Compatibility

Go to Top of “Windows Operating System Compatibility”

Microsoft

Microsoft – Windows Server 2008 R2

1. To install Backup Exec on Windows 2008 R2 Operating System. Please refer to the following Tech note: https://www.veritas.com/content/support/en_US/article.100047607.html

Microsoft – Windows Server 2012

Microsoft – Windows Server 2012 R2

Microsoft – Windows Server 2016

Microsoft – Windows Server 2019

1. Backup Exec installed on Windows Server 2019, does not support GRT processing for VMware virtual machines running Windows Server 2016 or later. Refer to the technote for details : https://www.veritas.com/support/en_US/article.100044076

Microsoft – Windows Small Business Server 2011

Agent Operating System Compatibility

Agent for Windows Compatibility

Notes:
• To install Remote Agent on Windows 2008 or 2008 R2 ( Including Essential Business and Small Business Server edition ) Operating System. Please refer to the following Tech note: https://www.veritas.com/content/support/en_US/article.100047607.html
• Backup Exec 16 and 20 Agents are backwards compatible with Backup Exec 21 servers for the purpose of upgrades only. This configuration is not recommended or supported for extended periods. Every effort should be made to get all Backup Exec components to the same version as soon as possible.
• The Windows Operating Systems listed below are supported using both the Full version and Server Core version, where applicable.

Microsoft

Microsoft – Windows 7

Go to Top of “Microsoft”

Microsoft – Windows 8

Microsoft – Windows 8.1

Go to Top of “Microsoft”

Microsoft – Windows 10

Microsoft – Windows 10 LTSB 2016

Microsoft – Windows 10 LTSC 2019

Microsoft – Windows Essential Business Server 2008

Microsoft – Windows Server 2008

Microsoft – Windows Server 2008 R2

Microsoft – Windows Server 2012

Microsoft – Windows Server 2012 R2

Microsoft – Windows Server 2016

Microsoft – Windows Server 2019

Microsoft – Windows Server Semi-Annual Channel

Microsoft – Windows Small Business Server 2008

Microsoft – Windows Small Business Server 2011

Microsoft – Windows Vista

Agent for Linux Compatibility

Notes:
• File system support includes ext2, ext3, ext4, VxFS, REISER and JFS.
• The Remote Agent for Linux Servers (RALUS) does not support Linux servers that have been installed using the ‘minimal’ installation option.
• The Advanced Open File feature for Agent for Linux is supported only on select Red Hat Enterprise Linux (RHEL) and SUSE Enterprise Linux Server (SLES) platforms. Please refer to the RHEL and SLES footnotes to identify the supported versions.
• Some versions of Linux may require that you install the libstdc++.so.5 package. http://www.veritas.com/docs/TECH52256
• The Agent for Linux requires that the Linux server have Perl 5.8.8 or later installed.

Canonical

Citrix

Debian

Oracle

1. Refer to the following Tech note for installing the Backup Exec Remote Agent for Linux (RALUS) on Oracle Linux 8.x https://www.veritas.com/content/support/en_US/article.100046985.html
2. Refer to the following Tech note for Push installation of Linux Agent on Oracle Linux 8.x https://www.veritas.com/content/support/en_US/article.100047387.html

Red Hat

1. Advanced Open File Option for Linux file system support includes ext2, ext3 and ext4.
2. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
3. File system support includes XFS.
4. Refer to the following Tech note for installing the Backup Exec Remote Agent for Linux (RALUS) on Redhat 8.x https://www.veritas.com/content/support/en_US/article.100046985.html
5. Refer to the following Tech note for Push installation of Linux Agent on Redhat 8.x https://www.veritas.com/content/support/en_US/article.100047387.html

SUSE

1. Advanced Open File Option for Linux file system support includes ext2, ext3 and ext4.
2. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
3. Advanced Open File Option is not supported for BTRFS.
4. File system support includes Btrfs.( Backup jobs will complete with exception )
5. Advanced Open File Option is not supported.

The CentOS Project

Agent for Unix Compatibility

IBM

Sun

Remote Media Agent for Linux Compatibility

• The Advanced Open File feature for Remote Media Agent for Linux is supported only on select Red Hat Enterprise Linux (RHEL) and Novell SUSE Enterprise Linux Server (SLES) platforms. Please refer to the RHEL and SLES footnotes to identify the supported versions.
• The Remote Media Agent for Linux requires that the Linux server have Perl 5.8.8 or later installed.

Red Hat

1. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
2. File system support includes ext2, ext3, and ext4.
3. File system support includes XFS.
4. Refer to the following Tech note for installing the Backup Exec Remote Agent for Linux (RALUS) on Redhat 8.x https://www.veritas.com/content/support/en_US/article.100046985.html
5. Refer to the following Tech note for Push installation of Linux Agent on Redhat 8.x https://www.veritas.com/content/support/en_US/article.100047387.html

SUSE

1. Backup Exec client-side deduplication is supported for 64-bit Linux systems.
2. File system support includes Btrfs.( Backup jobs will complete with exception )
3. libncurses5 is required to run mktls utility.
4. Advanced Open File Option is not supported.

Agent for Applications and Databases Compatibility

Notes:
• The Backup Exec Agent for Oracle on Windows or Linux Servers does not support multiple Oracle database versions that are installed on the same computer.
• Advanced Disk-based Option off-host backups of clustered Exchange databases in Exchange 2010/2013 Clustering solutions are not supported.
• Legacy mailbox backups are no longer supported with any version of Exchange. This functionality has been replaced by the Granular Recovery Technology (GRT) feature.

Microsoft

Microsoft – Exchange

1. To back up Microsoft Exchange Server 2010, you must install Backup Exec on a Microsoft Windows 2008 SP2 64-bit server or newer.
2. Backup Exec does not support Microsoft Exchange Management role scopes.
3. To back up Microsoft Exchange Server 2013, you must install Backup Exec on a Microsoft Windows 2008 R2 SP1 64-bit server or newer.
4. To back up Microsoft Exchange Server 2016, you must install Backup Exec on a Microsoft Windows 2012 64-bit server or newer.
5. To back up Microsoft Exchange Server 2019, you must install Backup Exec on a Microsoft Windows 2012 64-bit server or newer.

Microsoft – SharePoint Foundation

Microsoft – SharePoint Server

Microsoft – SQL Express

Microsoft – SQL Server

1. For mirroring and log shipping, only Full/Copy backups on the primary nodes are supported.
2. For “AlwaysOn Availability Groups”, the Full backup method is supported for the Primary Replica SQL instance, or the Full Copy backup method is supported for the Secondary Replica SQL instance. Backups and restores are not supported via the SQL Listener name. Please see the following TechNote for further details: http://www.veritas.com/docs/000021670
3. Backup Exec does not support in-memory databases.

Microsoft – Windows Active Directory

1. To perform a GRT-enabled backup of an Active Directory Application Server on Windows 2012 R2 or later, the Backup Exec server must be the same version or a later version of Microsoft Windows. Please see the following TechNote for further details http://www.veritas.com/docs/000087447.

Oracle

1. Oracle Fail-safe is supported only on Windows.
2. Oracle Real Application Cluster (RAC) support for Windows and Linux.
3. Oracle versions Enterprise, Standard, Standard One, Lite, and Personal supported.
4. Supported on all supported Windows and Linux versions.
5. Supported with ASM, OCFS and all supported file systems by operating systems.
6. The Oracle Agent does not run on 32-bit versions of Oracle installed on a 64-bit system.
7. Oracle Fail-safe is not supported.

Veritas

1. Backup Exec Migrator for Enterprise Vault is available for this version.
2. Although this version of Enterprise Vault supports databases on SQL “Always On Availability Groups”, the Backup Exec Agent for Enterprise Vault does not support the protection.

Agent for VMware and Hyper-V Compatibility

Agent for Hyper-V Compatibility

Microsoft

1. VSS writers report as failed on a Windows Server 2008-based virtual machine. http://support.microsoft.com/kb/2952783

Hyper-V: Partition / Volume Structure

Hyper-V: File System Support

Hyper-V: VM Disk Structure

Hyper-V: Advanced Configuration

Agent for VMware Compatibility

VMware

1. Install “VMware ESXi 6.0, Patch Release ESXi600-201511001 (2137545)” for consistent backups. This ESX patch is mandatory, according to VMware, to fix the data loss situation reported in VMware KB article 2136854. For more information about the cause and the resolution of this issue, see: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2136854
2. For BE 20.1, Protection of virtual machines with hardware version 14 is supported. However with exceptions, that “Conversion”, “Instant Recovery” & “redirected restores (most recent hardware version option)” targeted to vSphere 6.7, will create virtual machines with hardware version 13.
3. From BE 20.2 onwards, there is complete support for vSphere 6.7 (including hardware version v14).

VMware: vCenter Compatibility

VMware Cloud Solutions

1. The nbd, nbdssl, and san transport modes are not supported in VMware Cloud environment.
2. Backup Exec’s Instant Recovery and Recovery Ready features are not supported in VMware Cloud environment.
3. For more information on pre-requisites and configuration of Backup Exec in VMC please refer, https://kb.vmware.com/s/article/80963

VMware: Partition / Volume Structure

VMware: File System Support

VMware: VM Disk Structure

Cloud File Share Compatibility

Notes:
•Backup Exec can be deployed on-premises or in the cloud, to protect Azure file and Amazon FSx for Windows File Server.
•Backup throughput rate depends on the Internet bandwidth available between the on-premises network and the Amazon or Azure infrastructure.
•Ensure Amazon FSx for Windows File Server or Azure Files accessible and you can access them as SMB shares from the Backup Exec server. You must have full rights for Amazon FSx for Windows File Server and Azure Files.

Backup Exec Upgrade Compatibility

Upgrade and Rolling Upgrade Compatibility

Notes:
– Features or requirements that are no longer supported by Backup Exec may affect your ability to restore backed-up resources. Please review the section titled ‘Features or requirements no longer supported by Backup Exec’ in this document.
– Upgrade to BE 21 and above on Windows 2008 R2 require some Operating System patches. For more details, refer to the following technote: https://www.veritas.com/content/support/en_US/article.100047607.html Go to Top of “Upgrade and Rolling Upgrade Compatibility”

Direct upgrade to Backup Exec 21

Agent versions that can be temporarily used with Backup Exec 21

1. You can use previous versions of an Agent with Backup Exec during a rolling upgrade. A warning message is displayed in the job log when previous versions of an Agent are used, but backups and restores can continue normally. New features are disabled until you upgrade the Agent to the same version as the Backup Exec server.

Temporarily Manage Backup Exec Servers with Backup Exec 21

1. You can perform rolling upgrades in the Backup Exec 20 Central Admin Server Option (CASO) environment, which is included in the Enterprise Server Option. A rolling upgrade lets you upgrade the central administration server from the previous version to the current version first, and then upgrade the managed Backup Exec servers from the previous version to the current version over a period of time. A warning message is displayed in the job log when previous versions of a server are used, but backups and restores can continue normally. New features are disabled until you upgrade the version of all of the Backup Exec servers.

Backup Exec Feature Specific Compatibility

Instant Recovery (IR)

Minimum requirements to use the Instant Recovery feature:

Microsoft Hyper-V:
• Backup Server on Windows Server 2008 SP2 or later

VMware vSphere:
• Backup Server on Windows Server 2012 or later
• Server for NFS (Windows Role) installed on Backup Exec Server

Simplified Disaster Recovery (SDR)

Notes:
• The Create Disaster Recovery Disk Wizard is not supported on 32 bit systems, only use on 64 bit systems.
• SDR Disk creation using Microsoft Assessment and Deployment Kit (ADK) v10 is supported on all Windows OS versions from Windows Server 2008 R2 to Windows Server 2016.
• SDR Disk creation on Windows Server 2008 SP2 is supported using Microsoft Assessment and Deployment Kit (ADK) v8.1.
• The Agent for Linux and the Remote Media Agent for Linux do not support the Simplified Disaster Recovery feature.
• If the Backup Exec server on which you want to create the Simplified Disaster Recovery disk image does not have an internet connection, and does not have ADK installed, instructions are provided on how to install the ADK. You can then use the Create Simplified Disaster Recovery Disk Wizard to create the recovery disk.
• SDR Disk creation using Microsoft Assessment and Deployment Kit (ADK) 1809 is supported on Windows Server 2019.

Backup Exec Servers recoverable by SDR

Microsoft

Microsoft – Windows Essential Business Server 2008

Microsoft – Windows Server 2008

Microsoft – Windows Server 2008 R2

Microsoft – Windows Server 2012

Microsoft – Windows Server 2012 R2

Microsoft – Windows Server 2016

Microsoft – Windows Server 2019

Microsoft – Windows Small Business Server 2008

Microsoft – Windows Small Business Server 2011

Agent for Windows recoverable by SDR

Microsoft

Microsoft – Windows 7

Microsoft – Windows 8

Microsoft – Windows 8.1

Microsoft – Windows 10

Microsoft – Windows 10 LTSB 2016

Microsoft – Windows 10 LTSC 2019

Microsoft – Windows Essential Business Server 2008

Microsoft – Windows Server 2008

Microsoft – Windows Server 2008 R2

Microsoft – Windows Server 2012

Microsoft – Windows Server 2012 R2

Microsoft – Windows Server 2016

Microsoft – Windows Server 2019

Microsoft – Windows Server Semi-Annual Channel

Microsoft – Windows Small Business Server 2008

Microsoft – Windows Small Business Server 2011

Microsoft – Windows Vista

ISO Creation Supported by SDR

Microsoft

Microsoft – Windows 7

Microsoft – Windows 8

Microsoft – Windows 8.1

Microsoft – Windows 10

Microsoft – Windows 10 LTSB 2016

Microsoft – Windows 10 LTSC 2019

Microsoft – Windows Essential Business Server 2008

Microsoft – Windows Server 2008

Microsoft – Windows Server 2008 R2

Microsoft – Windows Server 2012

Microsoft – Windows Server 2012 R2

Microsoft – Windows Server 2016

Microsoft – Windows Server 2019

Microsoft – Windows Small Business Server 2008

Microsoft – Windows Small Business Server 2011

Convert to Virtual

Notes:
• The Convert to Virtual feature supports both Hyper-V and VMware ESX environments.
• Windows Server 2008 SP2 is not supported as a target Hyper-V host for the virtual machine. The target machine must be running Windows Server 2008 R2, or later.
• For the Convert to Virtual feature, conversion of Fibre Channel disk devices (not used as Windows volumes), USB devices, Removable disks, and ISCI disks are not supported. Both Hyper-V and VMware have these limitations.
• VMware Converter does not convert GPT disks.
• Physical-to-virtual and one-time conversions of 32-bit servers to VMware are no longer supported. However, Backup-to-Virtual and conversion from Point-In-Time are supported for 32-bit servers to VMware.

Supported Operating Systems

1. Windows 2008 R2 SP1 or later required

Supported Applications

1. Requires SQL Server/Express 2005 SP4

Remote Admin Console (RAC)

Notes:
The Remote Administrator Console can be installed on any operating system listed in the “Backup Exec 20 Server – Operating System Compatibility” section and on any operating systems listed in the following table. Go to Top of “Remote Admin Console (RAC)”

Additional Operating System Compatibility

Backup Exec Server Compatibility

Backup Exec Database Repository Compatibility

The following data management systems can be used for the Backup Exec Database (BEDB) when installing Backup Exec.

Backup Exec Management Command Line Interface

Note:
• BEMCLI is installed with Backup Exec and replaces BEMCMD.

Minimum requirements to run BEMCLI:

• Windows PowerShell V2 or V3

• .NET 3.5 SP1 or higher versions

• PowerShell’s execution policy must set to a value that is less restrictive than Restricted (e.g. AllSigned). For more information, see Get-Help Set-ExecutionPolicy.

Exchange GRT restore to PST file

This feature allows a user to restore directly to a PST file from a GRT enabled backup of a Exchange database. The PST file must use Outlook friendly mailbox folder structure of being beneath the ‘Top of Information Store’ only. Sub-folder below this level are not supported.

Outlook versions required on the target server:

• 32-bit Outlook 2010

• Outlook 2013 is not supported.

• 64-bit Outlook clients in any version are not supported.

File naming convention:

• Restore creates PST file name which matches mailbox display name in UI

• File name collisions handled with ‘(n)’ suffix. IE: John Smith [John Smith].pst and John Smith [John Smith](1).pst

File size limits:

• The maximum size of the .PST file is 20 GB. If the restore exceeds the size limit, the data is spanned across multiple .PST files which are numbered consecutively.
• When you restore multiple mailboxes in the same job, each mailbox that you restore has a PST file.

Microsoft articles on how to change PST file size limits:
• http://support.microsoft.com/kb/832925
• http://support.microsoft.com/kb/830336

3rd Party Software Compatibility

32-bit and 64-bit Interoperability

Notes:
• The 64-bit Backup Exec server table illustrates interoperability between a 64-bit Backup Exec server and various remote systems and applications.
• If an agent or option is not listed in the tables below, it is supported on both 32-bit and 64-bit (64-bit) platforms. Go to Top of “32-bit and 64-bit Interoperability”

64-bit Backup Exec server

1. SQL Server/Express 2008 32-bit and 64-bit versions are supported as database backend servers.

Cluster Support

For Windows operating systems, Backup Exec supports file share clusters for all supported versions and variations of Windows that feature cluster services (MSCS).

Note:
• File System Archiving cannot be done from the Windows 2008 cluster shares. Windows 2008 R2 cluster shares are required.

1. Window Enterprise Edition is still required since a DAG (Database Availability Group) still uses pieces of Windows Failover Clustering.

End-of-Life information

Features and requirements no longer supported by Backup Exec

EOL Notice: These operating systems, backward compatibility for restores, rolling upgrades, third-party software applications, and Veritas products are no longer supported for use with this version of Backup Exec for Windows.
• The Version EOL Started identifies the version of Backup Exec that no longer provides the support and includes all subsequent releases. Go to Top of “Features and requirements no longer supported by Backup Exec”

Backup Exec Feature

Retiring Soon: Items planned for end-of-life

The Backup Exec Agents, Options, and functionality that are listed in this section may not be listed as supported in a future Software Compatibility List. This list of items may change up until a Feature Pack or new Backup Exec version is released. To help customers plan accordingly, Veritas will provide advance notice of the items that will be unavailable.

Current supportability of these items is not affected. Normal Technical Support lifecycle policies for Veritas enterprise products still apply to these items. To provide Veritas with direct feedback, please use the Veritas Connect Ideas forum located here: http://www.veritas.com/community/backup-and-recovery/ideas Go to Top of “Retiring Soon: Items planned for end-of-life”

Backup Exec Feature