Converse agora com nosso suporte
Chat com o suporte

Rapid Recovery 6.9 - Azure Setup Guide

Creating Azure virtual machines for replication target

This procedure includes general guidance for creating a VM in Azure to serve as your Rapid Recovery Core, and configuring the required speed, networking and compute resources. Available resources may include VM disk type, number of virtual CPUs, amount of random access memory (RAM), and performance range (measured in Input/Output Per Second, or IOPS). You may be prompted for other Azure options such as disk support type and load balancing. Because the Azure interface changes frequently, some steps may not match precisely. Conceptually, this procedure includes the following aspects:

  • Locating the Rapid Recovery Core VM template in the Azure marketplace and adding it to your subscription.
  • Configuring the VM basic settings. These may include VM name, authentication information, and properties such as resource group and location.
  • Choosing the VM size. While details for this option often change, this step involves selecting a disk type (solid state or standard hard disk drive). Choose an option with enough RAM and Input/Output per Second (IOPS).
  • Configure optional features. These may include managed disks, network and IP address settings, security group settings (which may include public inbound ports), and other Azure options such as auto shut-down, monitoring, and so on.
  • Review the summary, which includes a cost per hour to run the VM with the selected attributes.

NOTE: The configuration options and resources you select can affect your hourly cost to operate the VM. before you click Create, you can confirm the price per hour for your selected configuration.

Caution: Once you enable the VM, you incur hourly charges in your Azure subscription for the duration of time that the VM is allocated. To perform regular backups or replication, the VM must be enabled and allocated. When not using your Rapid Recovery Core VM, you can de-allocate the VM, which pauses hourly billing. The VM remains associated with your subscription but does not incur hourly charges until it is allocated.

For more information about Azure configurations and pricing, see the virtual machines pricing page on the Azure website. For links to other useful references on Microsoft websites, see Microsoft Azure documentation.

This procedure assumes you have not yet created your Core VM.

Follow this procedure to create your Rapid Recovery Core VM.

  1. Log into your Azure subscription.
  2. From the left Azure navigate menu, click [Create resource icon] Create a resource to access the Azure marketplace.
  3. In the [Marketplace logo] Search the Marketplace field, type Rapid Recovery Core and then press Enter.
  4. Click to select the Rapid Recovery Core VM in the Compute category.

    A Description pane expands on the right side, showing information about the Core VM. Optionally, read information about Rapid Recovery Core and explore the web links. Note that this VM uses the Resource Manager model.

  5. In the bottom of the Description pane, click Create.

    The Create Virtual Machine pane appears, listing the 4 basic steps required for this process. To the right, the Basics pane appears, with prompts for basic information about your VM.

  6. Configure basic VM settings, as appropriate.

    While basic settings available in the Azure UI may change, please note the following:

    • Name refers to the name you want to use for the virtual machine.
    • The values you provide in the Username and Password fields define login credentials for the Windows user account on the virtual machine. When you connect to the VM in the future, use these credentials.
    • A Resource group is a unique name Azure Resource Manager applies to resources (associated with your current Azure subscription only) that groups resources together.
    • If you own a Windows license than you can apply to this VM, you can select an option that will result in a less expensive overall VM cost. Other steps are required as directed in the Azure UI.

    When satisfied, click OK. The Choose a size pane appears. You can search or filter to select from various VM size configurations.

  7. Configure VM size settings, as appropriate, noting the following considerations:
    • The VM sizes that appear in the list are relevant for the selected disk type (SSD or HDD).
    • Some VM sizes that meet minimum requirements are marked with a star [Reccomended]. If those sizes are not clearly displayed, click the Recommended column to sort the view using this criterion.
    • You can select any VM size that meets or exceeds the sizes of the recommended VMs. However, you cannot change the VM size for your Core in Azure later, so consider the intended use.
    • The processing, compute, and memory resources you select determine the robustness of your Rapid Recovery Core VM. Physical Rapid Recovery Cores in release 6.9 require a minimum of 8GB RAM and quad-core processor; these are minimum recommended specifications. The minimum disk size is not relevant, since repository storage is considered separately.

    When satisfied, click Select. Your selections are saved and the Settings pane appears.
  8. Configure optional features, as appropriate, noting the following considerations:
    • If you select high availability, you must reside in a region supporting availability zones. This requires using managed disks. For more information, see Overview of Availability Zones in Azure.
    • If prompted to specify public inbound ports, specify RDP at minimum, since you must connect to your Azure VM by Remote Desktop Protocol after it has been created.
    • If your Core requires other ports to be opened, select the appropriate options. For example, if your Core also requires SQL Server, select MS SQL.

      Caution: Quest strongly recommends avoiding Azure's Auto-shutdown feature. Allowing Azure to shut down the VM without gracefully stopping the Rapid Recovery Core service may lead to repository corruption or data inconsistencies.

    • For more information about the options available, see Azure documentation.

    When satisfied, click OK. Your selections are validated, and the Create pane appears.

  9. Review a summary of your VM configuration options, including the estimated hourly cost for running the VM on Azure These costs are charged by Microsoft on a monthly basis according to your subscription details and usage. When satisfied, click Create.

When the VM creation and deployment is complete, the VM creation options window closes, and the Azure dashboard displays. While the VM deploys, you can see a representation of it on the desktop. When complete, a notification appears briefly, and an overview with details for your VM appears in Azure.

Next steps

Before you can use your Rapid Recovery Core VM, you must attach one or more storage disks. Proceed to the next step in the setup process, Adding storage to your Azure VM.

Accessing your virtual machine from your Azure account

This procedure assumes that you have a Microsoft Azure subscription associated with a Microsoft user account, and that you have already created a Rapid Recovery Core VM in that Azure account.

  1. If necessary, log into your Azure user account.
  2. From the dashboard, from the Microsoft Azure left navigation menu, click [Virtual Machines icon] Virtual Machines.

    The Virtual machines page appears, showing all VMs in your current Azure subscription.

  3. Click the VM name for your Rapid Recovery Core VM.

    The Virtual machines details pane appears, with icons at the top. Some of the actions you can perform with each VM are described in the following table.

    Table 1: Virtual machine pane options
    Icon Function Description
    Connect Starts an RDP or SSH session to connect to your VM.
    Start Starts the VM from a paused or unallocated state.
    Restart Restarts the VM.
    Stop Stops, or de-allocates, the VM. This causes compute costs to stop accruing.
    Move Moves the selected VM to another resource group or subscription.
    Delete Delete the virtual machine from your account.
    Refresh Update the view of the VMs displayed on the page.
  4. To access your VM, you must connect to it using the Remote Desktop Protocol (RDP). From the top menu, click Connect.
  5. If you see the Connect to virtual machine pane, select the RDP protocol, verify the IP address and port number (the default RDP port is 3389), and then click Download RDP File.
  6. If prompted to save the RDP file, click Save, or select Save as and name the file, and then click Open.
  7. If prompted in a dialog box to connect, do the following:
    1. Optionally, if you want the browser to remember this selection, select Don't ask me again for connections to this computer. If you select this option, the Connect prompt does not display in the future.
    2. Confirm any requests to connect by clicking Connect.
  8. In the Enter your credentials dialog box, enter credentials for the Rapid Recovery Core VMfor the do the following:
    1. If necessary, in the User name field, enter the Windows username associated with this VM.
    2. In the Password field, enter the password associated with this VM.
    3. Optionally, to remember your credentials, select Remember me.
    4. To enter credentials other than the currently displayed user account, click More choices and then select Use a different account and enter the correct credentials.
    5. When satisfied, click OK.
  9. If you see a Remote Desktop Connection dialog box related to the security certificate, and you are prompted to confirm the connection, click Yes.

    The RDP session connects, and your Rapid Recovery Core VM desktop displays.

Next steps

