Sure! Here’s the blog post based on the information provided:
Mounting Object Storage Repository for Streaming Disaster Recovery
As we move closer to the general availability of Veeam Backup & Replication v10, I am excited to share one of my personal favorite new enhancements in this upcoming release. With v10, we have made it even easier to recover from disaster by introducing a Mount function that enables users to import backup restore points for recovery purposes directly from Object Storage repositories.
In Veeam Backup & Replication 9.5 Update 4, we introduced the Cloud Tier feature, which allowed customers to offload data from their local repositories to Object Storage repositories, reducing the cost and overhead of ever-growing local primary repositories. However, this feature also presented new use cases beyond data offloading, such as recovery options. Because we hold a replicated copy of the VBK metadata as well as the actual backup data that is indexed as blocks in Object Storage, we have the ability to leverage the data sitting there for recovery purposes.
During Cloud Field Day 5, I presented on the recovery and resiliency of the Cloud Tier, showcasing how this feature can be used for disaster recovery. With v10, we have made this process even easier by introducing a Mount function that enables users to import backup restore points for recovery purposes directly from Object Storage repositories.
To mount an Object Storage repository for disaster recovery, follow these steps:
Step 1: Recreate the Object Storage Repository with the same settings as the original location.
Step 2: Right-click on the repository and select Import Backups. This will store the available restore points in the Backup & Replication database and have them appear under Imported Backups in the console.
It’s important to note that at this stage, we haven’t downloaded the metadata shells that constitute the de-hydrated VBK. One of the extra smart things we have built into this feature is that the metadata and VBK shells are only downloaded once a restore operation has been started, meaning quicker setup and more specific re-syncing of the metadata shells.
Once a restore operation is triggered, only then is the required metadata downloaded and reconstructed into the required shell chain to a temp directory. The example below shows the shells of a full and an incremental triggered by an Instant VM Recovery (IVMR) Operation. The data required to perform the IVMR is streamed from the Object Storage Repository (Capacity Tier Extent).
Once restore operations have been completed, you can go back to the Object Storage Repository, right-click and select Detach. This unmounts the Object Storage and removes the restore points from the Imported Backup view and deletes the downloaded contents of the temp folder where the metadata shells were staged.
This new Mount function in v10 streamlines the disaster recovery process by allowing users to quickly import backup restore points directly from Object Storage repositories, making it easier and more efficient to recover from disaster. When combined with the new Copy mode being introduced into v10, we have a solution that can achieve very low RPO and RTO for disaster recovery.
Stay tuned over the next few weeks as I go through some more hidden gems in v10. Disclaimer: The information and screen shots in this post are based on BETA code and may be subject to change come final GA.
Copyright © 2024 VIRTUALIZATION IS LIFE!. Powered by WordPress & Infinite Theme