800xA redundant system restore
Today I tried to restore a redundant system backup. I take a full system backup of system. Deleted system runnung on both server.
Then restored 800xA full backup on primary server(AS+CS+RAS). Restoration went well. System is working fine in primary server.
Then through configuration wizard I tried to connect the redundant server(run cfg on secondary server...connect node). Node got connected.But the services related to the redundant server all are in error state except aspect directory and FSD service; those two are in service.
I don't know what went wrong. I can see both servers in RNRP. Can ping with IP and name.Already tried restart of secondary no luck. I couldn't restart primary since the process is running.
Already tried to disconnect the secondary from primary server configuration wizard.Then tried to connect again as redundant server to primary. No luck
I doub't suppose while taking the full backup secondary server was acting as the active server. Does that make any problems like I am having.
Is there any way to fix this issue. Any valuable suggestion appreciable.
Re run the system user settings in secondary aspect server via configuration wizard.
Run the afwsysinfo -csd in secondary and primary and see the database differences.
Is opc da/ae configured in opc panel for Mconnect services.
cause for services going error might be user account problem check affinity for the services
For the error services try uncheck and check the services.
Suspend and select restart and run for each error services.
Check the affinity it gets deleted on node removal from pri aspect server
Share the snap of service str
You followed the correct procedure as far as I can tell.
Did you remove the OperateITData folder from the secondary server before trying to connect it again to the restored primary? Removing the data folder and removing the system registry key from registry will have the node forgetting it was a server (installed software will remain of course).
Aspect Directory and FSD are the essential services of an aspect server (there are more of course, but those to mentioned are "databases" that *need* to be restored).
What error code(s) are the failing services taking?
What is output in the System Event List as they start & fail?
Sometimes I've seen the Node field of a service provider go corrupt, so try "resetting" one of the failed services by changing to a different node, then back to the desired (secondary aspect server) and finally hit Apply button.
If possible, engage regional support. Maybe we can have some expertise taking a look at the problem if remote connection is possible.