Scott Goley on 02 May 2019 03:19:36
Is there any possibility of adding a parameter to the Set-OnPremisesDataGateway module that can change the "Anchor Gateway" for that cluster?
Example:
Set-OnPremisesDataGateway -ClusterObjectId **example-clusterid** -GatewayObjectId **example-gatewayid** -MemberStatus Enabled -isAnchorGateway True
Granted, this might be an extremely rare use case but it would prevent me from having to go through the lengthy process of removing all gateways, remove cluster, and then reinstall all gateways following installation of new cluster on new anchor machine.
Thanks.
- Comments (4)
RE: Change Set-OnPremisesDataGateway in Powershell to set parameters
A must have.My understanding is that all connection strings default to the primary node. So the 'path' to the data source is relative to the primary node. When one changes the primary node (through the convoluted process outlined by Scott) the new primary node must have the same 'visibility' as the replaced node [Same domain or access to folder shares or suchlike].
RE: Change Set-OnPremisesDataGateway in Powershell to set parameters
This is an extremely important feature to have in gateway and will help in reducing the work of reinstalling-reconfiguring everything.
RE: Change Set-OnPremisesDataGateway in Powershell to set parameters
The issue with not having the ability to move the anchor without tearing down the cluster and rebuilding, is having to reconfigure all of the data sources and in turn, reconfiguring all of the reports to use those data sources.
RE: Change Set-OnPremisesDataGateway in Powershell to set parameters
Having ability to change primary node in a cluster will simplify maintenance procedures or rotating out nodes of a cluster for maintenance/upgrades over time.