How to redeploy a local disk instance - Elastic Compute Service

Respond to SystemMaintenance.Redeploy or SystemFailure.Redeploy events by redeploying the instance to a new host.

See O&M scenarios and system events for local disk-based instances.

Important

Redeployment migrates the instance to a new host with new local disks. Data on the original local disks is lost. Back up your data before you proceed. See Back up files on a local disk.

Prerequisites

A system event is received for your local disk-based instance.

(Recommended) Configure read/write isolation at the application layer and update /etc/fstab to improve availability.

Preparations

Connect to an ECS instance.

For information about the connection methods, see Connection method overview.
(Optional) Configure read/write isolation for local disks at the application layer.

Note
Read/write isolation reduces data conflicts, prevents data corruption from incorrect operations, and improves performance in high-concurrency environments.

For Linux instances only: Add the nofail parameter for all local disk entries in /etc/fstab. This allows the system to start even if a local disk fails to mount.

Example: add nofail for /dev/vdd:

/dev/vdd /mnt/vdd ext4 defaults,barrier=0,nofail 0 0

Parameter	Description
UUID	The UUID of the local data disk. Run the `blkid` command to query it.
/path/to/mountpoint	The mount point of the local disk. Run the `blkid` command to query it.
fstype	The file system type. Run the `blkid` command to query it.
barrier	Whether to enable the write barrier. 0 means disabled, and 1 means enabled.
nofail	Mount failure does not block instance startup.

Procedure

Log in to the ECS console.
In the left-side navigation pane, click Events.
Click Local Disk-based Instance Events.
On the Local Disk Damage Events tab, find the instance and click Redeploy in the Actions.
In the Redeploy Instance dialog box, confirm the redeployment impacts, select I am aware of the risk of data loss., and click OK.

Next steps

Local disks
1. Initialize the new local disks. See Initialize a data disk on a Linux instance and Initialize a data disk on a Windows instance.
2. Restore data from backups. See Back up files on a local disk.
Data disks

If a data disk is attached but not configured to auto-mount on startup, manually mount it after redeployment.
Procedure
1. Run mount or bring the disk online.
  - Linux instances
    
    Connect to the ECS instance and run the mount command:
    
    sudo mount <cloud-disk-partition-name> <mountpoint>
    
    <cloud disk partition name>: The cloud disk partition name. Run sudo fdisk -lu to obtain it. Example: /dev/vdc.
    
    <mountpoint>: An existing directory or a new one created with sudo mkdir -p <new_directory>, such as sudo mkdir -p /data.
    
    mount example: sudo mount /dev/vdc /data
    
    Add the partition to /etc/fstab for auto-mount at startup. See Initialize a data disk (Linux).
  - Windows instances
    
    Connect to the instance, click the icon, and select Disk Management.
    
    In Disk Management, right-click the target disk that is in offline status (such as Disk 1), and select Online from the context menu.
2. (Conditional) If the new cloud disk is created from a snapshot and attached to the source Linux instance, change the disk UUID to avoid conflicts. See Change the UUID of a cloud disk.
3. (Conditional) If the new cloud disk capacity exceeds the original, extend the partition and file system to use the additional space.
  - Linux instances: Extend partitions and file systems of a disk on a Linux instance.
  - Windows instances: Extend partitions and file systems of a disk on a Windows instance.
4. (Optional) Configure auto-mount at startup. See Initialize a data disk on a Linux instance.