Transitioning to New Production Server

     We migrated to our new servers a while ago.  Basically we treated it the same as loading our test environment.  The new server was joined to the domain and setup with a temporary name and IP address.  We did all of the software config and then an initial migration so we could test the server.  Once it was deemed ready for production we picked a downtime window to prevent any untracked changes to the live DB.  Then we re-migrated the database.  Once the live database was in place we removed the old live server from the domain and shut it down, assigned the IP address from the old server to the new one and renamed the new server to the same name as the old one.  Then we brought everything back online.  This way if there are any problems you can immediately pull the new server offline and bring the old one back up.  It also does not require any client changes.  Once your downtime window is done the clients just see the new server the same as the old one.  I realize this is a simplified summary.  If you have any questions feel free to contact me.
     One word of caution though.  Make sure you pull the network cable out of your old server once you have the transition complete.  Bringing it back online with a duplicate name and IP address would be BAD to say the least.

-Rich

Rich Tepper
McCarter Theatre

     We migrated to our new servers a while ago.  Basically we treated it the same as loading our test environment.  The new server was joined to the domain and setup with a temporary name and IP address.  We did all of the software config and then an initial migration so we could test the server.  Once it was deemed ready for production we picked a downtime window to prevent any untracked changes to the live DB.  Then we re-migrated the database.  Once the live database was in place we removed the old live server from the domain and shut it down, assigned the IP address from the old server to the new one and renamed the new server to the same name as the old one.  Then we brought everything back online.  This way if there are any problems you can immediately pull the new server offline and bring the old one back up.  It also does not require any client changes.  Once your downtime window is done the clients just see the new server the same as the old one.  I realize this is a simplified summary.  If you have any questions feel free to contact me.
     One word of caution though.  Make sure you pull the network cable out of your old server once you have the transition complete.  Bringing it back online with a duplicate name and IP address would be BAD to say the least.

-Rich

Rich Tepper
McCarter Theatre

Also, I had to do this recently and, an additional detail when renaming a SQL server, if it applies to you: http://msdn.microsoft.com/en-us/library/ms143799.aspx

     We migrated to our new servers a while ago.  Basically we treated it the same as loading our test environment.  The new server was joined to the domain and setup with a temporary name and IP address.  We did all of the software config and then an initial migration so we could test the server.  Once it was deemed ready for production we picked a downtime window to prevent any untracked changes to the live DB.  Then we re-migrated the database.  Once the live database was in place we removed the old live server from the domain and shut it down, assigned the IP address from the old server to the new one and renamed the new server to the same name as the old one.  Then we brought everything back online.  This way if there are any problems you can immediately pull the new server offline and bring the old one back up.  It also does not require any client changes.  Once your downtime window is done the clients just see the new server the same as the old one.  I realize this is a simplified summary.  If you have any questions feel free to contact me.
     One word of caution though.  Make sure you pull the network cable out of your old server once you have the transition complete.  Bringing it back online with a duplicate name and IP address would be BAD to say the least.

-Rich

Rich Tepper
McCarter Theatre

I have a new Tessitura Production server ready to go.

I am wondering what methods folks have used for the easiest way to

switch over to the new server. I have read the Tess Database and Client installation doc and other documents including moving a database.

Anyone who has recently transitioned to a brand new db server, I'd be interested to hear your migration plan.

Thanks,

T.Jesperson

Laguna Playhouse

I believe we had planned for around four hours but it took less than that.  You can get a pretty good idea of how long it will take when you do the initial DB load onto the new server.  Just add another 20-30 minutes for the renaming and domain changes.

-Rich