Configuring oVirt Backup

Configuring oVirt Backup

Step 1: Adding Basic Job Details

Get started by creating a backup job by choosing Job Create Option, choose to Create Job without using a template if you want to create a backup from scratch, or choose to Create Job using an existing template if you would like to use an already created template for the backup job creation.

Backup Job Name

In the Backup Job Name filed, Provide a name for the backup job to identify it. The allowed characters in the backup job name are [A-Z][a-z][0-9][ – _ ]. Space and Special characters are not allowed.

Backup Repository

Choose Block storage or the Object storage as per requirement.

Immutable Backups (Only for Object Storage)

You have the option to enable this feature by checking the box, which will secure your backups as immutable for a specific duration. The duration can be specified and you do it for up to 999 day(s). The duration set will be applied to this backup job, which you’ll configure in subsequent steps. When configuring other backup jobs, ensure to adjust the duration according to your needs.

Immutable backup in the BDRSuite Backup Server is a backup strategy or system you can use where once the data is backed up, it cannot be edited, deleted, or tampered with until a predefined time period expires that can be set up as shown below in the image representation. This approach adds an extra layer of protection to the backup data, making it resistant to ransomware attacks, accidental or malicious changes.

Repository Name

After selecting the Backup Repository type, you have to select the name of the Block Storage or Object Storage repository to store the backup data. Click on the drop-down to select the backup repository name.

Job Description

In the Job Description field, provide a description for future reference. You can provide additional information related to this backup job in the description field.

Step 2: Host Selection

‌If you have added a host, then it will be listed and you can select the entire host or just the VMs to be backed up. VMs from different hosts can also be backed up in a same backup job.

All the selected hosts and VMs are shown on the right hand side of the page for your reference.

Step 3: Scheduling

The schedule option defines the frequency of your oVirt Backup job.

Incremental Backup Schedule

You can configure the incremental backup schedules by choosing between Run Every/Run Daily/Run Weekly options.
  1. Select Run Every option if you want to run your backup at regular intervals on a specific day(s). The time frame ranges from 15 minutes to 12 hours a day on specific days a week. By default, all the days in the week will be selected. If you don’t want to run your backup on all days, manually select the days on which you want to run the backup.
  2. If you want to run your backup every day, select the Run Daily option and configure the period in which your backup has to occur.
  3. If you want to run your backup every week on a specific day and time, choose the Run Weekly option. Select the time frame and day in which you want to run the backup.
Notes
Note: By default, Run Every option will be selected for the backup schedule.

Synthetic Full Backup

Instead of creating a new full backup periodically by creating a snapshot of the source VM, BDRSuite creates synthetic full backup by merging full and subsequent incremental in the repository without running an additional full backup. A synthetic full backup is an optional configuration, you can save the backup job without enabling the Synthetic merge.

Enable the synthetic full backup by toggling the slider to the right. Once enabled you to have to specify the scheduling for the synthetic merge to happen.

Specify the synthetic full backup frequency. You can specify the synthetic merge to happen on a weekly or monthly basis.

Additional Full Backup Schedule

In some cases, you may require to create a periodic full backup weekly or monthly, or quarterly basis to adhere to your organization policy. Also, it is not a best practice to configure a backup job with one full backup followed by forever incremental backups. BDRSuite’s Additional full backup option allows you to comply with your requirements by creating a full backup periodically.

The additional full backup resets a backup chain and the subsequent incremental are based on the recent full backup. Running additional full backups frequently may sometimes lead to storage space consumption, you can automatically delete the older full backups chain by setting the appropriate retention policy for the additional full backups or deleting it manually when required.

Enable the additional full backup by toggling the slider to the right. Once enabled you will have to specify the scheduling for the synthetic merge to happen.
  1. Specify the Additional full backup frequency. You can specify to run the additional full backups on a weekly or monthly basis.
  2. If you have scheduled the incremental backups to run Every Few Hours/Min or Daily or After Backup, then you can set the additional full backups frequency as Daily or Weekly or Monthly.
  3. If you have scheduled the incremental backups to run Weekly or Monthly, then you can set the additional full backups to run on a Weekly or Monthly basis.
  4. Additional full backups are disabled Manually & One Time backup schedules
