Backup and DR Service end-of-support-life policy
The Backup and DR End-of-Support-Life ("EOSL") Policy covers the process and details regarding the end of support from Backup and DR for third-party systems and software, as well as Backup and DR software and hardware.
Third-party hardware and software include hardware platforms, operating systems, and application software protected by Backup/DR appliances. When a third-party hardware, operating system, or application software/configuration reaches EOSL from the vendor, Backup and DR support for such configurations will be limited to commercially reasonable assistance. Backup and DR will not issue any more hotfixes or updates to support software and hardware systems that are beyond the end of support life from their respective vendors.
For Actifio GO support, see https://docs.actifio.com/Actifio-GO
Supported network protocols
Backup and DR supports data movement over:
iSCSI
Network Block Device (NBD) - this transport mode is used to backup VMware virtual machines.
NFS - Backup and DR supports NFS V3 (only) for capturing and presenting data in following deployment configurations:
Presenting any backups to VMware hosts via a NFS datastore
Presenting a staging disk for agent-based data capture within a Compute Engine or VMware VM
Supported environments for backups
Agent based backups
The Backup and DR agent (connector) can back up and recover supported databases and file systems of supported Microsoft Windows & Linux operating systems in the following environments.
| Application Type | Running on Compute Engine instances 1 | Running on VMware Engine VMs 1 |
|---|---|---|
| Databases | Yes | Yes |
| File Systems | Yes | Yes |
1 CBT on Compute Engine instance and GCVE VMs requires UEFI Secure Boot to be disabled.
Agentless backups
Backup and DR Service supports VM backups in the following environments without needing an agent inside the VM:
Compute Engine instances (leverages Google Persistent Disk snapshot APIs)
VMware Engine VMs (leverages VMware vSphere Storage APIs - Data Protection (formerly known as vStorage APIs for Data Protection or VADP)
Object storage compatibility for OnVault
OnVault supports the following Google Cloud storage.
| Storage Type | Min required Backup and DR Service Version |
|---|---|
| Standard storage | V11.0.1 |
| Nearline storage | V11.0.1 |
| Coldline storage | V11.0.1 |
| Archive storage | V11.0.1 |
Application data virtualization with Backup and DR agent (Connector)
Backup and DR agent (commonly also known as connector) is a lightweight executable that delivers the following advanced capabilities during the data capture and recovery processes.
Application Discovery: Backup and DR agent enables deep discovery of databases and file systems configured on a production host
API integration: Where possible, Backup and DR agents integrate with the application specific native APIs/commands for efficient capture of application data
Change Block Tracking: In situations where the production applications do not have a built-in change block tracking, Backup and DR introduces change block tracking on select platforms
Application aware recovery/mount: Backup and DR agents have built in application awareness. The Backup and DR agent (Connector) enables users to leverage this awareness to instantiate usable instances of applications during recovery mount operations thereby eliminating the need for performing manual/scripted actions post mount.
Generic Application (LVM) Data Capture framework: Backup and DR agents provide a generic framework to capture data from any application running on supported Linux operating systems. This framework provides hooks to call custom scripts to achieve application consistent data capture and application instantiation from backup data.
Microsoft Windows server support
The Backup and DR agent supports the following Microsoft Windows operating systems.
| Operating System Version | Basic Backup and DR agent (Connector) Support | Change Block Tracking Support 1 | Min required Backup and DR agent (Connector) Version |
|---|---|---|---|
| Windows Server 2012 | Yes | Yes | V11.0.1 |
| Windows Server 2012 R2 | Yes | Yes | V11.0.1 |
| Windows Server 2016 | Yes | Yes | V11.0.1 |
| Windows Server 2019 | Yes | Yes | V11.0.1 |
| Windows Server 2022 | Yes | Yes | V11.0.1 |
1 CBT is only supported for Microsoft SQL server.
Linux operating system support
Backup and DR agent (Connector) supports the following Linux (x86) operating systems.
Basic support includes support for file systems and Oracle databases.
Change Block Tracking (CBT) support includes incremental forever backup capability for other databases.
| OS | Version | Basic Backup and DR agent (Connector) Support | Change Block Tracking Support | Min required Backup and DR agent (Connector) Version |
|---|---|---|---|---|
| RHEL1, 4, 5 | 7.0-7.8 | Yes | Yes | V11.0.1 |
| 7.9 | Yes | Yes | V11.0.1 | |
| 8.0-8.17 | Yes | Yes | V11.0.1 | |
| 8.2 | Yes | Yes | V11.0.1 | |
| 8.3 | Yes | Yes | V11.0.1 | |
| 8.4 | Yes | Yes | V11.0.1 | |
| 8.5 | Yes | Yes | V11.0.1 | |
| 8.6 | Yes | Yes | V11.0.4 | |
| 8.7 | Yes | Yes | V11.0.5 | |
| 8.8 | Yes | No | V11.0.8 | |
| 8.9 | Yes | No | V11.0.9 | |
| 9.0 | Yes | No | V11.0.4 | |
| 9.2 | Yes | No | V11.0.8 | |
| 9.3 | Yes | No | V11.0.9 | |
| RHEL for SAP 1, 5 | 7.7 | Yes | Yes | V11.0.1 |
| 7.9 | Yes | Yes | V11.0.1 | |
| 8.1 | Yes | Yes | V11.0.1 | |
| 8.2 | Yes | Yes | V11.0.1 | |
| 8.4 | Yes | Yes | V11.0.1 | |
| 8.6 | Yes | Yes | V11.0.4 | |
| 8.8 | Yes | No | V11.0.8 | |
| 9.0 | Yes | No | V11.0.8 | |
| 9.2 | Yes | No | V11.0.8 | |
| SLES 1, 3, 6 | 12 SP0-4 | Yes | Yes | V11.0.1 |
| 12 SP5 | Yes | Yes | V11.0.1 | |
| 15 SP0-1 | Yes | Yes | V11.0.1 | |
| 15 SP2 | Yes | Yes | V11.0.1 | |
| 15 SP3 | Yes | Yes | V11.0.1 | |
| 15 SP4 | Yes | Yes | V11.0.4 | |
| 15 SP5 | Yes | Yes | V11.0.9 | |
| SLES for SAP 1, 3, 6 | 12 SP4 | Yes | Yes | V11.0.1 |
| 12 SP5 | Yes | Yes | V11.0.1 | |
| 15 SP1 | Yes | Yes | V11.0.1 | |
| 15 SP2 | Yes | Yes | V11.0.1 | |
| 15 SP3 | Yes | Yes | V11.0.1 | |
| 15 SP4 | Yes | Yes | V11.0.4 | |
| 15 SP5 | Yes | Yes | V11.0.9 | |
| Rocky Linux 5 | 8.7 | Yes | Yes | V11.0.7 |
| 8.8 | Yes | No | V11.0.8 | |
| 8.9 | Yes | No | V11.0.9 | |
| 9.0 | Yes | No | V11.0.8 | |
| 9.1 | Yes | No | V11.0.8 | |
| 9.2 | Yes | No | V11.0.8 | |
| 9.3 | Yes | No | V11.0.9 | |
| Rocky Linux optimized for Google Cloud | 8.7 | Yes | No | V11.0.5 |
| 8.8 | Yes | No | V11.0.8 | |
| 8.9 | Yes | No | V11.0.9 | |
| 9.2 | Yes | No | V11.0.8 | |
| 9.3 | Yes | No | V11.0.9 | |
| CentOS 1 | 7.0-7.6 | Yes | Yes | V11.0.1 |
| 7.7 | Yes | Yes | V11.0.1 | |
| 7.8 | Yes | Yes | V11.0.1 | |
| 7.9 | Yes | Yes | V11.0.1 | |
| Ubuntu | 16.04 LTS | Yes | No | V11.0.1 |
| 18.04 LTS | Yes | No | V11.0.1 | |
| 20.04 LTS | Yes | No | V11.0.1 | |
| 22.04 LTS | Yes | No | V11.0.1 | |
| Oracle Enterprise Linux 1, 2 | 6.0-6.10 | Yes | No | V11.0.1 |
| 7.0-7.6 | Yes | No | V11.0.1 | |
| 7.7 | Yes | No | V11.0.1 | |
| 7.8 | Yes | No | V11.0.1 | |
| 7.9 | Yes | No | V11.0.1 | |
| 8.0-8.1 | Yes | No | V11.0.1 | |
| 8.2 | Yes | No | V11.0.1 | |
| 8.3 | Yes | No | V11.0.1 | |
| 8.4 | Yes | No | V11.0.1 | |
| 8.5 | Yes | No | V11.0.1 | |
| 8.6 | Yes | No | V11.0.1 | |
| 8.7 | Yes | No | V11.0.4 | |
| 8.88 | Yes | No | V11.0.8 | |
| 9.0 | Yes | No | V11.0.4 | |
| 9.18 | Yes | No | V11.0.8 | |
| 9.28 | Yes | No | V11.0.8 |
1 Symantec (Veritas) Dynamic Multi Pathing (DMP) is NOT supported.
2 Supported only on VMware Engine VMs and not on Compute Engine instances/VMs
3 During "offline" upgrade of SuSE (upgrade from ISO), the SuSE installer does not run a reconfigure on external packages, including the CBT module and DLKM. As a result, when the system boots up with the updated kernel, the dlkm is unable to load because the old configuration files still point to the older kernel module. Upgrade of OS from ISO is not supported.
4 Google Cloud Backup and DR Service does not support RHEL HA.
5 Does not support CBT if the kernel version > 4.18.0-425.3.1.
6 Does not support CBT if the kernel version > 5.14.21-150400.22.1.
7 In rare cases, LVM snapshot command on this OS version may cause the backups to hang. This is a known Red Hat issue. Internal bug ID for this bug as maintained by Red Hat is 1758605. Upgrade the Linux kernel to the latest available one on RHEL/CentOS 8.1 release. For more information, visit https://access.redhat.com/solutions/5049041 or contact the Red Hat/CentOS support team for further assistance.
8 Supported on both Red Hat Compatible Kernel (RHCK) and Unbreakable Enterprise Kernel (UEK) versions.
Microsoft SQL server
Backup and DR agents support database consistent data capture (snapshots) from Microsoft SQL Server.
| Version | Supported Configurations | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 2019 | Standalone | V11.0.1 |
| Always on Availability Groups | V11.0.1 | |
| Distributed Availability Groups | V11.0.1 | |
| Failover Instance 1 | V11.0.1 | |
| 2017 | Standalone | V11.0.1 |
| Always on Availability Groups | V11.0.1 | |
| Distributed Availability Groups | V11.0.1 | |
| Failover Instance 1 | V11.0.1 | |
| 2016 | Standalone | V11.0.1 |
| Always on Availability Groups | V11.0.1 | |
| Distributed Availability Groups | V11.0.1 | |
| Failover Instance 1 | V11.0.1 | |
| 2014 | Standalone | V11.0.1 |
| Always on Availability Groups | V11.0.1 | |
| Failover Instance 1 | V11.0.1 |
1 No support for app-aware mounts into a SQL Server Instance running on a Microsoft Failover Cluster if any of its nodes have been discovered as a VMware VM.
IBM Db2
Backup and DR Service supports the following data capture methods:
Db2 on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for Test Data Management (TDM). This leverages Linux LVM and Backup and DR's Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, Db2 on Linux can alternatively be captured using full + incremental backup. This uses the database's traditional dump-based backup.
| Supported IBM DB2 versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 10.5 | CentOS 7.x RHEL 7.x SLES 12 |
V11.0.1 |
| 11.1.0 | CentOS 7.x RHEL 7.x SLES 12 |
V11.0.1 |
| 11.5.0 | CentOS 7.x RHEL 7.x SLES 12 |
V11.0.1 |
| 11.5.8.0 | CentOS 7.x RHEL 7.x RHEL 8.x SLES 12 and 15 |
V11.0.4 |
MariaDB
Backup and DR Service supports the following data capture methods:
MariaDB on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, MariaDB on Linux can alternatively be captured using full + incremental backup. This uses the database's traditional dump-based backup and typically runs as a weekly full and daily incremental. Recovery involves reconstructing the incrementals on top of the latest full backup.
| Supported MariaDB versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 10.3.9 | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| 10.4 | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
10.5 |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
10.11 |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 |
MySQL
Backup and DR Service supports the following data capture methods:
MySQL on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR's Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, MySQL on Linux can alternatively be captured using full + incremental backup. This uses the database's traditional dump-based backup and typically runs as a weekly full and daily incremental. Recovery involves reconstructing the incrementals on top of the latest full backup.
| Supported MySQL versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 5.7 | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| 8.0 | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 |
Oracle
Backup and DR agents enable database consistent data capture of Oracle databases. Oracle must be run in ARCHIVELOG mode. Data capture supports capturing data to staging disks formatted as file systems or presented as ASM disk group targets.
Data can also be captured from Oracle Non Active Data Guard and Active Data Guard configurations.
| Oracle family | Config types | Supported OSes | Min required Backup and DR agent version |
|---|---|---|---|
| Oracle 21c
All Versions |
Standalone | RHEL 8.4
Rocky Linux 8.7 Windows 2012, 2016, 2019 |
V11.0.7 |
| RAC | RHEL 8.4
Rocky Linux 8.7 Windows 2012, 2016, 2019 |
V11.0.7 | |
| Exadata 1 | RHEL 8.4
Rocky Linux 8.7 Windows 2012, 2016, 2019 |
V11.0.7 | |
| Non Active Data Guard 2 | RHEL 8.4
Rocky Linux 8.7 Windows 2012, 2016, 2019 |
V11.0.7 | |
| Active Data Guard 2 | RHEL 8.4
Rocky Linux 8.7 Windows 2012, 2016, 2019 |
V11.0.7 | |
| Oracle 19c 3
All Versions |
Standalone | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 |
| Rocky Linux 8.7 | V11.0.7 | ||
| RAC | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Rocky Linux 8.7 | V11.0.7 | ||
| Exadata 1 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Rocky Linux 8.7 | V11.0.7 | ||
| Non Active Data Guard 2 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Rocky Linux 8.7 | V11.0.7 | ||
| Active Data Guard 2 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Rocky Linux 8.7 | V11.0.7 | ||
| Oracle 18c 3
All Versions |
Standalone | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 |
| RAC | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Exadata 1 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Non Active Data Guard 2 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 | |
| Active Data Guard 3 | CentOS 7.x
OEL 7.x, 8.x, 9.0 RHEL 7.x, 8.x SLES 12, 15 Windows 2012, 2016, 2019 |
V11.0.1 |
1 Oracle Exadata system is supported with iSCSI and NFS
2 Oracle database RMAN change block tracking is available on Active Data Guard only
3 Data capture of Oracle 18c and above is at container level (that includes all PDBs). App-aware mount on a target is at container level. Virtual PDBs to an existing container is supported using custom scripts.
Supported data capture and data presentation methods
Backup and DR Service supports a variety of capture and presentation methods for Oracle databases under various configurations. This includes backup, recovery and App aware mount operations of Oracle database with TDE (Transparent Data Encryption). For Oracle databases with TDE, the wallet for TDE can be captured by setting the Oracle Configuration file location advanced setting for the Oracle app. App aware mounts for TDE enabled databases requires the wallet to be copied to the appropriate location on the mount host.
Also note that dNFS with Oracle is supported on Linux operating systems.
| Production DB Configuration | Capture Format1 | Presentation Format |
|---|---|---|
| DB files on ASM/RAC | Filesystem (Block Device) | Standalone Filesystem |
| Filesystem (NFS) | Standalone Filesystem (NFS) | |
| Filesystem (NFS) | RAC Filesystem (NFS) | |
| ASM Disk Group 3, 5 | Standalone ASM | |
| ASM Disk Group 3, 5 | ASM RAC (one or more nodes) | |
| DB files on filesystem | Filesystem (Block Device) | Standalone Filesystem |
| Filesystem (NFS) | Standalone Filesystem (NFS) | |
| ASM Disk Group 3, 4, 5 | Standalone ASM | |
| ASM Disk Group 3, 4, 5 | ASM RAC (one or more nodes) |
1 Capture Format is the resulting format of the copy managed by Backup and DR.
3 Capture from ASM to ASM and presentation of backups in ASM format not supported on Windows operating systems
4 Oracle ASM instance required on the source system for this capture method
5 The combination of ASM Disk (capture format) is not supported when data is captured over NFS
| Supported Data Capture formats |
Using File System
Using ASM Disk Group |
|---|---|
| Backup support | HCC or Non HCC Data |
| Traditional Recovery using RMAN | HCC or non HCC |
| App-Aware Mount 1 | Exadata to non Exadata |
1 Accessing data from virtual copies of HCC compressed data will require the data to be uncompressed before access
Oracle exadata support
Backup and DR Service supports the following configurations of Oracle Exadata.
Exadata Database Machine versions: X4 and higher
Oracle versions: 18c and 19c
PostgreSQL
Backup and DR Service supports the following data capture methods:
PostgreSQL on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR's Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, PostgreSQL on Linux can alternatively be captured using full + incremental backup. This uses the database's "pg_dump" command, that does not support incremental backup, so each backup will be a full database dump backup.
Due to limitations with PostgreSQL, the roll forward recovery is not supported for full+incremental backups restore operation.
| Supported PostgreSQL versions |
Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
10.23 |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
11.x |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
12.x |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
13.x |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
14.x |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
15.x |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 |
SAP
Backup and DR Service supports SAP on all the databases covered/supported in this document.
SAP ASE (formerly Sybase ASE)
Backup and DR Service supports the following data capture methods:
SAP ASE on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR's Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, SAP ASE on Linux can alternatively be captured using full + incremental backup. This uses the database's traditional dump-based backup and typically runs as a weekly full and daily incremental. Recovery involves reconstructing the incrementals on top of the latest full backup.
| Supported SAP ASE versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 16.0.x | CentOS 7.x RHEL 7.x SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| SLES 15 SP4 | V11.0.4 | |
| SLES 15 SP5 | V11.0.9 |
SAP HANA
Backup and DR agent supports capturing SAP HANA in the following configurations.
| Supported Configuration | SAP HANA SavePoint API 2 | SAP file-based (HDBSQL/Backint) 3 | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|---|---|
| Scale-out HANA 2.0, non shared storage | Yes (preferred) 1 | Yes | RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| Yes (preferred) 1 | Yes | RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| Yes (preferred) 1 | Yes | RHEL 8.7 | V11.0.5 | |
| Yes (preferred) 1 | Yes | SLES 15 SP5 | V11.0.9 | |
| Scale-out HANA 2.0, shared storage 4 | Not Supported | Yes | RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| Not Supported | Yes | RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| Yes (preferred) 1 | Yes | RHEL 8.7 | V11.0.5 | |
| Yes (preferred) 1 | Yes | SLES 15 SP5 | V11.0.9 | |
| SAP HANA 2.0 Standalone or HA (1+1) | Yes (preferred) 1 | Yes | RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| Yes (preferred) 1 | Yes | RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| Yes (preferred) 1 | Yes | RHEL 8.7 | V11.0.5 | |
| Yes (preferred) 1 | Yes | SLES 15 SP5 | V11.0.9 | |
| Single Container System (HANA 1.0) 5 | Yes (preferred) | Yes | RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| Yes (preferred) | Yes | RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| Yes (preferred) 1 | Yes | RHEL 8.7 | V11.0.5 | |
| Yes (preferred) 1 | Yes | SLES 15 SP5 | V11.0.9 |
1 Requires SAP HANA 2.0 SPS 04 or above
2 SAP HANA SavePoint API leverages Backup and DR CBT and supports incremental-forever and app-aware instant mount feature with log roll forward option. Backup and DR Service supports CBT with HANA on RHEL 7.2 and above. For a full list of CBT qualified RHEL versions, see Linux Operating System Support.
3 SAP HANA Backint mode only supports weekly full with daily incrementals. Supports traditional recovery using HANA HDBSQL/Backint commands. Also App-aware instant mount capability is not supported with HANA File-based (HDBSQL/Backint) API
4 Supports only Backup and DR NFS disk mapping option. NFS disk is always mapped to all HANA nodes
5 Supports both Backup and DR block and NFS disk mapping options
SAP MaxDB
Backup and DR Service supports the following data capture methods:
SAP MaxDB on Linux can be captured at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR Changed Block Tracking capabilities and is the recommended alternative.
For customers not using LVM or who cannot use volume level capture, MaxDB on Linux can alternatively be captured using full + incremental backup. This uses the database's traditional dump-based backup and typically runs as a weekly full and daily incremental. Recovery involves reconstructing the incrementals on top of the latest full backup.
| Supported SAP MaxDB versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| 7.9.09 | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
7.9.10 |
RHEL 7.x RHEL 8.1-8.5 |
V11.0.1 |
| RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
| SLES 15 SP5 | V11.0.9 |
SAP IQ (formerly Sybase IQ)
Backup and DR Service supports capturing SAP IQ at the volume level in an incremental-forever fashion with instant access and virtual clone creation for TDM. This leverages Linux LVM and Backup and DR Changed Block Tracking capabilities and is the recommended alternative.
| Supported SAP IQ versions | Supported OSes | Min required Backup and DR agent (Connector) version |
|---|---|---|
| SAP IQ 16.x (Full + Incremental) | CentOS 7.x RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
SAP IQ 16.x (LVM + CBT) |
CentOS 7.x RHEL 7.x RHEL 8.1-8.5 SLES 12 SP5 SLES 15 SP3 |
V11.0.1 |
| CentOS 7.x RHEL 8.6 SLES 15 SP4 |
V11.0.4 | |
| RHEL 8.7 | V11.0.5 | |
| SLES 15 SP5 | V11.0.9 |
File systems
Backup and DR agents discover each volume/network mount point as a protectable application. For each of these discovered applications, Backup and DR agent orchestrates the process of achieving consistency (through VSS/LVM snapshots), presents a staging disk which will be formatted with a file system of the same type as source or a compatible file system type as documented below.
| Operating System | Source FS | Staging Disk FS | Min required Backup and DR agent (Connector) Version |
|---|---|---|---|
| Windows | NTFS | NTFS | V11.0.1 |
| SMB | NTFS | V11.0.1 | |
| ReFS | ReFS | V11.0.1 | |
| Linux 1 | EXT2 | EXT2 or NFS 4 | V11.0.1 |
| EXT3 | EXT3 or NFS 4 | V11.0.1 | |
| EXT4 | EXT4 or NFS 4 | V11.0.1 | |
| XFS | XFS or NFS 4 | V11.0.1 | |
| ReiserFS | ReiserFS or NFS 4 | V11.0.1 | |
| NFS | EXT3 or NFS 4 | V11.0.1 | |
| BTRFS | EXT3 or NFS 4 | V11.0.1 |
1 LVM snapshot is used as source, if present. LVM mount back to same server is supported
2 Built in versions only
3 Encryption not supported
4 Only V3 of NFS protocol is supported
Test data management with containers
Backup and DR leverages NFS volumes to make captured application data available as NFS shares to containers. This allows for creating virtual clones of supported databases that's easily accessible from within the containerized environment.
Data virtualization for virtual environments
VMware (GCVE)
Backup and DR Service supports capturing data from VMware virtual machines by leveraging VMware vSphere Storage APIs - Data Protection (formerly known as vStorage APIs for Data Protection or VADP) calls to capture an entire virtual server. Specifically, the API calls can:
Perform change block tracking: Makes an initial full snapshot of a database, then going forward only snapshots the changes to the database thereby enabling Backup and DR's incremental forever capture strategy.
Quiesce applications: Ensures application consistency during capture.
| vCenter 1, 6 | 7.0, 7.0 U1, 7.0 U2, 7.0 U3 |
| ESX Server 6 | 7.0, 7.0 U1, 7.0 U2, 7.0 U3 |
| Virtual Hardware 2 | 7 to 15 and 17 to 19 |
| Guest OS | All VMware supported OSs |
| Quiesce applications 3 | Yes, based on VMware Tools |
| vSAN Support 4 | vSAN 7.0 U1, vSAN 7.0 U2, vSAN 7.0 U3 |
| Change Block Tracking5 | Leverages VMware vSphere Storage APIs - Data Protection (formerly known as vStorage APIs for Data Protection or VADP) |
1 Leverages VMware VDDK version 7.0.
2 NVME Controller types (found on ESX 7.0 and above) are not supported. Virtual hardware version 14 and above are supported only with ESX 7.0 (and above)
3 Capability applicable to any application with a VSS Writer or pre/post scripts to achieve application consistent capture.
4 Since VMware vSAN does not support RDM device access features, mounting of a VM is not supported by Backup and DR when using RDMs. Restores and Clones of VMs are supported. However, mounting of a VM is supported on Backup and DR when using NFS transport instead of RDM.
5 Not supported for disks presented to production VMs as pRDM.
6 Configuring SAN transport mode to backup staging disk (agent based backups) and mount/restore backup images via iSCSI is not supported.