Upgrade Database and Re-Deploy Acumatica

Question

Hi AllI’m looking for some advise on the best path to take to update a database an re-deploy an Acumatica instance.My scenario is as follows:The deployment is PCS, it was initially started with a database, let’s call it ‘DB’ and Acumatica 2019R1. There was then a change in company and it was decided to create a new database, let’s call it ‘DB2’ and we deployed Acumatica 21R2.‘DB’ and ‘DB2’ are hosted on the same server, let’s call it ‘SRV1’‘DB2’ and the Acumatica instance were then upgraded over the years and we are now at 25R1 and ‘DB’ was left as is with 2019R1 for archival data. The 2019R1 instance can still be accessed as the site files still exist. Currently, 2019R1 is not able to be supported on any modern browser so the database - ‘DB’ will need to be upgraded.I can spin up a server to accomodate the upgrade of ‘DB’ from 2019R1 to 25R1 as I have the various Acumatica installers required.Where I would need clarification is when I have to restore ‘DB’ to ‘SRV1’ and deploy a new instance of 25R1 using ‘DB’, what would happen to the site files that are currently there? Would there be any conflict or would it be overwritten and the instance will be successfully deployed? Also, what about IIS, would there need to be any consideration there? Would there be anything else that I have to consider as well?Please let me know if I need to calrify anything.ThanksAmit

darylbowman · Answer

I can spin up a server to accomodate the upgrade of ‘DB’ from 2019R1 to 25R1 as I have the various Acumatica installers required.

I don’t really see any reason to move ‘DB’ before upgrading, but that’s your call. You could either uninstall the 25 R1 Acumatica ERP Configuration and then install each required version from 19 → 25 or extract the installers, which can then exist side-by-side.

Where I would need clarification is when I have to restore ‘DB’ to ‘SRV1’ and deploy a new instance of 25R1 using ‘DB’, what would happen to the site files that are currently there?

I think this largely depends upon what you name the new instance (and therefore installation folder). If the name is different, the existing files should be left intact. Similarly, if you would rename the existing installation, you could reuse the old name if you’re attached to it 😀

Also, what about IIS, would there need to be any consideration there? Would there be anything else that I have to consider as well?

Personally, I would recommend creating a new IIS AppPool in the process (separate from your production instance). Overlapping can create unhandy situations.

It shouldn’t be a big deal honestly. Just make sure you have backups in case of unforeseen oopsies.

Sign up

Social Login

Login to the community

Social Login

Scanning file for viruses.

This file cannot be downloaded