4 4 3 Beefalo:RHV Backup: Difference between revisions

From SEPsesam
(Updated screenshots.)
(Marked this version for translation)
(20 intermediate revisions by the same user not shown)
Line 1: Line 1:
<translate><!--T:1-->
<noinclude><div class="noprint"><languages />
{{Copyright SEP AG|en}}</translate>
{{draft‎}}
{{draft‎}}
{{Copyright SEP AG|en}}
<translate><!--T:2--> {{Navigation_latest|release=[[SEP_sesam_Release_Versions|4.4.3 ''Beefalo''/''Beefalo V2'']]|link=[[Special:MyLanguage/RHV|RHV archive]]}}</div></translate><br />
{{Navigation_latest|release=4.4.3|link=[[Special:MyLanguage/RHEV|RHEV archive]]}}<br />


=={{anchor|overview}}Overview==
<translate>==Overview== <!--T:3--></translate>
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Additional resources</b></center>
<div class="boilerplate metadata" id="Additional resources" style="background-color: #f0f0f0; color:#636f73; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate><!--T:4--> Additional resources</translate></b></center>


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=RHEV Restore]]
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_next.png|45px|link=Special:MyLanguage/4_4_3_Beefalo:RHV_Restore|RHV Restore]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also: [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]] – [[Special:MyLanguage/4_4_3:RHEV_Restore|RHEV Restore]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:5--> See also: [[Special:MyLanguage/4_4_3_Beefalo:RHV_Configuration|RHV Configuration]] – [[Special:MyLanguage/4_4_3_Beefalo:RHV_Restore|RHV Restore]]</translate>
|}
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_Video.png|45px|link=https://www.youtube.com/watch?v=xgZKEuAR3i4|]]
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_Video.png|45px|link=Video Tutorials & Screencasts]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Watch [https://www.youtube.com/watch?v=xgZKEuAR3i4 SEP sesam RHV & RHEV backup].
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" |<span style="color:black"><sup>'''<translate><!--T:6--> NEW</translate>'''</sup></span> <translate><!--T:7--> Watch SEP sesam video [https://www.youtube.com/watch?v=W29MOFTAZ3M Backup of RHV/OLVM with SEP sesam].</translate>
|}
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Troubleshooting_Guide#Red_Hat_Enterprise_Linux]]
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Troubleshooting_Guide#RHEV]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? Check [[Special:MyLanguage/Troubleshooting_Guide#Red_Hat_Enterprise_Linux|Troubleshooting Red Hat Enterprise Linux]].  
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:8--> Problems? Check [[Special:MyLanguage/Troubleshooting_Guide#RHEV|Troubleshooting Red Hat Enterprise Linux]].</translate>
|}
|}


{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=RHEV]]
| rowspan="2" style="padding:0px 10px 0px;" | [[File:icon_archived_docs.png|45px|link=RHV]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | If you are using an older SEP sesam version, refer to [[Special:MyLanguage/RHEV|RHEV previous version]] of the documentation.
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate><!--T:9--> If you are using an older SEP sesam version, refer to [[Special:MyLanguage/RHV|RHV archive]].</translate>
|}</div>
|}</div></noinclude>
SEP sesam backup solution for RHEV environments was developed together with Red Hat. SEP sesam uses components of the <tt>libvirt</tt> 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.  
<translate><!--T:10-->
SEP sesam backup solution for RHV* environments was developed together with Red Hat. SEP sesam uses RHV Manager backup (<tt>libvirt</tt>) API to perform snapshot-based backups of virtual machines (VMs) in RHV environments.  


