Compatibility Matrix
Compatibility Matrix
Trademarks
By using the Data Security Posture application, you understand and acknowledge that the pre-existing
Policies and Analyzers of Data Security Posture contain general suggestions for data elements and formats
based on common data sets and formats. The suggested data elements and formats in Data Security
Posture are not intended to be a comprehensive or exhaustive list of data elements and formats regulated
by the GDPR, CCPA or any other applicable laws and regulations. We also do not guarantee that your Data
Support
Use one of the following methods to contact Rubrik Support.
Related documentation
Rubrik provides documentation that covers a broad range of related concepts, tasks, and reference
information.
• Rubrik Security Cloud User Guide
• Rubrik CDM Release Notes
• Rubrik CDM User Guide
• Rubrik CDM Install and Upgrade Guide
• Rubrik CDM Security Guide
• Rubrik CDM Cloud Cluster Setup Guide
• Rubrik CDM Hardware Guide
• Rubrik CDM CLI Guide
• Rubrik CDM Events Guide
• Rubrik Edge Install and Upgrade Guide
• Rubrik Virtual Cluster Install Guide
• Rubrik Compatibility Matrix
Preface 06/13/2024 | iv
Comments and suggestions
We welcome your comments and suggestions about our products and our product documentation.
Products
To provide comments and suggestions about our products contact Rubrik Support, as described in Support.
Product documentation
To provide comments and suggestions about the product documentation, send an email to:
[email protected].
To help our writers identify the area that you are referencing, include the following requested information.
For HTML documentation, include:
• Page title
• Page address
• Page date
For PDF documentation, include:
• PDF title
• Part number
• Revision
• Relevant page numbers
Preface 06/13/2024 | v
Contents
Document scope...............................................................................................................................8
Version designations........................................................................................................................9
VMware Cloud................................................................................................................................ 24
KMIP support................................................................................................................................. 39
Third-party hardware.....................................................................................................................40
Third-party firmware................................................................................................................ 40
Third-party hardware power ratings.......................................................................................... 44
Contents 06/13/2024 | vi
Fileset cluster support................................................................................................................... 53
MongoDB protection...................................................................................................................... 63
Oracle Database............................................................................................................................. 64
Oracle Database support limitations.......................................................................................... 68
SAP HANA....................................................................................................................................... 72
Archival locations........................................................................................................................... 74
RBS support....................................................................................................................................87
Replication...................................................................................................................................... 91
Kubernetes......................................................................................................................................92
Rubrik Envoy.................................................................................................................................. 98
Rubrik CDM version requirements for Rubrik Security Cloud - Private.................................... 120
Document scope
The Rubrik Compatibility Matrix provides information about features, requirements, and compatibility for
Rubrik® CDM software and Rubrik Security Cloud™.
This compatibility matrix covers Rubrik CDM version 4.2 and later and the latest deployed version of Rubrik
Security Cloud (RSC).
Rubrik only supports configurations and integrations specified in this document. Other configurations and
integrations have not been tested by Rubrik and cannot be affirmed to be compatible by Rubrik or any
representative of Rubrik, Inc.
Version designations
The following table describes the version designation conventions used to specify versions and version
ranges in the Rubrik Compatibility Matrix.
Range within • 4.2.0-4.2.3The information in the table row applies to all versions within the specified
a branch • 4.0.1-4.0.5range, inclusive.
• 4.1.0- For example:
p2-4.1.n
• 4.2.0-4.2.3 applies to the following versions: 4.2.0, 4.2.1, 4.2.2, and
4.2.3.
• 4.1.0-p2-4.1.n applies to version 4.1.0 patch 2 and all newer version of
the 4.1 branch.
Entire branch • 4.0.0-4.0.nThe information in the table row applies to all versions in the branch that is
• 4.2.0-4.2.nspecified by the first two numbers in the designation.
For example, 4.2.0-4.2.n applies to all versions in the 4.2 branch but does
not apply to later branches, such as 5.0.
Specified • 4.0.0+ The information in the table row applies to the specified version and all
version and • 4.1.3+ newer versions in that branch and in newer branches. When the information
all newer does not apply to all versions in a newer branch, then the range within a
• 4.2.2-
versions and branch method is used instead.
p1+
branches
• 5.1.0-5.1.nFor example, "4.1.7+" applies to version 4.1.7 and all versions of 4.1 that
are newer than version 4.1.7, all versions of 4.2, and all versions of 5.0.
In the same example, if release timing excludes the information from
versions 4.2.0-4.2.3 of the 4.2 branch, the designations to show this are:
• 4.1.7-4.1.n
• 4.2.4+
5.0.0+ 10 Gb or 25 Gb, The bond0 10GBASE- • The data network, or the shared
depending on the T ports must operate data and management network,
connected optical at 10 Gb and be must use the bond0 network
transceiver and switch. connected to a connection: 10 Gb (r300/r500) or
The 10GBASE-T ports 10GBASE-T switch. 10/25 Gb (r6000).
operates at 10 Gb or 1 The bond1 10GBASE- • The management network can use
GB, depending on the T management ports the bond1 network connection: 1
connected switch. may be connected to Gb 1000BaseT (r300/r500) or 10
either a 10GBASE-T Gb/1 Gb 10GBaseT (r6000).
switch or a 1GBASE-T
• Rubrik Edge, Rubrik Air, and Rubrik
(1000BASE-T) switch.
cloud cluster support data and
management networks using 1 GbE
or faster network connections.
Rubrik CDM supports specific versions of the Acropolis Operating System (AOS) and Nutanix REST API.
9.0.3+ AOS 6.7, 6.6, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.5.3.x, 6.5, (NC2).
6.1, 6.0, 5.15– • Supports Nutanix Prism Central
5.20, 5.8–5.11, (Managed by RSC).
5.6, 5.5, 5.1
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
9.0+ AOS 6.7, 6.6, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.5.3.x, 6.5, (NC2).
6.1, 6.0, 5.15– • Supports Nutanix Prism Central
5.20, 5.8–5.11, (Managed by RSC).
5.6, 5.5, 5.1
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
8.1+ AOS 6.7, 6.6, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.5.3.x, 6.5, (NC2).
6.1, 6.0, 5.15– • AOS 6.5.3.x supported from 8.1.2-p2
5.20, 5.8–5.11, and later.
5.6, 5.5, 5.1
• AOS 6.7, 6.6 supported from 8.1.3-p7
and later.
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
8.0.2+ AOS 6.5, 6.1, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.0, 5.15–5.20, (NC2).
5.8–5.11, 5.6, • Rubrik does not support VM linking
5.5, 5.1 in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
8.0.1+ AOS 6.5, 6.1, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.0, 5.15–5.20, (NC2).
5.8–5.11, 5.6, • Rubrik does not support VM linking
5.5, 5.1 in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
8.0.0+ AOS 6.1, 6.0, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
5.15–5.20, 5.8– (NC2).
5.11, 5.6, 5.5, • Rubrik does not support VM linking
5.1 in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
7.0.4+ AOS 6.5.3.x, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.5, 6.1, 6.0, (NC2).
5.15–5.20, 5.8– • AOS 6.5.3.x supported from 7.0.4-p10
5.11, 5.6, 5.5, and later.
5.1
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
7.0.3+ AOS 6.1, 6.0, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
5.15–5.20, 5.8– (NC2).
5.11, 5.6, 5.5, • Rubrik does not support VM linking
5.1 in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
7.0.2+ AOS 6.0, 5.15– Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
5.20, 5.8–5.11, (NC2).
5.6, 5.5, 5.1 • Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
7.0.1+ AOS 6.0, 5.15– Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
5.20, 5.8–5.11, (NC2).
5.6, 5.5, 5.1 • Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
6.0.3–p10+ AOS 6.5, 6.1, Nutanix REST API v3.1 • Supported for Nutanix Cloud Cluster
6.0, 5.15–5.20, (NC2).
5.8–5.11, 5.6, • Rubrik does not support VM linking
5.5, 5.1 in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
6.0.3–p7+ AOS 6.1, 6.0, Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
5.15–5.20, 5.8– cluster DR failovers for Metro, NearSync,
5.11, 5.6, 5.5, Async, and Sync.
5.1
6.0.3+ AOS 6.0, 5.15– Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
5.20, 5.8–5.11, cluster DR failovers for Metro, NearSync,
5.6, 5.5, 5.1 Async, and Sync.
6.0.2+ AOS 6.0, 5.15– Nutanix REST API v3.1 • The Rubrik CDM Nutanix Live Mount
5.20, 5.8–5.11, feature requires AHV 6.0.2.
5.6, 5.5, 5.1 • Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
6.0.1+ AOS 6.0,15– Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
5.20, 5.8–5.11, cluster DR failovers for Metro, NearSync,
5.6, 5.5, 5.1 Async, and Sync.
6.0.0+ AOS 6.0, 5.15– Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
5.20, 5.8–5.11, cluster DR failovers for Metro, NearSync,
5.6, 5.5, 5.1 Async, and Sync.
5.3.3+ AOS 5.15–5.20, Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
5.8–5.11, 5.6, cluster DR failovers for Metro, NearSync,
5.5, 5.1 Async, and Sync.
5.3.0+ AOS 5.19, 5.20 Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
cluster DR failovers for Metro, NearSync,
Async, and Sync.
5.2.2+ AOS 5.18 Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
cluster DR failovers for Metro, NearSync,
Async, and Sync.
5.2.1+ AOS 5.17 Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
cluster DR failovers for Metro, NearSync,
Async, and Sync.
5.2.0+ AOS 5.15, 5.16 Nutanix REST API v3.1 Rubrik does not support VM linking in AHV
cluster DR failovers for Metro, NearSync,
Async, and Sync.
5.0.1 AOS 5.8.x, Nutanix REST API v3.1 • For AOS version 5.9.x, contact Rubrik
5.9.x, 5.10 Support.
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
4.2.1–p2 to AOS 5.8.x, Nutanix REST API v3.1 • Regex change required for use with
5.0.0 5.9.x, 5.10 CDM 4.2.1–p2 and 5.0.0 only. Newer
releases do not require the regex
change.
• For AOS version 5.9.x, contact Rubrik
Support.
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
4.2.1+ AOS 5.6.x, Nutanix REST API v3.1 • For AOS versions prior to 5.6, use
5.8.x, 5.9.x Nutanix REST API V3.0.
• For AOS version 5.9.x, contact Rubrik
Support.
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
4.2.0 AOS 5.0–5.6.x Nutanix REST API v3.1 • When virtual machines are protected by
NearSync on Nutanix, Nutanix does not
allow creating snapshots.
• For AOS versions prior to 5.6, use REST
API V3.0.
• Rubrik CDM 4.2.0 does not officially
support AOS 5.8.x. Contact Rubrik
Support for changes to provide AOS
5.8.x support.
• Rubrik does not support VM linking
in AHV cluster DR failovers for Metro,
NearSync, Async, and Sync.
Rubrik CDM provides support for direct file restore to AHV virtual machines.
Direct file restores use snapshots of AHV virtual machines that were created, ingested, indexed, and
managed by the Rubrik cluster.
4.2.0+ Microsoft Microsoft System • Hyper-V backups can only be used with
Hyper-V 2016 Center Virtual Machine Hyper-V 2016 or later.
Manager 2016 • The optional configuration of SCVMM with
(SCVMM) Rubrik enables the automated discovery of
the full Hyper-V environment.
• Incompatible with Windows Server Storage
Replica technology.
• Hyper-V 2019 is not supported.
• English language pack must be installed
on the Hyper-V host to allow discovery of
virtual machines.
Rubrik CDM provides support for Microsoft Azure Stack HCI using Hyper-V protected objects.
Specific versions of Rubrik CDM support specific versions and configurations of vCenter Server and ESXi.
Note:
• Support for vCenter Server and ESXi in Rubrik CDM versions 5.n are removed as of July 2022.
• Rubrik recommends that you recover virtual machine snapshots to a destination vCenter Server of the
same or later version than the source vCenter Server. If you recover virtual machine snapshots to a
destination vCenter Server that is an earlier version of the source vCenter Server, the recovery may
fail. The reasons for recovery failure can vary, but in most cases, the recovery fails as the later vCenter
Server versions contain new fields in the virtual machine configuration files that are not present in the
earlier vCenter Server versions.
For example, Rubrik Security Cloud does not support recovery of virtual machine snapshots taken on
source vCenter Server version 6.7 or later to a destination vCenter Server version 6.5.
The following table lists the specific versions of VMware vSphere supported by Rubrik CDM versions for
Snapshot protection.
The following table lists the specific versions of VMware vSphere supported by Rubrik CDM versions for
Continuous Data Protection (CDP).
VMware Cloud
Specific versions of Rubrik CDM support specific versions and configurations of VMware Cloud.
Rubrik does not support the following features on VMware Cloud environments:
• Live Mount
• Instant Recovery
• Rubrik Edge
• Rubrik Air
• Rubrik Virtual Cluster
Rubrik CDM supports specific versions of VMware Cloud (VMC) software-defined data center (SDDC) on
AWS.
Rubrik CDM supports specific versions of Google Cloud VMware Engine (GCVE).
Rubrik Security Cloud provides protection for Atlassian Jira sites based on different data types. To protect
your Atlassian Jira data, you can back up and restore data such as projects, issues, settings, and workflows
in your Jira site.
The following tables show the Atlassian Jira data types that Rubrik Security Cloud can back up and restore.
Rubrik CDM provides support for direct file restore to VMware virtual machines.
Direct file restores uses snapshots of VMware virtual machines that were created, ingested, indexed, and
managed by the Rubrik cluster.
Rubrik CDM 5.1 and newer versions provide Continuous Data Protection (CDP) with some platform
restrictions.
• r6000S, r6000SE, and The following platforms are not supported for CDP:
r6000F platforms
5.1.0+ • e1000
• r300 series
• Rubrik Cloud Cluster
• r500 series
• Rubrik Edge
• r6000S, r6000SE, and Rubrik clusters with Rubrik CDM 5.3.0+ have the CDP
r6000F platforms Resynchronization feature. These Rubrik clusters provide
• r300 series additional recovery points when replicating to a target
• r500 series that is running Rubrik CDM 5.3.0+. When replicating to a
target that is running a version of Rubrik CDM less than
5.3.0, recovery from the target is available from the next
5.3.0+ replicated snapshot instead of a resynchronization point.
The following platforms are not supported for CDP:
• e1000
• Rubrik Cloud Cluster
• Rubrik Edge
Rubrik CDM supports specific VMware Cloud Director versions and vCenter Server and ESXi versions
associated with them.
VMware Cloud Director versions supported by the specific Rubrik CDM version are provided in the table
with additional information on usage.
Note: Support for VMware Cloud Director in Rubrik CDM versions 5.n is removed as of July 2022.
Note: Support for VMware Cloud Director in Rubrik CDM versions 5.n is removed as of July 2022.
Rubrik software supports Rubrik Cloud Vault for the specified versions.
Rubrik CDM supports indexing of the specified guest OS file systems for all virtual environments.
Rubrik CDM provides support for volume protection with specified Microsoft Windows configurations.
8.1+ • Windows Server 2012 • NTFS • Volume can only be restored to the
• Windows Server 2012 R2 • ReFS same or newer Windows version.
• Windows Server 2016 • To restore a Windows 2012 volume, the
• Windows Server 2019 target Windows host must be a member
• Windows Server 2022 of the Active Directory domain.
• Windows 10
• Windows 11
8.0+ • Windows Server 2012 • NTFS • Volume can only be restored to the
• Windows Server 2012 R2 • ReFS same or newer Windows version.
• Windows Server 2016 • To restore a Windows 2012 volume, the
• Windows Server 2019 target Windows host must be a member
• Windows Server 2022 of the Active Directory domain.
• Windows 10
7.0+ • Windows Server 2012 • NTFS • Volume can only be restored to the
• Windows Server 2012 R2 • ReFS same or newer Windows version.
• Windows Server 2016 • To restore a Windows 2012 volume, the
• Windows Server 2019 target Windows host must be a member
• Windows Server 2022 of the Active Directory domain.
• Windows Server 2022 is supported on
Rubrik CDM version 7.0.3 and later.
6.0.1+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 • ReFS same or newer Windows version.
• Windows Server 2012 R2 • To restore a Windows 2012 volume, the
• Windows Server 2016 target Windows host must be a member
• Windows Server 2019 of the Active Directory domain.
• ReFS indexing support is limited to
filesets.
• Deprecates support for Windows
Server 2008 and Windows Server 2008
R2. Future releases of Rubrik CDM
will discontinue the support of these
operating systems.
6.0+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 • ReFS same or newer Windows version.
• Windows Server 2012 R2 • To restore a Windows 2012 volume, the
• Windows Server 2016 target Windows host must be a member
• Windows Server 2019 of the Active Directory domain.
• ReFS indexing support is limited to
filesets.
• Deprecates support for Windows
Server 2008 and Windows Server 2008
R2. Future releases of Rubrik CDM
will discontinue the support of these
operating systems.
5.3.0+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 • ReFS same or newer Windows version.
• Windows Server 2012 R2 • To restore a Windows 2012 volume, the
• Windows Server 2016 target Windows host must be a member
• Windows Server 2019 of the Active Directory domain.
• ReFS indexing support is limited to
filesets.
• Deprecates support for Windows
Server 2008 and Windows Server 2008
R2. Future releases of Rubrik CDM
will discontinue the support of these
operating systems.
5.2.0+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 • ReFS same or newer Windows version.
• Windows Server 2012 R2 • To restore a Windows 2012 volume, the
• Windows Server 2016 target Windows host must be a member
• Windows Server 2019 of the Active Directory domain.
• ReFS indexing support is limited to
filesets.
5.0.0+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 R2 • ReFS same or newer Windows version.
• Windows Server 2016 • To restore a Windows 2016 or 2019
• Windows Server 2019 volume, the target Windows host must
be a member of the Active Directory
domain.
• ReFS indexing support is limited to
filesets.
4.2.0+ • Windows Server 2008 R2 • NTFS • Volume can only be restored to the
• Windows Server 2012 R2 • ReFS same or newer Windows version.
• Windows Server 2016 • To restore a Windows 2016 volume, the
target Windows host must be a member
of the Active Directory domain.
• ReFS indexing support is limited to
filesets.
KMIP support
Rubrik CDM provides support for specific KMIP versions for external KMS servers.
Rubrik CDM versions 5.0.0 and later support key management interoperability protocol (KMIP) versions 1.2
and later for external key management service (KMS) servers.
Third-party hardware
Rubrik supports third-party hardware platforms with different versions of Rubrik CDM.
Third-party firmware
Rubrik CDM supports BIOS and BMC firmware that is qualified on Rubrik third-party platforms.
The following table lists an HBA firmware version only when it is required for compatibility with other
versions listed on that row. If a row does not specify an HBA version, the third-party platform supports any
HBA version the server vendor qualifies.
Rubrik CDM provides support for the application programming interfaces of specified file system arrays.
5.3.0+ Rubrik Rubrik NAS Cloud • (Minimum) Supports Rubrik NAS Cloud
Direct Purity//FB Direct.
2.4.12 KB 000008439 describes
• OneFS 8.0.2+ that the ONTAP multi-admin
• Qumulo Core verification (MAV) feature
2.9+ introduced in ONTAP 9.11.1
• ONTAP is not supported
8.3SP3+
Rubrik CDM provides physical host support for specific operating systems.
5.2.1+ • CentOS and Oracle Linux 8.x Ext3, Ext4, XFS, Cluster-aware support for
• RHEL 8.x Btrfs filesets is not provided.
5.2.0+ • Solaris 10: Solaris 10 Update 11 ZFS • Supports both x86 and
(Solaris 10 1/13s10s_u11wos_24a) SPARC.
or later updates • Cluster-aware support
• Solaris 11: Solaris 11.1 SRU 14.5 for filesets is not
(Branch: 0.175.1.14.0.5.0) or later provided.
SRUs and updates
5.0.4+ • CentOS and Oracle Linux 8.x Ext3, Ext4, XFS, • Installation of Rubrik
• RHEL 8.0 Btrfs Backup Service requires
a manual workaround,
described in KB
000004503.
• Cluster-aware support
for filesets is not
provided.
4.2.1+ • AIX 6.1, 7.1 TL3+, 7.2 • JFS, JFS2 • Technology Level 9 and
• Microsoft Windows Server 2008 R2, • FAT, FAT32, later.
2012, 2012 R2, 2016 NTFS, ReFS • Cluster-aware support
• Ubuntu 14.04 LTS, 16.04 LTS, 17.04 • Ext3, Ext4, for filesets is not
• SLES 11, 12 XFS, Btrfs provided.
• RHEL 6, 7 • 64-bit only.
• Oracle Linux 6, 7 • The Rubrik CDM version
• Debian 8.x 5.3 release deprecates
support for Windows
• CentOS 6, 7
Server 2008 R2. Future
releases of Rubrik CDM
discontinues the support
of this operating system.
• RHEL 5.11 support has
been removed. Rubrik
CDM requires TLS 1.2
and RHEL 5.11 only
supports TLS 1.0.
Rubrik CDM provides limited support for backup of file placeholders left by file stubbing and file data tiering
solutions.
Test file stubbing and file data tiering applications before deploying Rubrik CDM in a production
environment that relies on the successful backup of file stubbed data and data that has been tiered.
Rubrik CDM provides support for specific file system network protocols.
Rubrik CDM provides fileset cluster support for specific operating systems and services.
Rubrik provides support for on-premises Active Directory for specific Windows operating systems and
Rubrik CDM versions.
Rubrik CDM provides support for Microsoft SQL Server using specified operating systems and database
management systems.
Rubrik CDM does not support SQL Server 2005 and earlier, and does not support SQL Server databases
that use FULLTEXT file groups that have carried over from SQL Server 2005 (9.x). Within the specified
version support of SQL Server, Rubrik CDM supports the following editions of SQL Server: Developer,
Enterprise, Standard, and Express. Other SQL Server editions may work but have not undergone testing.
8.1.1+ Windows Server SQL Server 2012, 64-bit • The Rubrik cluster supports Live
2012, 2012 R2, 2014, 2016, 2017, Mount to a standalone instance
2016, 2019, 2022 2019, 2022 and a failover cluster instance for
SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT.
• Rubrik has deprecated support
for 2008 and 2008 R2 because
they have reached their end of life
and are no longer supported by
Microsoft.
8.0.0–8.0.3-p2 Windows Server SQL Server 2012, 64-bit • The Rubrik cluster supports Live
2012, 2012 R2, 2014, 2016, 2017, Mount to a standalone instance
2016, 2019 2019 and a failover cluster instance for
SQL Server 2012 and later.
• SQL Server 2022 is not supported.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT.
• Rubrik has deprecated support
for 2008 and 2008 R2 because
they have reached their end of life
and are no longer supported by
Microsoft.
7.0.4-p6+ Windows Server SQL Server 2012, 64-bit • The Rubrik cluster supports Live
2012, 2012 R2, 2014, 2016, 2017, Mount to a standalone instance
2016, 2019, 2022 2019, 2022 and a failover cluster instance for
SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT.
• Rubrik has deprecated support
for 2008 and 2008 R2 because
they have reached their end of life
and are no longer supported by
Microsoft.
7.0.0+ Windows Server SQL Server 2012, 64-bit • The Rubrik cluster supports Live
2012, 2012 R2, 2014, 2016, 2017, Mount to a standalone instance
2016, 2019 2019
6.0.0+ Windows Server SQL Server 2012, 64-bit • The Rubrik cluster supports Live
2012, 2012 R2, 2014, 2016, 2017, Mount to a standalone instance
2016, 2019 2019 and a failover cluster instance for
SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT.
• Rubrik has deprecated support
for 2008 and 2008 R2 because
they have reached their end of life
and are no longer supported by
Microsoft.
5.3.0 Windows Server SQL Server 2008, 64-bit • The Rubrik cluster supports Live
2008 R2, 2012, 2008 R2, 2012, Mount to a standalone instance
2012 R2, 2016, 2014, 2016, 2017, and a failover cluster instance for
2019 2019 SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT.
• Future releases of Rubrik CDM will
discontinue support for SQL Server
2008 and SQL Server 2008 R2.
5.1.0 Windows Server SQL Server 2008, 64-bit • The Rubrik cluster supports Live
2008 R2, 2012, 2008 R2, 2012, Mount to a standalone instance for
2012 R2, 2016 2014, 2016, 2017 SQL Server 2008 R2 and later.
• The Rubrik cluster supports Live
Mount to a failover cluster instance
for SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT. Rubrik CDM does not support
this feature on failover cluster
instances.
5.0.4–5.0.n Windows Server SQL Server 2008, 64-bit • The Rubrik cluster supports Live
2008 R2, 2012, 2008 R2, 2012, Mount to a standalone instance for
2012 R2, 2016, 2014, 2016, 2017, SQL Server 2008 R2 and later.
2019 2019 • The Rubrik cluster supports Live
Mount to a failover cluster instance
for SQL Server 2012 and later.
• The Rubrik cluster does not
support Live Mount to AlwaysOn
Availability Groups.
• The database must be at least 50
GB to use Rubrik CDM SQL Server
CBT. Rubrik CDM does not support
this feature on failover cluster
instances.
5.0.0+ Windows Server SQL Server 2008, 64-bit • The Rubrik cluster supports Live
2008 R2, 2012, 2008 R2, 2012, Mount to a standalone instance for
2012 R2, 2016 2014, 2016, 2017 SQL Server 2008 R2 and later.
• The Rubrik cluster supports Live
Mount to a failover cluster instance
for SQL Server 2012 and later.
4.2.0+ Windows Server SQL Server 2008, 64-bit • Rubrik CDM does not support
2008 R2, 2012, 2008 R2, 2012, backup and restore of databases
2012 R2, 2016 2014, 2016, 2017 that have non-ASCII characters in
their names.
• For SQL Server databases that are
configured to enable log shipping,
Rubrik CDM cannot provide backup
protection that includes the
database log. To protect these
databases, use the Copy Only
setting provided by the Rubrik CDM
instance.
• The Rubrik cluster does not
support Live Mount with SQL
Server 2008.
Rubrik CDM provides support for log truncation for specific versions of Microsoft Exchange Server.
6.0+ Microsoft Exchange Server 2013 and later • vSphere virtual machines
• AHV virtual machines
• Windows full volume protection
7.0+ Microsoft Exchange Server 2013 and later • vSphere virtual machines
• AHV virtual machines
• Windows full volume protection
Microsoft Entra ID
Rubrik Security Cloud supports backup and recovery of Microsoft Entra ID workloads.
If you have added Microsoft Entra ID as a protected workload to an SLA Domain, you can use the
snapshots from the Microsoft Entra ID directory to recover objects deleted by a user. You can recover
objects such as Sharepoint or Microsoft Teams users and groups.
Even if a user has not deleted users or groups, you can use Microsoft Entra ID to update user or group
attributes. The updates you make are reflected in the subsequent snapshot.
You can use RSC to search snapshots for specific users and groups. After you have recovered information
for a user, you can restore the M365 application data for the user with the snapshots provided by the M365
protected workload on RSC.
MongoDB protection
The Rubrik cluster provides a variety of features that ensure data protection and facilitate efficient recovery
for MongoDB databases.
The following table lists MongoDB compatibility with Rubrik CDM versions. Rubrik supports community and
enterprise variants of MongoDB but does not support MongoDB Atlas.
9.0.2-p1+ 4.x, 5.x, and 6.x • Rubrik does not support time
series collections.
• Rubrik supports Percona
variants of MongoDB.
Oracle Database
9.1.0 For Oracle Database 21c, 19c, 18c, For Oracle Database versions
versions earlier than 21c, 12cR2, 12cR1, 11gR2 earlier than 21c, the default
the supported host OS are: ORACLE_HOME layout includes
• AIX 6, AIX 7.x the configurations ORACLE_HOME,
• Oracle Linux 6, Oracle ORACLE_BASE_HOME, and
Linux 7, Oracle Linux 8, ORACLE_BASE_CONFIG.
and Linux 9 In Oracle Database 21c, the
• RHEL 6, RHEL 7, RHEL 8, default ORACLE_HOME layout
and RHEL 9 includes only the read-only
• SLES 11, SLES 12, SLES ORACLE_HOME configuration.
15 The ORACLE_BASE_HOME
6.0+ • AIX 6, AIX 7.x 19c, 18c, 12cR2, AIX PowerHA is not supported.
• Oracle Linux 6, Oracle 12cR1, 11gR2
Linux 7, Oracle Linux 8
• RHEL 6, RHEL 7, RHEL 8
• SLES 11, SLES 12, SLES
15
5.1.1+ • AIX 6, AIX 7.x 19c, 18c, 12cR2, • AIX 7.x is not supported for 19c,
• Oracle Linux 6, Oracle 12cR1, 11gR2 18c, 12cR2.
Linux 7 • For Oracle Database 19c, 18c,
• RHEL 6, RHEL 7 12cR2, recovery is supported at
• SLES 11, SLES 12, SLES the Oracle Database level, and
15 tablespace level recovery is not
supported.
5.0.3+ • AIX 6, AIX 7.x 19c, 18c, 12cR2, • AIX 7.x is not supported for 19c,
• Oracle Linux 6, Oracle 12cR1, 11gR2 18c, 12cR2.
Linux 7 • For Oracle Database 19c,
• RHEL 6, RHEL 7 18c, and 12cR2, the recovery
• SLES 11, SLES 12, SLES method is limited to manual
15 recovery from RMAN Backup
files.
5.0.1+ • AIX 6, AIX 7.x 12c R1, 11g R2 Oracle RAC on ASM for AIX 7.x is
• Oracle Linux 6, Oracle not supported.
Linux 7
• RHEL 6, RHEL 7
• SLES 11, SLES 12
Exadata, For Rubrik CDM versions 5.2 and For export operations on a database hosted on the
ODA newer, backup and recovery is Oracle Exadata platform to a non-Exadata platform,
supported for Oracle versions listed in HCC compressed tables must be uncompressed
Oracle Database. before queries can resolve against the exported
TDE Recovery is limited to a manual Backup for supported Oracle Database versions
recovery from RMAN backup files. requires the local Oracle Wallet be open at the time
of backup. The associated Oracle Wallet must be
copied to the target host.
Tablespace For Oracle versions 19.7 and earlier, Refer to Oracle MOS document Doc ID 2565885.1
recovery tablespace recovery can fail with error at https://support.oracle.com/.
code ORA-01256: Error In Locking
Database. This typically happens
because the file is in use by another
database instance.
Oracle For Oracle Database versions Workaround:
Database earlier than 21c, the default Create a softlink for the directory dbs in
21c ORACLE_HOME layout includes ORACLE_HOME pointing to ORACLE_BASE_HOME.
the configurations ORACLE_HOME,
ORACLE_BASE_HOME and Example:
ORACLE_BASE_CONFIG. ORACLE_HOME = /u01/app/oracle/
In Oracle Database 21c, product/21.3.0.0/db1
the default ORACLE_HOME ORACLE_BASE_HOME = /u01/app/oracle/
layout includes only read-only orabase
ORACLE_HOME configuration.
The ORACLE_BASE_HOME and Steps:
ORACLE_BASE_CONFIG configurations On the target host, as oracle (db OS user):
are located in a separate location from
ORACLE_HOME. cd /u01/app/oracle/product/21.3.0.0/
db1
Due to this limitation in Oracle 21c, mv dbs dbs.old
the location of spfile is moved to ln -s /u01/app/oracle/orabase/dbs
ORACLE_BASE_HOME. In Oracle dbs
Live Mount, the spfile is created cp dbs.old/* dbs
in ORACLE_HOME and it is not
recognized by Oracle Database and Make sure all the files in the dbs.old directory
causes a Live Mount failure. are copied to dbs. The ORACLE_HOME/dbs
directory is usually empty as the files are created in
ORACLE_BASE_HOME/dbs.
If you want to rollback the changes, remove the
soft link for the directory dbs using the following
steps:
Rubrik CDM supports IBM Db2 with specific backup types based on the versions of IBM Db2 and host
operating systems.
8.1.2+ 9.7, 10.x, and 11.x • CentOS All versions of CDM support host
• RHEL 7.x, 8.x architectures of Intel x86 on all
supported Operating Systems listed and
• SLES
of IBM PowerPC on AIX only.
• AIX 6.x, 7.x
SAP HANA
Rubrik CDM supports SAP HANA with specified backup types based on the version of SAP HANA and the
SAP HANA host OS.
Archival locations
Rubrik CDM provides support for data archiving in a variety of locations based on archive types, vendors,
products, and features.
Rubrik clusters that use Azure Disk Encryption (ADE) cannot index ADE-encrypted virtual machines
because Azure Kubernetes Service (AKS), which Azure Exocompute uses, does not support ADE encryption.
Red Hat Red Hat Ceph object S3- 4.2.0+ NA • Object granular
storage with S3 API compatible encryption.
access object • Supports
storage incremental
backups.
• Supports
consolidation.
• Supports encryption.
RBS support
Rubrik CDM supports these operating systems for Rubrik Backup Service.
5.3.2+ • Ubuntu 18.04, 20, 20.04 RBS does not support Amazon Linux
• Microsoft Windows Server 2019 2.
• Debian 9, 10
5.3.+ • Ubuntu 18.04, 20, 20.04 RBS does not support Amazon Linux
• Microsoft Windows Server 2019 2.
• Debian 10
5.2.1+ • CentOS and Oracle Linux 8.x RBS does not support Amazon Linux
• RHEL 8.x 2.
5.2.0+ • Solaris 10: Solaris 10 Update 11 (Solaris 10 RBS does not support Amazon Linux
1/13s10s_u11wos_24a) or later updates 2.
• Solaris 11: Solaris 11.1 SRU 14.5 (Branch: • Supports both x86 and SPARC.
0.175.1.14.0.5.0) or later SRUs and updates
5.0.4+ • CentOS and Oracle Linux 8.x RBS does not support Amazon Linux
• RHEL 8.0 2.
• Installation of Rubrik Backup
Service requires a manual
workaround, described in KB
000004503.
5.0.0+ • Solaris 10: Solaris 10 Update 11 (Solaris 10 RBS does not support Amazon Linux
1/13s10s_u11wos_24a) or later updates 2.
• Solaris 11: Solaris 11.1 SRU 14.5 (Branch: • SPARC only.
0.175.1.14.0.5.0) or later SRUs and updates
4.2.1+ • AIX 6.1, 7.1 TL3+, 7.2 RBS does not support Amazon Linux
• Microsoft Windows Server 2008 R2, 2012, 2012 2.
R2, 2016 • Technology Level 9 and newer.
• Ubuntu 14.04 LTS, 16.04 LTS, 17.04 • 64-bit only.
• SLES 11, 12 • The Rubrik CDM version 5.3
• RHEL 6, 7 release deprecates support for
• Oracle Linux 6, 7 Windows Server 2008 R2. Future
• Debian 8.x releases of Rubrik CDM will
• CentOS 6, 7 discontinue the support of this
operating system.
• RHEL 5.11 support has been
removed. Rubrik CDM requires
TLS 1.2 and RHEL 5.11 only
supports TLS 1.0.
Replication
Rubrik CDM provides forward and backward replication compatibility between specified versions of Rubrik
CDM.
The format of the partition-file has changed in Rubrik CDM version 6.0. This change affects filesets. If
a Rubrik cluster is upgraded to Rubrik CDM version 6.0, the target replication partners using previous
versions of Rubrik CDM are not supported. If the replication site is replicating filesets, the target clusters
must be upgraded to Rubrik CDM version 6.0 to resume replication.
Replication partnership is supported between Rubrik clusters up to two major versions under active
support earlier or later than the source cluster version.
For example, a Rubrik cluster 8.0.x can replicate to Rubrik CDM versions 6.0, 7.0.n, 8.0.n, 9.0.n, and
10.0.n, reciprocally.
Replication 06/13/2024 | 91
Chapter 36
Kubernetes
Kubernetes
Rubrik Security Cloud data protection for Kubernetes supports specific versions and configurations of
Kubernetes.
Rubrik CDM, CC, or CCES Vendor platform Vendor platform Kubernetes Distribution
versions versions Version
9.1.1-p1+ Azure Red Hat OpenShift OpenShift 4.12.x, 4.13.x, v1.25, v1.26, v1.27,
(ARO) 4.14.x v1.28
Red Hat OpenShift on OpenShift 4.12.x, 4.13.x, v1.25, v1.26, v1.27,
AWS (ROSA) 4.14.x v1.28
9.1.0+ Azure AKS v1.26.x, v1.27.x, v1.28
AWS EKS v1.26.x, v1.27.x, v1.28
Rancher Rancher v2.7.6 or later v1.26.x, v1.27.x, v1.28
Red Hat OpenShift OpenShift 4.12.x, 4.13.x v1.25.7, v1.26.x, v1.27.x,
v1.28
Note: Rubrik CDM
versions 9.1.1-p1 and Note: Rubrik CDM
later support OpenShift versions 9.1.1-p1 and
version 4.14.x later support Kubernetes
Distribution versions
v1.26.x, v1.27.x, v1.28.x
Kubernetes 06/13/2024 | 92
Rubrik CDM, CC, or CCES Vendor platform Vendor platform Kubernetes Distribution
versions versions Version
VMware Tanzu Grid TKG 2.2, 2.3 v1.25.7, v1.26.x, v1.27x
(TKG)
Note: Kubernetes
protection is supported
only on the worker
nodes in VMware Tanzu
Grid.
Longhorn CSI
Netapp Trident -
csi.trident.netapp.io
Rook Ceph
vSphere CSI driver
Kubernetes 06/13/2024 | 93
Chapter 37
Rubrik CDM virtual platforms
Rubrik CDM running on a single virtual node using Rubrik Edge supports the specified hypervisors.
Rubrik Cloud Cluster and Rubrik Cloud Cluster Elastic Storage (ES) are Rubrik CDM software running on an
AWS, Azure, or GCP virtual private cloud.
Rubrik Cloud Cluster uses dense node configurations. Rubrik Cloud Cluster Elastic Storage (ES) uses
standard and dense node configurations. Rubrik Cloud Cluster ES does not support mixing standard nodes
with dense nodes.
Rubrik Cloud Cluster has the following requirements:
• A minimum of four nodes per cluster
• A minimum of three data disks per node
Rubrik Cloud Cluster ES has the following requirements:
• A minimum of three nodes per cluster
• One data disk per node
Standard nodes do not support the following Rubrik CDM features supported on dense nodes:
• Direct Archive
• Managed Volumes
• Continuous Data Protection (CDP)
A Rubrik Cloud Cluster ES standard node cluster cannot scale beyond five nodes.
The following table describes standard node compatibility.
Cloud provider Instance type and Rubrik CDM Workloads and deployment
version
AWS • m4.xlarge running on Rubrik • Includes support for AWS
CDM version 4.2.x. GovCloud.
• m5.xlarge running on Rubrik • Includes support for AWS
CDM versions 5.0–8.0.3. Commercial.
• m6i.2xlarge running on Rubrik • Includes support for AWS
Cloud Cluster ES versions Outposts with supported
8.0.3+. versions of NAS, Windows
volumes, filesets, and SQL
Server databases. AWS
Outposts support requires gp2
disk for storage instead of st1.
• Does not support AWS China.
Cloud provider Instance type and Rubrik CDM Workloads and deployment
version
AWS • m5.4xlarge running on Rubrik • Using Cold HDD (sc1) disks for the data disks is
CDM versions 5.0–8.0.3. supported only with CDM v5.2 and higher.
• m6i.4xlarge running on Rubrik • Using Cold HDD (sc1) disks is supported
CDM versions 8.0.3+. only with node capacities of 24 TB due to
performance reasons.
• Mixing Throughput Optimized HDD (st1) disks
and Cold HDD (sc1) disks is not supported on
the same node or in the same Rubrik cluster.
• Using Cold HDD (sc1) data disks provides lower
performance when compared with Throughput
Optimized HDD (st1) performance, resulting in
slower backups, restores, and other disk-related
tasks. Initially ingesting data using st1 and then
switching to the sc1 disk type is supported.
• Includes support for AWS GovCloud.
• Includes support for AWS Commercial.
• Does not support AWS China.
• Includes support for Oracle.
• Includes support for AWS Outposts with
supported versions of the following protectable
objects: NAS, Windows volumes, filesets, and
SQL Server databases. AWS Outposts support
requires gp2 disk for storage instead of st1.
Rubrik Envoy
Rubrik CDM provides the Rubrik Envoy, trusted managed service provider software, in the specified
configurations.
Rubrik NAS Cloud Direct provides petabyte-scale unstructured data backup, archive, and storage system
solutions.
Rubrik NAS Cloud Direct is Trusted Partner Network (TPN) certified.
The following table describes backup destination support.
The following table describes the API integrations for Rubrik NAS Cloud Direct.
The following table describes the protocol and file type support for Rubrik NAS Cloud Direct.
The following table describes the generic Server Message Block (SMB) support for Rubrik NAS Cloud Direct.
The following table describes the On-premises S3 supported for Rubrik NAS Cloud Direct.
The following table describes the third-party applications that are not supported for Rubrik NAS Cloud
Direct.
The following table describes the hypervisors supported for Rubrik NAS Cloud Direct.
Hypervisor Supported
AWS Yes
Azure Yes
Linux KVM Yes
Nutanix AHV Yes
VMWare ESXi Yes
Windows Hyper-V Yes
Rubrik CDM provides support for Rubrik Security Cloud products in the specified configurations.
The following table lists the Rubrik Security Cloud (RSC) products and the supported Rubrik CDM versions.
The following table lists the support matrix for Data Security Posture product category.
User Intelligence 9.0.3, 9.1.1, or later User access and user activity
information is supported for:
• Windows virtual machines on
vSphere hypervisors
• Windows virtual machines on
Nutanix AHV hypervisors
• Windows virtual machines on
Hyper-V hypervisors
Additionally, user access
information is also supported
for Windows filesets and
Windows Volume Groups.
The following table lists the support matrix for Data Threat Analytics product category.
With Rubrik Security Cloud, you can protect the data of specific cloud workloads and their configurations.
The following table describes various Azure workloads and their compatibility with cloud native protection
and Rubrik Cloud Cluster Elastic Storage (CCES).
The following table describes various AWS workloads and their compatibility with cloud native protection
and Rubrik Cloud Cluster Elastic Storage (CCES).
The following table describes various GCP workloads and their compatibility with cloud native protection
and Rubrik Cloud Cluster.
GCP workload Cloud native protection Rubrik cloud Rubrik CDM version
cluster applicable only to Rubrik
cloud cluster
Google Compute Engine (GCE) Yes Yes Rubrik Cloud Cluster
instance supports the file-level
backup only. Rubrik
Cloud Cluster does not
support an image-level
backup.
Persistent disk Yes No Not applicable
Microsoft SQL Server running in No Yes 6.0 or later
a GCE instance
Oracle database running in a No Yes 7.0 or later
GCE instance
SAP HANA database running in No Yes 7.0 or later
a GCE instance
IBM Db2 running in a GCE No Yes 8.0 or later
instance
Google Cloud VMware Engine No Yes 8.0 or later
Windows volume groups No Yes 6.0 or later
Managed volumes (legacy) No Yes 6.0 or later
SLA Managed volumes No Yes 6.0 or later
Windows Filesets No Yes 6.0 or later
Linux Filesets No Yes 6.0 or later
Related reference
Virtual machine limitations
Rubrik Security Cloud has some limitations when protecting Azure virtual machines and AWS EC2
instances.
Database protection with Rubrik Security Cloud
Information about the various databases that Rubrik Security Cloud protects and their associated
limitations.
Rubrik Security Cloud security features
Supported disks for Azure virtual RSC supports the following disks for Azure virtual machines:
machines
• PREMIUMV2_LRS: Backup, archival, and replication operations are
supported, but file-level recovery and indexing operations are not
supported.
• PREMIUM_LRS: Backup, archival, replication, and indexing
operations are supported.
• PREMIUM_ZRS: Backup, archival, replication, and indexing
operations are supported.
• STANDARDSSD_LRS: Backup, archival, replication, and indexing
operations are supported.
• STANDARDSSD_ZRS: Backup, archival, replication, and indexing
operations are supported.
• STANDARD_LRS: Backup, archival, replication, and indexing
operations are supported.
• ULTRASSD_LRS: Backup, archival, and replication operations are
supported, but file-level recovery and indexing operations are not
supported.
RSC supports the following recovery operations for all supported
disks:
Azure Virtual Machine Scale Sets RSC does not support backup operations, including all the virtual
(VMSS) machines associated with VMSS.
Virtual machines with Azure Disk RSC supports the primary backup, archival, and replication features.
Encryption (ADE) enabled ADE will be enabled for the recovered virtual machine or managed
disk.
The recovery of Azure virtual machine with ADE and Platform
Managed Keys (PMK) to:
• Same Region and same Azure subscription is supported.
• Different region and same Azure subscription is not supported.
• Different region and different Azure subscription is not supported.
The recovery of Azure virtual machine with ADE and Customer
Managed Keys (CMK) to:
• Same Region and same Azure subscription is supported.
• Different region and same Azure subscription is not supported.
• Different region and different Azure subscription is supported.
Rubrik clusters that use ADE cannot index ADE-encrypted virtual
machines because Azure Kubernetes Service (AKS), which Azure
Exocompute uses, does not support ADE encryption.
Virtual machines with unmanaged RSC cannot take snapshots of virtual machines that have unmanaged
disks disks.
Virtual machines and managed RSC cannot protect virtual machines and managed disks that are
disks encrypted with storage encrypted with Storage Service Encryption using customer-managed
service encryption keys.
Virtual machines with the RSC supports the following actions:
encryption at host feature enabled
• Exporting a virtual machine using the source snapshot.
• Exporting a virtual machine using an archived snapshot.
• Exporting a virtual machine using a replicated snapshot.
• Exporting a virtual machine to a different- or cross-region.
• Exporting a virtual machine to a different- or cross-Azure
subscription.
To take backups for a virtual machine with the encryption at host
feature enabled, you must contact Rubrik Support.
To facilitate the cross-subscription export of a virtual machine, it is
required that you enable the encryption at host feature across the
relevant Azure subscriptions. You must contact Rubrik Support for
assistance in enabling this feature.
The following table describes various AWS virtual machines and their associated limitations.
Marketplace EC2 Instances and The marketplace EC2 Instances and EBS Volumes have the following
EBS Volumes limitations:
• RSC does not support cross-account replication and recovery for
EC2 instances launched from an AWS Marketplace AMI or an AMI
derived, either directly or indirectly, from an AWS Marketplace
AMI.
This is a limitation of AWS and impacts the backup and restore
functionality of RSC.
• RSC cannot archive EC2 instances created from AWS Marketplace
Amazon Machine Images (AMIs) to low-cost storage tiers.
• RSC excludes the EBS Volumes with marketplace tag from the
indexing job while performing indexing for an EC2 Instance.
• RSC does not support storage tiering for marketplace EBS
Volumes, marketplace EC2 instances, or instances with
marketplace tags.
Related reference
Cloud data protection with Rubrik Security Cloud
Database Description
Azure SQL Databases The process of taking immutable backups of Azure SQL databases has the
following limitations:
• Rubrik Security Cloud (RSC) requires enabling Change Data Capture
(CDC) on Azure SQL databases and tables for taking immutable
backups. Enabling CDC restricts schema changes, such as truncating
tables, renaming columns, and changing primary keys. To work around
this restriction, RSC provides procedures that you can invoke in your
database to disable CDC, perform the schema change, and enable
CDC again.
• RSC takes up to 24 hours to back up a 1 TB database.
• The Azure SQL databases in the basic tier and S0, S1, and S2 standard
service tiers are not eligible for immutable backups because Azure
does not support CDC for databases in these tiers.
• For Azure SQL databases with CDC enabled, the CDC schema is
excluded from the backup and is absent in the recovered database.
This exclusion is not dependent on whether CDC was set up manually
or using RSC.
• RSC does not support immutable backups for Azure SQL databases in
the Elastic pool with a maximum elastic Data Throughput Unit (eDTU)
of less than or equal to 100 or a maximum Virtual Core (vCore) of less
than or equal to 1.
• RSC does not support immutable backups for Azure SQL databases
that have ledger enabled.
• RSC does not support immutable backups for Azure SQL databases
that have encrypted objects.
• RSC does not support immutable backups if CHAR, VARCHAR, or TEXT
data types have collation settings different from those in the Azure
SQL database.
Amazon Relational Database RSC supports the following Amazon RDS database engines:
Service (RDS)
• MySQL, MariaDB, PostgreSQL
• Oracle and SQL Server
• Amazon Aurora
Amazon RDS protection with RSC has the following limitations:
• RSC supports replication only for policy-based snapshots.
• RSC does not support replication for continuous log backups or RDS
automated backups.
• RSC does not support archival or storage tiering for Amazon RDS
snapshots.
When using the replication feature across AWS accounts or regions,
Rubrik recommends that you coordinate with AWS Support to ensure that
Related reference
Cloud data protection with Rubrik Security Cloud
With Rubrik Security Cloud, you can protect the data of specific cloud workloads and their configurations.
Sensitive Data Monitoring RSC supports the Sensitive Data Monitoring feature only for Azure
virtual machines and managed disks using RCV for storing archived
snapshots.
RSC does not support the Sensitive Data Monitoring feature for the
following workloads:
• Azure SQL Databases and Managed Instances
• Amazon RDS
• Amazon Aurora
• AWS EC2 instances and EBS volumes
• Amazon S3
• GCE instance
• Azure virtual machine with Premium SSD v2 and Ultra disks
However, the Laminar application supports the Sensitive Data
Monitoring feature for these workloads.
Bring Your Own Kubernetes RSC supports the BYOK feature for AWS workloads for Kubernetes
(BYOK) for Exocompute version 1.27.
RSC does not support this feature for Azure workloads.
Two-Person Rule (TPR) RSC supports TPR for the following actions:
• Editing an SLA Domain
• Deleting an SLA Domain
• Deleting a snapshot
RSC does not support TPR for the following workloads:
• Windows and Linux filesets (protected through Rubrik Cloud
Cluster Elastic Storage (CCES))
• NAS Filesets (protected through Rubrik CCES)
Static Retention RSC supports the static retention feature on an RSC SLA Domain for
workloads protected through Rubrik CCES.
RSC does not support this feature for the following workloads:
• Azure virtual machines and managed disks
• AWS EC2 instances and EBS volumes
• GCE instance
• Azure SQL Databases and Managed Instances
• Amazon RDS
• Amazon S3
Retention Lock RSC supports the retention lock feature on an RSC SLA Domain for
workloads protected through Rubrik CCES.
RSC does not support this feature for the following workloads:
• Azure virtual machines and managed disks
• AWS EC2 instances and EBS volumes
• GCE instance
• Azure SQL Databases and Managed Instances
• Amazon RDS
• Amazon S3
Rubrik Cloud Vault (RCV) RCV supports archiving the backups of Azure workloads only to the
support for Azure workloads source region and not to a cross-region.
RSC only supports the RCV backup tier, not the archive tier.
The retention policy for the SLA Domain that uses RCV as the archival
location must have at least 30 days of archival retention. The RCV
Backup tier also has a minimum retention period of 30 days. To prevent
any early deletion fees, RSC ensures that any SLA Domains that are
created meet this requirement.
If you have removed an SLA Domain with RCV as the archival location
after taking the snapshot and need to perform in-place file recovery,
you must configure an Exocompute instance in your Azure tenant to
proceed with the recovery operation.
RSC does not support the RCV feature for the following operations that
require network connectivity between RSC and Azure workloads:
• Azure SQL v2 workflows
• Application-consistent snapshots of Azure virtual machines
• Azure In-place File Recovery
Archival destination tiers RSC supports the following archival destination storage tiers or classes:
• Azure storage access tiers: Hot, Cool
• Amazon S3 storage classes: S3 Standard, S3 Standard-IA, and S3
One Zone-IA
Azure virtual machine disk size RSC does not support archival of an Azure virtual machine with a disk
for archival size greater than 16 TiB.
Archival of on-demand RSC does not support the archival of on-demand snapshots for the
snapshots following workloads:
• Azure virtual machines and managed disks
• AWS EC2 instances and EBS volumes
Report Description
Object capacity report The object capacity report does not provide information for AWS accounts or
Azure subscriptions.
The object capacity report also does not include information about Azure SQL
databases and Azure SQL Managed instances.
Replication report Rubrik Security Cloud (RSC) does not support the replication report for Azure
workloads.
Kubernetes workload The available Kubernetes workload reports are Protection Status by Object,
report Compliance Status by Object, Monthly Compliance Status, Compliance Report,
and All Recovery Failure Events. All reports related to capacity will not include
data for the Kubernetes workload.
Related reference
Cloud data protection with Rubrik Security Cloud
With Rubrik Security Cloud, you can protect the data of specific cloud workloads and their configurations.
Rubrik CDM works with directory information from the services in the folllowing table.
Service Notes
Microsoft Microsoft Active Directory groups are mapped
to roles in Rubrik CDM and the permissions are
inherited by all members of the group.
The Orchestrated Application Recovery feature supports a specific set of operating systems.
Rubrik Security Cloud - Private (RSC-P) version 2.3.3 depends on specific Rubrik CDM versions to protect
supported workloads.
Rubrik CDM version requirements for Rubrik Security Cloud - Private 06/13/2024 | 120
Chapter 47
Rubrik API character set
The Rubrik CDM REST API supports only a specific character set.
The Rubrik CDM REST API requires the UTF-8 character set. All REST API calls to the Rubrik REST API
server must use UTF-8.
Web browser
For best results with the Rubrik web UI, use the newest version of the Google Chrome web browser.
The web UI supports the three most recent versions of Chrome.
The newest version of Chrome provides the most secure experience and is the preferred version for the
Rubrik web UI.
Running a web UI session with an older version of Chrome can result in some loss of functionality and
some deterioration of appearance and layout.