Skip to content

Latest commit

 

History

History
189 lines (137 loc) · 7.49 KB

using-veeam-agent.md

File metadata and controls

189 lines (137 loc) · 7.49 KB
Raw
copyright lastupdated keywords subcollection
years
2020
2020-07-01
vpc

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:external: target="_blank" .external} {:pre: .pre} {:tip: .tip} {:note: .note} {:important: .important} {:table: .aria-labeledby="caption"}

Using Veeam Agent

{: #using-veeam-agent}

The Veeam Agent for Linux{: external} is supported on the Linux® operating systems, which you can deploy on a virtual server instance for {{site.data.keyword.vpc_full}}, including CentOS, RHEL, Ubuntu, and Debian. Similarly, the Veeam Agent for Windows{: external} is available for use on Windows instances for {{site.data.keyword.vpc_short}}.

The following example provides information on installing, configuring, and using the Linux Agent on a virtual server instance that is provisioned with CentOS. Similar instructions apply to the other operating system types, although you need to replace any OS-specific commands. In addition, the example specifically provides instructions on how to perform a volume backup and restore, but you would use similar instructions if you prefer to do full system or file and folder backup and restore operations.

Full image-level restore is not supported. Instead, for restore operations of full, volume, or file and folder backup types, you can use the same method. The desired restore point is mounted, and the desired backup files are copied to the virtual server instance. {: tip}

Before you begin

{: #before-you-begin-veeam-agent}

  • Make sure that you order a Veeam license.
  • Provision and set up a CentOS virtual server instance for VPC (CentOS is used for this example).
  • Ensure that your secondary volume is properly configured before you install the Veeam software on the instance. In the following example, it is expected that an ext3 file system exists on the secondary volume and mounted on /veeam_disk.

Installing and configuring

{: #installing-configuring-veeam-agent}

After you have provisioned your instance and configured the secondary volume, download the Veeam Agent for Linux{: external} software installation package onto the instance.

  1. Install the downloaded package:
yum install ./veeam-release-el7-1.0.7-1.x86_64.rpm

{: pre}

  1. After the package is installed, install the Veeam Linux agent:
yum install veeam

{: pre}

  1. Transfer the Veeam license ID file to the instance. The Veeam Linux agent is configured by the Veeam configuration tool. From the command line, run:
veeamconfig ui

{: pre}

  1. Follow the menu prompts and use the license ID to activate the software.

Backing up

{: #backing-up-veeam-agent} To perform a backup operation of a volume on the CentOS virtual server instance, complete the steps that are outlined in this Veeam Agent for Linux 4.0 guide{: external}.

To begin, select Configure from the initial menu pane. As you navigate through the Veeam Agent control panes, be sure to make the following selections:

Menu pane Value
Name Input a name for the backup job.
Backup Select Volume Level Backup.
Volumes Add either a Device, Mountpoint, LVM, or BTRFS. In this example, add a Mountpoint and select the "/" mount point.
Destination Choose Local and input the location of the secondary volume to be used for the Veeam backup repository. For this example, the location input is /veeam_disk.
Advanced Select any options that you want. This example uses the default options.
Schedule Input the time schedule for the backup job to run.
Summary Select start job now, if wanted, and then select Finish.
{: caption="Table 1. Veeam Agent for Linux menu panes and values" caption-side="top"}

The backup job runs at the scheduled time. {: note}

Restoring

{: #restoring-veeam-agent}

  • Original CentOS instance for VPC refers to a virtual server instance for VPC that successfully completed a volume backup to the secondary volume.
  • New CentOS instance for VPC refers to a virtual server instance for VPC that has been provisioned with CentOS with no secondary volume and has activated the Veeam Linux Agent.

Restoring files to original CentOS virtual server instance

{: #restore-files-original-instance}

The following example shows how you can restore files from a volume backup to the original CentOS virtual service instance.

  1. Log in to the CentOS virtual server instance. From the command line, start the Veeam configuration tool:
veeamconfig ui

{:pre}

  1. Select Recover Files, and then select the Job Name of the backup you want to recover.
  2. Select the Restore Point (creation timestamp of the backup). This mounts the backup into /mnt/backup. Each individual device and volume that is backed up is mounted inside of /mnt/backup.
  3. When you recover your files, unmount the backup.

Restoring files to new CentOS virtual server instance

{: #restore-files-new-instance}

The following example shows how you can take a secondary volume that holds a Veeam backup repository and import the repository onto a new CentOS virtual server instance for {{site.data.keyword.vpc_short}}.

Detaching secondary volume from original instance

{: #detach-secondary-volume}

The original CentOS instance for VPC needs to be shut down so that it doesn't have access to the secondary volume. The secondary volume can be detached through the {{site.data.keyword.cloud_notm}} CLI:

ibmcloud is in-vold <Original VPC instance ID> <volume attachment ID>

{: pre}

Attaching secondary volume to new instance

{: #attach-secondary-volume} The secondary volume is then attached to the new CentOS instance for VPC by running:

ibmcloud is in-vola <volume attachment name> <New VPC instance ID> <volume  ID>

{: pre}

Verifying secondary volume

{: #verify-secondary-volume} After the secondary volume is attached to the new CentOS instance for VPC, verify that the secondary volume is available. For example:

# lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
vda    253:0    0  100G  0 disk
├─vda1 253:1    0    1G  0 part /boot
└─vda2 253:2    0   99G  0 part /
vdb    253:16   0  368K  0 disk
vdc    253:32   0   44K  0 disk [SWAP]
vdd    253:48   0  300G  0 disk

{:screen}

In this example, the secondary volume is the vdd device.

Mounting the volume

{: #mount-volume} Make a mount point directory and mount the volume. For example:

mkdir /veeam_disk
mount /dev/vdd /veeam_disk

{: screen}

Importing the backup repository

{: #import-backup-repository} At this point, the secondary volume is now ready for the Veeam Agent to import the backup repository.

  1. Start the Veeam Agent:
veeamconfig ui

{: pre}

  1. Select Recover Files, Import backup, then select the backup location. In this example, it is:
vdd	virtio /veeam_disk

{: screen}

  1. In Browse For Backup Files, select the appropriate backup job file directory, and then select the backup job file. In this example, it is:
BackupJob1.vdm

{: screen}

  1. Select the backup creation timestamp. This mounts the backup into /mnt/backup. Each individual device and volume that is backed up is mounted inside of /mnt/backup.

  2. When you recover your files, unmount the backup.