veeamconfig config import fails

[splummer]

The step where jobs are imported fails.

Notice: /Stage[main]/Profile::Veeam_linux_client/Veeamagent::Backup_job[Morning Backup]/Exec[Import Backup Job - Morning Backup]/returns: Unable to import file [/etc/veeam/Morning Backup.xml]. Error: /Stage[main]/Profile::Veeam_linux_client/Veeamagent::Backup_job[Morning Backup]/Exec[Import Backup Job - Morning Backup]: Failed to call refresh: 'veeamconfig config import --file "/etc/veeam/Morning Backup.xml"' returned 255 instead of one of [0] Error: /Stage[main]/Profile::Veeam_linux_client/Veeamagent::Backup_job[Morning Backup]/Exec[Import Backup Job - Morning Backup]: 'veeamconfig config import --file "/etc/veeam/Morning Backup.xml"' returned 255 instead of one of [0]

veeamconfig job list shows no jobs.

running the command outside of puppet returns this error.

[root@plummertest1 etc]# veeamconfig config import --file "/etc/veeam/Morning Backup.xml" Error: No VBR server with id[{06cd0498-77f6-4e47-919f-6f764e5b1833}] found. Unable to update db. Unable to import file [/etc/veeam/Morning Backup.xml].

Maybe this is a veeam agent issue not an issue with the way the module works. either way it seems very odd.

[yachub]

Hi @splummer, I would be happy to help out. It could be a Veeam agent issue, but either way, it may be worth documenting.

A few questions to get us going in the right direction:

• Are you using the agent with Veeam B&R, or just the agent standalone?
• If using Veeam B&R, does the repo_name parameter for your backup_job resource match the the exact Name of the backup repository in Veeam B&R located in the "Backup Infrastructure --> Backup Repositories" section?
• If using Veeam B&R, have you entered correct values (i.e. credentials, domain, FQDN of Veeam B&R server) to all vbrserver_* parameters for your backup_job resource?
• If using Veeam B&R, are you running 9.5 Update 2?

[splummer]

Thanks for helping out!

• I am using the agent with Veeam B&R
• Yes it matches exactly
• Yes they are correct. They are also present even though the jobs fail to import. If I manually create a job using the pre-filled values the job succeeds.
• Yes I am running Update 2. 9.5.0.1038

Interestingly if I create a job in the interface, export it, delete it, then try to import it I get the same error.

[splummer]

I also have submitted a support ticket to veeam. I will be sure to report anything I discover from them here.

[genebean]

@splummer did you ever get this worked out?