If you are selecting the additional full backups to run on a daily basis, then you have to select the start time to run the additional full backups.

If you are selecting the additional full backups to run on a weekly basis, then you have to select a day and start time to run the synthetic merge. You can select one or more days in a week to run the additional full backups.

If you are selecting the additional full backups to happen on a monthly basis, then you have to select the month, select a day in the month and start time to run the additional full backups. You can select one or more months in a year to run the additional full backups.

Advanced Schedule Settings

The Advanced Schedule Settings allow you to specify the Backup Window time and Backup Validity for your backup job.

Backup Window

If you don’t want the backup run at a specific time interval, then you can specify it in the backup time window. The backup window prevents the backup job from running during peak production hours and ensures there is no unwanted overhead in the production environment. Select one of the available options to set up the backup window for your backup job

Use Global Settings: Selecting the‘ Use Global Settings’ option will apply the Backup Window setting of your backup server to this backup job. You can set up the global backup window settings for your entire backup server at Backup > Configure Backup Settings > Backup Window.
  1. In case, if you are selecting the ‘Use Global Settings’, but if global backup window settings are disabled for your backup server, then the job will run as per its schedule
  2. If you are modifying the Global Backup Windows settings later, it will affect all the backup jobs that are selected with ‘Use Global Settings’
Use Custom Settings: On selecting ‘Use Custom settings’, you have to specify the start time and end time for the window. The backup job will not during the selected time interval. You can also specify the applicable days for the backup window settings such as Mon-Fri or All days. Selecting the ‘Use Custom settings’ will override the global backup window settings.

No Preferences: Selecting ‘No Preferences’ will override the global backup window settings and the backup job will run as per the schedule.

Backup Validity

Set the validity for your backup job by specifying the start date and the expiration date. The Backup job will start to run
only after the start date.

If you want a backup job to start to run later, for example, 5 days later from the day you have created the backup job, then you can specify the start date of the backup job accordingly. The expiry date is optional for a backup job, if the expiry date is set the incremental backup or additional full backup does not proceed after that.

Step 4: Backup Job Settings

Retention

Version Based Retention
If you are selecting the version-based retention for the incremental backups, then you have to specify the number of versions to be retained. You can select from 1 to 999 versions.
Notes
Note: For example, if you configure hourly incremental backups and select ‘10 versions’ to retain, BDRSuite Backup Server will retain only the last 10 hours of recovery points of the backed-up machine.
Day Based Retention

The “day-based retention” feature in BDRSuite allows users to specify the number of days that incremental recovery points should be retained. This means that users can select a specific number of days, such as 14, to retain 2 weeks of recovery points. Additionally, the “Minimum version(s)” option can be selected to avoid losing recovery points due to backup failures.

This ensures that the BDRSuite will retain the minimum number of recovery points specified in the “Minimum version(s)” field, even if the backup job does not run for a certain number of days.

Without this option, the BDRSuite would remove all incremental recovery points. By default, the “Minimum version(s)” option is set to 3 versions, but it can be increased as needed.

An example of how this feature might be used is as follows:

A user sets up the BDRSuite to perform hourly incremental backups. They then select the “day-based retention” option for the incremental backups and specify that they want to retain 14 days of incremental recovery points. The BDRSuite then begins performing hourly incremental backups and saves each recovery point for 14 days, as specified by the user. In total, the backup server retains 336 recovery points (14 days x 24 hours per day). When backup jobs are running successfully, the exceeding recovery points will be removed according to the “day-based retention” option. So, on the 15th day, the first day’s incremental data will be merged with the full backup and the incremental backup’s timestamp will be removed. However, if the backup job does not run for the next 15 days, all incremental recovery points should be removed according to the “day-based retention” option. But, If you have updated to keep “Minimum version(s)” as 24, as per the “Minimum version(s)” configuration, the BDRSuite will still retain 24 recovery points (one day’s worth of incremental timestamps). This ensures that a certain number of recovery points are always available, even if backup jobs are not running as expected.

