Skip to main content
Druva Documentation

System requirements

Phoenix Editions: File:/tick.png Business File:/cross.png Enterprise File:/tick.png Elite

Support matrix

This topic contains information about the Windows server that Phoenix certifies and supports.

Support levels

Druva categorizes its platform support levels as follows:

  • Certified Platforms: Druva certifies these environments and performs regular verification to ensure the functionalities work as expected.
  • Supported Platforms: The Druva QA team does not test a supported platform with every cloud release. However, the functionality should work as expected. Druva will provide support for such platforms. Druva may not address issues that require time and resources beyond commercial viability.

Certified platforms

Windows Server (64-bit)

Microsoft Windows Server 2016 (Standard and Datacenter editions)
Microsoft Windows Server 2012 R2  (Standard and Datacenter editions)
Microsoft Windows Server 2012  (Standard and Datacenter editions)
Microsoft Windows Server 2008 R2  (Standard and Enterprise editions)

Supported platforms

Windows Server (64-bit)

Microsoft Windows Server 2008 (Standard and Enterprise editions)
Note: If you are using SCVMM for managing virtual machines on Windows Server 2008 and Windows Server 2008 R2 hosts:
  • When you activate the Phoenix agent, select the type as standalone or cluster (based on your setup). Do not  select the type as scvmm to register your hosts through SCVMM.
  • Phoenix does not support registration of Microsoft Windows Server 2008 and Microsoft Windows Server 2008 R2 hosts through SCVMM. 

Hardware requirements for Phoenix agent on Windows

See, Hardware requirements.

Partition type and file systems for file-level restore (FLR) 

Windows:

  • Primary

  • Extended

  • Basic disk (Partition type: MBR/GPT)

  • Dynamic disk (Partition type: MBR. (simple/spanned volume)

Note: Dynamic Disk with GPT partition type is not supported.

Linux:

LVM (Simple/Spanned/Mirror/Stripped)

File-systems:

  • NTFS

  • FAT

  • FAT32

  • Ext2/3/4

  • XFS

System requirements for 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. 

Prerequisites

  • Phoenix agent interacts with Volume Shadow Copy Service to back up your data. To ensure successful backups, make sure that the Volume Shadow Copy Service is running. 
  • For Phoenix to use the Resilient Change Tracking (RCT) feature:
    • The agent version must be 4.7.5 or later, and
    • The agent must be installed on a Windows Server 2016 or later with virtual machine configuration version 6.2 or later. If the virtual machine is hosted on a Hyper-V cluster, then the virtual machine cluster functional level must be level 9 or higher. 
  • Druva recommends that you use the Microsoft’s native VSS provider. If you are using a third-party VSS provider, you must configure Phoenix agents to recognize this provider. 
  • Ensure that you enable Hyper-V role on the host.
  • Ensure that Phoenix service is running as administrator.
  • Ensure that you set the shadow storage value according to the virtual machine size.
  • Correctly configure SMB shares.  Windows Server VSS Agent Service must be installed on the server that hosts SMB shares.
  • Hyper-V host should have full control on SMB share. For a full list of requirements for SMB3 shares, see http://technet.microsoft.com/en-us/library/jj612865.aspx.
  • Druva recommends that you enable Backup (volume snapshot) under Hyper-V Integration Services. If the Backup (Volume snapshot) is enabled, Phoenix can take a virtual machine backup without interrupting services on the virtual machine. 
    Note: Integration Services are available for virtual machines with Windows guest OS. However, Microsoft provides Integration Services for certain Linux distributions also. For more information, see:
  • If you are installing and activating the agents on clustered hosts, ensure that Windows Remote Management (WinRM) is enabled. To enable WinRM, run the following command using the PowerShell:
    winrm quickconfig
  • If you are installing and activating the agents on clustered hosts and you are using a domain user, ensure that the domain user can start or stop services on the host. 
  • Ensure that the English language pack is installed on the Hyper-V hosts with a certified operating system that is localized to a language other than English. If the English language pack is not installed, the Phoenix Management Console is unable to list the number of virtual machines running on the host.  To add the English language pack on Windows, see Available Language Packs for Windows. [External link to Microsoft documentation]

Ports and communication protocols for Phoenix

Phoenix communicates with your hosts to backup and restore data on your hosts. Phoenix talks to your Hyper-V host through ports and protocols that are secure for communication and transition of data.

Phoenix uses Transport Layer Security (TLS) protocol for establishing the connection and initiating communication between Phoenix components and your Hyper-V hosts.

The following diagram depicts the ports and communication protocols that are used by Phoenix for secure connection and communication during the backup and restore operations.

port_and_protocol_for_hyperV.png