All Products
Search

This Product

    :End-of-life notice for Alibaba Cloud Shared Block Storage

    Document Center

    :End-of-life notice for Alibaba Cloud Shared Block Storage

    Last Updated:Mar 29, 2024

    Alibaba Cloud announced the end of life (EOL) of Shared Block Storage (in public preview). The last day when you can use Shared Block Storage was on June 29, 2023. To prevent data security risks that may be caused by the EOL of Shared Block Storage, we recommend that you back up and migrate your data from the Shared Block Storage devices that you no longer need and then delete the Shared Block Storage devices as soon as possible.

    If you want to share a block storage device among multiple Elastic Compute Service (ECS) instances after June 29, 2023, you can use the multi-attach feature that is provided by Elastic Block Storage (EBS). The multi-attach feature was released for commercial use and is supported by all enhanced SSD (ESSD) series. For more information, see Support for the NVMe protocol and multi-attach feature.

    Service discontinued

    Alibaba Cloud announced that Shared Block Storage (in public preview) reached EOL on June 30, 2023.

    EOL date

    June 30, 2023

    Impacts

    Starting June 30, 2023, Alibaba Cloud Shared Block Storage (in public preview) is unavailable and related services such as ECS may also be unavailable.

    Solution

    Step 1: Back up and migrate data

    1. Create a snapshot for each Shared Block Storage device whose data you want to migrate. For more information, see Create a snapshot for a disk.

      The snapshot creation process requires a specific period of time to complete. If data changes occur during the process, you must migrate the incremental data. To ensure data consistency, we recommend that you stop the ECS instance to which the Shared Block Storage device is attached before you create a snapshot for the device.

      Warning

      When you stop the ECS instance, services that run on the instance are interrupted. Proceed with caution.

    2. Create a Non-Volatile Memory Express (NVMe) disk from the snapshot. For more information, see Create a disk from a snapshot.

    3. Attach the NVMe disk to the destination ECS instance to which you want to migrate data. For more information, see Attach a data disk.

      Currently, only specific instance families, such as g7se, c7se, and r7se, support the NVMe protocol and allow NVMe disks to be attached. If no ECS instances that support the NVMe protocol are available, create an ECS instance that supports the protocol. For more information, see Create an instance on the Custom Launch tab. For information about other limits on NVMe disks, see NVMe disks.

    4. Restart the destination ECS instance. For more information, see Restart an instance.

      Warning

      The restart operation stops the ECS instance for a short period of time and may interrupt services that run on the instance. We recommend that you restart the instance during off-peak hours.

    Step 2: Detach Shared Block Storage devices

    After you verify that your business runs as expected on the destination instances, we recommend that you detach Shared Block Storage devices from ECS instances and then release the ECS instances based on your business requirements.

    • Detach Shared Block Storage devices from ECS instances. For more information, see Detach a data disk.

    • (Optional) Release the ECS instances. For more information, see Release an instance.

    Step 3: Delete Shared Block Storage devices

    In this example, a Shared Block Storage device that resides in Beijing Zone C and whose ID is v-2zeftu16j27q5hwl**** is used.

    1. Call an API operation in the OpenAPI Explorer to query whether a Shared Block Storage device is attached.

      1. Debug the DescribeDisks operation.

      2. Select China (Beijing) from the Region drop-down list.

      3. In the DiskIds field, enter the ID of a Shared Block Storage device. Example: ["v-2zeftu16j27q5hwl****"].

        Important

        You must enter the Shared Block Storage device ID in the following format: ["Shared Block Storage device ID"]. Otherwise, the query fails. For more information, see DescribeDisks.

      4. Click Initiate Call.

      5. In the right-side pane, check whether the value of the Status response parameter is Available.

        The value Available indicates that the Shared Block Storage device is not attached. Shared Block Storage devices can be deleted only when they are in the Available state.

    2. Call an API operation in the OpenAPI Explorer to delete the Shared Block Storage device.

      1. Debug the DeleteDisk operation.

      2. Select China (Beijing) from the Region drop-down list.

      3. In the DiskId field, enter the ID of the Shared Block Storage device. Example: v-2zeftu16j27q5hwl****.

      4. Click Initiate Call.

      For more information, see DeleteDisk.