4 4 3 Beefalo:RHV Configuration

From SEPsesam
Revision as of 13:40, 29 November 2016 by Sta (talk | contribs) (Created page with "{{draft‎}} {{Copyright SEP AG|en}} {{Navigation_latest|release=4.4.3|link=RHEV archive}}<br /> =={{anchor|overview}}Overview== <div class="boile...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Draft.png WORK IN PROGRESS
This page is a draft. Treat the information on this page with caution as it may be incomplete.

Copyright © SEP AG 1999-2020. 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.

Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check RHEV archive.


Overview

This article describes requirements and configuration steps for SEP sesam integration with Red Hat Enterprise Virtualization (RHEV) environments. Note that the procedures introduced in this article are the required configuration steps to set up RHEV SEP sesam integration. For details on RHEV integration key features and backup configuration, see RHEV Backup.

Prerequisites

  • Only Red Hat Enterprise Linux Server 7 (RHEL7) can be used as data mover for backups and restores. Check the support matrix for the list of supported RHEV versions.
  • SEP sesam Server v. 4.4.3 or higher.
  • SEP sesam Client 4.4.3.x.
  • Working name resolution for RHEV nodes and the RHEV resource (RHEV Manager).
  • Access to the RHEV management center (administrative user).
  • For RHEV 4.0 and SEP sesam versions ≤ 4.4.3.22, an additional service pack has to be installed on the data mover system: download service pack.
Information sign.png Note

It is recommended to upgrade RHEV to the latest stable version. Older RHEV versions often have problems with snapshot consolidations that can result in broken backups.

RHEV configuration

Installing SEP sesam Client on RHEV

To use the SEP sesam RHEV backup module, a SEP sesam Client with additional components must be installed on a VM running RHEL 7 OS inside the RHEV environment.

Download and install the SEP sesam Client package on the RHEL 7 OS:

rpm -ihv sesam_cli-4.4.xxx.rhel7.x86_64.rpm

Preparing SEP sesam Server

Prepare the SEP sesam Server as follows:

  1. Login via SSH with root rights to your backup server and running the SEP sesam profile file at the command prompt:
  2. source /var/opt/sesam/var/ini/sesam2000.profile
    
  3. Set the global variable for multi restore:
  4. sm_glbv w gv_multi_restore 1
    

Configuring RHEV client as data mover

Add the virtual machine with installed SEP sesam Client by using SEP sesam Server GUI. This client acts as a data mover for backups.

  1. From Main Selection -> Components -> Topology, select the location of your choice (e.g., RHEV) and click the New client button. The New client window appears.
  2. In the New client window, enter the name of the data mover; this must be the same name as is the name of the VM in RHEV.
  3. Information sign.png Note

    The RHEV virtual machine name for the data mover must be the same as the hostname of the SEP sesam client.

  4. From the Platform drop-down list, select Unix. From the Operating system drop-down list, select Linux.
  5. Rhev-data-mover.jpg


  6. Click OK to add the new client.

Configuring RHEV Manager as client

The RHEV Manager must be added as client. {note| It is not required to install a SEP sesam client on the RHEV Manager system.}}

  1. From Main Selection -> Components -> Topology, select the location of your choice (e.g., RHEV) and click the New client button. The New client window appears.
  2. In the New client window, enter the name of the RHEV Manager.
  3. From the Platform drop-down list select Unix, and from the Operating system select Linux.
  4. Change the Access Mode from CTRL to PROXY.
  5. Change the VM Server Type to RHEV-Management-Server.
  6. Rhev-m.jpg


  7. Click the tab RHEV Access tab and enter RHEV-M credentials with administrator rights. Then select a data mover.
  8. Rhev-access.jpg


Known issues

If you have problems with RHEV Linux issues, check the Troubleshooting Guide.

See also

RHEV BackupRHEV Restore