4 4 3 Beefalo:RHV Backup: Difference between revisions

From SEPsesam
(Rewrite in progress.)
Line 1: Line 1:
{{draft‎}}
<div class="noprint">{{draft‎}}
{{Copyright SEP AG|en}}
{{Copyright SEP AG|en}}
{{Navigation_latest|release=4.4.3|link=[[Special:MyLanguage/RHEV|RHEV archive]]}}<br />
{{Navigation_latest|release=[[Special:MyLanguage/SEP_sesam_Release_Versions|4.4.3/4.4.3 ''Beefalo'']]|link=[[Special:MyLanguage/RHEV|RHEV archive]]}}</div><br />


=={{anchor|overview}}Overview==
=={{anchor|overview}}Overview==
Line 7: Line 7:


{|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:RHEV_Restore|RHEV 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;" | See also: [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]] – [[Special:MyLanguage/4_4_3:RHEV_Restore|RHEV Restore]]
|}
|}
Line 25: Line 25:
| 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;" | If you are using an older SEP sesam version, refer to [[Special:MyLanguage/RHEV|RHEV previous version]] of the documentation.
|}</div>
|}</div>
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.  
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 (RHEV) virtual machines, regardless of their workload or operating system.  


=== {{anchor|features}}Key features ===
=== {{anchor|features}}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 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'''.
* SEP sesam supports backup for '''RHEV single server''' and '''RHEV cluster''' with '''<tt>libvirt</tt> API'''.
* The backup of '''individual VMs''' is supported on RHEV single server as well as on RHEV cluster.
* 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:
* 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.
** A '''config only backup''' backs up only the VM 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 '''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).
***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.
*[[Special:MyLanguage/SEP_sesam_Glossary#COPY|''COPY'']] backup is currently the only supported RHEV backup level. This means that all data defined by the backup task is backed up (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]].


=== {{anchor|workflow}}Backup workflow ===
=== {{anchor|workflow}}Backup workflow ===


The backup process uses the following workflow:
The backup process uses the following workflow:
* A snapshot of the virtual machine is created.
#A snapshot of the virtual machine (VM) is created.
* Virtual machine configuration is exported from the snapshot and backed up as the first save set stream.
#VM configuration is exported from the snapshot and backed up as the first saveset stream.
* The virtual disks represented in the snapshot are attached to the [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover virtual machine]].
#The virtual disks represented in the snapshot are attached to the [[Special:MyLanguage/SEP_sesam_Glossary#SDM|data mover]] VM.
* The data of the virtual disks is backed up.
#The data of the virtual disks is backed up.
* The snapshot of the virtual machine is removed.
#The snapshot of the VM is removed.


=== Prerequisites ===
=== Prerequisites ===
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
* 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.
* Check the [[SEP_sesam_OS_and_Database_Support_Matrix#Red_Hat|support matrix]] for the list of supported RHEL versions.
* Check [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]].
* Make sure your RHEV environment is configured properly, as described in [[Special:MyLanguage/4_4_3:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]].


== {{anchor|LAN}}LAN or LAN-free backup ==
== {{anchor|LAN}}LAN or LAN-free backup ==
Line 58: Line 56:
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).  
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.  
The following pictures show how to use the backup module for LAN or LAN-free backup. Steps 1-5 in the graphics are showing the direction of the connection establishment for communication and metadata transfer. Step 6 is showing the direction of the connection establishment for data transfer to the connected storage.  


;LAN based backup scenario
;LAN based backup scenario
<ol>
<ol>
<li>Start backup process with connection to the RHEV Manager host.</li>
<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>Create consistent snapshot of VM with RHEV Manager backup API.</li>
<li>Mount snapshot to SEP sesam data mover VM.</li>
<li>Mount snapshot to SEP sesam data mover VM.</li>
<li>Transfer snapshot from SEP sesam data mover VM to Sesam Server via LAN.</li>  
<li>Transfer snapshot from SEP sesam data mover VM to SEP 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> 
<li>Store a snapshot on the connected storage devices ([[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 deduplication store]], [[Special:MyLanguage/SEP_sesam_Glossary#loader|tape library]]).</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;"
Line 72: Line 70:
! scope="col" style="width: 100px;" | LAN based backup
! scope="col" style="width: 100px;" | LAN based backup
|-
|-
|[[File:Rhev-lan-bck.jpg]]
|[[File:SEP-sesam-RHV-LAN-Based.png|center|link=]]
|}
|}
</ol> 
   
   
;LAN-free backup scenario
;LAN-free backup scenario
<ol>
<ol>
<li>Start backup process with connection to the RHEV Manager host.</li>
<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>Create consistent snapshot of VM 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>Mount snapshot to SEP sesam data mover VM (SEP sesam Remote Device Server) which is directly connected to the 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>Transfer snapshot from SEP sesam data mover VM (SEP sesam RDS) 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>   
<li>Store a snapshot on the connected storage device ([[Special:MyLanguage/SEP_sesam_Glossary#data_store|SEP sesam data store]], [[Special:MyLanguage/SEP_sesam_Glossary#Si3_store|SEP sesam Si3 deduplication store]], [[Special:MyLanguage/SEP_sesam_Glossary#loader|tape library]]).</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;"
Line 87: Line 86:
! scope="col" style="width: 100px;" | LAN free backup
! scope="col" style="width: 100px;" | LAN free backup
|-     
|-     
|[[File:Rhev-san-bck.jpg]]     
|[[File:SEP-sesam-RHV-LAN-Free.png|center|link=]]     
|}
|}
</ol>
</ol>
Line 93: Line 92:
=={{anchor|backing up}}Backing up RHEV virtual machines==
=={{anchor|backing up}}Backing up RHEV virtual machines==


Create new backup tasks for the RHEV Manager client.  
Create new backup tasks for the RHEV Manager client. Note that you can only back up one VM per backup task. You must configure a separate backup task for each VM that you want to back up. 
<ol>
<ol>
<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>In the '''Main Selection''' -> '''Tasks''' -> '''By clients''', select the ''RHEV Manager'' client and then click '''New backup task'''. The ''New backup task'' window opens.</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>  
<li>Specify the '''Source''' of the VM you want to back up. You can browse for the source or enter it manually. If you browse for the source, the ''task type'' and ''task name'' are set automatically. If you enter the source manually, you have to enter the ''task name'' and select the RHV task type from the drop-down list.</li>  
 
[[image:RHEV_bck_task_Beefalo.jpg|link=]]
[[image:Rhev-task_4.4.3.png|link=]]
<br clear=all>
<br clear=all>
<li>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 they are shown in the RHEV managment center. If you want to exclude multiple disks, enter them one by one followed by a comma with no whitespace, for example: ''disk_name1,disk_name2''.</li>
<li>If you want to define other options (such as pre/post backup and restore commands, set encryption, 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.</li>
Click '''OK''' to create the task.</li>
<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 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]].</li>
{{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. Additionally, you can group your backup tasks to task groups. For details, see [[Special:MyLanguage/Adding_a_Task_to_the_Task_Group|Adding a Task to the Task Group]].}}
<li>Once you have configured a schedule, you must create a new backup event for it. Note that ''COPY'' is currently the only supported backup level for SEP sesam RHEV clients. For details, see [[Special:MyLanguage/Creating_a_Backup_Event|Creating a Backup Event]].</li>
</ol>


<li>You can exclude individual disks from backup by entering them in the '''Exclude List''' field. You have to use the logical disk(s) name(s) as they are shown in the RHEV managment center. If you want to exclude multiple disks, enter them one by one followed by a comma with no whitespace, for example: ''disk_name1,disk_name2''.
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>Click '''OK''' to create the task.</li>
 
<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>Check backup status in SEP sesam GUI under (Main Selection) '''Job State''' -> '''Backups'''.</li>
 
[[File:Result_4.4.3.png|link=]] 
<br clear=all>
{{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.}}
 
<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]].


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


