Chatee ahora con Soporte
Chat con el soporte

Rapid Recovery 6.7 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Managing privacy Encryption Authentication Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore Differences in bare metal restore for Windows and Linux machines Understanding boot CD creation for Windows machines Managing a Linux boot image Performing a bare metal restore using the Restore Machine Wizard 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 Core Console references REST APIs Glossary

Setting up continual export to VirtualBox

To export to Oracle VM VirtualBox on a remote Windows host, you should have VirtualBox installed on the Core machine.

NOTE: For exporting to VirtualBox on a remote Linux host, VirtualBox is not required on the Core machine.

Complete the steps in this procedure to perform a continuous export to a VirtualBox virtual machine (VM) using Rapid Recovery. This process is also known as setting up virtual standby.

  1. In the Rapid Recovery Core Console, do one of the following:
    • From the Core Console, in the button bar, click the [Restore]Restore drop-down menu, and then select [VM Export]VM Export.
      1. In the Virtual Machine Export Wizard, select Continual export (virtual standby).
      2. Click Next.
    • From the Core Console, in the icon bar, click [Virtual Standby] (Virtual Standby).
      • On the Virtual Standby page, click Add to launch the Virtual Machine Export Wizard.
  2. On the Machines page of the Virtual Machine Export Wizard, select the protected machine that you want to export, and then click Next.
  3. On the Destination page of the wizard, in the Export a virtual machine to drop-down menu, select VirtualBox.
  4. On the Destination page of the wizard, to set up continual virtual export of a Windows VM to a local directory or to a network shared directory, do the following:
    • Select Use Windows machine.
    • To export locally, in the Target path text box, type a local path; for example, type E:\VirtualExports.
    • To export the VM to a network shared directory, enter the required information as described in the following table.
      Table 127: Network shared location parameters
      Option Description

      Target path

      Specify the path of the network shared directory in which to create the exported virtual machine. For example, enter \\ServerName\MySharedDirectory:\VirtualExports\.  

      User name

      Enter the user name for an account that is registered on the target machine. The account must have read and write permissions to the network share.

      NOTE: Credentials are required to address the case in which multiple user accounts exist on the virtual machine. When the user is authenticated, only this user will see this Virtual Machine in VirtualBox manager. If an account is not specified, then the Virtual Machine will be registered for all existing users on the Windows machine with VirtualBox.

      NOTE: Optionally, you can select credentials for a user in the Credentials Vault, or you can save credentials you add here to the vault. For more information, see Credentials Vault.

      Password Enter the password for the specified user account.
    • To set up continual virtual export to a remote Linux machine, do the following:
    • Click Next.
    • Proceed to step 6.
  5. On the Destination page of the wizard, to set up continual virtual export to a remote Linux machine, select Remote Linux machine, and then enter information about the virtual machine as described in the following table.
    Table 128: Remote Linux machine settings
    Option Description
    VirtualBox host name Enter an IP address or host name for the VirtualBox server. This field represents the IP address or host name of the remote VirtualBox server.
    Port

    Enter a port number for the machine. This number represents the port through which the Core communicates with this machine.

    For Linux machines, the default is port 22.

    Target path

    Specify a target path to create the virtual machine.

    For example, enter /home/username/VirtualExport/VMname.

    NOTE: It is recommended that you create a root folder from root so that the virtual machine runs from root. If you do not use root, you will need to create the destination folder manually on the target machine prior to setting up the export. You will also need to manually attach or load the virtual machine after the export.

    User name

    User name of the account on the target machine, for example, root.

    NOTE: Optionally, you can select credentials for a user in the Credentials Vault, or you can save credentials you add here to the vault. For more information, see Credentials Vault.

    Password Password for the user account on the target machine.
  6. Click Next.
  7. On the Virtual Machine Options page, enter the settings for the new virtual machine, as described in the following table.
    Table 129: Virtual machine parameters
    Option Description
    VM name

    Enter a name for the virtual machine being created; for example, VM-0A1B2C3D4.

    NOTE: The default name is the name of the source machine.

    Amount of RAM

    Specify the amount of RAM for the exported virtual machine to use by selecting one of the following:

    • Same as source machine. Select this option to specify that the amount of RAM allocated to the exported VM is identical to the RAM allocated to the source machine.
    • Specific. Select this option, and then enter the amount of RAM in megabytes for the exported virtual machine to use.

    The minimum amount is 1024 MB and the maximum allowed by the application is 65536 MB. The maximum amount of memory usage is limited by the amount of RAM available to the host machine.

    Number of processors Enter the number of virtual CPUs you want for the exported virtual machine. The minimum is 1.
    Cores per processor Enter the number of cores to use for each processor. The minimum is 1.
    Perform initial one-time export Select this option to queue the export job immediately. Clear this option if you want the Core to wait until the next forced or scheduled backup snapshot.
  8. Click Next.
  9. On the Volumes page, select the volumes to export (for example, C:\ and D:\), and then click Finish to close the wizard and start the export.

    NOTE: You can monitor the status and progress of the export by viewing the Virtual Standby or Events pages.

Exporting data to an Azure virtual machine

In Rapid Recovery, you can export data to Azure by performing a one-time export, or by establishing a continual export (for virtual standby). One-time export to the Azure platform includes deployment in the workflow. If using a continual export, you can also later deploy the exported files to a bootable VM.

Azure supports virtual export of machines with 64-bit operating systems, including those that use BIOS firmware and those that use UEFI, such as Generation 2 virtual machines. For specific information about operating systems that support export to Azure, see the operating system installation and compatibility matrix in the appropriate edition of the Rapid Recovery System Reqirements Guide..

NOTE: While Rapid Recovery supports the export of Generation 2 virtual machines to Azure, there are limitations to the size and types of disks that Azure supports. For more information, see https://docs.microsoft.com/en-us/azure/virtual-machines/generation-2#generation-2-vm-sizes.

NOTE: If using virtual export to Azure in Rapid Recovery 6.2.x or earlier, you will see a compatibility warning when you upgrade. Since Microsoft no longer supports its classic Azure Service Management model, users upgrading to Rapid Recovery as of this release must re-create virtual standby to Azure using the updated Rapid Recovery Core Console. When you create a new continual export to Azure, the virtual standby definition uses the Azure Resource Manager model.

Working with Microsoft Azure

Microsoft Azure is a subscription-based cloud computing platform. The following information is provided to Rapid Recovery customers to facilitate using Azure with our product.

Azure login requires JavaScript. You may need to enable JavaScript or otherwise adjust security settings in the browser accordingly. For more information, consult your systems administrator.

Azure interface disclaimer

Caution: The Microsoft Azure interface is subject to change.

The information provided in this document relating to steps required in Azure were current as of the date of publication. This information is provided as a service to our customers to assist them with Azure prerequisites.

However, when working with Azure, be aware that specific steps, URLs or even the Azure interface may change at any time, which is beyond our control.

If you are having difficulty performing any steps related to your Azure subscription, please seek the advice of a Microsoft Azure representative.

Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación