Skip to content

Add documentation on KBOSS#664

Open
JoaoJandre wants to merge 1 commit into
apache:mainfrom
JoaoJandre:add-kboss-doc
Open

Add documentation on KBOSS#664
JoaoJandre wants to merge 1 commit into
apache:mainfrom
JoaoJandre:add-kboss-doc

Conversation

@JoaoJandre

@JoaoJandre JoaoJandre commented Jun 29, 2026

Copy link
Copy Markdown
Contributor

@winterhazel winterhazel left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@JoaoJandre I left some suggestions.

- VMware with Veeam Backup and Recovery
- KVM with DELL EMC Networker
- KVM with NAS B&R Plugin (4.20 onwards)
- KVM with KBOSS Plugin

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- KVM with KBOSS Plugin
- KVM with KBOSS Plugin (4.23 onwards)

- Support for backup compression.
- Support for backup validation.
- Support for "quick restore", inspired by Veeam's Instant Recovery.
- Incremental disk-only VM snapshot compatible (see :ref:`Disk-only-File-based-Storage-Instance-Snapshots-on-KVM`).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Incremental disk-only VM snapshot compatible (see :ref:`Disk-only-File-based-Storage-Instance-Snapshots-on-KVM`).
- Compatible with incremental disk-only VM snapshots (see :ref:`Disk-only-File-based-Storage-Instance-Snapshots-on-KVM`).

A little rewording. I think it reads better this way.

Comment on lines +33 to +34
While by default the backups are stored in any secondary storage available, sharing the same space with templates, ISOs and snapshots,
using the :ref:`Direct resources to a specific secondary storage` feature, it is possible to create backup-exclusive secondary storages.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
While by default the backups are stored in any secondary storage available, sharing the same space with templates, ISOs and snapshots,
using the :ref:`Direct resources to a specific secondary storage` feature, it is possible to create backup-exclusive secondary storages.
By default, the backups are stored in any secondary storage available, sharing the same space with templates, ISOs and snapshots.
However, it is possible to create backup-exclusive secondary storages using the :ref:`Direct resources to a specific secondary storage` feature.

While by default the backups are stored in any secondary storage available, sharing the same space with templates, ISOs and snapshots,
using the :ref:`Direct resources to a specific secondary storage` feature, it is possible to create backup-exclusive secondary storages.

Currently, only backup of VMs from the NFS, File-based Shared Mountpoint and Local Storage based Primary Storage are supported.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Currently, only backup of VMs from the NFS, File-based Shared Mountpoint and Local Storage based Primary Storage are supported.
Currently, only the backup of VMs consuming NFS, File-based Shared Mountpoint, and/or Local Storage is supported.


Currently, only backup of VMs from the NFS, File-based Shared Mountpoint and Local Storage based Primary Storage are supported.

Since the KBOSS plugin is fully implemented by ACS, and does not depend on any outside provider, the **importBackupOffering** API is not used.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Since the KBOSS plugin is fully implemented by ACS, and does not depend on any outside provider, the **importBackupOffering** API is not used.
Since the KBOSS plugin is fully implemented by ACS, and does not depend on any external provider, the **importBackupOffering** API is not used.

* - Setting
- Description
* - `backupValidationCommand`
- Command to be executed during the command execution step. The step will not run if this configuration does not have a value

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Command to be executed during the command execution step. The step will not run if this configuration does not have a value
- Command to be executed during the execute_command step. The step will not run if this configuration does not have a value

* - `backupValidationCommand`
- Command to be executed during the command execution step. The step will not run if this configuration does not have a value
* - `backupValidationCommandArguments`
- Arguments to be passed to the command executed during the command execution step

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Arguments to be passed to the command executed during the command execution step
- Arguments to be passed to the command executed during the execute_command step

* - `backupValidationCommandArguments`
- Arguments to be passed to the command executed during the command execution step
* - `backupValidationCommandExpectedResult`
- Expected result of the command execution, coded in Base64. If not provided, the process exit code will be checked for value `0`

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Expected result of the command execution, coded in Base64. If not provided, the process exit code will be checked for value `0`
- Expected output of the command's execution, coded in Base64. If not provided, the process exit code will be checked for value `0`

* - `backupValidationCommandExpectedResult`
- Expected result of the command execution, coded in Base64. If not provided, the process exit code will be checked for value `0`
* - `backupValidationCommandTimeout`
- Timeout for the command executed during the command execution step. Overrides the global configuration

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- Timeout for the command executed during the command execution step. Overrides the global configuration
- Timeout for the command executed during the execute_command step. Overrides the global configuration

* - `backupValidationBootTimeout`
- Timeout for the VM boot. Overrides the global configuration

To check information about validation jobs, the **listBackupServiceJobs** API may be added.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To check information about validation jobs, the **listBackupServiceJobs** API may be added.
To allow checking the existing validation jobs, the **listBackupServiceJobs** API may be added in the future.

@weizhouapache weizhouapache added this to the 4.23.0 milestone Jul 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants