5 0 0:OLVM Configuration

From SEPsesam
Jump to: navigation, search
Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2022. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.

Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.
Docs latest icon.png Welcome to the latest SEP sesam documentation version 5.0.0 Jaglion. For previous documentation version(s), check OLVM in previous versions.


Overview

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

SEP sesam provides support for oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM), which is based on the RHV backup module. So, to back up and restore virtual machines running on OLVM, you need to configure an RHV VM client that acts as a data mover for backups.

Prerequisites

To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:

Installing SEP sesam Client on VM

As OLVM backup is based on 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.

Configuring the OLVM environment

After you install 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 OLVM Manager as SEP sesam Client.

Preparing SEP sesam Server

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

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

Configuring RHV client as a data mover

A SEP sesam data mover is required to perform a SEP sesam backup and restore in an RHV and OLVM 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 an RHV VM with installed SEP sesam Client to the SEP sesam environment. This client acts as a data mover for backups.

  1. Under Main Selection -> Components -> Topology, select the appropriate location (e.g., Virtualization/RHV) and click New Client. The New Client window opens.
  2. Enter the client name.
  3. Information sign.png Note
    The RHV VM name for the data mover must match the host name of the SEP sesam Client.
  4. If not already set, select Linux from the Platform drop-down list. By selecting the Linux platform the Linux operating system is set automatically.
  5. RHV client-data mover Jaglion.jpg

  6. 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 OLVM as a SEP sesam Client

After configuring RHV client as a data mover, add your Oracle Linux Virtualization Manager (OLVM) as a client to the SEP sesam environment.

Information sign.png Note
It is not mandatory to install a SEP sesam Client on the OLVM Manager.

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

  1. From Main Selection -> Components -> Topology, select the appropriate location (e.g., Virtualization/OLVM) and click New Client. The New Client window is displayed.
  2. Enter the name of the OLVM.
  3. From the Platform drop-down list, select Linux. By selecting the Platform the Operating system - Linux is set automatically.
    • As of v. ≥ 5.0.0 Jaglion, you first have to select the Virtualization server option. Then from the VM server type drop-down list, select Oracle-VM Server.
    • OLVM client-OLVM.jpg

    • In v. 4.4.3 Beefalo V2, from the VM server type drop-down list, select RHV-Management-Server.
    • RHV client-RHV Manager.jpg


  4. Change the Access Mode from SMSSH to PROXY.
  5. This step is only neccessary for version 4.4.3 Beefalo V2: 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 Oracle-VM Access tab (or to the RHV Access tab in 4.4.3 Beefalo V2), enter the credentials for OLVM (user name, i.e., admin@internal and password) and select the RHV data mover that you created before.
  7. OLVM client-OLVM access.jpg
    Click OK.