Upgrading from V2.1 to Labs 3 Final

Document created by resplin Employee on Jun 6, 2015
Version 1Show Document
  • View in full screen mode

Obsolete Pages{{Obsolete}}

The official documentation is at: http://docs.alfresco.com



Draft PagesUpgrading3.02.1
WORK IN PROGRESS

This page is a temporary location for merging the two instruction sets for V2.1 to Labs 3 and the General Upgrade Process.


V2.1 to Labs 3


To upgrade your existing Alfresco installation to Labs 3 Final, you need to backup your existing data, download and install Labs 3 Final, and then restore the exiting data.

These instructions describe the upgrade procedure for using a MySQL database.


  1. Shutdown your existing Alfresco installation, including any visualization servers and file system receivers. Alfresco Runtimes may be left running and upgraded at a later time using this same process.
  2. Back up your database.
  3. Back up the alf_data directory. (see Backup and Restore)
  4. Back up any configuration overrides from the <extension> directory.
    Note do not copy the files; copy only the override settings so that you will not overwrite the new extension files in Labs 3 Final.
  5. Uninstall the existing Alfresco installation.
  6. Clean out the Tomcat temporary files (temp and work). Use the script in the bin directory (clean_tomcat).
  7. Download and install Labs 3 Final.
  8. Restore your database.
  9. Copy the alf_data directory to Labs 3 Final.
  10. Copy your configuration overrides into the relevant new override files in the <extension> directory.




The Upgrade Process


The recommended process for upgrading involves a new installation of the Alfresco binaries and configuration and an in-place upgrade of a copy of the repository. In-place upgrade of the Alfresco binaries and configuration is not recommended.

Note: If you have any customizations (AMPs, patches, and so on) in your existing Alfresco installation, recompile all Java code against the new version of Alfresco and regression test against the new version of Alfresco (this is best done prior to the upgrade itself, since it could be a lengthy exercise).

The upgrade process involves:


  1. Shutdown your existing Alfresco instance, including any virtualization servers and file system receivers. Alfresco Runtimes may be left running and upgraded at a later time using this same process.
  2. Perform a cold backup of your repository, as described at Backup and Restore.
  3. Back up any configuration overrides from the <extension> directory.
    Note do not copy the files; copy only the override settings so that you will not overwrite the new extension files in the new version.
  4. Install the new version of Alfresco (including any virtualization servers) in a different directory to the existing installation.
  5. Validate the new installation to check that it is working correctly. For example:
    1. Configure the new installation with a new repository (not the existing one).
    2. Start Alfresco and validate that the system works correctly.
    3. Shutdown Alfresco and (optionally) wipe the new repository.
  6. Restore the backup taken in step 3 into the new repository (not the existing one), as described at Restore procedure.
  7. Manually apply your configuration overrides into the relevant new override files in the <extension> directory.
  8. Reinstall all customizations into the new Alfresco instance.
  9. Start Alfresco, monitoring the startup log messages for information on the status of the upgrade.
  10. Validate that the system works correctly.
  11. If you are satisfied that the upgrade is successful, remove the old Alfresco installation and repository. This may be done at a later time, once the new installation has been thoroughly validated.

Attachments

    Outcomes