One of the interesting things you can do when you have added an OpenStack Swift Provider to an Account is to automate the backing up off data to another Cloud, something we call ‘Cloud Safe’. This means if the OpenStack Swift data is not available then you can access the data from the backup Cloud.
We’ll step through an example of how to automate the backing up of data from OpenStack Swift to Amazon S3.
First you’ll need an account that supports such a backup. For this you’ll need either a Personal Lifetime Cloud or an Organisation Cloud File Server Account, or you’ll need to be using the SMEStorage Open Cloud Platform Appliance.
Once you have mapped OpenStack to your Account you can proceed to the Cloud Dashboard to assign a backup Cloud Provider for OpenStack:
If you click on the “Add Cloud Provider” dialog you will be asked to choose whether you wish to add a primary cloud provider or a backup cloud provider:
Ensure you Select the backup provider radio button and also Amazon S3 as the cloud to be used for backup. Once you have done this you will be taken to a wizard to enter your Amazon S3 Details:
Once you have stepped through the wizard and completed adding your S3 account a sync task will be generated that will synchronise the existing data that resides on OpenStack with the Amazon S3 Cloud you just added. You can check on the status of this Cloud sync task from the Cloud Sync task link in the right sidebar after login from SMEStorage.com.
Once this task has completed your data is sync’d to S3. If you upload any new data a sync task will be created to also transfer this to S3. If you delete any data then it will be deleted from your primary cloud but the default action is not to remove it from your backup cloud, in the event you later wish to find such removed data.
This mechanism of “Cloud Safe” or Cloud-to-Cloud backup will actually work with any combination of Clouds that are mapped to your account.
Latest posts by admin (see all)
- Ransomware Protection and Recovery with the File Fabric - February 14, 2018
- GDPR Watch – Transparent encryption of data - February 2, 2018