Converse agora com nosso suporte
Chat com o suporte

Rapid Recovery 6.6 - 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 Credentials Vault 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

Working with Linux recovery points

The recommended and supported method to mount and unmount recovery points from a protected Linux machine is to use the local_mount utility.

The procedures referenced above specifically address using local_mount to mount and unmount Linux recovery points.

NOTE: For managing Linux recovery points from the Rapid Recovery Core Console, see Managing snapshots and recovery points.

Mounting a recovery point volume on a Linux machine

Using the local_mount utility in Rapid Recovery, you can remotely mount a volume from a recovery point as a local volume on a Linux machine.

NOTE: When performing this procedure, do not attempt to mount recovery points to the /tmp folder, which contains the rapidrecovery-vdisk files.

  1. Create a new directory for mounting the recovery point (for example, you can use the mkdir command).
  2. Verify the directory exists (for example, by using the ls command).
  3. Run the Rapid Recovery local_mount utility as root, or as the super user, for example: 
    	sudo local_mount
  4. At the Rapid Recovery mount prompt, enter the following command to list the protected machines. 
    	lm
  5. When prompted, enter the IP address or hostname of your Rapid Recovery Core server.
  6. Enter the logon credentials for the Core server, that is, the user name and password.

    A list of the machines that are protected by the Rapid Recovery server displays. Each machine is identified by the following: line item number, host/IP address, and an ID number for the machine.

    For example: 7d658e5f-fa08-4600-95f0-5f486bc1b6a4#de0896fd-571a-4cc5-aeed-264d2c3c72f4#f377e145-dd4d-3ac3-5b15-37ce8f4913ba

  7. Enter the following command to list the recovery points that are available for a specified machine: 
    	lr <line_number_of_machine>

    NOTE: You can also enter the machine ID number in this command instead of the line item number.

    A list of the base and incremental recovery points for the machine appears. The list includes the line item number, date and timestamp, location of volume, size of recovery point, and an ID number for the volume, which includes a sequence number at the end to identify the recovery point.

    For example, 7d658e5f-fa08-4600-95f0-5f486bc1b6a4#de0896fd-571a-4cc5-aeed-264d2c3c72f4#f377e145-dd4d-3ac3-5b15-37ce8f4913ba:2

  8. Enter the following command to select and mount the specified recovery point at the specified mount point/path. 
    	m <volume_recovery_point_ID_number> <volume-letter> [flag] <path>

    The flag in the command determines how to mount the recovery point. You can use one of the following options:

    [r] - mount read-only (default). This flag lets you mount a recovery point but does not let you make changes to it.
    [w] - mount writable. This flag lets you mount the recovery point and lets you make changes.
    [v] - mount with previous writes. Mounting with the “v” flag lets you mount the recovery point and include any changes that were made during the previous writable mount but are not present in the recovery point.
    [n] - do not mount nbd to <path>. A nbd (network block device) makes a socket connection between the Core and the protected machine when you perform a local mount. This flag lets you mount the recovery point without mounting the nbd, which is useful if you want to manually check the file system of the recovery point.
     

    NOTE: You can also specify a line number in the command instead of the recovery point ID number to identify the recovery point. In that case, you would use the machine line number (from the lm output), followed by the recovery point line number and volume letter, followed by the path, such as, m <machine_line_number> <recovery_point_line_number> <volume_letter> <path>. For example, if the lm output lists three protected machines, and you enter the lr command for number 2 and you mount the twenty-third recovery point volume b to /tmp/mount_dir, then the command would be:
m 2 23 b /tmp/mount_dir.

    NOTE: If you are mounting a BTRFS volume from a compatible operating system (see the "Rapid Recovery release operating system installation and compatibility matrix" topic in the Rapid Recovery System Requirements Guide), then you must include the following parameter: 

    	mount -o nodatasum,device=/dev/xxx /dev/xxx /mnt/yyy
  9. To verify that the mount was successful, enter the following command, which should list the attached remote volume: 
    	l

Unmounting a recovery point on a Linux machine

Complete the steps in this procedure to unmount a recovery point on a Linux machine.

  1. Run the Rapid Recovery local_mount utility as root, or as the super user, for example: 
    		sudo local_mount
  2. At the Rapid Recovery mount prompt, enter the following command to list the protected machines. 
    		lm
  3. When prompted, enter the IP address or hostname of your Rapid Recovery Core Core server.
  4. Enter the logon credentials (user name and password) for the Core server.

    A list of the machines that are protected by the Rapid Recovery Core server displays.

  5. Enter the following command to list the recovery points that are available for a specified machine: 
    		lr <line_number_of_machine>
    Note: Note that you can also enter the machine ID number in this command instead of the line item number.

    A list of the base and incremental recovery points for the machine will display and includes. The list includes the line item number, date and timestamp, location of volume, size of recovery point, and an ID number for the volume that includes a sequence number at the end, which identifies the recovery point.

    For example: 7d658e5f-fa08-4600-95f0-5f486bc1b6a4#de0896fd-571a-4cc5-aeed-264d2c3c72f4#f377e145-dd4d-3ac3-5b15-37ce8f4913ba:2

  6. Run the l or list command to obtain a list of mounted Network Block Device (NBD)-devices. If you mount any recovery point, you will get a path to NBD-device after executing the l or list command.
  7. Enter the following command to unmount a recovery point. 
     unmount <path_of_nbd-device>
  8. Run the l or list command to verify that the unmount of the recovery point was successful.

Forcing a snapshot

Forcing a snapshot lets you force a data transfer for the current protected machine. When you force a snapshot, the transfer starts immediately or is added to the queue if other jobs are running.

You can choose from two types of snapshots.

If you select an incremental snapshot and there is no previous recovery point, a base image is captured. Forcing a snapshot does not change the timing for any schedules snapshots.

  • A base image is a snapshot of all data on the selected volumes of the machine.
  • An incremental snapshot captures all data that has been changed since the last snapshot.
  1. In the Rapid Recovery Core Console, navigate to the machine or cluster with the recovery point for which you want to force a snapshot.
  2. On the Summary page, in the Summary pane, click Force Snapshot.

    The Force Snapshot dialog appears.

  3. In the Force Snapshot dialog box, in the check box, click one or more volumes or protection groups.
  4. Click Force Snapshot or Force Base Image, respectively.
  5. If you selected a base image, click to confirm that you want to take a base image.

    A base image could take a substantial amount of time, based on the amount of data in the volumes you want to back up.

    The snapshot you selected is queued and begins as soon as other jobs have completed.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação