Openstack made easy – Volume Backups

by | Dec 30, 2020

You want additional backups for your volumes? Preferably on another independent storage? Here you will learn in a few minutes how to configure daily volume backups in the NWS cloud.

For volume backup, NWS offers a simple backup functionality. This copies selected volumes to a second independent storage to protect your most important data from small mishaps and large disasters.

Create daily backups automatically

Daily backups for your volumes can be activated with a click in the internal area from nws.netways.de . There you can decide individually for each volume whether an automatic nightly backup is to be created. You can also set the maximum number of backups; once this number is reached, the oldest backup is deleted with each new backup. In this way, you also have the costs under control.

For managing the backups on nws.netways.de

The configuration of daily backups is therefore similarly simple as that of snapshots. But what is the difference and why can both make sense?  

Volume Snapshot vs. Volume Backup

With a volume snapshot, a snapshot is created in the central Openstack storage. In the event of an outage, this snapshot is quickly available. The snapshot is replicated three times over two locations. By replicating your data, you are protected against daily disruptions such as hardware defects.  The snapshots also protect you from major disasters such as fire or floods at a location.  Why is a backup still useful? 

Protection against human error:

If a wrong volume is accidentally deleted, all current data and all associated snapshots are deleted. However, an existing backup is not affected and the volume can be restored. Of course, you can hope that you and your team don’t make any mistakes, but after a few years in IT, everyone has probably caused one or two mishaps.

Protection against bugs:

Even if current storage systems are of high quality and run reliably and safely over years of experience, errors in the software can lead to data loss. A second independent storage for your backup reduces this risk considerably. 

 

While reading, you will have noticed that there was always talk of volume snapshots and backups. But what about virtual servers without a volume? 

 

Virtal servers without volumes

When starting a virtual server in the NWS cloud, you have the option of storing the root partition on a volume or not. In the first case, all data is stored in the central storage and thus replicated three times over two locations and the backups can be managed as described above.
 

If you do not use the volume, the root partition of the virtual server is located directly on a hypervisor. If you create a snapshot in this case, all data is copied from the hypervisor to the central storage. There, it is replicated three times over two locations, just like the volumes. This means that the data is already stored in two independent systems and is thus safe from small stupidities and large catastrophes. You can find out how to configure automatic daily snapshots for your virtual servers here .

Have you lost track of all the replicating and copying? If you have any questions, we will be happy to help!

More about OpenStack
OpenStack made easy – Creating and Using S3 Object Storage

OpenStack made easy – Creating and Using S3 Object Storage

In times of high availability and multiple web servers, the balancing act between central data storage, data security and fast access times must somehow be achieved. This is precisely why more and more users are now using technologies that entice them with buzzwords...

OpenStack made easy – Corosync Cluster with Failover IP

OpenStack made easy – Corosync Cluster with Failover IP

One of the first customer requirements you usually read is High availability. For a long time now, it has been more the norm that the project is still accessible without problems even in the event of partial failures and that "single points of failure" are avoided. A...

OpenStack made easy – Autoscaling on Demand

OpenStack made easy – Autoscaling on Demand

Depending on the type of production, it may be worthwhile for some server operators to automatically create virtual machines for a certain period of time and - after the work is done - to delete them again just as automatically; for example, if a computing job with...