Chat now with support
Chat mit Support

Rapid Recovery 6.9 - Azure Setup Guide

Licensing and privacy considerations

The Rapid Recovery License Portal periodically checks each Rapid Recovery Core to verify licensing and to monitor uptime status for reporting. A limited amount of PII is used to compare the Core and protected or replicated machines with the license portal. This includes IP addresses, hostnames, or email addresses associated with Rapid Recovery licenses. This mode is known as "phone-home" mode. Most Rapid Recovery licenses are used in this mode, which has several advantages.

For GDPR compliance, Rapid Recovery requires users to read about how the application uses their PII, and to explicitly consent to this use in order to use a standard phone-home license. Thus, after creating and configuring a Rapid Recovery Core on Azure, you must access Core general settings and confirm that you agree to this use of personal data. See Agreeing to use personal data for details. This is a one-time requirement. Once you consent, you will not need to specify this setting when upgrading to new Core versions.

Of course, users have the ability to control this already limited use of PII. If you opt out, you must obtain a "non-phone-home" license which does not use your PII. However, use of a non-phone-home license prevents the Core from providing auto-update notifications and updates. You also cannot use the Data Protection Portal if using a non-phone-home key. If you want to operate Rapid Recovery licenses in non-phone-home mode, you must explicitly contact the Quest licensing team and request non-phone-home licenses.

For details, see the "Managing Privacy" section of the Rapid Recovery User Guide.

Next steps

To consent to the use of PII for using a standard phone-home license, see Agreeing to use personal data

To obtain a non-phone-home key, see the "Managing Privacy" section of the Rapid Recovery User Guide.

Agreeing to use personal data

To use your Rapid Recovery Core VM in the standard phone-home license mode, you must agree to the use of personal data in General settings in the Rapid Recovery Core Console. For more information, see Licensing and privacy considerations.

Follow this procedure to let your Core use personal data.

  1. Log into your Rapid Recovery Core VM on Azure.
  2. Navigate to the Rapid Recovery Core Console.
  3. On the icon bar, click [Settings] (Settings), and then click General.
  4. In General settings, if the value associated with the option Agree to use of personal data is Yes, no changes are required.
  5. In General settings, if the value associated with the option Agree to use of personal data is No, click the setting once to make it editable; then click inside the checkbox so that a check mark appears; finally, click the check mark to the right of your selection to confirm it.
  6. Click OK to confirm that auto update, license portal, and Data Protection Portal settings must be changed individually, if appropriate.

    When you allow the use of personal data, this choice automatically enables three Core features: auto-update, communication with the license portal, and enabling connection to the Data Protection Portal. If you want to disable any of these while agreeing to the use of personal data, adjust each Core setting individually.

    Use the new license key when first starting your Cores. You must obtain a long-term license to continue using the Core. For more information about licenses, see Understanding licensing. For instructions on activating a license, see Activating your Rapid Recovery license.

Next steps

Setup and configuration of your Rapid Recovery Core VMis now complete. For information about using Rapid Recovery, see the Rapid Recovery User Guide.

05_Seeding_Considerations

Once you start replicating to your target Core VM, any new recovery points saved to your source Core are replicated on your VM in the Azure cloud.

For more information on replication in Rapid Recovery, see the Rapid Recovery User Guide, including the parent topic Replication and the topic Replication with Rapid Recovery.

If your source Core captured one or more base image backups before you started replicating to the Azure VM, you may have incomplete recovery point chains in your target Core. Until all backup data from the source Core is transmitted to the target Core, creating full recovery point chains from the orphans, you can only perform file-level restore.

For more information on recovery point chains and orphans, see the Rapid Recovery User Guide topics Recovery point chains and orphans and When replication begins.

If you want your replicated target Core to have access to data saved previously on the original source Core, seed your target Core. The process of seeding unites each incremental backup with its base image, repairs the orphaned data with full recovery point chains. There are two approaches to seeding:

  1. You can seed to the target Core over a network connection.

    For large data or slow connections, seeding by this method can take a substantial amount of time.

  2. You can also create a seed drive from the source Core, saving backup data to external media and then transferring the initial data to the target Core.

If you do not need to seed data (for example, if you capture a base image after starting replication, and don't need access to earlier data), then replication can be completed entirely from the source Core.

To help decide which seeding approach is more appropriate, see the Rapid Recovery User Guide topics Determining your seeding needs and strategy and Performance considerations for replicated data transfer.

If using a seed drive to seed data for your replication target, you must send the storage media containing the seed drive file to a Microsoft Azure data center. An Azure data center representative attaches the media, and notifies you when it is ready (typically within hours). You can then consume (or import) the seed data in your target Core.

For information and links specific to seeding for Azure, see Seeding data to Azure using the Microsoft Azure Import/Export service.

For a detailed procedure to consume the data, see the Rapid Recovery User Guide topic Consuming the seed drive on a target Core.

Seeding data to Azure using the Microsoft Azure Import/Export service

If seeding your data to an Azure replication target, use the Microsoft Azure Import/Export service. This service has certain prerequisite and requirements. These are documented on the Azure website, and links to some relevant articles are included below.

Following are some guidelines for seeding to Azure.

  • Transfer your repository archives to one or more 3.5-inch Serial Advanced Technology Attachment (SATA) II or SATA III internal hard drives, 8TB or smaller.
  • You can transfer a maximum of 80TB of data, based on Microsoft's guidelines. Microsoft charges a nominal fee per drive to seed your data. For current pricing, see the Azure website or contact an Azure representative.
  • You must have an existing Azure subscription and one or more Classic storage accounts to use the Azure Import/Export service.

Since Microsoft can change prerequisites, requirements, costs, and so on, always verify this information.

For more information, including specific articles regarding pricing and procedure for using the Microsoft Azure Import/Export service, see Microsoft Azure documentation.

Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen