Thanks for the clarification regarding Set-VBRJobObjectVssOptions and how it overwrites existing entries.
Regarding VSS Options, we’re using a dedicated LogShipping server for each VSSObject, although all sites point to the same LogShipping server. What I’ve noticed when working with VSSOptions objects in PowerShell is that the LogShipping server isn’t explicitly specified in the object. There’s a property to check if AutomaticProxy is enabled, but no clear identifier (like a ProxyID) to determine which proxy is actually selected.
This makes implementation tricky, especially since applying new settings via Set-VBRJobObjectVssOptions will override everything to default unless all parameters are explicitly defined.
Is there any known method or workaround to retrieve the ProxyID or identify the LogShipping server used in the current VSS settings?
Regarding VSS Options, we’re using a dedicated LogShipping server for each VSSObject, although all sites point to the same LogShipping server. What I’ve noticed when working with VSSOptions objects in PowerShell is that the LogShipping server isn’t explicitly specified in the object. There’s a property to check if AutomaticProxy is enabled, but no clear identifier (like a ProxyID) to determine which proxy is actually selected.
This makes implementation tricky, especially since applying new settings via Set-VBRJobObjectVssOptions will override everything to default unless all parameters are explicitly defined.
Is there any known method or workaround to retrieve the ProxyID or identify the LogShipping server used in the current VSS settings?
Statistics: Posted by Kosk — Jul 15, 2025 9:17 am
