Corero Resource 32000 Migration

[MYK-IT]

Just fact-finding options at present... so any feedback / advice would be appreciated.

 

An existing Server which has Corero Resource 32000 installed on, is due to be decommissioned, and replaced with virtualised Server. After speaking with Civica, they advised that they don't offer documentation, help etc. in relation to migration of their software, although some customers have done it themselves (and it works), or it doesn't work (and have had to pay for consultancy to resolve) or 3rd option is to pay them to do the entire migration.

 

I know that at the least I could do a P2V conversion, but that wouldn't achieve/gain anything as I want to be upgrading OS/SQL to latest versions etc.

 

So, has anyone else migrated their own installation of Corero Resource 32000?

 

Thanks.

[Zammo]

What OS is the server currently on?

[MYK-IT]

What OS is the server currently on?

 

Hi @Zammo

 

Currently W2008 R2 with SQL 2012, want to upgrade to W2016 with SQL 2016.

 

I'm sure it's a case of moving folders, and exporting/importing SQL Database with some ODBC jiggery-pokery! But I'm no SQL expert!

[MYK-IT]

Well, a quick update for you...

 

Considering we completed a full SIMS / SOLUS / DISCOVER migration from an old Server 2008 R2 / SQL 2012 to Server 2016 / SQL 2016 last week, with assistance from our LEA's SIMS Support Team in a few hours, including updating to Summer 2018 release, SQL 2016 and workstations too you'd 'expect' a migration of a Corero (Civica) database to be relatively easier?.... right?

 

...Well, going by the quotation I've received from Civica for them doing this, I must be so wrong.... at over £1300+VAT! for a member of their 'team' to 'remote access' our current server, back it up, install on new server (we have to setup Server OS and all SQL installation / configuration beforehand), reinstate all linked applications and 'fully' test... Oh, and a 4-week lead time from receipt of order too!

 

So, take this into account if you are using Corero Resource 3200 / Civica, planning on migrating to a new server, or indeed incorporate and factor this in into your Disaster Recovery plans for your (Civica) finance server!

[yac2016]

Damn...I need to do this asap. Just found out we have it running on a 2008 server VM. Existing support have not done anything about it.

 

£1300 is abit steep really!

[eddyc]

We managed to do it ourselves from 2008 (non R2) to 2012 r2 a couple of summers ago.

 

Off of the top of my head I’m sure we just took a backup of the database and restored it

 

Copied the folder and shared it with the same permissions then repointed the ODBC on the clients to the new box.

 

It was a couple of years ago now though so not 100% certain but fairly sure that’s all we did

[yac2016]

Don't think there is any harm trying it on another VM.

[BigG]

Sorry to dig up an old thread, did anyone manage to get this done ok without having to pay for it to be done? We would be going from a 2008R2/SQL 2012 VM to a new Server 2016/SQL2016 VM. I have the new VM setup with SQL installed. Any tips / pointers if you have done this please?

[supportman]

We decided it wasn't worth it and got a new Finance system that works in the cloud. Options we looked at included HCSS and sage 200. Both of which were lightyears ahead of RES32000

[NetworkNinja]

We also decided to change our Finance Package. We ended up going with XERO which is much cheaper than resource was.

[kingoranks]

Anyone done Resource 32000 Migration from 2008 recently? We also got this steep £1300

[TomFreeman]

We're looking at this at the moment, upgraded our server from 2008 r2 to 2012r2 last week, left it on the 2008 instance which luckily still runs on 2012 r2 and was going to speak to them to move it over to the 2012 sql. Looks like we might look at new finance system as well then.

[MYK-IT]

I should had updated this thread.

 

Over summer, I built / configured a new Hyper-V Server (Server 2019) with SQL Server 2017 (and MS SQL Server Manager Studio 18.3) in readiness to attempt a migration of our Corero R32000 system... with success!

 

Basically created a 'back up' copy of the SQL database, then 'restored' it on the new server. Then had to do some minor configuration changes in relation to the 'Connection IQ' settings, as well as a a couple of settings within R32000 (as they were referring to old server name / shares etc.). I kept the compatibility level at 'SQL Server 2008 (100)'. (Original server was on Server 2008, later in-placed upgraded to 2008 R2).

 

Finally, changed the ODBC settings on the client computers accordingly.

 

Using a virtualised server etc, will give you flexibility to test, change (create checkpoints etc.) as you go along whilst testing and checking that it migrated across and works on the new server etc.

Edited November 12, 2019 by MYK-IT