Storage, stopping and data retention
Specify the data behaviour you need before choosing capacity.
Local and boot storage
Local storage belongs to a host or instance. Confirm the included capacity, mount path and behaviour on stop, rebuild and termination. Do not treat files on a local disk as an independent backup.
Persistent or shared storage
State whether data must survive instance termination and whether multiple instances need concurrent access. Confirm the actual storage type, compatible location, attachment limits, read/write semantics, performance requirements and independent retention charges with Arvica. A volume request does not guarantee every attachment mode.
Before stopping or terminating
Export required data and check that the export can be read. Identify each volume to retain or delete. Confirm which charges continue and when termination becomes effective. Stopping a process, container or operating system is not proof that the cloud resource has been released.
What to include in a storage request
Include capacity in GB, deployment reference if known, preferred location, number of connecting instances, shared read/write needs, desired retention and backup responsibility. Use the notes field in Create Volume. Arvica confirms placement, compatibility and price before activation.