08-22-2021 12:37 PM
I recently lost servers on Side A.
I am rebuilding Side A of AW-HDS-DDS. As shown in teh screenshot While running WebSetup on Side B to copy settings I noticed in the Administration & Data Server Connectivity that both Primary and Secondary Servers are the same. The Pair Site Name is prod2, which is also different from what I had in Side A. I think in side A the Pair Site name was prod.
I never noticed it before because Config Manager used to work on Side A and Side B without issues.
Not that I am rebuilding Side A I wanted to make things right. My question is.
When I rebuild Side A can use the same Pair Site name prod2 and update the Primary/Secondary servers accordingly?
Will it break anything? Or am I safer to just use different Pair Site Name = prod unique to Side A and fill in Primary/Secondary servers field with Side A server only?
It seems Configuration Manager was in sync before without issues. I wonder if there is any reason to change.
Anyone with experience who may be aware of negative impact?
Thank you.
Solved! Go to Solution.
08-23-2021 02:35 AM
Hi,
Follow the below steps for changing the site name there won’t be any negative impact.
Indicate whether the server being setup is the Primary or Secondary Administration & Data Server at the site, by clicking on the radio button. Next enter the host name or IP address of the Primary and Secondary Administration and Data Server at the site. TheSecondary Administration and DataServer field is mandatory. If there is no secondary Administration and DataServer being deployed at the site, then the same host name asthat of the primary needsto be provided in this field. Each primary and secondary pair must have its own Site Name, and the Site Name must be exactly the same on both Administration & Data Servers for them to be logically viewed as one.
Primary AW
Administration & Data Server Connectivity
*Primary Administration & Data Server: Side-A Hostname
*Secondary Administration & Data Server: Side-A Hostname
*Common Site Name for Primary / Secondary Administration & Data Server : prod1
Secondary AW
Administration & Data Server Connectivity
*Primary Administration & Data Server: Side-B Hostname
*Secondary Administration & Data Server: Side-B Hostname
*Common Site Name for Primary / Secondary Administration & Data Server : prod2
Ram.S
08-23-2021 02:35 AM
Hi,
Follow the below steps for changing the site name there won’t be any negative impact.
Indicate whether the server being setup is the Primary or Secondary Administration & Data Server at the site, by clicking on the radio button. Next enter the host name or IP address of the Primary and Secondary Administration and Data Server at the site. TheSecondary Administration and DataServer field is mandatory. If there is no secondary Administration and DataServer being deployed at the site, then the same host name asthat of the primary needsto be provided in this field. Each primary and secondary pair must have its own Site Name, and the Site Name must be exactly the same on both Administration & Data Servers for them to be logically viewed as one.
Primary AW
Administration & Data Server Connectivity
*Primary Administration & Data Server: Side-A Hostname
*Secondary Administration & Data Server: Side-A Hostname
*Common Site Name for Primary / Secondary Administration & Data Server : prod1
Secondary AW
Administration & Data Server Connectivity
*Primary Administration & Data Server: Side-B Hostname
*Secondary Administration & Data Server: Side-B Hostname
*Common Site Name for Primary / Secondary Administration & Data Server : prod2
Ram.S
08-23-2021 08:44 AM
Thanks @Ramamoorthy Shanmugam that appears to work and both AW Side and Side B are able to update the config successfully
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide