Register a prepared storage backend in Virtualizor so it can allocate VPS disks there. Storage registration and disk initialization are different operations. A pool entry in the panel does not protect you from selecting a device that already contains valuable data.
IN THIS ARTICLE
Check access and requirements
Confirm the active server, virtualization type and supported backend. Inventory existing disks, volume groups and mount points, and retain current backups. Define capacity alerts and consider snapshot, template and migration compatibility before choosing a format.
01 Add storage to a Virtualizor host
- Prepare the intended backend through its supported operating-system or storage procedure. Confirm device identity by stable identifiers and existing contents before any destructive initialization.
- Open Storage > Add Storage for the correct node. Choose the actual backend type and supply its prepared path, volume group or pool identifier.
- Review permissions and host security labels according to the selected backend. Avoid broad world-writable permissions or disabling enforcement to hide an ownership error.
- Set placement choices deliberately and save. Keep experimental or nearly full storage out of normal provisioning until validation finishes.
- Deploy a disposable VPS on this storage and test guest writes, reboot, backup and any required template or snapshot operations. Check both panel capacity and the underlying backend.
Will adding storage move existing VPS disks?
No. Existing disks remain where they are until a supported migration or disk-movement operation moves them. Plan that transfer separately and verify the target capacity first.
Confirm the expected result
Confirm the VPS disk resides on the intended pool and persists after host-managed restart. Monitor physical use and, for thin storage, metadata use as well. Keep capacity reserved for operations that create temporary copies or snapshots.
Resolve setup problems
If the pool cannot be selected, inspect node association, storage type, backend availability and permissions. If displayed free space differs, refresh through the supported panel workflow and inspect the host directly. Do not delete an unfamiliar logical volume or an apparently orphaned disk until its ownership and recovery value are established.