disaster recovery scenario

Scenario:
Production location – domain controller, Lawson apps/web server, lawson sql server
Backup location – domain controller(online active), restored VMWare vranger full server OS backup of Lawson apps/web server, different sql server with restored backup of lawson Gen, LOGAN, & PROD db’s.

Abbeville goes down for whatever weather type event. Birmingham domain controller becomes the domain controller the restored Lawson apps/web server should be configured to talk to for LDAP/AD authentication.

After restoring the sql db’s to the Bham sql server and fixing orphan sql accounts/schemas and changing sql db config files on restored Lawson apps/web server to point to new sql server I can see GEN and LOGAN connections in SQL activity monitor. I do not see any for PROD, which doesn’t make sense but possibly not a direct concern right now. I CAN login to LID on the restored Lawson apps server and inquire to PROD and get into LAUA. BUT BUT BUT I cannot even get to the Portal login, cannot connect to Lawson Security GUI, nor perform some commands within ssoconfig. I was able to change the LDAP server Lawson uses to get LDAP data from AD from gswabb802( no longer available in ABB in this scenario) to the backup DC in Bham, but this didn’t solve the issue.

All signs and errors within server event logs and Lawson logs point to some problem with LDAP, AD, the backup DC, sso, websphere and portal and the other Lawson utils not working or erroring out.