Hi Kosk,
Thanks for the information. I wasn't confident it would update like in the other thread since Tags are handled a bit differently than folders in VMware (tags are a separate entity entirely that VMs sit under, so kind of makes sense it wouldn't update).
> Re-add them using Add-VBRViJobObject and then remove the old ones with Remove-VBRViJobObject,
Use this.
As for the custom application aware processing and exclusion entries, these will NOT be reset/overwritten, but they will also not be cleared, meaning the existing entries will remain in the job, but they won't do anything but take up space. You can remove the old exclusions/entries with Remove-VBRViJobObject. For VSS, Set-VBRJobObjectVssOptions is necessary; observe the note on that page, as the cmdlet will _overwrite_ the existing Set-VBRJobObjectVSSOptions, so you can simplify this a bit by just creating an array of the new VBRJobObjectVSSOptions and then overwrite the existing ones with this cmdlet.
Thanks for the information. I wasn't confident it would update like in the other thread since Tags are handled a bit differently than folders in VMware (tags are a separate entity entirely that VMs sit under, so kind of makes sense it wouldn't update).
> Re-add them using Add-VBRViJobObject and then remove the old ones with Remove-VBRViJobObject,
Use this.
As for the custom application aware processing and exclusion entries, these will NOT be reset/overwritten, but they will also not be cleared, meaning the existing entries will remain in the job, but they won't do anything but take up space. You can remove the old exclusions/entries with Remove-VBRViJobObject. For VSS, Set-VBRJobObjectVssOptions is necessary; observe the note on that page, as the cmdlet will _overwrite_ the existing Set-VBRJobObjectVSSOptions, so you can simplify this a bit by just creating an array of the new VBRJobObjectVSSOptions and then overwrite the existing ones with this cmdlet.
Statistics: Posted by david.domask — Jul 14, 2025 7:48 am
