Volume Guides on Documentation

Volume Attachment Limits

Mon, 01 Jan 0001 00:00:00 +0000

Overview

If you need to attach more than the default limitation of volume attachments, then this is possible by using a custom image and changing the properties of the image to use a non-default scsi driver.

Please note that any servers created before the image properties are set need to be re-created in order to use the updated driver.

The following properties need to be set in order to achieve this.

Volume Backup & Restore

Mon, 01 Jan 0001 00:00:00 +0000

Overview

Volume backups in Elastx OpenStack uses Swift as the storage backend. This means that your backups will automatically be placed in all availability zones. This guide will help you get started with how to create volume backups and how to restore them using OpenStack’s Horizon and CLI.

Backup and restrore from Horizon

Backup from Horizon

Navigate to “Project” → “Volumes” pick the volume you want to backup and choose Create Backup

Volume migration

Mon, 01 Jan 0001 00:00:00 +0000

Overview

To migrate volume data between Availability Zones (sto1|sto2|sto3) you can use Openstacks backup functionality. This backup process uses our Swift object storage, which is available across all Availability Zones.

Shutdown the instance whose volume will change Availability Zone. Let’s say it’s in sto1 now.
Take a backup of the volume (this may take some time, depending on the size of the volume).
Create a new volume in Availability Zone sto2 and select the backup as the source.
Create a new instance in Availability Zone sto2 and attach the newly created volume.

To get a more in-depth look at how to perform backup and restore of a volume, follow our Volume Backup & Restore guide.

Volume Retype

Mon, 01 Jan 0001 00:00:00 +0000

Overview

This guide will help you getting started with changing volume type in OpenStack.

Note

For v2 volumes as well as the deprecated ’enc’ volume types you will need to detach the volume from your server before retyping. Either shut down your server or unmount the volume in your operating system before detaching the volume in Openstack.

You cannot change a volume type from v1 to v2 if it has an existing snapshot.

Windows volume offline after restart

Mon, 01 Jan 0001 00:00:00 +0000

Issue description

In certain circumstances, extra disks can be marked as offline after a hard reboot is performed and have to be manually brought online again.

By default Windows machines will have the SAN policy set to be “Offline Shared”, thus in most virtualization platforms this issue will occur when a disk is completely shut down and started again.

The reason behind this is that the disk may be assigned to a different virtual PCI device in the underlying host which causes the OS to block the volume from going online automatically when using the default policy.