Deboarding Lucidity Managed Disk
What is Deboarding?
Deboarding disk operation is essentially the reverse of an onboard operation. Deboarding removes specific disks from the management of Lucidity AutoScaler, returning them to their original configuration. This allows you to stop storage autoscaling on specific volumes while keeping data intact. You can deboard any onboarded data disk directly from the Lucidity Dashboard. Depending on the OS, deboard operation may or may not need a reboot. Please check the below table for cases which need a reboot. Choose the reboot window.
Configuration | Reboot Needed (Yes / No) |
|---|---|
Windows 2019 (Data) | Yes |
All other Windows data volumes | No |
All Linux VMs (Data) | Yes |
Note
Currently, deboard operation is supported only for Data partitions on both Linux and Windows.
To Deboard a data disk,
Once logged into Lucidity Dashboard, from the left navigation menu, select Scaler.
.png?sv=2022-11-02&spr=https&st=2026-04-01T17%3A25%3A54Z&se=2026-04-01T17%3A37%3A54Z&sr=c&sp=r&sig=pTNTmDu33p9DDJGmiRoBOF5u0LLauM3CfRKem4eAwBE%3D)
Select the Virtual Machine under Managed VMs to bring up the ‘More Details’ popup. Click the Mount Point to display the list of onboarded volumes.
Click on the three dots under the Actions column next to the volume you wish to deboard and select Deboard Disk.
.png?sv=2022-11-02&spr=https&st=2026-04-01T17%3A25%3A54Z&se=2026-04-01T17%3A37%3A54Z&sr=c&sp=r&sig=pTNTmDu33p9DDJGmiRoBOF5u0LLauM3CfRKem4eAwBE%3D)
Specify the volume size that you wish to have provisioned for the deboarded volume. Depending on the data currently stored in the volume, the dashboard will show only the next feasible size. For example, if the volume has 256 GB of data before deboarding, then the size dropdown will show available options greater than 256 GB.
.png?sv=2022-11-02&spr=https&st=2026-04-01T17%3A25%3A54Z&se=2026-04-01T17%3A37%3A54Z&sr=c&sp=r&sig=pTNTmDu33p9DDJGmiRoBOF5u0LLauM3CfRKem4eAwBE%3D)
Note
The Time taken for deboard completion depends on the data size present on the disk. Once the deboarding is completed, you can see the disk displayed under Unmanaged VMs again.
Choose to delete the residual volumes after certain days and click deboard. After this period, these disks are fully removed from:
OS view
Cloud provider console
Repeat this process for more volumes if needed.
FAQ
1. Why do I still see extra disks attached to the Virtual Machine after deboarding ?
The extra disks seen after deboarding is a copy of your data retained, allowing you to perform data integrity checks. By default, duplicate disks are kept for 3 days and this time period can be configured while deboarding the disk. Post deletion of these disks, you would not see them in the Operating system view nor the Cloud service provider portal.
View from the Operating system and Cloud provider portal once the deboarding is complete.
Cloud Provider View (Azure)
.png?sv=2022-11-02&spr=https&st=2026-04-01T17%3A25%3A54Z&se=2026-04-01T17%3A37%3A54Z&sr=c&sp=r&sig=pTNTmDu33p9DDJGmiRoBOF5u0LLauM3CfRKem4eAwBE%3D)
OS Disk - The root/OS partition of the Virtual machine
Data Disks -
Lun 1: One single large data disk of the virtual machine (back to the original state).
Lun 0 ,3: These volumes represent a copy of the disks managed by lucidity and are retained by default for 7 days allowing you to perform data integrity checks.
Windows Operating System
.png?sv=2022-11-02&spr=https&st=2026-04-01T17%3A25%3A54Z&se=2026-04-01T17%3A37%3A54Z&sr=c&sp=r&sig=pTNTmDu33p9DDJGmiRoBOF5u0LLauM3CfRKem4eAwBE%3D)
C: - OS/Root partition of the Virtual machine
D: - Default Temporary disk. Read more about this here.
F: - Single large disk attached to the VM (back to the original state)
Z: - Copy of lucidity managed disks. By default this volume is retained for 7 days after deboarding.