Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
AI

Welcome to Cohesity Documentation.

Ask me anything — from configuration steps and architecture overviews to troubleshooting, feature details, and release notes.


AI may make mistakes. Always verify critical information.

Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. HSCL
  3. Recovery to Azure
  4. Compatibility matrix for disaster recovery of physical machines to Azure

Compatibility matrix for disaster recovery of physical machines to Azure

Compatibility matrix for disaster recovery of physical machines to Azure lists the compatibility matrix for disaster recovery of physical machines to Azure.

Table: Compatibility matrix for disaster recovery of physical machines to Azure

Supported physical machines

Operating systems

Versions

RHEL

7.4, 7.5, 7.6, 7.7, 7.9, 8.0, 8.3, 8.6, and 9.0

CentOS

7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.6, 7.7

SLES

12.5, 15.2

OEL UEK

7.7

Windows Server

2012, 2012 R2, 2016, 2019, and 2022

Notes:

  • The replication technology for recovery to Azure is Veritas Resiliency Platform Data Mover.

  • For Windows workload physical machines, the PowerShell version equal to 2.0 and above but less than 3.0 the required .Net version must be in range of 3.5 to 4.5. For PowerShell version equal to 3.0 and above, the minimum required .Net version is 4.5.

  • RHEL hosts having multiple NICs need to have NetworkManager-config-routing-rules package installed on them.

  • Multipathing on target side virtual machines is not supported.

  • Physical machines require an additional internal or fiber channel disk connected which needs to be a separate disk and not an existing partition or added partition to an existing disk, this disk acts as a replication block tracking disk required for replication.

Feedback

Was this page helpful?
Previous
Compatibility matrix for disaster recovery of virtual machine from Azure / Azure Stack to Azure / Azure Stack
Next
Compatibility matrix for disaster recovery of virtual machines to Azure using NetBackup MSDP-C

Feedback

Was this page helpful?