Preview of Vinchin Backup & Recovery v6.0 - Archive VM backups to AWS
Hello everyone, in today's topic I will bring you a new feature in upcoming Vinchin Backup & Recovery v6.0 – Archive VM backups to AWS S3 storage.
Archiving backups to AWS is a great feature Vinchin developed this year, it is the first step in moving Vinchin backup solution from a private cloud to hybrid cloud. Although the globe is suffering from COVID-19 pandemic, Vinchin R&D never stops its steps developing new features for the market!
At the beginning, I would like to give a brief introduction about this archive solution, how it works, and what it can bring customers? Take a look at the below diagram:
Backup archive applies to a company that needs to save backups to AWS S3 storage for disaster recovery.
Before archiving backup data to AWS, you need to first do a local backup, you got a backup file in your local backup storage. Then archive the backup file to your AWS S3 storage via the internet, then you got an archive of your backup file in the AWS cloud. When disaster happens to your primary location and local backups are also damaged, you can transfer the backup archives back to your primary location and recover failed VM using Vinchin Backup & Recovery.
Now let’s take a look at how to configure and perform archive job with Vinchin unified management web console.
Log in Vinchin web console:
In version 6.0, the default login password is changed back to 123456.
First make sure you have an AWS account with S3 storage available. In my AWS storage, it's nothing in yet.
Get your AWS S3 storage connected with Vinchin backup server. Go to “Resources”-“Storage” to add your AWS storage.
Then do a backup job for target VM. To learn how to do a backup for target VM, please refer to our other documents or keep following us for updates.
To save time, I've already done a backup job for target VM.
Now let’s do an archive job. Find “Backup Archive” - “Archive”. Select the target VM which you want to archive its backups.
Then set up a schedule for this archive job as above. Each archive is a newly merged full backup restore point at that certain time. For example, I set up the archive job running at Every Friday, 23:00:00 start. Then a full backup restores point at 11 pm Friday will be merged and transferred to AWS cloud for archiving.
Then choose “Cloud Storage” as archive destination which you have pre-added in your storage in the first step. Set up a transmission network and retention policy as usual.
Once submitted, the archive job will be listed in the Current Job List.
Once you preset a time schedule for the archive job, you can let it be and wait for the first trigger automatically. To show you how it runs, now let’s start this archive job manually.
After the job finish, your VM backups are successfully archived to AWS storage. Login your AWS account, you can see that a backup file is stored there.
You will also find this archived restore point from “Backup Archive”-“Archive Data” in Vinchin web UI.
As I explained before, when your primary site is damaged together with all local backup files. What can you do? Don't forget you have archived your backup files to AWS, let's get them back to us from AWS.
Getting archived backups back from AWS we use “Archive Restore” to do so. First, create an Archive Restore job, choosing target VM from the archive job which you have done.
Choose local storage to store the backup file transferred from AWS.
Set up a transmission network and submit the job. The archived backup file will be transferred to local storage from AWS.
Once the Archive Restore Job finishes, it will be showing in the History Job list. You can check your “Archive Data” list to see if the data is in your local storage again, like below, it's there!
The last and most important thing you need to do is to use the archive data (from AWS) to restore target VM to your new local production system via “VM Backup”-“Restore” / “Instant Restore”/”Granular Restore”.
That's it! Let me have a summary of Archiving flow:
1. Add your AWS S3 storage account on Vinchin via “Resources”-“Storage”-“Add” and choose “Cloud Storage”.
2. Do a local backup job for target VM, you got a backup file in local storage.
3. Do an archive job for target VM, destination choose “Cloud Storage”, the backup file will be archived to AWS.
4. When you need to get the backup file back to local from AWS, do an archive restore job for target VM, destination choose local storage, the backup file in AWS will be returned to your local site.
5. Do a restore job (can be full VM restore, instant restore, file-level restore) for target VM. The VM or files in the VM will be able to use in a short time!
Thank you very much!