Chat now with support
Chat with Support

Rapid Recovery 6.2 - User Guide

Introduction to Rapid Recovery Core Console Core settings
Core settings key functions Rapid Recovery Core settings Core-level tools
Repositories Managing privacy Encryption Protecting machines
About protecting machines with Rapid Recovery Understanding the Rapid Recovery Agent software installer Deploying Agent to multiple machines simultaneously from the Core Console Using the Deploy Agent Software Wizard to deploy to one or more machines Modifying deploy settings Understanding protection schedules Protecting a machine About protecting multiple machines Enabling application support Settings and functions for protected Exchange servers Settings and functions for protected SQL servers
Managing protected machines Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
Bare metal restore for Windows machines Understanding boot CD creation for Windows machines Using the Universal Recovery Console for a BMR Performing a bare metal restore for Linux machines Verifying a bare metal restore
Managing aging data Archiving Cloud accounts The Local Mount Utility Core Console references REST APIs About us Glossary

Considering cloud storage options

This topic discusses support for US Government cloud storage accounts. It also discusses tradeoffs between cost and other factors when selecting cloud accounts for archiving.

Secure cloud accounts for US Government

United States federal, state, and local government agencies and their partners have access to increasing cloud account options. Rapid Recovery supports the following offerings for Government and related cloud accounts:

AWS GovCloud (US). Amazon Web Services offers a service called AWS GovCloud (US). This is an isolated AWS region designed to meet specific regulatory and compliance requirements. Using this service lets United States government agencies and customers join private businesses in leveraging cloud accounts. Rapid Recovery supports archiving to Amazon S3 storage accounts in the AWS GovCloud.
Azure Government. Azure Government is a United States government-only cloud platform exclusively for US federal, state, local, and tribal government agencies and their partners. Rapid Recovery supports Azure Government in the same manner that we offer standard Azure support. For example:
Rapid Recovery supports archiving to Azure Government and standard Azure storage accounts.
Rapid Recovery supports virtual export to an Azure virtual machine (one-time, or virtual standby) on public and Azure Government platforms.
Rapid Recovery supports replicating on-premises Cores to a replication target in the public or Azure Government cloud platform. For either platform, when logged into the Azure marketplace, you can select the "Rapid Recovery Replication Target. " from the Azure Government marketplace. Using this VM, Azure compute services, and storage that you add to the VM for your repository, users can quickly and easily set up a target Core that replicates your on-premises backup data in the Azure Government cloud.

Balancing access time, cost and convenience for archiving to cloud accounts

To offer our users cost-effective cloud archiving and virtual export options, Rapid Recovery continues to expand support of cloud storage providers (and storage classes for leading providers that offer them). Educated users can leverage policies to balance data archive convenience, data access time, and cost.

When considering strategies for archiving or exporting to the cloud, Rapid Recovery users are encouraged to understand the tradeoffs between initial cost to store data, how frequently the data is expected to be used, the need to access that data within a prescribed period of time, and costs associated with retrieving the data.

Some providers (such as Amazon S3) offer different storage classes. Choosing the correct storage class can save you money if your assumptions regarding these factors are accurate. Quest recommends that Rapid Recovery users review data storage policies at least once annually to ensure you are using your resources effectively. Similarly, administrators are cautioned to review the data being archived or exported to cloud accounts so you can update planning assumptions and migrate data accordingly.

The act of storing data, for some vendors, is extremely low or in some cases free. However, cloud service providers often apply charges to your account when you access or retrieve that data. There are often different fees based on how quickly you need to access the data. In some cases, using more expensive storage (such as Amazon S3 standard) is more cost effective if you plan to restore from recovery points than if you store data in Glacier and need to restore.

Amazon lets you define data life cycle policies that move data between Amazon S3 storage classes over time. For example, you could store freshly uploaded data using the Standard storage class, move it to Standard – Infrequent Access 30 days later, and then to Reduced Redundancy Storage after another 60 days have passed. You can also explicitly archive data for any type of Amazon S3 cloud account to Glacier, using the Archive Wizard. This is recommended if data recovery is expected very infrequently. Before selecting this option, familiarize yourself with fees related to access, storage age, and so on. See the topic Amazon storage options and archiving.

Some Rapid Recovery features are designed specifically for the cloud. If performing virtual export to the cloud using Azure, consider virtual standby. This process lets you create a fully bootable virtual machine in the Azure cloud. The VM files are continually updated with newly captured recovery points. Unlike virtual standby performed on-premises, the VM files are not deployed into a bootable VM until or unless you need them. Your initial cost for virtual standby in Azure involve only storage. Compute costs (which in Azure can be considerable in the long term) are incurred only if the VM is deployed, which is required to spin up a VM and perform a restore.

You can also replicate an on-premises Core in the Azure cloud using Rapid Recovery Replication Target. You can quickly and easily set up a target Core by selecting "Rapid Recovery Replication Target" from the Azure marketplace. The target core incurs compute costs. You also need to plan for repository storage within Azure. New to release 6.2, you can also use replication target in the Government cloud. For information about replicating to Azure, see the Rapid Recovery Replication Target for Microsoft Azure Setup Guide

