4 4 3 Beefalo:RHV Configuration

Overview

This article describes the requirements and configuration steps for SEP sesam integration with RHV* (and OLVM) environments. Note that the procedures presented in this article are the required configuration steps for setting up RHV SEP sesam integration. For details on RHV key features and backup configuration, see RHV Backup. For OLVM specific configuration, see OLVM Configuration.

The SEP sesam backup solution for RHV environments was developed together with Red Hat. SEP sesam uses the RHV Manager backup (libvirt) API to perform snapshot-based backups of virtual machines (VMs) in RHV environments.

As of v. 4.4.3 Beefalo, the RHV module also provides support for oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM) in the same way as for RHV environments. For more information, see OLVM Configuration.

To learn more about the key features of SEP sesam RHV backup and restore, see RHV Backup and RHV Restore.

*RHV is a rebranding of Red Hat Enterprise Virtualization (RHEV).

Prerequisites

• Only Red Hat Enterprise Linux version ≥ 7 can be used as a data mover for backups and restores.
• Check the RHV support matrix for a list of supported RHV versions.
• SEP sesam Server ≥ v. 4.4.3 Beefalo. Check hardware requirements for SEP sesam Server, RDS or SEP sesam Client.
• SEP sesam Client with additional components must be installed on a VM running supported RHEL OS inside the RHV environment.
• Working name resolution for RHV nodes and RHV resource (RHV Manager).
• Administrator access to the RHV Manager.
• It is strongly recommended to install the Qemu Guest Agent on virtual machines that are backed up to ensure file system consistency during snapshot creation. For more information, see the Red Hat documentation Installing Guest Agents and Drivers: Red Hat Virtualization Guest agents and tools.

Installing SEP sesam client on VM

To use the RHV backup module, you have to install a SEP sesam Client on a virtual machine running supported RHEL version, as described in Installing RHEL/CentOS-based distributions. Before installing the selected SEP sesam component, make sure that you have correctly configured the RPM repository for RHEL-based distributions. For details, see RPM Repository.

RHV environment configuration

After installing a SEP sesam Client in an RHV environment, proceed as follows:

1. Prepare SEP sesam Server.
2. Configure the RHV SEP sesam client as a data mover.
3. Configure the RHV Manager/OLVM as SEP sesam Client.

Preparing SEP sesam Server

To prepare the SEP sesam Server, log in via SSH as root user and enter the following command in the command prompt:

source /var/opt/sesam/var/ini/sesam2000.profile

Configuring RHV client as data mover

A SEP sesam data mover is required to perform a SEP sesam backup and restore in an RHV environment. The data mover must match the version of your SEP sesam Server. This means that you need to update the data mover to the same version as your SEP sesam Server every time you update the server.

To ensure efficient data protection and restorability of your data, check the above requirements for RHV data mover and configure your RHV client that will serve as a data mover with a fully qualified domain name (FQDN). This step should be performed before adding your RHV data mover as a client to the SEP sesam environment.

Open SEP sesam GUI and add RHV VM with installed SEP sesam Client to SEP sesam environment. This client acts as a data mover for backups.

1. Under Main Selection -> Components -> Topology, select the relevant location (e.g., RHV) and click New Client. The New Client window opens.
2. Enter the client name.

	Note
	The RHV VM name for the data mover must be the same as the host name of the SEP sesam Client.

3. From the Platform drop-down list, select Linux. By selecting the Platform the Operating system is set automatically.
4. SMSSH (SEP sesam SSH based control communication) is already set as the default Access mode.


5. Click OK to add it as a client.

To verify that your data mover is configured correctly, proceed as follows:

1. From the Main selection -> Components -> Clients, double-click your data mover for RHV.
2. Check the Interfaces field: Make sure that a fully qualified domain name (FQDN) is specified for your client. If the FQDN is not yet specified, enter it on a new line and click OK to apply the changes.
3. Ensure that the FQDN is resolvable by using the sm_setup tool from the command line. For syntax details, see Using sm_setup check_resolution. The returned addresses and hostnames must match. If the reverse resolve returns a different name than the name specified on the command line, there will be problems with backing up the client.
4. A regular path backup has to work. For details on the typical backup configuration, see Standard Backup Procedure.

Configuring RHV Manager as a SEP sesam Client

After configuring RHV client as a data mover, add your RHV Manager as a client to the SEP sesam environment.

	Note
	It is not mandatory to install a SEP sesam Client on the RHV Manager system.

This section contains version-specific steps that you should follow.

1. From Main Selection -> Components -> Topology, select the relevant location (e.g., Virtualization/RHV) and click New Client. The New Client window is displayed.
2. Enter the name of the RHV Manager.
3. From the Platform drop-down list, select Linux. By selecting the Platform the Operating system - Linux is set automatically.
4. From the VM server type drop-down list, select RHV-Management-Server.
Make sure that the PROXY access mode is selected.
After selecting the VM server type - RHV-Management-Server, another tab RHV Access is displayed.
5. Switch to the OS Access tab and enter the credentials as an administrator to access the respective systems. You have to use DOMAIN\USER format for domain accounts or HOST\USER for local accounts.
6. Switch to the RHV Access tab, enter the credentials for RHV Manager (user name, i.e., admin@internal and password) and select the RHV data mover that you created before.

Click OK.

Next, create a new backup task for the RHV client that contains the virtual machines.