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 1, 2 Fedora 27+ 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 periodically be up

Question 2

Cirrus Migrate Cloud Licensing Model

Accepted Answer

This articles describe various types of Cirrus Migrate Cloud licensing and how you can use them.

| Contact Sales for Free Trial and other licensing inquiries including volume licenses and enterprise licenses. You can also send inquiries to info@cirrusdata.com

Licensing Scheme

Cirrus Migrate Cloud supports the the following scheme: Credits (Prepaid) and Subscriptions (Postpaid).

Credits-based licensing is similar to a prepaid phone card where migration license credits can be consumed and refilled at any time. Subscription-based licensing is a post-paid licensing scheme that migration usage is metered and billed on a monthly basis.

License schemes can be chosen whenever a project is created. Different licensing schemes can be applied to different projects at the same time.

Licensing Credits (Prepaid)

Credits-based licensing requires various types of license credits (see below) to be purchased before migration can start. Each user has a License Key that can be used to store license credits that the user owns. To go to your license key, click on your avatar on the top and select My License Key.

Every project with this licensing scheme selected will also have a license key that belongs to the project. Every hosts in this project will automatically consume credits from this project-level license key.

License Credits can be transferred between your user license key an

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 - On-Premises to Azure

Accepted Answer

The attached document provides detailed steps on how to use Cirrus Migrate Cloud to move data from On-Premises 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 5

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 6

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

Frequently Read Articles

Browse All Categories