サポートと今すぐチャット
サポートとのチャット

Rapid Recovery 6.9 - Azure Setup Guide

02_Upgrading

If you are new to the Rapid Recovery Core VM in release 6.9, proceed to the topic Setting up your Rapid Recovery Core VM.

When you upgrade to a new Core version, best practice is to upgrade your configuration scripts.

If upgrading from an older version to Rapid Recovery Core version 6.9, you should download the latest Azure configuration script, and replace the old script on your VM. This action lets you continue to use the configuration script to provision newly attached Azure storage disks, creating or adding an extent to your repository. For information on obtaining the latest configuration script, see Updating configuration scripts on the Azure VM.

You can expand storage for your existing Rapid Recovery Core VM at any time. Simply attach additional storage disks to your VM, and then run the configuration script on your desktop. If you did not already have a DVM repository created on your Core, running the script creates one. If you already had a repository, the script adds new disks as extents to your existing repository.

Most work environments expand over time, adding computer systems and complexity. Quest recommends customers review their environments before upgrading and adjust accordingly. As a best practice, Quest recommends performing this review at least once annually, whether or not you are upgrading.

The same is true for VMs created in Azure. The VM size and other properties you select when creating the VM determine the processing, compute, and memory resources associated with the VM. If you outgrow the original VM, Quest recommends creating a new VM using the latest Rapid Recovery Core VM template, and migrating your information from the original Core VM to the updated Core VM.

This section includes the following topics:

Updating the configuration script on the Azure VM

NOTE: Skip this task if using a new VM running Rapid Recovery Core version 6.9.0. This task only applies to VMs created using a Replication Target template from the Azure marketplace, on which the Core was upgraded to version 6.9 or later.

Each AppAssure or Rapid Recovery Core VM includes a shortcut to a configuration script on the VM desktop. The script prepares the VM to run Core and configures a repository for any attached storage disks. For the shortcut to continue functioning when the Core is upgraded on the VM, update the scripts to the latest version.

Complete the procedure below to replace outdated configuration scripts with current scripts.

  1. From your Core VM, visit your preferred download location for Rapid Recovery software.

    For more information, see the Rapid Recovery Installation and Upgrade Guide topic Obtaining Rapid Recovery software.

  2. Download the AzureConfigurationScripts.zip file to your VM.
  3. Decompress the package to a temporary location such as your Downloads folder.
  4. Open the readme.txt file included in the archive, and follow the instructions to replace outdated configuration scripts with the latest scripts.
  5. Optionally, close unneeded open windows.

Strategies for migrating data to a new Rapid Recovery Core VM

This section discusses general approaches for migrating data from an older Core VM to a new Rapid Recovery Core VM on Microsoft Azure.

NOTE: For detailed information on accomplishing these tasks, see the Rapid Recovery User Guide or see Knowledge Base articles on the Quest support website, at https://support.quest.com/rapid-recovery/kb.

If you want to migrate your data in a physical environment that uses direct attached storage, you could conceivably shut down your Core, detach the storage volumes, and connect them to the new Core location. Then, from the new Core, add all previously protected machines to protection in the newly relocated repository.

Both processes assumes you are replicating from an on-premises Core to the Azure replication target VM.

Since this option is not available for data maintained in Azure, consider at minimum the following approaches:

Migration using archiving

Archiving is a ready-made approach for migrating data. This approach is best for creating a point-in-time complete archive of data in your repository, and moving it to a new repository. However, this process is very time-consuming both for capturing the original archive and for consuming the archive in the new Core VM.

This process assumes you are replicating from an on-premises Core to the Azure replication-only target VM.

General steps for this approach include:

  1. Pause replication to your target Core. Most Cores currently in Azure are target Cores for replication. You must pause replication during migration.
  2. Save an archive. Based on the amount of data in your Core, the range of dates of data, and your network infrastructure, cabling, and throughput, this process can be time-consuming.
  3. Create a new Rapid Recovery Core VM. Follow the steps in this guide to create a new Core VM in Azure.
  4. Consume the archive in the new Core VM. Import the archive into your new Core. This process is likely to take a similar amount of time as saving the original archive.
  5. Start new replication from your source to your new Core VM. On your source Core, enable replication to your new Core VM in Azure.
  6. Delete your original Azure VM. After your new VM is in place and working, Quest recommends deleting the outdated VM from your Azure account.

For more information, see Quest Knowledge Base article 182089, "How to Migrate Agents from one DVM Repository to Another."

Migration using replication

  1. Create a new Rapid Recovery Core VM. Follow the steps in this guide to create a new Core VM in Azure.
  2. Start replication to your new Core VM. From your replication-only VM, enable replication to your new Core VM in Azure.
  3. Disable all replication. After all data has been replicated to the new Core VM, disable all replication.
  4. Start new replication from your source to your new Core VM. On your source Core, enable replication to your new Core VM in Azure.
  5. Delete your original Azure VM. After your new VM is in place and working, Quest recommends deleting the outdated VM from your Azure account.

For more information, see Quest Knowledge Base article 118382, "How to migrate AppAssure Core to a new server."

03_Setting_Up_VM

This section includes the tasks required to set up your Rapid Recovery Core VM for use on Azure.

Topics include:

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択