Upgrade Community 3.4.c to 3.4.d

[gdowrey]

I have an existing vm with 3.4.c with an iscsi target as the repository.  I've built a new vm with 3.4.d.  Can I just point the new vm at the existing repository on the iscsi target after shutting down the vm with the previous version?

[gnyce]

So, normal upgrade procedure is install new version, start it, shut it down, delete alf_data and put previous version alf_data there, start Alfresco, and it recognizes as an older rev and does the upgrade.  So, I _think_ you could do what you describe, as long as 1) the alf_data ISCSI target is mounted in the same place/structure as the new-version install, and 2) you don't mentioned how you have the mysql db setup… see upgrade procedure for that, but take care of that, think the VM approach should work.

[gdowrey]

I used the quick install procedure on Ubuntu 10.04 server using the bundled mysql database that comes with the installer.

[gnyce]

Likely you will need to start the bundled mysql (separately perhaps) and dump the Alfresco mysql db, save it elsewhere… then after the new install, shutdown Alfresco, start mysql separately again, delete the Alfresco db, create a new one and  restore the backed-up DB.  But test firstly.  Something like this…
- mysqldump -uUSER -pPASSWORD alfresco > /tmp/alfresco-dump.db
- install new, start, then shutdown alfresco and start bundled mysql separately
- mysql -u USER -p
- show databases; drop database alfresco; create database alfresco; edit
- msyql -uUSER -pPASSWORD alfresco < /tmp/alfresco-dump.db
- start alfresco/tomcat and watch the ~/tomcat/log/catalina.out to see it upgrades it ok.

Test this first - I could easily have some of this not-quite-right (just back from holiday)