-
Notifications
You must be signed in to change notification settings - Fork 0
Best Practices
The following recommendations describe supported and safe usage patterns when operating Proxmox together with JovianDSS through the JovianDSS Proxmox Plugin. They are intended to help prevent accidental data loss, service disruption, or inconsistent system state caused by bypassing Proxmox resource management.
Collection of recommendations regarding usage of Proxmox in pair with JovianDSS through JovianDSS-Proxmox-Plugin
This recommendations aims to prevent user from inflicting self harm due to missmanagement.
Volumes created and managed by Proxmox must not be deleted directly from the JovianDSS Web UI. Proxmox maintains its own internal state and metadata for managed volumes, and deleting them outside of Proxmox can lead to orphaned resources, broken VM configurations, or failed storage operations.
All Proxmox-managed volumes should be removed using Proxmox tools such as the Web UI or CLI.
For example, to delete the Proxmox-managed volume vm-100-disk-4 located on storage jdss-Pool-0, use the Proxmox CLI:
pvesm free jdss-Pool-0:vm-100-disk-4IMPORTANT: Never delete volumes that are attached to an iSCSI target created or managed by the Proxmox plugin.
Such volumes are very likely in active use by a virtual machine, container, or internal Proxmox service. Deleting them directly from JovianDSS interferes may result in immediate data loss, VM failure, or inconsistent behavior of Proxmox storage services.
High Availability (HA)–managed virtual machines and containers are governed by Proxmox HA policies. Operations such as rollback, migration, or other direct state-changing actions are not recommended while a resource is under active HA control, as they may conflict with HA rules and trigger unexpected recovery actions (for example, automatic restarts or failovers). In such cases, a rollback or similar operation may be blocked or fail, even though the underlying storage is functioning correctly.
To safely perform these operations, users must first adjust the HA state of the affected VM or container by temporarily disabling HA management or marking the resource as ignored in HA. This ensures that HA does not interfere with the requested operation. Failures caused by HA restrictions are expected behavior and do not indicate a malfunction of the storage plugin.