Support matrix
Before you set up Druva Phoenix, you must ensure that the virtual machines or the servers that you plan to use, meet the system requirements.
This article gives you information about:
- Browser support
- Software requirements
- Hardware requirements
- Network requirements
- Security considerations
- Supported storage regions of Druva Phoenix
Browser support
The following table lists the supported browsers for accessing the Management Console.
| Browser | Minimum requirements |
|---|---|
|
Web browser |
|
Software requirements
The following sections provide the software requirements for Druva Phoenix to back up data residing on servers.
Software requirements for files and folders
Ports and communication protocols for Druva Phoenix
Software requirements for Hyper-V
Ports and communication protocols for Druva Phoenix
Software requirements for MS-SQL server
Certified platforms
Prerequisites
-
The Hybrid Workloads agent interacts with Volume Shadow Copy Service (VSS) to perform full backups. Ensure that the Volume Shadow Copy Service is not disabled.
-
The Hybrid Workloads agent uses Microsoft SQL Server Virtual Device Interface (VDI) for differential and transaction log backups.
-
The account used for SQL backups and restores must also have the CREATE DATABASE permission for successful restores from snapshots. If the account used for SQL backups and restores does not have the CREATE DATABASE permission, the restores may fail with the SQL7 error. For more information, see GRANT Database Permissions.
Note: As with any other third-party backup software, Druva Phoenix interfaces with Microsoft Virtual Device Interface (VDI) to perform differential and transaction log, backups and restores. The SysAdmin role is mandatory for VDI backups and restores. If the user account used for SQL VDI differential backups does not have the sysadmin role, the backups will fail in the initial stages. If differential and transaction log backups and restores are not required, sysadmin permissions are not required. For more information, see SQL Server VDI backup and restore operations require Sysadmin privileges.
-
Druva recommends that you use the Microsoft’s native VSS provider. If you are using a third-party VSS provider, you must configure Hybrid Workloads agents to recognize this provider.
- Ensure that the SQL Writer Service on your MS-SQL servers is running.
- Ensure that the disk space on the drive where your shadow copy storage is located is adequate for the cumulative size of your databases. To know how you can configure VSS to write shadow copies to a separate drive, see Set VSS to write shadow copies to a separate NTFS volume.
- Ensure that you enabled Windows authentication for your SQL servers. For more information, see Change Server Authentication Mode.
- Ensure that the Local System account has permissions listed in the following table:
Permission Description Sysadmin Required for SQL server backup and restores.
Note: As with any other third-party backup software, Druva Phoenix interfaces with Microsoft Virtual Device Interface (VDI) to back up and restore SQL Database Transaction Logs. To use VDI, SysAdmin role is mandatory. If transaction log backups and restores are not required, sysadmin permissions are not required.
For more information, see Backup (Transact-SQL), and Restore Statements (Transact - SQL)
- If you want to perform log backups for the database, ensure that you set the databases to FULL RECOVERY mode. For more information about modifying recovery mode, refer to View or Change the Recovery Model of a Database.
- Druva Phoenix supports backup of availability group databases in MS-SQL server 2012 onward since Microsoft introduced availability group in SQL 2012.
- Ensure that you install Hybrid Workloads agent on all primary and secondary nodes in the availability group.
- Ensure that you enable the Readable secondary option for the secondary nodes for successful backups from that node.
- Ensure that all the nodes in an availability group must have the same Hybrid Workloads agent version installed on them.
- If you want the Hybrid Workloads agent to run under a domain user account:
- Ensure that the domain user is added under the local administrative group of the SQL server
- Ensure that Hybrid Workloads agent and SQL Server VSS writer service log on using the same domain user account. (By default both services log on using the local system account.)
- Ensure that Sysadmin right is assigned to the domain user in the SQL server.
Software requirements for NAS devices
Permissions for NAS auto-discovery
Software requirements for NAS proxy
Ports and communication protocols for Druva Phoenix
Druva Phoenix communicates with your NAS shares to back up and restore the data. This occurs through ports and protocols that are secure for communication and transition of data. Druva Phoenix uses Transport Layer Security (TLS) protocol to establish a connection and initiate communication between Druva Phoenix components and your NAS device.
The following diagram depicts the ports and communication protocols that Druva Phoenix uses for secure connection and communication during the backup and restore operations.
Software requirements for Oracle Druva Phoenix Backup Store
Software requirements for Oracle Direct to Cloud
Software requirements for VMware
Software requirements for Nutanix AHV
Software requirements for Phoenix CloudCache
Ports and communication protocols for Druva Phoenix
Hardware requirements
The Hybrid Workloads agent installer, VMware backup proxy appliance, Hyper-V FLR proxy appliance, Phoenix Backup Store package, and the CloudCache installer are available at http://downloads.druva.com/phoenix/.
You can also download the installer at the time of registering servers.
Prerequisites for Hybrid Workloads agent
This section contains the prerequisites for the Hybrid Workloads agent. This configuration is applicable for one backup or restore job at a time. Applies to:
- Hyper-V virtual machines
- Files on a server
- MS-SQL server
Hardware requirements for installing Hybrid Workloads agent
| Hardware | Minimum requirements |
|---|---|
|
CPU |
|
| RAM | 3 GB |
|
Free space |
|
Hardware requirements for Hyper-V FLR proxy
Before you deploy and activate the FLR proxy, ensure that following system requirements on the Hyper-V host are met for the proxy:
- Memory: 2 GB
- vCPUs: 2
This is a recommended configuration for two restore jobs. If you want to run multiple restore jobs, increase the memory and number of vCPUs.
Disks, partitions, and files supported for File Level Restore (FLR) on Hyper-V hosts
-
Item Certified Disk Types
- Thin
- Thick
Partition Tables
- MBR
- GPT (Linux)
Partition Types
- Primary
- Extended
- LDM (Only Simple and Spanned Volumes with MBR)
- LVM (Simple/Spanned/Mirror/Striped)
File Systems
- NTFS
- FAT
- FAT32
- Ext2/3/4
- XFS
File Type
- Regular Files
- Sparse Files
- Hidden Files
Hardware requirements for NAS shares
Hardware requirements for VMware
This table lists the minimum requirements for deploying a backup proxy that is available as a virtual appliance.
Backup proxy requirements
Backup proxy is available as a virtual appliance. Deploying backup proxy creates a virtual machine with the configuration that is listed in this table. Ensure that your VMware setup can assign resources to support this requirement.
- For more information, see Prerequisites to install the backup proxy.
-
Hardware requirements for the Druva Phoenix Backup Store
Hardware requirements for Phoenix CloudCacheNetwork requirements
Field Requirement Network Traffic rules
Hybrid Workloads agent:
Hybrid Workloads agents connect to Druva Cloud using port 443.
Phoenix CloudCache:
Phoenix CloudCache connects to Druva Cloud using port 443.
Hybrid Workloads agents connect to Phoenix CloudCache using port 443.
Druva Phoenix Backup Store
Druva Phoenix Backup Store connects to the Druva Cloud using port 443.
Firewall For all the agents and CloudCache: If the firewall is enabled, allow all outbound TCP/IP traffic to *.druva.com through port 443. Web proxy Druva supports the following proxy types:
- http
- socks4
- socks5
For more information see:
- For more information, see Sizing for backup proxy.
-
Security considerations
One thing that is often overlooked when deploying a data protection solution is security. While Druva automatically handles the security of information in transit and at rest, there are other security mechanisms that organizations should consider for implementing beyond encryption when it comes to data protection. The following sections discuss the security considerations that organizations should take into account as they implement Druva Phoenix for their data protection solution.
Roles and responsibilities
To prevent privileged users from making unauthorized changes to resources within their organization, Druva Phoenix supports the Role Based Access Control (RBAC) for separation of duties. This capability allows organizations to limit privileged user access to a predefined set of roles and data assets. This RBAC capability makes it possible to create ethical walls to enforce privacy, as well as implement a delegated administration structure to meet customers’ organizational, compliance, or security requirements. To add RBAC in your Druva Phoenix deployment, see Manage administrators.
Global regulatory compliance
As part of your data protection strategy, organizations need to take into account where they operate and what requirements they have on security and availability of the data. With Druva Phoenix , organizations can store data in any of twelve global regions depending on their security, compliance, data access, and availability requirements. While not only a compliance requirement, proximity to data can also help shrink the time it takes to recover in the event of a disaster.
Single Sign-On
Druva Phoenix supports SAML which allows organizations to centralized authentication for the administration of their Druva Phoenix environment. This allows administrators to leverage existing centralized authentication mechanisms like Okta, Ping Identity, or Active Directory which are already being used today. The use of Single Sign-On (SSO) helps to guarantee the availability of access to Druva Phoenix and eliminates local authentication stores which cause audit and compliance headaches as well as create a security risk. To integrate Druva Phoenix with your SSO authentication mechanism, see Configure single sign-on for Druva Phoenix.
Testing your recovery
As part of your data protection strategy, it is important to see if what you are backing up is actually getting backed up, whether part of a normal business continuity and disaster recovery process.
Conclusion
While protecting data in flight and at rest are important security capabilities of any enterprise-level data protection solution, there are definitely more issues to take into account, and more capabilities to take advantage of when it comes to protecting the overall data attack surface. For identifying and implementing more such security considerations for Druva Phoenix , contact Druva Support.
Supported storage regions
The supported storage regions for Druva Cloud and Druva Phoenix GovCloud are mentioned on the Cloud Status page of the Druva Support Portal.
You can hover over the relevant donut chart on the Cloud Status page or click VIEW DETAILS to see the information.