5 0 0:OLVM Backup

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

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

SEP sesam provides support for oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM), which is based on the RHV backup module. You can perform agentless snapshot-based backups of all OLVM virtual machines, regardless of their workload or operating system.

Before proceeding, ensure that your OLVM environment is properly set up and all requirements are met. For details, see OLVM Configuration.

Key features

  • SEP sesam supports backup of single (individual) VMs in OLVM environment.
    • Backup of individual VMs with the ability to combine tasks into a task group and trigger their start with a single event.
    • Backup of VMs with specific disks (disk exclusion).
  • Currently, only the backup level COPY is supported, which means that all data defined by the backup task is backed up (provisioned space).
  • SEP Tip.png Tip
    Use SEP Si3 target deduplication for your OLVM backups to reduce the size of the 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 on the virtual disks is backed up.
  5. The snapshot of the VM is removed.

Backup modes

SEP sesam OLVM backup can operate in two modes: LAN-based backup and LAN-free backup.

Backup creates a VM snapshot and mounts it on the SEP sesam data mover. Snapshots can be transferred via LAN or SAN (Storage Area Network). If a SAN storage device is available to SEP sesam, the transfer is direct (LAN-free). For details on both backup scenarios, see LAN-based or LAN-free backup.

Backing up OLVM virtual machines

SEP Tip.png Tip
If you intend to back up multiple VMs, you can automate the process by automatically generating tasks for VMs that are connected to the same host; you can also automatically create clients for VMs to which the created tasks and ACLs can be assigned. It is recommended to use these features when a new hypervisor is added and many new VMs need to be backed up. For details, see Automating Backup Process.

Create a new backup task for the 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.

  1. In the Main Selection -> Tasks -> By Clients, select the 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 Oracle-VM task type from the drop-down list.
  3. 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 OLVM 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.
  4. OLVM bck task.jpg

  5. By default, the RHV backup module used for OLVM backups 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 created. You can disable the automatic creation of memory snapshots by using the additional options: Click the Options tab -> Additional call arguments -> enter -a qui=0 in the Backup options field.
  6. OLVM bck task options.jpg

  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.
  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 OLVM clients. For detailed procedure, see Creating a Backup Event.

Monitoring backups

You can view the status of your backup jobs in the GUI (Monitoring -> Last Backup State or Job State -> Backups) or SEP sesam Web UI. The backup status overview provides detailed information about 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.