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. |
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. |
mkdir
command).
ls
command).
sudo local_mount
lm
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
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
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:
|
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 |
|
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 |
l
Complete the steps in this procedure to unmount a recovery point on a Linux machine.
sudo local_mount
lm
A list of the machines that are protected by the Rapid Recovery Core server displays.
lr <line_number_of_machine>
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
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.
unmount
<path_of_nbd-device>
l or list
command to verify that the unmount of the recovery point was successful. 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.
The Force Snapshot dialog appears.
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center