[sims] SIMS rebuild - What order?!

[eddyc]

Hi all,

 

I am after a bit of advice. Our current SIMS server is shot, a daily reboot is required - Lots of hangs, maybe a weekly BSOD plus various other anomalies. It's virtual and running Server 2008 R2 on SQL Server 2012, with SOLUS 2.24, Discover is around but not used.

 

The master plan is to build a new virtual server, migrate SIMS to Server 2012 R2, on SQL 2014 and also move to SOLUS 3.8.

 

How would you go about this? I'm fine with a standard SIMS server rebuild, however the SOLUS migration is kind of throwing me.

 

Do I need to obtain a SIMS installation ISO and install SIMS on the new server before downloading and installing SOLUS 3.8? I assume yes, to set up DOCSTORAGE, etc.

 

Any pointers would be appreciated. I know what I need to do, I just want some reassurance \ confirmation of the order you would go about this in.

 

So far, I've build a clean Windows Server 2012 R2 Server and patched it up to date. I am about to install SQL 2014.

 

Thanks in advance :-) Ed

[Cache]

What I did for our SIMS/SOLUS migration from 2008 to 2012 (both server and SQL) earlier this year was copy the SIMS share across, download the latest installable ISO and install that and the update ISO's into the copied SIMS share.

 

Run the standard SIMS server installer so it's all configured and ready to go, use the migration tool to export the SIMS db, connect it to the new server using the migration tool, same process for discover and then reconfigure SOLUS3 so that all the targets are updated to point to the new server.

 

Left it for a month and then migrated SOLUS3 across once I was certain that SIMS was working correctly on the new server.

 

So pretty much the way you've planned to do it.

[eddyc]

That's a better idea to be honest. Do the SIMS migration first and once that has been up and running throughout January I will then do the migration to SOLUS 3.8

 

Thanks!