(You must already be logged in to Gitlab or you’ll hit a 404)
You can attach up to eight discs in total using our control panel.
You can choose from two grades of storage:
Each storage grade is priced differently.
Before adding a new disc, shut down your Cloud Server.
Click the blue
Add disc button, choose the size and type of disc you want,
and click the green
Add new disc button. Note that changing the label of a
disc doesn’t affect how your operating system will see it.
Start your Cloud Server. Your operating system should now detect a new empty
disc. The first disc in your server is usually labelled
subsequent discs labelled
/dev/vdc etc. Run this command if
you are not sure what discs are attached:
ls -1 /dev/[sv]d[a-z]
Once you have determined the name of the new disc, create a filesystem. NB: Make sure you specify the correct disc, as this command will DESTROY ANY EXISTING DATA!
sudo mkfs.ext4 /dev/vdb
Now you can mount the disc somewhere suitable. For example, you might want
/dev/vdb at the
sudo mkdir /mnt/extra-storage sudo mount /dev/vdb /mnt/extra-storage
To make sure it gets mounted at every boot, add this line to
/dev/vdb /mnt/extra-storage ext4 defaults 0 0
Optional, and for Symbiois users only] Using the disc for Symbiosis backups:
Our Symbiosis operating system makes daily backups in /var/backups. This is more robust (and uses cheaper storage) if you put those backups onto the archive disc: that storage is bound to be on different hardware, so the backups will survive even a catastrophic hardware failure.
sudo mv /var/backups /mnt/extra-storage; sudo ln -s /mnt/extra-storage/backups /var/backups
You can check that all is well with this command:
df -h /var/backups
You should see output something like this, but the numbers will vary:
/dev/vdb 50G 53M 47G 1% /mnt/extra-storage
Find your Cloud Server and click on the
Add disc button. Note that if you
change the label of a disc, it doesn’t affect how your operating system
will see the disc.
Open Windows Disk Management.
Partition your disc as required.