For more information about the items that appear on the desktop of your VM, see Exploring your Rapid Recovery Core VM desktop

Exploring your Rapid Recovery Replication Target VM desktop

This topic describes the items you see on your Rapid Recovery Core VM before and after setup using the configuration script.

Your Rapid Recovery virtual machine uses the Windows Server 2019 Data Center operating system. Each time a virtual or physical machine using this OS starts, Windows opens the Server Manager utility. Unless you need it, you can click the X in the top right of the Server Manager window to close Server Manager.

When you first connect to your Rapid Recovery Core VM, and before you run the configuration script, four desktop shortcuts appear. After you run the configuration script, two additional items appear. These items are described in the following table. The last column in the table describes whether the desktop item appears before the configuration script is initially run.

Table 2: Rapid Recovery Core VM desktop items
Item Name Description Path Appears Before Setup
Configure Rapid Recovery Core This Windows shortcut launches a script or sequence of scripts to configure your Core. Also use each time you attach new virtual disks for repository storage for your Core. C:\Program Files\AppRecovery\Core\ PowerShellScripts\VM_FTBU\Setup.cmd Yes
Core Console This Windows shortcut to the Rapid Recovery Core Console. A sample URL is  https://MyVM:8006/apprecovery/admin/

https://[vmname]:[port]/apprecovery/admin/

No
Rapid Recovery Documentation This Internet URL opens technical product documentation on the Quest Support website. https://support.quest.com/rapid-recovery/6.9/technical-documents Yes
Rapid Recovery License Portal This Internet URL opens the Rapid Recovery License Portal in your web browser, where you can manage Rapid Recovery licenses. https://rapidrecovery.licenseportal.com/ Yes
Rapid Recovery Software Support This Internet URL opens the Rapid Recovery Support portal for self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. You can browse video tutorials, knowledge base articles, access user forums, start a Live Chat session, and more. When you click Contact Support from this page, you have direct access to product support engineers through an online Service Request system. https://support.quest.com/rapid-recovery/6.9 Yes
Rapid Recovery 14-day trial key.lic The first time you open the Rapid Recovery Core Console, you are prompted to associate a license key with your Core. You can use the temporary key on the desktop, or obtain a perpetual or subscription license from Quest and enter the long-term license key. C:\Users\[username]\Desktop\ Rapid Recovery 14-day trial key.lic No

The first time you open your Core and associate it with a license, the Quick Start Guide appears. This is a Rapid Recovery feature that provides you with a guided flow of suggested tasks for configuring and using Rapid Recovery Core.

You are not required to perform any steps suggested by the guide. You can simply view the suggested tasks, navigating through them using the Skip Step and Back options. Optionally, to hide the guide at any point, click Exit Guide. For more information, see the topics "Understanding the Quick Start Guide" and "Hiding the Quick Start Guide" in the latest version of Rapid Recovery User Guide.

Next steps

Adding storage to your Azure VM

This procedure assumes that you have a Microsoft Azure subscription, and that you have already created a VM in Azure to use as a Rapid Recovery Core.

When you create a virtual machine from the Azure Marketplace, the VM includes only the amount of storage reserved for the operating system and Core application. From your Azure subscription, you must attach at least one additional data disk to your Core VM, which will be used as the storage location for the repository.

Caution: The current maximum storage size for any single disk that can be purchased from the Marketplace is 1023GB (for practical purposes, in this document we refer to this as 1TB). For best results, Quest recommends that you add storage disks for working with Rapid Recovery in 1TB increments. If you need more storage for your Rapid Recovery Core, you can attach additional 1TB disks to your Azure VM.

You can add storage to your Azure VM before you run the script to configure your Rapid Recovery Core VM, or any time afterward. Quest recommends adding storage first, for the sake of simplicity.

  • If you add storage before setting up your Rapid Recovery Core VM using the configuration script, the repository is automatically defined as the storage location for your repository.
  • If you attach storage to your VM after the Core is configured, you can run the configuration script again to automatically associate that storage disk with your repository. From a Rapid Recovery perspective, additional storage disks are viewed as extents to your DVM repository.

If you attach storage to your VM after the Core is configured, you can run the configuration script again to automatically associate that storage disk with your repository. From a Rapid Recovery perspective, additional storage disks are viewed as extents to your repository. Alternatively, you can add a new storage location to an existing Rapid Recovery DVM repository from the Core Console GUI on your VM. For more information, see the latest version of Rapid Recovery User Guide topic "Adding a storage location to an existing repository."

NOTE: While the precise steps or the user interface for adding storage to your Azure VM may change, the main purpose of this step is to attach at least one data disk to your replication target VM. You can also search for relevant articles in the Azure documentation center. For example, see How to attach a data disk to a Windows VM in the Azure portal.

Perform the following procedure in your Azure subscription to attach storage to the replication target VM.

  1. Log into your Azure VM.
  2. In the Azure dashboard, from the left navigation menu, click VM iconVirtual machines.
    The Virtual machines page appears.
  3. In the list of virtual machines, click the name of your Rapid Recovery Core VM.
    Two more panes appear. The first shows details for the selected VM, and the second pane shows settings for the VM.
  4. In the VM settings pane, click Disks.
    The Disks pane expands. You can see the OS disk attached to the VM, and below that, the data disks (if any) currently attached to the selected VM.
  5. In the Disks pane, in the Data Disks section, follow the UI to + Add data disk or Create disk.
  6. In the resulting pane, enter values as described in the following table to specify storage disk attributes.
    Option Description
    Name Type an appropriate name for your storage disk.

    For example, type RapidRecoveryCore_StorageVolume1.

    Source type Select the appropriate disk type.

    Account type Select the appropriate storage account type.

    Standard disks use standard magnetic disks. Premium (SSD) disks use solid state drives and have low latency.

    Quest recommends using premium disks on Azure for high transfer rates or frequent replication.

    Size (GiB) Enter the appropriate disk size.

    Quest strongly recommends using a 1023GB disk (the current maximum for Azure).

    NOTE: When you run the configuration utility (described in the topic Running the Core configuration script from the VM desktop), any empty storage disks that you attached to your Azure VM are automatically added to your Core as a DVM repository. If multiple disks are attached, each is configured as a separate storage location in the DVM repository. If you want to add more than one storage disk at the outset, add them all before running the configuration script.

    If you add more storage to your Azure VM later, you can run the configuration script again to automatically add the new disk as an extent (storage location) to your existing DVM repository.

    You can also add a new disk manually, by adding a storage location to a DVM repository from within the Core Console. For more information, see the latest version of Rapid Recovery User Guide topic "Adding a storage location to an existing repository."

    Storage container Navigate through your existing storage account, locate, and select the appropriate existing storage container. Rapid Recovery uses a default container called vhds that stores virtual hard disks that are shared among all VMs.
    Storage blob name Define a storage binary large object (blob) name, or leave the default name. This is the name of the virtual disk that you are attaching to the selected VM.
  7. Review the information you specified for the new disk, and then click OK. Then click Save disk Save.

    Caution: If you do not click Save diskSave, the disk configuration is not saved and the disk is not attached to your VM.

    .
    After a brief wait, the new disk appears in the Disks pane.
     

    NOTE: After creating the virtual disk, Quest recommends waiting 2 to 5 minutes before running the configuration script, to ensure the storage resources are discoverable.

  8. Optionally, if you want to add any additional disks, repeat steps 5 through 7 of this procedure.
  9. Optionally, verify whether each storage volume you attached is recognized by the VM by using utilities such as Disk Management or Device Manager from the VM. If any volume is not recognized, Microsoft recommends rebooting the VM to ensure all storage drives are accessible.
  10. Optionally, you can close the browser with your Azure account information.

Next steps

Proceed to the next step in the setup process, Running the Core configuration script from the VM desktop.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação