SEP sesam provides support for oVirt-based platforms within Oracle Linux Virtualization Manager (OLVM). 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.
- 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).
- COPY backup is currently the only supported OLVM 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 OLVM backups to reduce the size of backed up data.
- You can restore your data via GUI restore or via the web interface Restore Assistant. SEP sesam also provides a simple and flexible single file restore (SFR) for OLVM if you have the appropriate permissions. For more details, see OLVM Restore.
|You can simplify the backup of multiple VMs by automatically creating 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|
The backup process uses the following workflow:
- A snapshot of the virtual machine (VM) is created.
- The 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 data mover VM.
- The data on the virtual disks is backed up.
- The snapshot of the VM is removed.
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.
To ensure error-free operation of SEP sesam and improve performance, make sure that the following conditions are met:
- Check the support matrix for the list of supported OLVM versions.
- OLVM data mover must be configured. Only Red Hat Enterprise Linux version ≥ 7 can be used as a data mover for backups and restores. For details, see OLVM Configuration.
- Make sure your OLVM environment is set up properly with your OLVM configured as SEP sesam Client. For details, see OLVM Configuration.
- It is strongly recommended to install the Qemu Guest Agent on virtual machines that are backed up to ensure file system consistency during snapshot creation. For more information, see the Red Hat documentation Installing Guest Agents and Drivers: Red Hat Virtualization Guest agents and tools.
Backing up OLVM virtual machines
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. Note that it is strongly recommended to install the Qemu Guest Agent on the VMs to be backed up, see prerequisites above.
- In the Main Selection -> Tasks -> By Clients, select the OLVM client and then click New Backup Task. The New Backup Task window opens.
- 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.
- 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.
- By default, the 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 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.
- 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. Click OK to create the task.
- 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.
- 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.
|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.|
|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.|
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.