Backup and Restore : Retrieve objects from Repository : Perform File‑level Restore

Perform File‑level Restore
onQ provides a way for you to retrieve any combination of files and folders or entire drives from existing snapshots of any protected node. This process is known as a file‑level restore (FLR).
If, however, your protected node’s server failed, you need to perform a bare metal restore (BMR) as outlined in Restore PNs Using QUARK. You can choose to replace the current file, folder, or drive, or to store it on any protected node or standalone server so long as it is reachable from your network.
To retrieve a snapshot, using FLR:
If you have a 6.x RHEL PN, ensure that you have the nc utility installed as outlined in Step 7 of (Agent‑based Linux PNs) Enroll protected nodes.
1.
Log on to the Appliance’s onQ Portal.
2.
Click on the RESTORE tab > FILES page.
A page similar to the following appears:
3.
In the Available Snapshots pane, expand the folder for the protected node.
4.
Another page, labeled Step 1, appears:
5.
•
•
Click Files to display the individual files in the content pane to the right. Then, in the content pane, you can select the individual files that you want.
6.
•
You want to restore to a Protected Node. Do so if you want to restore to the same or other Protected Node.
•
You want to restore to a Standalone Server. Do so if you’d like to inspect the files before you restore a protected node with them.
7.
Based on your decision in Step 6, in the Destination PN to restore drop‑down, specify the recovery destination — the host where you want to store the retrieved files. The files will automatically be saved to a default restore location that distinguishes the FLR from multiple different snapshots and maintains the relation of the files to a given snapshot.
•
(Windows) - C:\onQRestore\pn name AND snapshot timestamp.
•
(Linux) - mountpoint/onQRestore/pn name/snapshot timestamp. /onQRestore... if you chose /or /boot/onQRestore... if you chose /boot.
Note:  To ensure that you restore your files correctly, only PNs that share the same operating system as the host that owns the snapshot that you want to restore appear in the list.
The destination can be on the same PN, any other PN, or some other destination.
•
(PN hostname) Choose this option if you chose “Protected Node” in Step 6, then select the drive. Skip the next step.
•
(Other) Choose this option if you chose “Standalone Server” in Step 6. When you select Other, a text box appears labeled Destination hostname or IP address. Type the address of your desired destination server. Proceed to the next step.
8.
a.
Download and execute one of the following files on that remote host, depending on your operating system.
•
(Windows) WVhdS. You need only download and execute this file on the remote host as the example below shows. From a DOS prompt, run the following command:
# WVhdS_version.exe 5000 0 restore-location
For example:
(where c:\temp in the following example is the restore location)
•
(Linux) onQFLRSelf.sh. Automatically untars a file to the recipient that you define:
# cd <restore-location>
# wget http://<OnQ-IP-address>/onQFLRSelf.sh
# sh onQFLRSelf.sh
9.
Begin the restoration. Click START RESTORE, then click Yes to confirm:
Note:  Protection must be ON in order for the START RESTORE button to appear.
If you chose PN hostname | Specify Restore Drive:
PN hostname | Specify Restore Drive
Afterward, the onQ Portal returns you to the main RESTORE page.
10.
a.
•
The left pane (Available Snapshots) - shows available snapshots, as folders, listed in a hierarchical structure by node, date, and time.
•
The right pane (Recovery Status) - shows your previous efforts at retrieving files from snapshots. The carat to the right symbolizes the result of each restore attempt.
Restore failed. If you roll your cursor over the icon, you see a reason for the failure. This error can occur if the Netcat (nc) utility is not installed on the target Linux node as outlined in Step 7 of (Agent‑based Linux PNs) Enroll protected nodes. Also, if this utility is missing, your var/log/messages indicate: /opt/quorum/bin/./FLR.sh: line 44: /usr/bin/nc: No such file or directory.
b.
(Standalone Server) Verify that the restored files appear in the expected destination.
 

v3.8 HF1
v3.8 HF1