Still an issue with this one and I noticed that you might be doing an update soon any chance this could be looked at and included, it now seems to not copy the objects in as per the original problem but now it creates "Legacy" jobs(even when the original isn't a legacy job)
I also uncovered a Replica Prefix in the shell, I'm assuming that this is for future as it doesn't work just yet but that feature would be awesome as well
Fully reproduced/confirmed, Copy-VBRJob has been broke since 5
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
Just installed EM to try it out, the clone feature is pretty cool with the rename functionality, if we could get that for the cmdlet then I would be very happy
ThomasMc wrote:Just installed EM to try it out, the clone feature is pretty cool with the rename functionality, if we could get that for the cmdlet then I would be very happy
Would Export-VBRJob & Import-VBRJob work for you? I have used these in the past to clone jobs with all their settings.
That'll keep the settings, but not the objects. If I recall it can also act-up with VSS (though I haven't tested it in a while). Handy workaround though, and it does do the export into fairly simple XML.
*EDIT*: Actually, looks like there's some issue(s) with Export-VBRJob in v6, so be warned. Seth and I are tossing that up internally.
Export-VBRJob has a -IncludeObjects parameter. What issues have you seen with the VSS? With my tests the encrypted credentials were exported and I was able to use them against other VMs without modification. I ask because I may be using this functionality in an upcoming project.
With 6, we are noticing some problems with Export-VBRJob that me and Justin are taking a look at. After lunch we'll post our finds
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
Export-VBRJob : There was an error reflecting type 'System.Collections.Generic.List`1[Veeam.Backup.PowerShell.Model.ExternalJob]'.
Something painfully wrong with Veeam.Backup.PowerShell.Model.ExternalJob currently during any reflection, tried re-writing the code by hand through powershell, no dice.
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
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.
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
Sethbartlett wrote: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 ?
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!
Skype: Sethbartlett88 - Make sure to label who you are and why you want to add me
Twitter: @sethbartlett
If my post was helpful, please like it. Sometimes twitter is quicker to hit me up if you need me.
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?
any chance this could be looked at and included, it now seems to not copy the objects in as per the original problem but now it creates "Legacy" jobs(even when the original isn't a legacy job)
