> Documentation > Backup and Restore Agents > Backup Agents > UNIX/Linux File Systems > Linux > Add-on Solutions > Bare Metal Recovery Using 1-Touch for Linux

1-Touch for Linux - Single Stage DVD

Overview

This process is mandatory for machines that are booted by using the Universal Extensible Firmware Interface (UEFI) boot loader.

This process is recommended for physical machines that are booted by using the BIOS boot loader.

System Requirements

Verify that the computer in which you wish to install the software meets the minimum requirements specified in System Requirements.

Deployment

You need to install the File System iDataAgent on the client computer. For more information, refer to Deployment.

Configuration

After you install the File System iDataAgent, you need to enable 1-Touch for the default subclient. For more information, refer to Configuration.

Recovery

You can restore to a computer which has the same or different storage configuration as that of the backed up computer using the following interactive recovery procedure. Virtualize Me for Linux is not supported.

Unlike traditional Linux 1-Touch recovery, you cannot use the DVD04.iso for recovery directly. Use the following steps to generate a per client per backup boot media that can be used to perform 1-Touch recovery of the systems booted via UEFI:

  1. Log on to any Linux client computer that is in the same CommCell as the client computer that was backed up. This computer can be the same computer that was backed up.

  2. Run the following commands:

     
    # cd <install_dir>/iDataAgent/systemrecovery

    For example, /opt/commvault/iDataAgent/systemrecovery.

    # ./create_1tchbootcd.sh <options>

    where the usage is:

    ./create_1tchbootcd.sh [-m <mode>] -s <src_client_name> [-d <dest_client_name>] -c <cs_hostname> -u <cs_username> [-o <cs_password>] [-p <copy_precedence>] [-b <backupsetname>] [-i <instance>] [-t <to_time>] -n <dvd04._path>

    where,

    • <mode>:

    • 0 - interactive, the default option

    • 1 - silent

      <instance>: the instance on the current client

    • <to_time>: for job restore in YYYY/MM/DD hh:mm:ss format

    • -d : defaults to the client on which this script is executed

      The following options are mandatory:

    • -s <src_client_name>: short name of the client for which the boot media is being created

    • -c <cs_hostname>: FQDN or the IP address of the CommServe

    • -u <cs_username>: CommServe user name that has required permissions to perform an out-of-place restore

    • -o <cs_password>: clear text password for the CommServe user name above (if not empty)

    • -n <dvd04._path>: local or network path to the latest DVD04.iso downloaded from the Cloud Services web site

      For example, -n /vol1/vol2/vol3/DVD4.iso

      The boot media gets created and placed in the system recovery directory.

  3. Keep the Client Information Checklist ready.

  4. Boot the client computer using the boot media.

  5. On the Network Config page, enter the IP address, network and name server details of the network specified in the client information checklist.

    Select Next and press Enter.

  6. On the Client Config page, enter the short name of the client, and then select the fully qualified client host name from the Current Client HostName selection box. It contains values of all of the host names entered on the previous Network Config page and the client host name present in the recovery response xml file, and also the host names resolved via nslookup for each of the IP address configured on the Network Config page. You can also manually enter a new client host name as specified in the client information checklist. This host name will be used during recovery and will persist on the machine after the recovery completes.

    Make sure that the hostname is resolvable from the CommServe and the MediaAgent to the client being recovered. This field may be left blank to enable installation of the client being recovered with an IP instead of a host name.

    Select Next and press Enter.

    If you want to clone the client computer, select the Clone client with new name check box, and then enter the new client name. Otherwise, continue with the next step.

  7. On the CommServe Config page, enter the details of the CommServe and the MediaAgent as specified in the client information checklist.

    Select Next and press Enter.

  8. The recovery process will now boot into the kernel that was restored from the backup of the source client. After the boot up completes, the GUI will restart and perform a temporary Commvault client install before showing up the Multipath Settings page.

    Select Next and press Enter.

    • If you want to enable Linux native multipathing, select the Configure multipathing during recovery check box.

    By default, the selection will be made based on the configuration of the backed up computer.

  9. On the Mountpoint Selection page, select Next and press Enter.

    By default, the system mount points are selected for restore. You can select the other mount points that you want to recover.

  10. On the Job Selection page, select Next and press Enter.

    By default the system state and the file system data, backed up during the most recent backup will be restored. You can select a backup job to restore the system state data and a backup job to restore the file system data.

  11. On the Network Persistence page, you can choose to persist the network configuration used during the recovery onto the computer after it boots up. The options available are:

    • No: Do not persist any configuration. Upon reboot, the computer will have the network configuration of the backed up computer

    • Yes Persist config only for those NICs configured during recovery: Persist the network configuration of only those NICs that were enabled and configured during the recovery. By default, this option is selected.

    • Yes Persist config for ALL NICs as seen during recovery: Persist the network configuration for all NICs detected during recovery. An empty configuration file will be created for the NICs that were detected but not configured during the process of this recovery.

    Select Next and press Enter.

  12. Press Enter.

  13. Remove the boot media and reboot the computer.

Best Practices

  • If you are using the same client to generate the boot media, generate the boot media periodically after the backup completes, especially if there were changes to the mountpoints/network/storage devices on the client.

  • If you are using the same client to generate the boot media, move the generated .iso out of the client computer and burn it to a physical media or store it at a safe location.

  • As subsequent backups back up the previously generated boot media, even if the client computer crashes due to a hardware issue or because of any other reason, you can always recover an earlier generated boot media by performing an out-of-place restore of the file by browsing the contents from the CommServe.

FAQ

If I change the boot loader from BIOS to UEFI or vice versa, can I perform 1-Touch recovery with the new boot loader?

Yes. You need to perform a new 1-Touch backup when you change the boot loader from BIOS to UEFI or vice versa to be able to perform 1-Touch recovery.

For more FAQs, refer to Frequently Asked Questions - 1-Touch for Linux.

Loading...