4 4 3 Beefalo:RHV Backup: Difference between revisions

From SEPsesam
(Updated screenshots.)
mNo edit summary
Line 99: Line 99:
<li>Specify the '''Source''' of the virtual machine you want to backup. By selecting the source, the ''backup type'' and ''task name'' are set automatically.</li>  
<li>Specify the '''Source''' of the virtual machine you want to backup. By selecting the source, the ''backup type'' and ''task name'' are set automatically.</li>  


[[image:Rhev-task_4.4.3.png|left]]
[[image:Rhev-task_4.4.3.png|left|link=]]
<br clear=all>
<br clear=all>


Line 108: Line 108:
<li>Check backup status in SEP sesam GUI under (Main Selection) '''Job State''' -> '''Backups'''.</li>
<li>Check backup status in SEP sesam GUI under (Main Selection) '''Job State''' -> '''Backups'''.</li>


[[File:Result_4.4.3.png]]   
[[File:Result_4.4.3.png|link=]]   
<br clear=all>
<br clear=all>
{{note|  
{{note|  

Revision as of 09:24, 3 August 2017

Draft.png WORK IN PROGRESS
This article is in the initial stage and may be updated, replaced or deleted at any time. It is inappropriate to use this document as reference material as it is a work in progress and should be treated as such.

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

SEP sesam backup solution for RHEV environments was developed together with Red Hat. SEP sesam uses components of the libvirt API to perform snapshot-based backups of virtual machines (VMs) in RHEV and provide consistent, agentless backups of all Red Hat Enterprise Virtualization virtual machines, regardless of their workload or operating system.

Key features

  • SEP sesam communicates directly with the RHEV hypervisor, therefore any operating system may be running as a virtual guest. Windows, Linux, or any other operating system supported by the RHEV hypervisor is treated as a virtual guest and backed up directly via communication with the hypervisor.
  • SEP sesam supports backup for RHEV single server and RHEV cluster with libvirt API.
  • The backup of individual VMs is supported on RHEV single server as well as on RHEV cluster.
  • The following backup methods are available for backing up multiple VMs in a RHEV cluster/data-center or RHEV single server:
    • A config only backup backs up only the virtual machine configuration.
    • Backup of individual VMs – VMs can be grouped together in one task group running on multiple hosts via the RHEV Manager resource.
    • Backup of VMs with specific disks (disk exclude).
  • COPY backup is currently the only supported backup type for RHEV. COPY backup will back up all data defined by the backup task (provisioned space), therefore it is recommended to use the SEP Si3 target deduplication for your RHEV backups.

For more information, see RHEV Requirements and Configuration and RHEV Restore.

Backup workflow

The backup process uses the following workflow:

  • A snapshot of the virtual machine is created.
  • Virtual machine configuration is exported from the snapshot and backed up as the first save set stream.
  • The virtual disks represented in the snapshot are attached to the data mover virtual machine.
  • The data of the virtual disks is backed up.
  • The snapshot of the virtual machine is removed.

Prerequisites

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

LAN or LAN-free backup

To use the SEP sesam RHEV backup module, a SEP sesam Client is required. This client acts as a data mover (central communication element) between SEP sesam Server and RHEV data center. For RHEV configuration with SEP sesam, see RHEV Requirements and Configuration.

During backup, a VM snapshot is created and mounted to the SEP sesam data mover. The snapshots can be transferred via LAN or SAN (Storage Area Network). If a SAN storage device is available for SEP sesam, the transfer is done directly (LAN-free).

The following pictures show how to use the backup module for LAN or LAN-free backup. The blue arrows in the illustrations are showing the direction of the connection establishment for communication and metadata transfer. The red arrows are showing the direction of the connection establishment for data transfer to connected storage.

LAN based backup scenario
  1. Start backup process with connection to the RHEV Manager host.
  2. Create consistent snapshot of virtual machine with RHEV Manager backup API.
  3. Mount snapshot to SEP sesam data mover VM.
  4. Transfer snapshot from SEP sesam data mover VM to Sesam Server via LAN.
  5. Store snapshot on connected storage devices (SEP sesam data store, SEP sesam Si3 DedupeStore, autoloader).
LAN based backup
Rhev-lan-bck.jpg
LAN-free backup scenario
  1. Start backup process with connection to the RHEV Manager host.
  2. Create consistent snapshot of virtual machine with RHEV Manager backup API.
  3. Mount snapshot to SEP sesam data mover VM (SEP sesam Remote Device Server) which is directly connected to a storage device via SAN.
  4. Transfer snapshot from SEP sesam data mover VM (SEP sesam Remote Device Server) to connected storage via SAN.
  5. Store snapshot on connected storage device (SEP sesam data store, SEP sesam Si3 DedupeStore, autoloader).
  6. LAN free backup
    Rhev-san-bck.jpg

Backing up RHEV virtual machines

Create new backup tasks for the RHEV Manager client.

  1. In the Main Selection -> Tasks -> By clients, select the RHEV Manager client and then click New backup task. The New backup task window appears.
  2. Specify the Source of the virtual machine you want to backup. By selecting the source, the backup type and task name are set automatically.
  3. Rhev-task 4.4.3.png


  4. Click OK to create the task.
  5. If you want to start the newly created task immediately, right-click the name of the task and click Immediate start. If you want to schedule the task, click New schedule in the Main Selection -> Scheduling -> Schedules.
  6. Check backup status in SEP sesam GUI under (Main Selection) Job State -> Backups.
  7. Result 4.4.3.png
    Information sign.png Note

    You can also add your backup task to an already existing schedule by double-clicking the backup task, selecting the tab Schedules and adding it to one or more schedules.

  8. Once you configured a schedule, you need to create a new backup event for it. Go to the Main Selection -> Scheduling -> New Backup Event, click the Parameter tab and select COPY backup from the Backup Type drop-down list.
  9. Information sign.png Note

    COPY is the only supported backup level type for SEP sesam RHEV clients.

For more information on schedules and related events, see Schedules 4.4. See also Adding a Task to the Task Group.

Known issues

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

See also

RHEV Requirements and ConfigurationRHEV Restore