Rapid Recovery users who use such cloud storage options are encouraged to understand the tradeoffs between initial cost to store data, the need to access that data within a prescribed period of time, and costs associated with retrieving the data.

For example, the act of storing data, for some vendors, is extremely low or in some cases free. However, cloud service providers often apply charges to your account when you access or retrieve that data. There are often different fees based on how quickly you need to access the data. In some cases, using more expensive storage (such as Amazon S3 standard) is more cost effective if you plan to restore from recovery points than if you store data in Glacier and need to restore.

Amazon lets you define data life cycle policies that move data between Amazon S3 storage classes over time. For example, you could store freshly uploaded data using the Standard storage class, move it to Standard – IA 30 days later, and then to Amazon Glacier after another 60 days have passed.

Adding a cloud account

Before you can move data in either direction between a cloud account and your Core, you must add cloud provider account information to the Rapid Recovery Core Console. This information identifies the cloud account in the Core Console while caching the connection information securely. This process then lets Rapid Recovery Core connect to the cloud account to perform the operations you specify.

To add a cloud account, complete the steps in the following procedure.

1.
On the Rapid Recovery Core Console icon bar, click the [More] More icon and then select [Cloud Accounts] Cloud Accounts.
The Cloud Accounts page appears.
2.
On the Cloud Accounts page, click Add New Account.

The Add New Account dialog box opens.

Table 163. Cloud account details

Cloud Type

Text Box

Description

Microsoft Azure

Display name

Enter a display name for this cloud account to display on the Rapid Recovery Core Console; for example, Azure Cloud Account 1.

Storage account name

Enter the name of your Microsoft Azure storage account.

Access key

Enter the access key for your account.

Use https protocol

Select this option to use the secure https protocol instead of the standard http protocol.

Amazon S3

Display name

Enter a display name for this cloud account to display on the Rapid Recovery Core Console; for example, Amazon S3 Cloud Account 1.

Access key

Enter the access key for your Amazon cloud account.

Secret key

Enter the secret key for this account.

Service endpoint

Optionally, if using an S3-compatible storage account other than a standard Amazon S3 storage account, enter the fully qualified http or https URL for that storage account.

Storage class

Select a storage class for the S3 account. You can choose from:

If you want to archive to Glacier, you can define your Amazon cloud account using any listed storage class. The option to select Glacier storage is accessible from the Archive Wizard.

Powered by OpenStack

Display name

Enter a display name for this cloud account to display in the Rapid Recovery Core Console; for example, OpenStack Cloud Account 1.

Region

Enter the region for your cloud account.

User name

Enter the user name for your OpenStack-based cloud account.

Password or API key

Select whether to use a password or an API key, and then enter your selection for this account.

Tenant ID

Enter your tenant ID for this account.

Authentication URL

Enter the authentication URL for this account. This the base URL for the cloud instance. If not provided, Rapid Recovery Core uses the default URL, https://identity.api.rackspacecloud.com.

Rackspace Cloud Files

Display name

Enter a display name for this cloud account to display on the Rapid Recovery Core Console; for example, Rackspace Cloud Account 1.

Region

Use the drop-down list to select the region for your account.

User name

Enter the user name for your Rackspace cloud account.

Password or API key

Select whether to use a password or an API key, and then enter your selection for this account.

Tenant ID

Enter your tenant ID for this account.

Authentication URL

Enter the authentication URL for this account. This the base URL for the cloud instance. If not provided, Rapid Recovery Core uses the default URL, https://identity.api.rackspacecloud.com.

Google Cloud

Display name

Enter a display name for this cloud account to display on the Rapid Recovery Core Console; for example, Google Cloud Account 1.

Certificate file

Browse for and select your Google certificate file to authenticate this cloud account.

Private key

Enter your private key for this account.

Project ID

Enter the Project ID associated with this account.

Service account email

Enter the email address registered with Google Cloud as the owner of this cloud service account.

5.
Click Save.

The dialog box closes, and your account appears on the Cloud Accounts page of the Core Console.

Editing a cloud account

If you need to change the information to connect to your cloud account, for example to update the password or edit the display name, you can do so on the Cloud Accounts page of the Rapid Recovery Core Console. Complete the steps in the following procedure to edit a cloud account.

1.
On the Rapid Recovery Core Console icon bar, click the [More] More icon and then select [Cloud Accounts] Cloud Accounts.
The Cloud Accounts page appears.

The Edit Account window opens.

Removing a cloud account

If you discontinue your cloud service, or decide to stop using it for a particular Core, you may want to remove your cloud account from the Core Console. Complete the steps in the following procedure to remove a cloud account.

1.
On the Rapid Recovery Core Console icon bar, click the [More] More icon and then select [More] Cloud Accounts.
The Cloud Accounts page appears.
3.
In the Delete Account dialog box, click Yes to confirm that you want to remove the account.
Related Documents