Title: Sql Backup And Restore To New Windows Box
Description: I think the title says it...
lawsonneophyte - November 7, 2007 09:41 PM (GMT)
It's probably a newbie question, but I've got a 7.33 database running on ancient equipment. I've been able to move the date to a new sql database, running on a new machine, and of course running a new install of the old lawson. Unfortunately I can't see the data on the new box. I'm running windows 2000 server, and am stuck. Did I miss a step? I'd like to migrate the whole darn thing for a test disaster recovery.... help?
Part Time Ruler of the universe,
Jerry
area51 - November 7, 2007 11:03 PM (GMT)
I haven't worked with Lawson on Windows. How did you move both data and lawson?
Keith_G_Thompson - November 7, 2007 11:54 PM (GMT)
Let us know the approx steps you did and we'll try to see what you missed. The 1st thoughts that come to mind are the MICROSOFT file. Did you configure that to point to the new database? And, is ladb setup to point to the correct tablespaces?
lawsonneophyte - November 10, 2007 01:06 AM (GMT)
Approximate steps were....
1. Install SQL 7
2. Install lawson and tools
3. Export sql database from orginal server
4. Import sql database into new server
5. Copy Registry settings from old box
6. attempt to access data
7. Pull remaining hairs from head
7. Join Lawsontalk and post....
area51 - November 12, 2007 07:24 PM (GMT)
I'm not too familiar with the Windows side of Lawson, but I believe that they are fairly standardized and this probably not the best way to do it.
Do you have access to Lawon's Knowledge base at all? If you don't I can post some steps and you will have to read up on the manuals.
Keith_G_Thompson - November 12, 2007 07:50 PM (GMT)
I don't think I've ever copied the restistries between boxes. I'm not saying it'll hurt, but I'm not sure that was necessary.
I would point you over to the %LAWDIR%/prod/MICOROSFT file (if not "prod", whatever your product line is). That must have the appropriate entries to tell the product line where your data is. Also check within dbdef to make sure your database spaces are defined.
You might also try the command "verifymsf2000". This will tell you if Lawson can even find defined tables within the DB or if it's not connecting at all. If it's connecting, but empty, perhaps you are just pointing to the wrong DB?
lawsonneophyte - November 14, 2007 05:08 PM (GMT)
Hey all,
Thanks so far for the quick notes... I've gotten quite a bit further than before, and I've even seen parts of my database! Not the parts I need, but hey! You can't have everything. Thanks Keith for pointing out the way, it's definitely helping. I just found my pdf manual as well, which will also assist. I'll try again on my own, but would like to reserve the right to recall my witnesses... :-)