Welcome. We've created this tips and tricks video to help you use Rapid Recovery's Cloud archive feature. Rapid Recovery has tight Cloud integration. And one of the many great Cloud features is recovery points archiving.
Rapid recovery supports all popular Cloud providers. Microsoft Azure, Amazon Web Service, OpenStack, Rackspace, and Google Cloud. Archives located in the Cloud can be imported back to the original Rapid Recovery core or attached without import in case only a small portion of the data is needed. The Cloud archive can also be imported or attached to any other Rapid Recovery core that has access. And in case of an emergency, the archive recovery point can be restored from the cloud to a bare metal machine directly, without involving the core server.
No matter how data is retrieved from the archive, whether it was imported or the archive was attached, all basic recovery point operations are available, such as mount, restore, or VM export.
In order to connect the Rapid Recovery core to the Cloud, you need to complete a few simple steps. In this example, we will use the Microsoft Azure Cloud. Please note that you have to have an Azure Cloud subscription and a storage account already created.
First, on the Cloud account page, add a new Cloud account. Next, copy your storage account name and access key. And now you're all set. Now you can export, import, or attach archives from the Cloud.
For demo purposes, we've already exported in archive to the Azure Cloud. And now we can attach it. To do that, you need to specify a display name for the archive. Enter the Cloud account where the archive is stored and its location, and press attach.
Archive is available in navigation pane on the left side of the screen. You can view recovery points and perform different actions. As you can see, this recovery point has an exchange database. So let's view the database content.
We now go to the mail restore page and open a database from the attached archive that is located in Azure Cloud. While the exchange database is being retrieved from the Cloud, you should also note that the Cloud account that we added can be used for multiple archives. In our demonstration, we used the one time archive, but Rapid Recovery also supports scheduled archive.
Roll up does not affect archives. You can use any retention policy on the Rapid Recovery core and keep the archive in its original state. Now database is open and we can browse the content.
The Rapid Recovery Cloud archive feature delivers many benefits. First, when backing up to a disaster recovery site, you don't need to create and manage separate remote Rapid Recovery core servers to replicate backups. All you need is a Cloud subscription. Second, for long-term backups, you don't need to upgrade your Rapid Recovery server with additional storage to store backups longer. Your local repository can be small. Instead, use cold Cloud storage like Amazon Glacier, which is cheaper.
And finally, Rapid Recovery gives you the ability to restore machines without a rapid recovery core. All you need is a USB stick, with the Universal Recovery console and a cloud archive to perform restores. Thank you for watching and stay tuned for more Rapid Recovery tips and tricks coming soon.
04:32