Help with exporting Veeam backup jobs via Powershell

[caolanoc]

Hi,

I would be massively grateful if someone could help me with exporting my Veeam backup jobs with their associated details/settings .csv or .xlsx using a Powershell script.

I use Veeam Backup & Replication 9.5 (ver 9.5.0.1536) - wondering if someone has used a script for this? or knows of an easy way to do this?

[Vitaliy S.]

Hello,

I'm a bit confused with your post. Do you want to export Veeam Agents jobs (since this is the forum you've made the post to) or you would like to export job config for any Veeam B&R job?

Thank you!

[caolanoc]

I would like to export the actual Veeam agent jobs primarily but also the config if possible?

Apologies for the late response - any help would be hugely appreciated

[Dima P.]

Hi Caolan.

1. Standalone Veeam Agent for Windows does not have PowerSell integration but it supports configuration import/export via command line utility.
2. Agent managed by backup server does not have PowerShell cmdlets for job management but we plan to add them in upcoming Update 4. Currently you can only manage protection groups via PowerShell.

[caolanoc]

Hi - Thanks for this. I have tried running the command as detailed in that article however CMD will not recognise "Veeam.Agent.Configurator.exe - export" as an internal/external command - Is there something im missing maybe?

[Dima P.]

Caolan,

Is that a licensed agent or your are running it in Free mode? Thanks.

[caolanoc]

it is a licensed agent, Im running that command as admin through cmd.exe on the server the back up jobs are configured on.

[Dima P.]

That's strange. Let me quickly check with RnD team, stay tuned.

[caolanoc]

Any idea why Veeam.Agent.Configurator.exe is not being recognised as a command in this scenario?

[Vitaliy S.]

Can you show the command line you're using? What directory do you specify for Veeam.Agent.Configurator.exe?

[Dima P.]

Caolan,

Can confirm that even if agent is managed by B&R server export should work without any issues. If you can confirm that command line is executed as it's stated in the User Guide and you still see this issue, please raise a support case and share the case ID in this thread. Thanks!