SIMS Server Migration

[mtillbrook]

Hi

Appologies if this has already been covered but i couldn't find it!

 

Does anyone have experience of migrating SIMS from one server to another? I am supposed to be doing it next week for the first time and I could really do with some help!

I need to know a). the order in which i need to do everything and b), a list of everything I need to do!

 

If anyone has done this before and written a procedure it would be very useful!!

 

Thanks in advance!

[Sarconia]

I'll be doing this at the end of this month in a few weeks so I might take some screenshots and write an actual instruction booklet on how to do it (as it's not something many of us do often so a nice instruction booklet would be handy I think).

 

Before you attempt the transfer, make sure that you have ample backups of the SIMS and FMS databases and the DOCSTORAGE folder.

 

Here is a quick guide:

 

On the old server: Detatch SIMS/FMS databases using DBattach, stop the SQL Service (services.msc), copy the relevant MDF/LDF's from the DATA directory where SQL is installed. Copy the DOCSTORAGE folder too.

 

On the new server: Copy the detatched MDF/LDF's across as well as the Setups folder (from the old server / Capita FTP site) or install from a CD. Dont forget about copying the DOCSTORAGE folder across too.

 

Install full SQL if the school has a license.

 

Run SIMSinst.exe and select all of the options for the Server (used as a server, setup as the document management server as well), this should then install all of the components which you need to run SIMS.net (if I remember correctly, it also installs SQL Express). Just make a note of the instance name and the SA password when you're prompted to enter one during the installation.

 

Run DBattach, select the SIMS/FMS MDF/LDF files which were detached from the old server and attach them to your new SQL instance.

 

Amend the connect.ini so that it reflects your new servername, instance name and database name. When SIMS.net runs, it will ask you to show it where your connect.ini resides so you'll need to think about how you're going to set this up. I usually put the connect.ini on a mapped network drive, usually S:\SIMS or S:\MIS and then have all of the connect.ini's on the workstations redirect to them.

 

I also wouldn't reformat/dismantle/do anything to the old server until I'd got everything working correctly on the new one, SIMS or otherwise.

[Banjo]

I'll be doing this at the end of this month in a few weeks so I might take some screenshots and write an actual instruction booklet on how to do it (as it's not something many of us do often so a nice instruction booklet would be handy I think).

 

Before you attempt the transfer, make sure that you have ample backups of the SIMS and FMS databases and the DOCSTORAGE folder.

 

Here is a quick guide:

 

On the old server: Detatch SIMS/FMS databases using DBattach, stop the SQL Service (services.msc), copy the relevant MDF/LDF's from the DATA directory where SQL is installed. Copy the DOCSTORAGE folder too.

 

On the new server: Copy the detatched MDF/LDF's across as well as the Setups folder (from the old server / Capita FTP site) or install from a CD. Dont forget about copying the DOCSTORAGE folder across too.

 

Install full SQL if the school has a license.

 

Run SIMSinst.exe and select all of the options for the Server (used as a server, setup as the document management server as well), this should then install all of the components which you need to run SIMS.net (if I remember correctly, it also installs SQL Express). Just make a note of the instance name and the SA password when you're prompted to enter one during the installation.

 

Run DBattach, select the SIMS/FMS MDF/LDF files which were detached from the old server and attach them to your new SQL instance.

 

Amend the connect.ini so that it reflects your new servername, instance name and database name. When SIMS.net runs, it will ask you to show it where your connect.ini resides so you'll need to think about how you're going to set this up. I usually put the connect.ini on a mapped network drive, usually S:\SIMS or S:\MIS and then have all of the connect.ini's on the workstations redirect to them.

 

I also wouldn't reformat/dismantle/do anything to the old server until I'd got everything working correctly on the new one, SIMS or otherwise.

 

I would do it in a different order.

Map a drive from the new sever to the old servers.

Copy the Sims folder and DOCstorage across.

Run Simsinst and install what you need workstation + docserver and possibly SQL express if you are going that route.

 

Backup Sims from System Manager on the old server, and restore backups onto the new servers Sims database.

Copy the Docstorage into the correct location > server name - instance, etc

Ready to Go.

 

Then test. When your happy do another backup restore (Friday night possibly) and create a logon script the remaps the workstations to the address of the new server rather than the old.

You could even change the original connect.ini on the old server to redirect to the new server as a temporary catchall.

[Stuart_C]

THere was a document on supportnet that details what to do in a "Capita Approved Style" ™

 

I assume it's still there though I've not looked in a while.

[timbo343]

