What do you mean?
Like if you have 4 ARS in server group start server 1, waiting it's started, then server 2, then server 3, then server 4?
Well less stress on database for example and it avoids the servers exchanging the failover operations at startup?
Its very important as primary server needs to be up first as it will take the responsibilities for Admin operations, as per the raniking mentioned in server group ranking form,
Also to sync in all servers, its important to start the servers one by one as per the ranking.
Otherwise as its server group and it self its very complicate it can cause other severe issues.
Like your server 1 is admin server, but if you modify any workfow it will say admin operations is disabled on this server.
1 of 1 people found this helpful
It's better indeed, though if you start another server in server group and if failover is configured so that this server takes over if "rank 1" isn't available, it'll assume the "admin" operations until its collegue is up.
You'll see in the logs that for a while the first server will be the admin one, then when the other is up, he'll "loose" the admin and the other one will get it.
So in the end, technically you don't have to follow the order defined in ranking form.
Is there perhaps formal BMC documentation that states the sequence in which each ARSystem Server and their services, in a Server Group, must be started and stopped?