---
title: "Run EZswitch on Linux from the Zesty platform"
slug: "run-ezswitch-from-the-zesty-platform-1"
updated: 2025-03-11T12:40:29Z
published: 2025-03-11T12:40:29Z
canonical: "docs.zesty.co/run-ezswitch-from-the-zesty-platform-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zesty.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Run EZswitch on Linux from the Zesty platform

This topic describes how to run EZswitch on a Linux instance from the Zesty platform.

Before beginning EZswitch, ensure that your environment is supported, as described in the “Limitations” section of [How EZswitch works on standalone instances](/v1/docs/how-ezswitch-works-on-standalone-instances).

#### Prerequisites

- The steps described in [Before you deploy on standalone instances](/v1/docs/before-you-deploy) If the installed Agent is not the most recent version, you cannot run EZswitch. First update the Agent by installing it again, as described in [Install the Zesty Disk Agent on standalone instances](/v1/docs/install-the-zesty-disk-agent-1).
- A mounted volume with data to be migrated
- An instance with a clean volume (not the root volume), that meets the volume, instance, and network settings described in [System requirements](/v1/docs/system-requirements)

In the following example, our data is at mount point **/data1**, a supported EXT4 filesystem on a 25GB volume, **/xvdb**.

Throughout this procedure, you can expand the accordion boxes to see further insights into what’s going on in the background.

**Click here to see the filesystem before beginning EZswitch**

On the Zesty platform:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_filesystem_before_zesty_platform.png)

Using `zestyctl disk list`:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_filesystem_before_zestycli.png)

Using `lsblk`:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_filesystem_before_instance.png)

On AWS:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_filesystem_before_aws.png)

#### To run EZswitch from the Zesty platform:

1. From the Zesty platform main menu, select **Zesty Disk**.
2. From the **Managed Filesystems** tab, identify the filesystem where the data is located then click **Select solution > Install Zesty Disk**. **Note**: this option will not be displayed unless the installed Agent is the most current version. To update the Agent, install it again, as described in [Install the Zesty Disk Agent on standalone instances](/v1/docs/install-the-zesty-disk-agent-1).

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_managed_fs_start_ezswitch(1).png)

The EZswitch wizard starts:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_wizard_11_24(1).png)

The time estimate depends on the amount of data to migrate.
  1. (Optional) To perform automatic restarts, select **Automatic Restart**.

You can then specify when to do the restarts, like during a maintenance window. In this example, we will show manual restarts from the UI.
  2. (Recommended) To automatically remove the old volume after completion, select **Remove old volume** and enter the number of days before removal.

In AWS, you still pay for the old volume until it is removed.
  3. (Optional) To skip the creation of a snapshot, select **Do not create snapshot**.
  4. (Recommended) If a snapshot is being made, to automatically remove the snapshots, select **Remove Snapshot** and enter the number of days before removal.
3. Click **Start**.
4. In the expanded view of the filesystem, click the **EZswitch** tab:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_started.png)

To modify the restart and remove options, click **Settings** to return to and modify those options. You can change the selections any time before the first or second restart.

EZswitch begins with your server initiating communication. This may take several minutes.

You can cancel EZswitch by clicking **X** to the right of the progress bar. You can cancel as long as the instance has not yet been restarted.

The preparation steps continue in the background until the first restart is required.

![zd_ezswitch_pending_first_restart](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_pending_first_restart.png)
5. When it’s time to restart (“Pending restart”), click **Reboot** (or reboot another way).

After the restart, all new data will be written to the Zesty Disk and the old data will start to be copied to the Zesty Disk. The time to complete the copying is determined by the amount of data to be transferred.

After the first restart, the name of your original mount point will change, and in its place you will see two mount points: **_old** (the original mount point) and **_new** (the Zesty Disk).

Note: **_new** has a small initial size, and it will increase, as needed.

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_after_first_restart.png)

During the data transfer, application reads and writes continue as normal under the original mount point name.

The Zesty Disk starts small, and then automatically expands as data is copied to it.

**To see the temporary mount points on the instance, click here**

You can see the mountpoints on the instance using `lsblk` and `zestyctl disk list`.

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_temp_mountpoints.png)

When all the data is copied, you are prompted to restart.
6. Click **Reboot** (or reboot another way).

After the second restart, you can see the following changes:

The temporary mount point names (**_old** and **_new**) are removed.

The old mount point (25GB) is no longer shown in the Managed Filesystems table.

The original mount point name has been returned and is now on a Zesty Disk filesystem!

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_complete(1).png)

The old volume is no longer used, but is still in the AWS account, and you will be charged for it until you remove it. You can remove it manually, or you may have configured it to be removed automatically when starting EZswitch.

**Congratulations! Your volumes are now being managed by Zesty Disk.**

**To see the mount points after EZswitch has completed, click here**

The original **/data1** mount point on **xvdf** has returned to its original name:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_mountpoint_after_ezswitch_instance.png)

Now, it’s managed by Zesty:

![](https://cdn.document360.io/0eb80240-664b-49f5-9181-5713ddf9f725/Images/Documentation/zd_ezswitch_mountpoint_after_ezswitch_zestyctl.png)