Skip to content

Commit f5a3de4

Browse files
committed
information on compatible backup providers
1 parent 40cd2fd commit f5a3de4

1 file changed

Lines changed: 20 additions & 0 deletions

File tree

source/adminguide/kvm_veeam.rst

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -411,6 +411,26 @@ For RHEL/CentOS-based hosts, run the following commands:
411411
dnf install epel-release -y
412412
dnf install ntfs-3g -y
413413

414+
Compatibility with other Backup Providers in CloudStack
415+
-------------------------------------------------------
416+
417+
Other backup providers available in CloudStack cannot be used alongside
418+
the CloudStack Veeam integration for KVM within the same Zone in this release.
419+
This restriction avoids conflicts and unintended interactions at the hypervisor level.
420+
421+
The only exception is the Veeam backup provider used for VMware environments.
422+
It can coexist in the same Zone as the KVM Veeam integration because
423+
the two integrations operate on different hypervisors.
424+
425+
If other zones have different backup providers configured, the **dummy** provider can
426+
be used as a placeholder in the zone where the Veeam integration for KVM is required to avoid conflicts.
427+
428+
To use the CloudStack Veeam integration for KVM, use one of the following configuration settings:
429+
430+
* **backup.framework.enabled** = false, or
431+
* **backup.framework.provider.plugin** = dummy, or
432+
* **backup.framework.provider.plugin** = veeam (if VMware integration is also needed in the same Zone).
433+
414434
Limitations and Recommendations
415435
-------------------------------
416436

0 commit comments

Comments
 (0)