I too wouldnt mind having a copy of a migration of SIMS server. I have been part of it before but it was 2 - 3 years ago and i have forgotten how to do it. I know you have to export the database and re-import it into the new SQL.

[Hecate]

If you're talking about moving SIMS to another server not the migration to SQL 2008, I do it by setting up SQL installing SIMS with a blank database then restoring a backup of the data using dbattach. I've done it a happily couple of times. One advantage of this is that you don't touch the original server or the data on it so if anything goes wrong you can carry on using it while you work out what happened then restore an up to date backup when you're happy. You can also do a trial run because until you remap the S drive (or it's equivalent) no one can see it. You also only need to take SIMS offline while you do the backup and restore.

[vikpaw]

All of the above look good to me, i've done this quite often, as i frequently make Virtual Machines to test updates out on, and basically it uses the same procedures. Except i change the server names, and this needs fiddling to get the doc storage sent to the right place, and correct folder name. Apart from that all goes well.

Now i tend to clone a working machine as it saves time, but i'll be doing some fresh tests when we start the migration testing to go do sql 2008.

There are some other threads on here regarding this topic, and there were some old instructions flying around from GREED too.

It would be good to get an up to date document produced Sarconia, maybe even put it in the wiki, or how do you do it forum...

[rh91uk]

I put together some really botched notes for our SQL 2005-2008 SIMS migration when we did it from our old sql2005 to a new sql2008 server. See attatched.

 

Our LEA has not tested FMS on SQL 2008 yet so I can't go ahead and migrate that - so it is still running on the old box.

 

I am not the master at writing guides but hope you get the jist, missed out a few things I suppose but this was just for our internal benefit.

SIMS SQL 2008 Migration to a new server edugeek.pdf

Edited May 12, 2010 by rh91uk

[Sarconia]

It would be good to get an up to date document produced Sarconia, maybe even put it in the wiki, or how do you do it forum...

 

I've had a look in my calendar and I'll be transferring the database across on June 1st, hopefully I'll have enough time to take ample screenshots and make notes. Then I'll write a step by step document which hopefully will include everything. (I do like writing documents... don't ask me why! I just do).

[splattthecat]

The following is a link to the Somerset guidance on moving SIMS to a new server (SQL2005 version only at the moment) Some elements are specific to Somerset schools setups, but this may help with the basics of the process.

 

[url=http://www.six.somerset.gov.uk/sixv3/content_view.asp?did=18604][/url]http://www.six.somerset.gov.uk/sixv3/content_view.asp?did=18604

[bossman]

Has anyone moved from a SQL2005 Enterprise instance to a SQL2008 Enterprise instance with DBs and Document server installations on a Windows 2003R2 Enterprise server?

 

I am looking at this at the moment as plans are to get SQL up to 2008, then build VM 2008R2 enterprise server, re-install SQL2008 instance and migrate DBs and install Document server. Would anyone see any problems with this?

[timbo343]

Has anyone moved SIMS onto Server 2008 R2 yet?

 

Tim

[RobFuller]

Not fully supported but it does work! Just make sure your using SQL2008 not R2.

[bossman]

@jinnantonnix:

 

Cheers do you have this documented at all and prepared to share

[bossman]

@RobFuller:

 

Do you mean Server 2008 with SQL2008 instance or Server 2008R2 with SQL2008 instance both 64bit I presume?

[mrbios]

I'm planning on migrating everything from Server 2003R2 + SQL Server 2005 to Server 2008R2 + SQL Server 2008R2, from a couple of posts back am i barking up the wrong tree here? i assumed everything was supported except for 64bit clients as of the sprint release?

 

I've got the new SQL 2008R2 server running on windows 2008R2 and im running a couple of databases off it already, just waiting till the June half term to move everything sims related across, but need to know if it's fully compatible!

[vikpaw]

SQL 2k8 R2 is not supported by Capita, and no plans have been revealed yet. I think a couple of people are using it though.

 

EDIT: ref - http://www.edugeek.net/forums/mis-systems/55108-sql-2008-a.html#post501581

Edited May 18, 2010 by vikpaw
citation

[mtillbrook]

Hi Guys

Thank you to all who responded. I ran into only one problem during the installation. I put the 64 bit edition of Windows on the server but then found unfortunatly, that I did not have the 64 bit installer for SQl express 2005 -only the 32 bit edition. I have tried just downloading it from Microsoft but of course that just installs a stupid default instance name and there doesn't seem to be a way to change it.

Does anyone have a copy of the Capita SQL server express 2005 64 bit installer that they could lend me?????? I could really do with this so any help would be very gratefully appriciated!

 

Cheers!