==See also==
==See also==
[[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:RHEV_Requirements_and_Configuration|RHEV Requirements and Configuration]] – [[Special:MyLanguage/4_4_3:RHEV_Restore|RHEV Restore]]</div>

Revision as of 15:17, 18 October 2019

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/4.4.3 Beefalo. 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 (RHEV) 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 VM 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 RHEV backup level. This means that all data defined by the backup task is backed up (provisioned space), therefore it is recommended to use the SEP Si3 target deduplication for your RHEV backups.

Backup workflow

The backup process uses the following workflow:

  1. A snapshot of the virtual machine (VM) is created.
  2. 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 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. Steps 1-5 in the graphics are showing the direction of the connection establishment for communication and metadata transfer. Step 6 is showing the direction of the connection establishment for data transfer to the connected storage.

LAN based backup scenario
  1. Start backup process with connection to the RHEV Manager host.
  2. Create consistent snapshot of VM with RHEV Manager backup API.
  3. Mount snapshot to SEP sesam data mover VM.
  4. Transfer snapshot from SEP sesam data mover VM to SEP sesam Server via LAN.
  5. Store a snapshot on the connected storage devices (SEP sesam data store, SEP sesam Si3 deduplication store, tape library).
  6. LAN based backup
    SEP-sesam-RHV-LAN-Based.png
LAN-free backup scenario
  1. Start backup process with connection to the RHEV Manager host.
  2. Create consistent snapshot of VM with RHEV Manager backup API.
  3. Mount snapshot to SEP sesam data mover VM (SEP sesam Remote Device Server) which is directly connected to the storage device via SAN.
  4. Transfer snapshot from SEP sesam data mover VM (SEP sesam RDS) to connected storage via SAN.
  5. Store a snapshot on the connected storage device (SEP sesam data store, SEP sesam Si3 deduplication store, tape library).
  6. LAN free backup
    SEP-sesam-RHV-LAN-Free.png

Backing up RHEV virtual machines

Create new backup tasks for the RHEV Manager client. Note that you can only back up one VM per backup task. You must configure a separate backup task for each VM that you want to back up.

  1. In the Main Selection -> Tasks -> By clients, select the RHEV Manager 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. If you browse for the source, the task type and task name are set automatically. If you enter the source manually, you have to enter the task name and select the RHV task type from the drop-down list.
  3. File:RHEV bck task Beefalo.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 they are shown in the RHEV managment center. If you want to exclude multiple disks, enter them one by one followed by a comma with no whitespace, for example: disk_name1,disk_name2.
  5. If you want to define other options (such as pre/post backup and restore commands, set encryption, 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.
  6. Click OK to create the task.
  7. 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.
  8. 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. Additionally, you can group your backup tasks to task groups. For details, see Adding a Task to the Task Group.
  9. Once you have configured a schedule, you must create a new backup event for it. Note that COPY is currently the only supported backup level for SEP sesam RHEV clients. For details, see Creating a Backup Event.

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.

Known issues

If you have problems, check the Troubleshooting Guide.

See also

RHEV Requirements and ConfigurationRHEV Restore