Restoring Veeam Backups on Linux

Overview

This article will assume that you already have a Linux system with the Veeam agent configured. You will need to be able to connect to the system over SSH and gain access to a user with superuser privileges.

This will be written assuming that you are saving backups to a Cloud Connect repository such as the one we provide, but the same general process can be followed to restore data from a network share or backup repository.

Restoring Files

  1. Run the following command to get a list of backups associated with the agent on the system. Once you have identified the backup you would like to restore from, copy the Backup ID column for use in the next step.

    # veeamconfig backup list
  2. Run the command below, keeping in mind that <Backup ID> is a placeholder that represents the ID saved in the previous step. This will mount the backup data into the directory /mnt/backup by default, however this can be modified by appending the argument --mountDir <directory> to the veeamconfig backup mount command. Once the backup is mounted, save the session ID from the output of the command as it will be needed shortly to unmount the backup.

    # veeamconfig backup mount --id <Backup ID>
  3. You can now access the files in the Veeam backup. You can restore data as needed using commands such as cp or rsync.
  4. Once you have finished restoring any data, you can unmount the backup data by running the command below. Replace <ID> with the session ID for the backup job. If you cannot remember the session ID for the backup mount, then you can run veeamconfig session list and search for the session that is still running.

    # veeamconfig session stop --id <ID>

Restoring Volumes

In order to restore a volume level backup, you will need a Veeam Recovery Media ISO and the ability to mount and boot into said ISO. On a baremetal server, this can be done through IPMI or by physically connecting a device with the ISO burned to it. If on a VM such as our Cloud product, you can upload the ISO and configure the VM to boot from it.

  1. Before proceeding with mounting the ISO, it is highly recommended to review and record the network configuration for the system. The Linux environment that the ISO provides will not automatically configure networking for you, and networking will be necessary to connect to the Cloud Connect repository.
  2. Mount the Recovery Media ISO to the server and reboot the system into the ISO. After the Linux environment on the ISO initializes, you will be shown a TUI (terminal user interface) which can be navigated using the keys shown. Before you are able to proceed, you must agree to Veeam's license agreement.
  3. Once you have agreed to the license terms, you should be on the main menu. Select Configure network and configure networking for the system. Return to the main menu once done.
  4. Select Restore volumes. To connect to the Cloud Connect repository, you need to select Add Cloud provider...and specify gateway.draas.hostdime.com as the address or 98.142.108.189 if DNS was not configured as part of networking (if you are using our Veeam-powered backup service). The default port of 6180 can be left as-is. When trying to proceed, you may encounter a self-signed SSL certificate warning. If so, it can be accepted.
  5. On the next step, you will be prompted for your Veeam Service Provider Console (https://draas.hostdime.com if you are using our service) credentials. Input your credentials, although you should not enter a company as part of the username.
  6. Once logged in, you will need to select the backup (left window pane) and associated restore point (right window pane) to restore data from.
  7. With a restore point selected, you can view the available volumes to restore on the right window pane. When selecting a volume on the left side to restore to, you will be prompted what volume is going to be restored from. Once you are ready to proceed with the restoration, type S.
  8. You will be shown a screen to monitor the progress of the restoration. If this finished successfully, you can then shutdown or restart the system from the main menu into the normal production environment.