Support Matrix
Business Enterprise Elite
Supported VMware setup
This section lists the supported versions for VMware vCenter Server and ESXi Hosts.
|
vCenter Server |
ESXi Host |
Backup Proxy Compatibility |
|---|---|---|
|
8.0 |
|
6.3.1-299480 or later |
|
7.0 |
|
4.8.15_96907 or later |
|
6.7 |
|
4.7.2-42700 or later |
|
6.5 |
|
|
|
6.0 |
|
|
|
5.5 |
|
|
- Druva does not certify VMware vCenter Server versions 5.5 and 5.1. However, backups and restores on these setups should work as expected. Druva strongly recommends you to upgrade the VMware vCenter Server to the latest supported version. Refer to the article for more information about the end of the general support for vSphere 5.5.
- Auto-upgrade will not be supported for proxies with versions less than 4.8.0. You must install the latest RPM manually. For more information, see Installing RPM for auto-upgrade.
- Druva supports vSphere 8.0 with DataSets. Therefore both vCenter Server and ESXi must be on version 8.0 or later, and the hardware version of the virtual machines must be version 20 or later. For more information on DataSet files, see vSphere DataSets.
- vSphere 8.0 is not certified for IR Agent.
- If the load balancer distributes the job to the VMware backup proxy, which is incompatible with DataSets recovery, then the DataSets file will not be backed up.
Guest operating systems
Druva qualifies virtual machines with the following guest operating systems for backup. However, any guest operating system should work if the virtual machine recovery point(VMware tools quiescing turned ON) works fine.
|
Operating System |
Editions |
|---|---|
|
Windows |
Note: Druva performs image-level backups of virtual machines. So, unless you plan to enable application-aware processing for a virtual machine, Druva continues to back up the virtual machine with any guest operating system. |
|
Linux |
|
Supported SQL application versions for Application-aware backups
|
Windows Server (64-bit) (Standard and Enterprise editions) |
SQL Server editions |
|---|---|
|
Windows Server 2019 |
|
|
Windows Server 2016 (x86-64) |
|
|
Microsoft Windows Server 2012 R2 |
|
|
Microsoft Windows Server 2012 |
|
|
Microsoft Windows Server 2008 R2 SP 1 |
|
|
Microsoft Windows Server 2008 R2 |
|
Note: Express editions are not supported.
Disks, partitions and, files for File Level Restore (FLR)
|
Item |
Supported |
|---|---|
|
Partition Types |
|
|
File Systems |
|
|
File Type |
|
OS, File System, and Volume types supported for Dynamic GPT
|
Item |
Supported |
|---|---|
|
Operating System (source backup set) |
|
|
File Systems |
|
|
Volume Type |
|
Note: For the REFS file system on any type of volume, the staging VM should be either the source backup set OS version or the next higher version for a successful browse and subsequent restore. For example, if the source backup set is Windows 2016, then the supported OS versions of the staging VM are 2016, 2019, and 2022.
vSAN versions
Druva backup proxy supports backup and restore of virtual machines on the following vSAN versions:
- 7.0
- 6.6
- 6.5
Note:
Phoenix backup proxy agent for VMware virtual infrastructure integrates with ESX and vSPhere vStorage API (VADP) to perform backup and restore.
If the ESX/vSphere host is not licensed for the vStorage APIs, the backup and restore operations fail.
To verify whether the ESX/vSphere host is licensed for vStorage APIs - Click here
Installing RPM for auto-upgrade
Following are the steps to manually install RPM:
- Download RPM from Druva downloads page and copy the rpm on the backup proxy that needs to be upgraded.
- List the installed RPM name on your proxy using the following command:
rpm -qa | grep druva - Uninstall the RPM using the following command. Select No to prevent cleaning all the installation files.
rpm -e <name from above command> - Install RPM and start the Phoenix service:
rpm -ivh <name of rpm copied from downloads page> - Set the vCenter credentials on proxy using the following command:
vCenterDetail set <hostfqdn> <username> <password> - Restart the Phoenix service.