If the Archive Shuttle Item databases have grown to over 30GB in size (for each database) the upgrade can take several hours.
It is possible to upgrade the Item databases manually before starting to upgrade the binaries. In order to do this follow the steps below:
- Stop all AS services on all machines (core & modules)
- Stop all Application pools related to Archive Shuttle in IIS (ArchiveShuttleUIAppPool, ArchiveShuttleWSAppPool)
- Check if everything is stopped (in IIS if the App pools are stopped and in SCM if all services related to Archive Shuttle are stopped, also open ArchiveShuttle.WebServicesLog file and check if new entries are added and open Archive Shuttle UI, it shouldn’t work)
- Check the current Item database Schema Version in SchemaVersion table in each Item database (ask support for the version)
- Update the Item Database(s) depends on the actual version as there were changes in the upgrade process between 8.4 and 9.0:
- upgrading to 8.4 from any below version, run CoreLinkDB_Update1 SQL update script on each item database this will upgrade your item database to version 8.4
- upgrading to 9.0 or above from version below 9.0 (like 8.4), you need to run CoreLinkDB_Update1 SQL update script on each item database first which upgrades your item database to version 8.4 and then, each ItemUpdate9_n.sql where “9_n” matches the target schema version.
Example1: Going to upgrade from 8.2 to 9.1. Firstly run CoreLinkDB_Update1 SQL update script on each item database and then ItemUpdate9_0.sql and ItemUpdate9_1.sql scripts
- upgrading to 9.0 or above from version higher than 8.4 (like 9.0), you need to run each ItemUpdate9_n.sql where “9_n” matches the target schema version
Example2: Going to upgrade from 9.0 to 9.6. Run sequentially scripts ItemUpdate9_1.sql, ItemUpdate9_2.sql, ItemUpdate9_3.sql, ItemUpdate9_4.sql, ItemUpdate9_5.sql, ItemUpdate9_6.sql
NOTE: for better performance, please run the update SQL script for 1 to 2 item databases at once, if the size of Item databases is more than 50GB we recommended to run the update script only on 1 database at the time
- Check the Item database Schema Version in SchemaVersion table in each Item database, the version should be higher than before the upgrade (if the version is higher, you can continue, if not you will wait and check it again later)
- Run AS Core installation msi file
- Run AS Module installation msi file
The installation should start all the App pools and services, if not start them manually.
Follow up with post-installation checks in the Archive Shuttle Upgrade Process article.