September 5, 2006 at 7:42 am
Can anyone help with this?
I have a SQL7 Database Server, which is going to be decommissioned, In it’s place will be a Win2k3 Server, I intend running SQLSVR2000 SP4 on this box.
Will creating backups for all databases including all of the system databases and restoring them directly onto a SQL2000 server work? If not suggestions greatly appreciated.
This is a 24 x7x365 server I think I will have about 6 hours to move 70+ databases, Although only half a dozen or so are needed 24x7.
The server will take on the old server name when it goes into production, but that's okay because I'm familiar with the process for doing that part.
September 5, 2006 at 7:56 am
That should work. I'd look to move the full backups the day before, or before your window and let transaction logs catch you up from there.
So if you plan on starting at midnight, start restoring full backups at 5pm the day before. Then at midnight start restoring your transaction logs for the critical databases since that full backup. Once you get those done, I'd do the name switch on both servers (rename old, shut old down, rename new, reboot, if it's ok, bring old back up). then work on the remaining databases.
September 5, 2006 at 8:14 am
Steve,
Thanks for that, I'd planned to back-up the non critical databases as they close for business, backup the system and 24X7 db's and restore them in the downtime I have, then sytematically restore the non-critical ones prioritised according to the SLA's we have in place. Some of these db's come down at 20:00 and are not required until 10:00 the next day!
September 5, 2006 at 8:35 am
That would be fine for the user databases but you seem to want to do that for your system databases as well i.e. master and msdb. I would say you can't just backup and restore SQL7 system databases onto SQL2000 so if you need to copy across logins, dts packages, jobs etc. you'll need to look at other methods.
cheers
September 5, 2006 at 10:26 am
System databases can't be upgraded by backup/restore.
1. Do a inplace upgrade from SQL 7 to SQL 2000 and then backup/restore will work as system database will be upgraded to 8.0 build. But this will be time comsuming
2. As beath said, use script to copy logins/dts/jobs etc. They are a knowledge base article on http://support.microsoft.com
HTH
-B
September 8, 2006 at 9:52 am
Its probably best you script everything out before hand and then just run them during your maintaince window. I did a similar migration a couple of years ago with a number of DB's - I had the db's already restored and in a standby mode - had a script that applied the last transactions and brought the Db's online and another script that restored jobs - fixed logins etc.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply