Chat now with support
Chat with Support

Welcome, ApexSQL customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

Rapid Recovery 6.3 - User Guide

Introduction to Rapid Recovery The Core Console Repositories Core settings 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 Credentials Vault Snapshots and recovery points Replication Events Reporting VM export Restoring data Bare metal restore
About bare metal restore BMR Windows and Linux 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

Downloading and viewing the log file for a protected machine

If you encounter any errors or issues with a protected machine, you can download the machine logs to view them or to share them with your Quest Support representative.

  1. In the left navigation area of the Core Console, under the Protected Machines menu, click the [Expand] arrow if necessary to expand the list of protected machines.
  2. For the relevant machine, then click the machine name.
    The Summary page for the selected machine appears.
  3. From the horizontal context-sensitive menu for the relevant protected machine, click More and then select [Agent log] Agent Log.
    The Download Agent Log page appears.
  4. On the Download Agent Log page, click [Download] Click here to begin the download.
  5. In the Opening AgentAppRecovery.log dialog box, do one of the following:
    To open the log file, select Open with, then select an application (such as Notepad) for viewing the text-based log file, and finally click OK.

    The AgentAppRecovery.log file opens in the selected application.

    To save the file locally, select Save File and then click OK.

    The AgentAppRecovery.log file saves to your Downloads folder. It can be opened using any text editor.

Converting a protected cluster node to a protected machine

In Rapid Recovery, you can convert a protected cluster node to a protected machine so that it is still managed by the Core, but it is no longer part of the cluster. This is helpful, for example, if you need to remove the cluster node from the cluster but still keep it protected.

  1. In the Rapid Recovery Core Console, navigate to the cluster that contains the machine you wish to convert, and then click Protected Nodes.
  2. On the Protected Nodes page, from the specific node you want to convert, click the Actions drop-down menu and select Convert to Agent.
  3. To add the machine back to the cluster, select the machine, and then on the Summary page, from the Actions menu, select Convert to Cluster Node, and then click Yes to confirm the action.

Understanding custom groups

The Rapid Recovery Core Console shows a Protected Machines menu in the left navigation area. This includes all machines or server clusters added to protection on your Rapid Recovery Core. Beneath this, other menus may appear, based on whether you include those objects in your Core. In the same manner, you can create a custom group, which displays as the last menu type in the left navigation area.

The main benefit of a custom group is the ability to group Core objects together in a logical container. This can help you organize and manage Core objects for a specific purpose (for example, by organization, cost center, department, geographical region, and so on).

The act of creating a group always adds one group member (for example, a protected machine or server cluster, a replicated machine, or a recovery points-only machine) to the new custom group. The object added is determined by your origin point when you create the group. Ideally, you would then add additional members to the group. Thereafter, you can perform group actions that apply to all like members of that custom group, as described in Performing group actions.

Custom groups can include protected machines, server clusters, replicated machines, and recovery point-only machines. Server clusters behave the same as protected machines, with the exception that a server cluster and its nodes behave as a single entity. If you attempt to add a node from a server cluster to a group, the entire cluster is added.

A custom group may contain similar or dissimilar members. For groups of similar members, all group actions apply to all members of the group. For example, if you force a snapshot for a custom group of protected machines, each machine will be backed up. For groups with dissimilar members (for example, protected machines and replicated machines), if you apply a group action such as forcing replication, this will only apply to the replicated machines.

You can create one or more groups. A single protected machine or replicated machine can be included in one or more groups. This way, you can group machines on your Core in any way you choose, and can perform actions on that specific group.

Each custom group appears in the left navigation area, with a label you designate. Groups with standard protected machines appear first in the custom group; replicated machines appear below protected machines, as applicable. If there are any recovery point-only machines, these are listed below replicated machines.

In the left navigation area, the objects that are protected on the Core appear each in their own menu. Of these menus, custom groups appear last.

Including a machine in a group does not remove it from its original location. For example, if you have three protected machines called Agent1, Agent2, and Agent3, and you add Agent1 to CustomGroup1, then Agent1 appears in both locations.

Related topics:

Creating custom groups

When you scroll your cursor over the name of any machine in the Protected Machines or replicated machines menu, you will see an arrow that opens a drop-down menu. From this menu, you can create a custom label.

Use the procedure below to create a custom group.

  1. Navigate to the Rapid Recovery Core Console.
  2. From the Protected Machines, replicated machines, or recovery points-only menu, do the following:
    1. Place your cursor over a machine in the menu.
    2. Click on the [More}(More) drop-down menu for that machine.
    3. Scroll down to [Label as...]Label as, scroll right, then click [Label as...]New Label.
    The Create Label dialog box appears.
  3. In the Name text box, enter an appropriate label for your custom group.
    Use a descriptive name that communicates the purpose of the group. For example, to group protected machines, replicated machines, and recovery point-only machines by department, type Accounting Department. You can rename a group later.

    NOTE: Labels must be 50 or fewer characters. You can include a single space between words. You must provide a label for your custom group.

  4. When you are satisfied with the label name, click OK.
    The dialog box closes, and the custom group appears as the last element in the left navigation area.
  5. Optionally, you can add other protected machines, replicated machines, or recovery point-only machines to this group. Navigate to the machine name in the appropriate menu, click its drop-down menu, scroll down and select [Label as...]Label as, and then click the name of the custom group.

    You can now perform group actions on this group. For more information, see Performing group actions.

Related Documents