Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Infor / Lawson Platforms
S3 Systems Administration
disaster recovery scenario
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jessica
Past 24 Hours:
2
Prev. 24 Hours:
0
Overall:
5164
People Online:
Visitors:
245
Members:
0
Total:
245
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
S3 Systems Administration
disaster recovery scenario
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
Chris Anderson
New Member
Posts: 4
10/26/2010 5:00 PM
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.
Tags:
portal domain controller sso ldap
Jimmy Chiu
Veteran Member
Posts: 641
10/26/2010 6:39 PM
I am assuming your Abbeville&Birmingham domain controllers are on the same domain:
%LAWDIR%\prodline\MICROSFT files need to be edited to point the different SQL server. If you are using alias with your SQL configuration, that need to be edited also.
do this for the following files:
%LAWDIR%\gen\microsoft
%LAWDIR%\logan\microsoft
%LAWDIR%\prod\microsoft
Tags:
portal domain controller sso ldap
Chris Anderson
New Member
Posts: 4
10/26/2010 6:52 PM
correct, are on the same domain, but the bham is disconnected to test this real life scenario. it is a lone dc in bham as if the abbeville dc's are no longer there. only the bham dc, lawson apps/web server and sql server are connected to a local subnet in bham all talking/pinging etc each other by name/ip. ive already changed the microsoft files to point to the bham sql server.
Tags:
portal domain controller sso ldap
ichiben
Advanced Member
Posts: 21
1/12/2011 8:09 PM
Has anyone tried snapshot backups with AIX and Lawson? What's the best way to be able to recover to a point in time?
Tags:
portal domain controller sso ldap
You are not authorized to post a reply.