Hi,
I've been working through this with support today but was hoping to get some additional insights on this topic.
Client has historically duplicated a disk image for their AIX servers, and hasn't had any issues with their applications to date.
They've then pivoted to using AIX NIM mksysb restores recently, but this is after the build of all but about 2-3 of their servers.
Surprise surprise, the duplicated disk image is where the trouble lies. When installing Veeam Agent, instead of VBR presenting a list of approximately 25-30 servers within my protection group, I have 4.
This is because Veeam keeps recognising each server that was made with a duplicated disk image as an identical UUID, overwriting its configuration with a different hostname & IP address, depending on which server registers with VBR last.
We were supplied the guidance from KB4205:
We've tried this (including making sure that the UUID in the /etc/veeamagentid has {} encapsulating it, and when then subsequently running /opt/veeam/bin/veeamagentid, I still see the identical ID being returned.Linux OS
Stop the veeamservice service.
Delete or rename the existing /var/lib/veeam/veeam_db.sqlite
Generate a random UUID and specify it in /etc/veeamagentid
The UUID value in the veeamagentid file must be in curly braces.
Start the veeamservice service.
My question is:
Where is the Veeam Agent generating this UUID from? As ultimately this guidance from Veeam is a workaround, but I need to look at where Veeam is seeing these servers as one and the same, to ensure they are presenting as unique servers. Especially as I'm not confident yet that these Linux instructions are identical for AIX.
Additional notes: Customer isn't ready for the jump to VBR v12, so this is VBR v11a with Veeam Agent for AIX v3, both on latest patches.