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
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
  3. NetBackup™ Web UI Cloud Administrator's Guide
  5. Recovering cloud assets
  7. Restore to a different cloud provider
NetBackup™ Web UI Cloud Administrator's Guide

Restore to a different cloud provider

NetBackup 10.5 or higher, lets you restore protected VMs from one cloud provider to another cloud provider from the backup from snapshot copy. For example, AWS to Azure and vice versa.

To restore across providers, at least one media server must be 10.5 or higher. This media server must have access the STU where the backed-up image resides.

Table: Steps to be performed to restore between AWS and Azure cloud provides the steps to be performed for the following operating systems:

  • RHEL

  • SLES

  • Ubuntu

  • Windows

Table: Steps to be performed to restore between AWS and Azure cloud

Steps

Description

Step 1: Prepare the VMs for back up

  • Check if the VM is part of supported VM (OS/Platform).

    Refer to the Hardware and Cloud Storage Compatibility List (HCL).

  • Back up the source VM before making any changes.

  • Identify and install the appropriate drivers that must be preinstalled before backing up the source VM.

Depending on the operating system, refer to the following specific sections for preparing the VMs:

  • RHEL

  • SLES

  • Ubuntu

  • Windows

Step 2: Backup the VMs

Back up the VM after installing the drivers.

Step 3: Cross cloud provider restore configuration

  • Select cross-provider configuration where you want to restore the target VM in the destination cloud provider.

  • Select the appropriate instance size of the target VM based on your requirement.

For target AWS:

  • Ensure that you have a compatible AMI ID while restoring the VM.

  • Required parameters to restore to AWS: ImageId (AMI) and Instance type

  • Select AMI and instance type that supports the source VM's boot mode (Legacy BIOS/UEFI)

    For more information, refer to Amazon EC2 boot modes.

  • Matching OS platform with source VM is required.

  • Log on using same username and password as source VM.

    Note:

    If the instance reachability check fails, then perform the steps mentioned in the following section after the VM is restored:

    Step 4: Post restore configuration

For target Azure:

Select instance type that supports the source VM's boot mode and supported number of attached disk drives.

Step 4: Post-restore configurations

Additional configuration to ensure that the restored instance is reachable.

Depending on the operating system, refer to the following sections for post restore configurations:

  • RHEL

  • SLES

  • Ubuntu

  • Windows

Feedback

Was this page helpful?
Previous

Perform rollback recovery of cloud assets

Next

Prepare the VMs for back up

Feedback

Was this page helpful?