Thursday
Hello,
A major migration of a customer's ACS Enterprise is planned from version 7.2.2 to 26.1.0.
Its 7.2.2 is currently under kubernetes (deployed via Helm chart).
I want to make sure I haven't forgotten anything in the migration stages on my plan.
In the critical points that I noted:
So my migration plan would be:
PROD 7.2
↓
Clone infra
↓
ACS 7.4.2 + PG13 + Solr (no need ATS I think ?)
↓
DB Migration
↓
Validation
↓
Dump PostgreSQL 13
↓
New environnement
↓
ACS 26.1 + PG16 + ASE + ATS
↓
DB Restore
↓
Full reindex
↓
Full Validation
with, in this plan, the contentstore in RO for the migration jump in 7.4.2.
Does this seem coherent to you?
are there any elements that I would not have taken into account?
Thank you for your feedback.
Sincerely.
Friday
Why not do the database migration in your current version already? Apart from the typical copy&paste recommendation of going to "the last patch of the current major release", in my experience you typically do not need to do that since there have been no relevant schema changes or patches since 7.1.
According to the documentation, you can also pre-build your Elastic index on your existing version since it is 7.2+. If you want to have content indexed, you would need either ATS or just Transform Core AIO for this, and the SFS component.
Friday
Thank you for your feedback.
To be sure I understand correctly, my "jump" by a 7.4 is therefore not necessary?
I can, with the 7.2 database, migrate it from a postgreSQL 13 to a postgreSQL 16 and point my alfresco to 26.1 on this basis directly?
Explore our Alfresco products with the links below. Use labels to filter content by product module.