Yes, currently you have to use object properties if you want to see the current configuration.
For configuring a job sometimes you also have to use object properties. We don't have parameters for every single available job option. There are far too many of them.
Which Options would you like to see as a cmdlet parameter for a potential GET and SET command?
@ratkinsonuk, just a note, that cmdlet is just for backup copies from External Repositories (like Veeam Backup for AWS/Azure/GCP repositories added to Veeam server as an external repository); I'm not sure why it's like that, but that's likely why it's like that and you have to do it the other way for non-ExternalRepository based Backup Copies.
David Domask | Product Management: Principal Analyst
Mildur wrote: ↑Dec 13, 2022 7:56 am
Which Options would you like to see as a cmdlet parameter for a potential GET and SET command?
Morning Fabian, and thanks for responding.
Really, I think a cmdlet to match the GFS enhancements introduced to B&R primary backups in v11. It would also be good if they covered the GFS settings in copy jobs too, as both sets of options are now very similar.
I'll continue using the object-level settings for now though.
david.domask wrote: ↑Dec 13, 2022 9:50 am
@ratkinsonuk, just a note, that cmdlet is just for backup copies from External Repositories (like Veeam Backup for AWS/Azure/GCP repositories added to Veeam server as an external repository); I'm not sure why it's like that, but that's likely why it's like that and you have to do it the other way for non-ExternalRepository based Backup Copies.
Thanks for pointing that out David. I certainly hadn't spotted that, and made the assumption that is was for B&R primary backups given the cmdlet name. It also explains why it doesn't seem to match the B&R GUI settings.