=== {{anchor|features}}Key features ===
<!--T:11-->
*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.
As of v. [[SEP_sesam_Release_Versions|4.4.3 ''Beefalo'']], the RHV module also provides support for <tt>oVirt</tt>-based platforms within '''Oracle Linux Virtualization Manager (OLVM)''' in the same way as for RHV environments. SEP sesam tight integration with RHV backup API enables consistent, agentless backups of all RHV virtual machines, regardless of their workload or operating system. Since the RHV module now supports OLVM the same options and steps apply for configuring the OLVM environment backup, with the only difference that the relevant OLVM components should be configured instead of RHV.</translate>
* 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).
*[[Special:MyLanguage/SEP_sesam_Glossary#COPY|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 [[Special:MyLanguage/SEP_sesam_Glossary#SEP_Si3|SEP Si3 target deduplication]] for your RHEV backups.


For more information, see [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]] and [[Special:MyLanguage/4_4_3:RHEV_Restore|RHEV Restore]].
<span style="font-size:92%; line-height: 1.3em; color:grey;">*<translate><!--T:12--> RHV is a rebranding of Red Hat Enterprise Virtualization (RHEV).</translate></span>


=== {{anchor|workflow}}Backup workflow ===
=== {{anchor|features}}<translate><!--T:13--> Key features</translate> ===
*<translate><!--T:14--> Since SEP sesam communicates directly with the RHV hypervisor, it does not matter what operating system is running as a virtual guest. Windows, Linux or any other operating system supported by the RHV hypervisor is treated as a virtual guest and backed up directly by communicating with the hypervisor.</translate>
* <translate><!--T:15--> SEP sesam supports backups for '''RHV single servers''' and '''RHV clusters''' with '''<tt>libvirt</tt> API'''.</translate>
* <translate><!--T:16--> Single (individual) VM backup is supported both on a RHV single server and on a RHV cluster.</translate>
* <translate><!--T:17--> The following backup methods are available for backing up VMs in a RHV cluster/data center or on RHV single server:</translate>
** <translate><!--T:18--> A '''config only backup''' backs up only the VM configuration.</translate>
** <translate><!--T:19--> Backup of '''individual VMs''' that can be grouped together in one task group running on multiple hosts via the RHV Manager.</translate>
**<translate><!--T:20--> Backup of VMs with '''specific disks''' (disks exclusion).</translate>
*<translate><!--T:21-->
[[Special:MyLanguage/SEP_sesam_Glossary#COPY|''COPY'']] backup is currently the only supported RHV backup level, which means that all data defined by the backup task is backed up (provisioned space). It is recommended to use [[Special:MyLanguage/SEP_sesam_Glossary#SEP_Si3|SEP Si3 target deduplication]] for your RHV backups to reduce the size of backed up data.


The backup process uses the following workflow:
=== {{anchor|workflow}}Backup workflow === <!--T:22-->
* 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 [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover virtual machine]].
* The data of the virtual disks is backed up.
* The snapshot of the virtual machine is removed.


=== Prerequisites ===
<!--T:23-->
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
The backup process uses the following workflow:</translate>
* Check the [[SEP_sesam_OS_and_Database_Support_Matrix##Red_Hat_Enterprise_Virtualization_.28RHEV.2FRHV.29|support matrix]] for the list of supported RHEV versions.
#<translate><!--T:24--> A snapshot of the virtual machine (VM) is created.</translate>
* Check [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]].
#<translate><!--T:25--> The VM configuration is exported from the snapshot and backed up as the first saveset stream.</translate>
#<translate><!--T:26--> The virtual disks represented in the snapshot are attached to the [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover]] VM.</translate>
#<translate><!--T:27--> The data of the virtual disks is backed up.</translate>
#<translate><!--T:28-->
The snapshot of the VM is removed.


== {{anchor|LAN}}LAN or LAN-free backup ==
=== Prerequisites === <!--T:29-->
To use the SEP sesam RHEV backup module, a [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]] is required. This client acts as a [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover]] (central communication element) between SEP sesam Server and RHEV data center. For RHEV configuration with SEP sesam, see [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|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).  
<!--T:30-->
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:</translate>
* <translate><!--T:31--> Check the [[SEP_sesam_OS_and_Database_Support_Matrix#RHV|support matrix]] for the list of supported RHV and OLVM versions.</translate>
* <translate><!--T:32-->
Make sure your RHV/OLVM environment is [[Special:MyLanguage/4_4_3_Beefalo:RHV_Configuration|set up properly]] with your ''RHV Manager/OLVM'' configured as [[Special:MyLanguage/SEP_sesam_Glossary#SBC|SEP sesam Client]]. For details, see [[Special:MyLanguage/4_4_3_Beefalo:RHV_Configuration|RHV Configuration]].


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.
== {{anchor|LAN}}LAN-based or LAN-free backup == <!--T:33-->


;LAN based backup scenario
<!--T:34-->
<ol>
SEP sesam’s Red Hat Virtualization backup can operate in two modes: LAN-based backup and LAN-free backup.
<li>Start backup process with connection to the RHEV Manager host.</li>
 
<li>Create consistent snapshot of virtual machine with RHEV Manager backup API.</li>
<!--T:35-->
<li>Mount snapshot to SEP sesam data mover VM.</li>
During the 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).
<li>Transfer snapshot from SEP sesam data mover VM to Sesam Server via LAN.</li>  
 
<li>Store snapshot on connected storage devices ([[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 DedupeStore]], [[Special:MyLanguage/SEP_sesam_Glossary#loader|autoloader]]).</li></ol>
<!--T:36-->
The following images show how to use the backup module for LAN-based and LAN-free backup. Steps 1-5 in the graphic show the direction of the connection establishment for communication and metadata transfer. Step 6 shows the direction of the connection establishment for the data transfer to the connected storage.
 
<!--T:37-->
;LAN-based backup scenario</translate>
<ul><li><translate><!--T:38--> Start the backup process with connection to the ''RHV Manager host'' or ''OLVM host''. Create a consistent snapshot of the VM. (''Step 1'')</translate></li>
<li><translate><!--T:39--> Once the snapshot is successfully created, the VM configuration is exported from the snapshot and backed up as the first stream in the saveset. (''Steps 2, 3, 4'')</translate></li>
<li><translate><!--T:40--> The VM disks present in the snapshot are then attached to the data mover VM using the backup API. Once attached, the data on these disks is backed up and upon success, the snapshot is removed again. The snapshot is transferred from the data mover VM to SEP sesam Server via LAN. (''Steps 5, 6'')</translate></li>  
<li><translate><!--T:41--> The backed up data is stored in backup storage (connected storage devices, such as [[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 deduplication store]], HPE StoreOnce, [[Special:MyLanguage/SEP_sesam_Glossary#loader|tape library]]).</translate></li>


{| border="2" cellpadding="4" cellspacing="0" style="width:100%; margin: 1em 1em 1em 0; border: 1px #aaa solid; border-collapse: collapse;"
{| border="2" cellpadding="4" cellspacing="0" style="width:100%; margin: 1em 1em 1em 0; border: 1px #aaa solid; border-collapse: collapse;"
|- style="background:#FFCC01; color:#002F55"
|- style="background:#FFCC01; color:#002F55"
! scope="col" style="width: 100px;" | LAN based backup
! scope="col" style="width: 100px;" | <translate><!--T:42--> LAN based backup</translate>
|-
|-
|[[File:Rhev-lan-bck.jpg]]
|[[File:SEP-sesam-RHV-LAN-Based.png|center|link=]]
|}
|}
</ul> 
   
   
;LAN-free backup scenario
;<translate><!--T:43--> LAN-free backup scenario: Use the SAN storage connected directly to the RHV cluster itself to perform backup transferred across your dedicated storage interface. In this case, the storage is attached directly to the data mover VM using the Storage Area network.</translate>
<ol>
<li>Start backup process with connection to the RHEV Manager host.</li>
<li>Create consistent snapshot of virtual machine with RHEV Manager backup API.</li>
<li>Mount snapshot to SEP sesam data mover VM (SEP sesam Remote Device Server) which is directly connected to a storage device via SAN.</li>
<li>Transfer snapshot from SEP sesam data mover VM (SEP sesam Remote Device Server) to connected storage via SAN.</li>
<li>Store snapshot on connected storage device ([[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 DedupeStore]], [[Special:MyLanguage/SEP_sesam_Glossary#loader|autoloader]]).</li>


<ul><li><translate><!--T:44--> Start the backup process with connection to the ''RHV Manager host'' or ''OLVM host''. Create a consistent snapshot of the VM. (''Step 1'')</translate></li>
<li><translate><!--T:45--> Once the snapshot is successfully created, the VM configuration is exported from the snapshot and backed up as the first stream in the saveset. (''Steps 2, 3, 4'')</translate></li>
<li><translate><!--T:46--> The VM disks present in the snapshot are then attached to the data mover VM using the backup API. Once attached, the data on these disks is backed up and upon success, the snapshot is removed again. The snapshot is transferred from the data mover VM to your backup storage via SAN. (''Steps 5, 6'')</translate></li>
<li><translate><!--T:47--> The backed up data is stored in backup storage (connected storage devices, such as [[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 deduplication store]], HPE StoreOnce, [[Special:MyLanguage/SEP_sesam_Glossary#loader|tape library]]).</translate></li>
{| border="2" cellpadding="4" cellspacing="0" style="width:100%; margin: 1em 1em 1em 0; border: 1px #aaa solid; border-collapse: collapse;"
{| border="2" cellpadding="4" cellspacing="0" style="width:100%; margin: 1em 1em 1em 0; border: 1px #aaa solid; border-collapse: collapse;"
|- style="background:#FFCC01; color:#002F55"     
|- style="background:#FFCC01; color:#002F55"     
! scope="col" style="width: 100px;" | LAN free backup
! scope="col" style="width: 100px;" | <translate><!--T:48--> LAN free backup</translate>
|-     
|-     
|[[File:Rhev-san-bck.jpg]]     
|[[File:SEP-sesam-RHV-LAN-Free.png|center|link=]]     
|}
|}
</ol>
</ul>


=={{anchor|backing up}}Backing up RHEV virtual machines==
<translate>=={{anchor|bck}}Backing up RHV virtual machines== <!--T:49-->


Create new backup tasks for the RHEV Manager client.  
<!--T:50-->
<ol>
Create a new backup task for the RHV VM or OLVM client. You can only perform one VM backup per backup task. You must configure a separate backup task for each VM that you want to back up.</translate>
<li>In the '''Main Selection''' -> '''Tasks''' -> '''By clients''', select the ''RHEV Manager'' client and then click '''New backup task'''. The ''New backup task'' window appears.</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>  
{{<translate><!--T:51--> tip</translate>|<translate><!--T:52--> If you prefer to watch a video rather than to read a step-by-step guide, you can learn all the steps of the backup procedure by watching ''Backup of Red Hat Virtualization (RHV)/Oracle Linux Virtualization (OLVM) with SEP sesam'' on {{SEP youtube}}.</translate>}}


[[image:Rhev-task_4.4.3.png|left]]
<ol><li><translate><!--T:53--> In the '''Main Selection''' -> '''Tasks''' -> '''By Clients''', select the ''RHV Manager'' client or ''OLVM client'' and then click '''New Backup Task'''. The ''New Backup Task'' window opens.</translate></li>
<li><translate><!--T:54--> Specify the '''Source''' of the VM you want to back up. You can browse for the source or enter it manually. When you browse for the source, the ''task type'' and ''task name'' are set automatically. If you enter the source manually, you need to enter the ''task name'' and select the RHV task type from the drop-down list.</translate></li>
<translate><!--T:55--> [[image:RHV_bck_task-source.jpg|650px|link=]]</translate>
<br clear=all>
<br clear=all>
 
<li><translate><!--T:56--> You can exclude individual disks from backup by entering them in the '''Exclude list''' field. You have to use the logical disk name(s) as displayed in the RHV management center. If you want to exclude multiple disks, enter them one by one followed by a comma without spaces, for example: ''disk_name1,disk_name2''.</translate></li>
<li>Click '''OK''' to create the task.</li>  
<translate><!--T:57--> [[image:RHV_bck_task-create.jpg|670px|link=]]</translate>
 
<br clear=all>
<li>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'''.</li>
<li><translate><!--T:58--> By default, the RHV backup module automatically creates memory snapshots of the virtual machine. Memory snapshots take time and resources, but allow reversion to a running VM state as it was when the snapshot was taken. You can disable automatic creation of memory snapshots by adding the option <tt>-a qui=0</tt> to the the ''Backup options'': Click the '''Options''' tab -> '''Additional call arguments''' -> enter <tt>-a qui=0</tt> to the '''Backup options''' field.</translate></li>
 
<li><translate><!--T:59--> If you want to define other options (such as pre/post backup and restore commands, set encryption, specify OS credentials,  consolidate individual tasks under a specific task group, or assign a task to the schedule), click the corresponding tabs in the ''New Backup Task'' window.</translate></li>
<li>Check backup status in SEP sesam GUI under (Main Selection) '''Job State''' -> '''Backups'''.</li>
<translate><!--T:60--> Click '''OK''' to create the task.</translate>
 
{{<translate><!--T:61--> tip</translate>|<translate><!--T:62--> You can add your tasks for individual node or individual VM to a task group and enable triggering all tasks at once with a single event. For details, see [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].</translate>}}</li>
[[File:Result_4.4.3.png]]  
<translate><!--T:63--> [[image:RHV_add_task_to_group.jpg|650px|link=]]</translate>
<br clear=all>
<li><translate><!--T:64--> 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 create a periodic backup, you have to create a schedule for your backup task: Click '''New schedule''' under '''Main Selection''' -> '''Scheduling''' -> '''Schedules''' and set up a schedule. For more details, see [[Special:MyLanguage/Creating_a_Schedule|Creating a Schedule]].</translate></li>
{{<translate><!--T:65--> tip</translate>|<translate><!--T:66--> You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the tab '''Schedules''' and adding it to one or more schedules.</translate>}}
<li><translate><!--T:67--> After you have configured a schedule, you must create a new backup event for it. From '''Main Selection''' -> '''Scheduling''' -> '''New Backup Event''', click the '''Parameter''' tab and select the task to which you want to link this event. Then select ''COPY'' from the '''Backup level''' drop-down list. Note that ''COPY'' is currently the only supported backup level for SEP sesam RHV clients. For detailed procedure, see [[Special:MyLanguage/Creating_a_Backup_Event|Creating a Backup Event]].</translate>
</li>
<translate><!--T:68--> [[image:RHV_bck_event.jpg|670px|link=]]</translate>
<br clear=all>
<br clear=all>
{{note|
</ol>
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.}}
<translate><!--T:69-->
 
You can view the status of your backup jobs by selecting '''Last Backup State''' in the ''Main Selection'' window. The backup status overview provides detailed information on the last run of backup jobs, including the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.
<li>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.</li>
 
{{note|
COPY is the only supported backup level type for SEP sesam RHEV clients.}}</ol> 


For more information on schedules and related events, see [[Special:MyLanguage/Schedules_4.4|Schedules 4.4]]. See also  [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].
<!--T:70-->
{{Note|As of [[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3 ''Beefalo V2'']], you can check the details of your backups online by using new Web UI. For details, see [[Special:MyLanguage/4_4_3_Beefalo:SEP_sesam_Web_UI|SEP sesam Web UI]].}}


==Known issues==
<noinclude><div class="noprint">
If you have problems with RHEV Linux issues, check the [[Special:MyLanguage/Troubleshooting_Guide#Red_Hat_Enterprise_Linux|Troubleshooting Guide]].
==Known issues== <!--T:71-->
If you have problems, check the [[Special:MyLanguage/Troubleshooting_Guide#RHEV|Troubleshooting Guide]].


==See also==
==See also== <!--T:72-->
[[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]] – [[Special:MyLanguage/4_4_3:RHEV_Restore|RHEV Restore]]
[[Special:MyLanguage/4_4_3_Beefalo:RHV_Configuration|RHV Configuration]] – [[Special:MyLanguage/4_4_3_Beefalo:RHV_Restore|RHV Restore]]</div></noinclude></translate>

Revision as of 10:31, 1 October 2020

Other languages:

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.

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.
Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3 Beefalo/Beefalo V2. For previous documentation version(s), check RHV archive.


Overview

SEP sesam backup solution for RHV* environments was developed together with Red Hat. SEP sesam uses 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. SEP sesam tight integration with RHV backup API enables consistent, agentless backups of all RHV virtual machines, regardless of their workload or operating system. Since the RHV module now supports OLVM the same options and steps apply for configuring the OLVM environment backup, with the only difference that the relevant OLVM components should be configured instead of RHV.

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

Key features

  • Since SEP sesam communicates directly with the RHV hypervisor, it does not matter what operating system is running as a virtual guest. Windows, Linux or any other operating system supported by the RHV hypervisor is treated as a virtual guest and backed up directly by communicating with the hypervisor.
  • SEP sesam supports backups for RHV single servers and RHV clusters with libvirt API.
  • Single (individual) VM backup is supported both on a RHV single server and on a RHV cluster.
  • The following backup methods are available for backing up VMs in a RHV cluster/data center or on RHV single server:
    • A config only backup backs up only the VM configuration.
    • Backup of individual VMs that can be grouped together in one task group running on multiple hosts via the RHV Manager.
    • Backup of VMs with specific disks (disks exclusion).
  • COPY backup is currently the only supported RHV backup level, which means that all data defined by the backup task is backed up (provisioned space). It is recommended to use SEP Si3 target deduplication for your RHV backups to reduce the size of backed up data.

Backup workflow

The backup process uses the following workflow:

  1. A snapshot of the virtual machine (VM) is created.
  2. The VM configuration is exported from the snapshot and backed up as the first saveset stream.
  3. The virtual disks represented in the snapshot are attached to the data mover VM.
  4. The data of the virtual disks is backed up.
  5. The snapshot of the VM is removed.

Prerequisites

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

LAN-based or LAN-free backup

SEP sesam’s Red Hat Virtualization backup can operate in two modes: LAN-based backup and LAN-free backup.

During the 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 images show how to use the backup module for LAN-based and LAN-free backup. Steps 1-5 in the graphic show the direction of the connection establishment for communication and metadata transfer. Step 6 shows the direction of the connection establishment for the data transfer to the connected storage.

LAN-based backup scenario
  • Start the backup process with connection to the RHV Manager host or OLVM host. Create a consistent snapshot of the VM. (Step 1)
  • Once the snapshot is successfully created, the VM configuration is exported from the snapshot and backed up as the first stream in the saveset. (Steps 2, 3, 4)
  • The VM disks present in the snapshot are then attached to the data mover VM using the backup API. Once attached, the data on these disks is backed up and upon success, the snapshot is removed again. The snapshot is transferred from the data mover VM to SEP sesam Server via LAN. (Steps 5, 6)
  • The backed up data is stored in backup storage (connected storage devices, such as SEP sesam data store, SEP sesam Si3 deduplication store, HPE StoreOnce, tape library).
  • LAN based backup
    SEP-sesam-RHV-LAN-Based.png
LAN-free backup scenario
Use the SAN storage connected directly to the RHV cluster itself to perform backup transferred across your dedicated storage interface. In this case, the storage is attached directly to the data mover VM using the Storage Area network.
  • Start the backup process with connection to the RHV Manager host or OLVM host. Create a consistent snapshot of the VM. (Step 1)
  • Once the snapshot is successfully created, the VM configuration is exported from the snapshot and backed up as the first stream in the saveset. (Steps 2, 3, 4)
  • The VM disks present in the snapshot are then attached to the data mover VM using the backup API. Once attached, the data on these disks is backed up and upon success, the snapshot is removed again. The snapshot is transferred from the data mover VM to your backup storage via SAN. (Steps 5, 6)
  • The backed up data is stored in backup storage (connected storage devices, such as SEP sesam data store, SEP sesam Si3 deduplication store, HPE StoreOnce, tape library).
  • LAN free backup
    SEP-sesam-RHV-LAN-Free.png

Backing up RHV virtual machines

Create a new backup task for the RHV VM or OLVM client. You can only perform one VM backup per backup task. You must configure a separate backup task for each VM that you want to back up.

SEP Tip.png Tip
If you prefer to watch a video rather than to read a step-by-step guide, you can learn all the steps of the backup procedure by watching Backup of Red Hat Virtualization (RHV)/Oracle Linux Virtualization (OLVM) with SEP sesam on SEP sesam YouTube channel.
  1. In the Main Selection -> Tasks -> By Clients, select the RHV Manager client or OLVM client and then click New Backup Task. The New Backup Task window opens.
  2. Specify the Source of the VM you want to back up. You can browse for the source or enter it manually. When you browse for the source, the task type and task name are set automatically. If you enter the source manually, you need to enter the task name and select the RHV task type from the drop-down list.
  3. RHV bck task-source.jpg
  4. You can exclude individual disks from backup by entering them in the Exclude list field. You have to use the logical disk name(s) as displayed in the RHV management center. If you want to exclude multiple disks, enter them one by one followed by a comma without spaces, for example: disk_name1,disk_name2.
  5. RHV bck task-create.jpg
  6. By default, the RHV backup module automatically creates memory snapshots of the virtual machine. Memory snapshots take time and resources, but allow reversion to a running VM state as it was when the snapshot was taken. You can disable automatic creation of memory snapshots by adding the option -a qui=0 to the the Backup options: Click the Options tab -> Additional call arguments -> enter -a qui=0 to the Backup options field.
  7. If you want to define other options (such as pre/post backup and restore commands, set encryption, specify OS credentials, consolidate individual tasks under a specific task group, or assign a task to the schedule), click the corresponding tabs in the New Backup Task window.
  8. Click OK to create the task.
    SEP Tip.png Tip
    You can add your tasks for individual node or individual VM to a task group and enable triggering all tasks at once with a single event. For details, see Adding a Task to the Task Group.

    RHV add task to group.jpg

  9. 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 create a periodic backup, you have to create a schedule for your backup task: Click New schedule under Main Selection -> Scheduling -> Schedules and set up a schedule. For more details, see Creating a Schedule.
  10. SEP Tip.png Tip
    You can also add your backup task to an existing schedule by double-clicking the backup task, selecting the tab Schedules and adding it to one or more schedules.
  11. After you have configured a schedule, you must create a new backup event for it. From Main Selection -> Scheduling -> New Backup Event, click the Parameter tab and select the task to which you want to link this event. Then select COPY from the Backup level drop-down list. Note that COPY is currently the only supported backup level for SEP sesam RHV clients. For detailed procedure, see Creating a Backup Event.
  12. RHV bck event.jpg

You can view the status of your backup jobs by selecting Last Backup State in the Main Selection window. The backup status overview provides detailed information on the last run of backup jobs, including the task name, start and stop time of the last backup, backup level, data size, throughput, assigned media pool, etc.

Information sign.png Note
As of 4.4.3 Beefalo V2, you can check the details of your backups online by using new Web UI. For details, see SEP sesam Web UI.

Known issues

If you have problems, check the Troubleshooting Guide.

See also

RHV ConfigurationRHV Restore