Copy-VBRJob

[soehl]

Any chance to get that fixed soon?!

thx.

[ThomasMc]

The export or copy? The copy cmdlet is a legacy cmdlet so would have to be something new like Copy-ViBackup or something.


p.s have you tried this: Copy a bunch of Backup Job to New Jobs

[soehl]

I meant the export-vbrjob cmdlet.

thanks for the link.

[Wintel]

will the export-vbrjob cmdlet be fixed anytime soon?

Is the format of the .xml output documented anywhere?

rgds

[Sethbartlett]

The problem is that the Import/Export Job cmdlets both reference the same issue. Even if you could get the syntax down to do the imports, you would get the same reflection error you get with Export.

[jpierre]

When will this be resolved? We'd like to backup our configuration and ExportJob doesn't work with the same errors listed above.

[claudiog64]

The problem is that the Import/Export Job cmdlets both reference the same issue. Even if you could get the syntax down to do the imports, you would get the same reflection error you get with Export.

Any news on this bug ? Any chance to have it fixed ?

Thanks
Claudio

[Gostev]

Not a bug. Apparently, Import/Export job cmdlet are simply stubs for the future functionality that is not yet implemented in the product. There is simply no code behind these cmdlets, as there is no configuration backup/restore functionality in the product itself yet. They were included in the reference accidentally, and will be removed with the next update until this functionality is actually implemented (chances are, in the next release). Thanks!

[RJI]

Did this make 6.1 or will it be implemented in a release after that?

[Sethbartlett]

Copy-VBRJob works in 6.1 now.

[RJI]

My question was regarding the export-vbrjobs and import-vbrjobs stubs. Has the equivilent funcionality made it into 6.1 as the commandlets now report that they are obsolete?