Skip to content

Commit 1b355bd

Browse files
committed
additonal notes
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
1 parent 7c99358 commit 1b355bd

1 file changed

Lines changed: 14 additions & 0 deletions

File tree

source/adminguide/kvm_veeam.rst

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -164,6 +164,14 @@ Once the manager is successfully added, Veeam will connect to CloudStack,
164164
discover the infrastructure resources, and make the virtual machines available
165165
for backup and restore operations.
166166

167+
.. warning::
168+
A CloudStack environment should be added to only one Veeam Backup & Replication
169+
platform to avoid conflicts and unintended interactions. To prevent accidental
170+
addition to multiple Veeam platforms, use the
171+
**integration.veeam.control.allowed.client.cidrs** global configuration to
172+
restrict control service access to the IP addresses of authorized Veeam
173+
platforms only.
174+
167175
Backup Proxy or Worker VM for Veeam Backup and Replication
168176
----------------------------------------------------------
169177

@@ -205,6 +213,12 @@ Backup and Replication platform to communicate with the worker VM, an Ingress
205213
rule for the service account's security group should be added for all TCP
206214
ports (1-65355), with the platform IP as the CIDR.
207215

216+
.. note::
217+
The integration has been tested only with the worker VM deployed on a
218+
shared network within the management traffic range or on a network with
219+
appropriate security group rules allowing connectivity to the management
220+
server and hypervisor hosts.
221+
208222
The following considerations should be taken into account when deploying the
209223
worker VM:
210224

0 commit comments

Comments
 (0)