Question 1

Cirrus Migrate Cloud OS/Kernel Requirements

Accepted Answer

Cirrus Migrate Cloud software is qualified for the following operation systems:

Qualified Windows Releases

Windows Server 2008R2 Windows Server 2012 Windows Server 2016 Windows Server 2019 Windows Server 2022

Qualified Linux Distributions

RHEL 6.0 - 8.4 (And all compatible distros such as RockyLinux, Oracle Linux or CentOS) Ubuntu 16.04, 18.04, 20.04 Amazon Linux 2 Fedora 27, 28, 33, 34 Debian 9, 10

Linux Installation Requirements

Cirrus Migrate Cloud contains software components that run in both userland and Linux kernel.

Pre-built kernel modules are available for a fleet of commonly used kernel versions and distributions. If your kernel version is not on the following list, the kernel component will have to be compiled on the host.

To compile the kernel module, you will need the following packages:

gcc
gnu make
kernel-devel and kernel-headers (or linux-headers for debian/ubuntu) that matches the version of the operating system's kernel version.

| If these packages are not available at the time of installation, the Cirrus Migrate Cloud Installer will attempt to obtain them from the system's existing package manager (yum or apt). However, if they cannot be downloaded due to network security or other reasons, these packages will have to be manually obtained and installed.

List of available pre-built kernel modules

If you kernel version is on the list below, no compilation tools will be required for installation

_This list will periodical

Question 2

HOWTO: Cirrus Migrate Cloud - Migration from AWS to Azure

Accepted Answer

The attached document provides detailed steps on how to use Cirrus Migrate Cloud to move data from AWS EBS volumes to Azure Managed Disks. A shorter version of this document can be found here.

**PLEASE NOTE: **The latest version of this document will always be available on this page.

${frame}PDF

Question 3

Migrating Boot Volumes

Accepted Answer

Cirrus Migrate Cloud (CMC) can be used by migrating boot volumes (os volumes) on all supported windows and linux operating systems. Many of the CMC functionalities benefits boot volume migration as well.

Note: Cirrus Migration Cloud Software Version 3.0.0+ is required

This includes:

Auto Destination Allocation
iQoS
Local / Remote Migration
Automatic resynchronization
Migration Automation (Pre/Post Migration Actions)

….and more.

Requirements

||| Before proceeding, you MUST ensure that you possess knowledge and ability to perform all necessary changes to your host (or other infrastructure) so that your hosts will boot from the migrated volumes. These configuration changes requirements vary depending on specific system configurations. They may include:

Filesystem mount point configuration
BIOS (or other boot system) settings
Volume Assignment settings (such as some SAN boot configurations where the lun number for booting is fixed)

How-To Migrate Boot Volumes

Creating Migration Session

Migration sessions for boot volumes can be created just like any other migration session. During Migration Session Creation, “Step 2. Select Migration Volume Type” allows selection of migration for Boot Volumes:

Follow the rest of the steps of the wizard to pair the source and destination boot volumes. It is highly recommended to use a separate migration session f

Question 4

HOWTO: Cirrus Migrate Cloud - Migration Between Azure Tiers

Accepted Answer

The attached document provides detailed steps on how to use Cirrus Migrate Cloud to move data from Azure Standard SSD to Azure Ultra Disk Storage. A shorter version of this document can be found here.

**PLEASE NOTE: **The latest version of this document will always be available on this page.

${frame}PDF

Question 5

How to establish host-to-host (H2H) network connections for remote migration?

Accepted Answer

How to establish host-to-host (H2H) network connections for remote migration?

What is H2H Connection

Host-to-Host (H2H) connections are optimized one-way TCP-based network connections that cirrus-migrate-cloud uses to facilitate remote-migration, which features always-on compression and encryption.

By design, NO PRODUCTION DATA / I/O leaves the production network during the entire migration phase. As a result, direct connectivity between the source and destination host is required.

Network Requirement

| Unless specifically specified, H2H connection uses port 4996 for communication.

H2H Connection is a one-way connection only and can be established in either direction. Ports and firewall rules only have to be opened on one of the servers (source host or destination host).

For example, for cloud migration back to on-premises, it might be easier to open up the inbound rule at the cloud, as it often takes a lengthy approval cycle for on-premises datacenters to change inbound firewall rules.

How to setup

To create a H2H connection, go to Host --> H2H Connections --> Create.
Specify the "from host" and "to host."
Enter a connection IP / Hostname. Most of the time, this will be the receiver host's IP address, unless more complex network configuration is involved.

|| H2H connectivity can be established to/from any direction and is NOT tied to migration direction.

Regardless of which host is source / destination, connect

Question 6

Creating an Azure Service Account for Cirrus Data Cloud

Accepted Answer

Creating an Azure Service Account for Cirrus Data Cloud

|| NOTE: To follow this guide, you will need the following roles or equivalent higher roles:

User Access Administrator (Subscription Level IAM)
Application Administrator (Directory Level IAM)

Register an Application for Cirrus Data Cloud

Go to 'App Registrations'
Name and Create the application
On the Overview page, copy the following values into a document:

Application (client) ID
Directory (tenant) ID

On the App page, go to 'Certificates & Secrets'
Click 'New Client Secret'
Copy the value generated somewhere secure

Create a Custom Role for Cirrus Data Cloud

Under the subscription to be used for Cirrus Data Cloud, first go to the IAM page and click 'Create Custom Rule'
Add a name and description and verify that 'create from scratch' is selected
On the permissions tab, add the following permissions:

Microsoft.Authorization/permissions/read
Microsoft.Compute/virtualMachines/read
Microsoft.Compute/virtualMachines/write
Microsoft.Compute/disks/read
Microsoft.Compute/disk/write
Microsoft.Network/networkInterfaces/join/action

Click 'review+create' ![](https://storage.crisp.chat/users/helpdesk/we

Frequently Read Articles

Browse All Categories