GFS stands for Grandfather, Father, and Son based retention that allows you to retain the recovery points of the backup jobs for long periods like weekly, monthly, quarterly, or yearly. Under the GFS retention, the weekly backups are referred to as “sons,” monthly backups as “fathers,” and yearly backups as “grandfathers”. BDRSuite Backup Server marks the GFS flag against the Additional full or Synthetic full backups or incremental backups.

There are two types of GFS retention
  1. GFS with Full Backups
  2. GFS with Incremental.
Notes
Note: If you need to enable GFS retention, it is necessary to choose either one of the options in basic retention, as GFS retention works in combination with basic retention.
 GFS with Full Backups
  1. The GFS restore points are created using additional full or synthetic full backups.
  2. The additional full backup or synthetic full backups are marked as weekly, monthly, quarterly, or yearly GFS recovery points.
  3. So, you should have already configured either the synthetic or additional full backup for the backup job.
  4. You can either choose weekly/monthly/quarterly/yearly or any combination of GFS recovery points.
For example, If you want to retain 4 weeks, 12 months, 4 quarters of GFS recovery points, the available full backups in the backup repository will be marked as per the GFS retention schedule. So, based on this configuration, 20 GFS full recovery points will be retained at the end of the year.

GFS with Incremental
  1. The GFS restore points are created using incremental backups without including additional full or synthetic full backups.
  2. The incremental backups are marked as daily, weekly, monthly, quarterly, or yearly GFS restore points.
  3. On the successful completion of the 3rd-day’s first incremental backup, the 1st-day increments will get merged, to form a daily GFS recovery point. Similarly, on the 4th-day, the increments of the 2nd day will be consolidated as a single restore point and so on for the 5th-day and the 6th-day. This process continues to maintain the daily GFS recovery points.
  4. Similarly, if you choose weekly/monthly/quarterly/yearly backups, the incremental backups from the previous week /month /quarter /year will be merged and a GFS recovery point will be created.

Encryption

You can encrypt all the backup data for an added protection. When encryption is enabled all the backup data blocks are encrypted using the AES-256 bit encryption algorithm both during the transfer and at the storage. For encrypting the backup data, you can use the system-generated encryption key or use a custom encryption key.
  1. By default, encryption is disabled for all the backups jobs, you can slide the toggle to the right to enable encryption for your backup data.
  2. Select ‘Use System Generated Encryption Key’ if you want to encrypt all your backup data using BDRSuite’s automatic System Generated Encryption Key. You do not need to specify any during the recovery or editing the backup job later.
  3. Select ‘ Use a Custom Encryption Key’ if you want to encrypt all your backup data using your own Encryption Key. You can select the already created encryption keys that are created for other backup jobs from the drop-down list or you can
  4. Add a new encryption key by providing the encryption password, encryption key hint.
  5. After providing the password and hint for the encryption key, click on the Save button.

Step 5: Review Configuration

You can review all the configurations made for the particular backup job. You can choose whether or not to run the backup job immediately after saving irrespective of the schedule chosen.

    • Related Articles

    • Adding oVirt Host for Backup

      oVirt VMs can be backed up using the BDRSuite Backup Server. You can simply add the source to the BDRSuite Backup Server and configure backups. Navigate to Data Sources tab -> Hypervisors -> oVirt. When a oVirt is added to the BDRSuite Backup server, ...

    • Quick Start Guide for oVirt Backup & Recovery

      About oVirt Backup & Recovery BDRSuite provides agentless, image-level backups for oVirt virtual machines, leveraging Changed Block Tracking (CBT) for efficient incremental backups and supporting automated scheduling. Backup data is secured with ...

    • What Is oVirt Backup?

      oVirt Backup involves creating copies of oVirt virtual machines to ensure data protection and facilitate recovery in the event of data loss or system failures. BDRSuite offers an agent-based backup solution specifically designed for backing up and ...

    • Can I receive alerts or notifications for Ovirt backup success or failure?

      Yes, you can configure alerts and notifications for Ovirt backup success or failure with BDRSuite. To do this, first enable SMTP settings and set up Email Notifications. This configuration allows you to receive alerts for various tasks, including ...

    • Can I Backup Multiple oVirt VMs Simultaneously?

      Yes, BDRSuite supports the simultaneous backup of multiple oVirt VMs, optimizing backup windows and improving overall efficiency.