PRIMARY ASPECT SERVER / CONNECTIVITY SERVER 5.0 SP2 REVC
We have a customer who he has installed 5.0 Sp2 Revc Harmony Connect.
Configuration is two redundant Aspect/ Connectivity Servers Windows 2003 Server R2 SP2 , 2 Operator Workplace one Domain Controller . Nowadays they are using Rack Server Proliant DL 380 G5 for ASCS1 ( primary ) and ASCS2 ( secondary)
One of them ASCS1 ( Primary aspect connectitivity server) has showed some problems and it is necessary to buy a server like this or similar as backup and if it fails we would install a new one . Because of Windows 2003 Server R2 SP2 standard edition for new servers nowadays they do not have drivers for Windows 2003 server because it is old. It has been difficult to get a refurbished Proliant DL 380 G5 . Now we have gotten Proliant DL 380 G7 Server ( newer than G5 ) with similar hardware but it is not the same hardware ( Hd bigger but SAS , RAID1 Controller another model , more than 4 Gb of Ram I know 4 Gb is enough )
According to ABB information Proliant DL 380 G7 Server is also allowed to be used in version 5.0 according to HW Party.
In this case if every is fine after installation we would have ASCS1 Proliant DL 380 G7 and ASCS2 Proliant DL 380 G5.
Here we would have two ways to do that :
1 - Before doing the procedure We could do Acronis Backup from ASCS1 , then we would install the OS Windows 2003 server R2 SP2 in newer ASCS1 (Proliant DL 380 G7 ) , drivers etc . Then we could do an acronis restore on this new server using acronis backup from G5 machine , it will have some different drivers because difference in some hardware then we could update them.
Then we could restart the ASCS1 with newer hardware ( Proliant DL 380 G7) , the Proliant DL 380 G7 ASCS1 would synchronize with ASCS2 and everything would be fine and customer would have a system more reliable until they can upgrade to version 6.0.
2 - If we do a fresh installation , I am not sure if they did an automation installation I am investigating about that .
If we choose this option we would have to install everything the components , Post installations , extension etc , doing that ASCS2 is up and running. I am not sure about if they have installed some roll ups I should verify it before doing anything , now I am investigating it.
Our concern is about when we do this installation procedures sometimes the node should be restarted before finishing everything but if it is connected to the system which it is up and running could it have some problems? ,
-How can avoid it ?
- How can we force from ASCS2 to send the information to ASCS1 after finishing all the steps and restart the node , from aspect directory ASCS2 object > Service provider > Run Command , which options , after ASCS1 has booted up do we need any specific Run command from aspect directory ASCS1 object > Service provider > Run Command
I understand that it is old system and it should be upgraded we have suggested it to the customer, but customer has had some administrative issues and it has not been possible
We appreciate your ideas and clarifications regarding to the procedures explained above
Thanks for your support
The Aspect servers will sync automatically once you have restored the node in question. Mostly you would not have to do much. However you may wish to ensure all AS services are forced to AS 2 beforehand (using Services) so as not to disrupt anything. A good guide is the 800xA 5.1 upgrade guide (as it tells you all needed before the upgrade and services).
Practice makes perfect I would suggest to create a similar system offline and and try how that works. That is build the offline system in VM's, remove AS1, create a new VM and restore using Acronis. This is much the same exercise as you are contemplating. Acronis does have universal restore which can handle different driver sets. Check with Acronis...