About locking LUNs
You can lock a LUN when you want to prevent Flex Appliance from placing new instance volumes on it.
Lock a LUN in the following situations:
You want to reserve a LUN for a workload that you plan to deploy later, so that instances you create in the meantime do not consume its capacity.
You want to keep an instance on a LUN of its own, so that a later instance or resize does not place another volume alongside it and affect its performance.
You want to take a LUN out of consideration while you investigate a problem with it or plan maintenance.
To see the LUNs on your appliance, how much space each one has available, and which instance volumes are on each one, use the Storage allocation tab.
See Viewing instance storage allocation across LUNs.
A lock reserves the LUN for the instance volumes that are already on it. While a LUN is locked:
No new volumes can be created on it. Its capacity is excluded from the storage that is shown as available when you create an application instance, and that capacity is shown separately as the total locked storage so that you can see how much is held back.
The volumes that are already on it can still be resized, and they grow within that LUN. Apart from that growth, the LUN's capacity is excluded from the storage that is shown as available when you resize an instance.
A volume cannot be moved onto it. A locked LUN is not listed as a target LUN for a volume move.
Locking a LUN does not change how the appliance uses the storage that is already allocated on it:
The LUN stays online and the instance volumes on it continue to serve backups. A lock affects placement decisions only, not I/O.
A lock is not data protection. If you delete an application instance, its volumes are removed even if they are on a locked LUN. To protect an instance from deletion, use lockdown mode.
See About lockdown mode.
The page and the page continue to show the full capacity of the appliance storage, including locked LUNs. The reduced figure appears on the create instance and resize pages.
Note the following before you lock or unlock LUNs:
You can lock a LUN whether or not it already has instance volumes on it.
You can lock or unlock more than one LUN at a time. All of the LUNs that you select must be in the same state, because only one of and applies to any one selection.
A lock persists until you remove it. It survives an appliance restart, a node failover, and an appliance update.
You need the administrator role to lock or unlock a LUN. Locking and unlocking are separate permissions, so you can grant one without the other through a custom role. Users without the relevant permission can see the Storage allocation tab but cannot change a LUN's lock state.
You can require multiperson authorization (MPA) approval for locking, for unlocking, or for both. In the multiperson authorization policy, the operations are under , where and can be selected independently.
Note:
On an appliance that has a single LUN, locking that LUN leaves no storage available for new instances. Unlock it before you create an instance. The volumes that are already on the LUN can still be resized, and they grow within the LUN.