| > Show on single page > Show on multiple pages |
The Squore installation package can be used to upgrade an existing Squore installation from Squore 2012-A-SP6.
When an installation is upgraded, the following happens:
The new version of Squore Server overwrites the previous one in the same installation directory.
The database is upgraded.
The data files are migrated.
The old basic configuration is kept: location of data, cluster and tmp folders as well as ports.
LDAP settings, licence server sharing, SSL configuration are discarded and will need to be configured again. The old <SQUORE_HOME>/config.xml and <SQUORE_HOME>/server/standalone/configuration/standalone.xml are backed up for your convenience next to the new ones (i.e. <SQUORE_HOME>/config.xml.bkp and <SQUORE_HOME>/server/standalone/configuration/standalone.xml.bkp).
Folders inside the installation directory are deleted during an upgrade, including the default tmp, data, cluster and backup folders. Before you attempt to upgrade Squore, run a full backup of your data (and move it outside <SQUORE_HOME>) using the provided backup scripts described in the section called “Backing-Up the Squore Data”
On Linux, if you used the -x and/or -s parameters in your initial installation or if you manually edited the value of postgreSQL's shared_buffer or java Xmx parameters after installing, you must pass -x and/or -s on the command line for the upgrade as well, as they are not read from the previous installation. For more details on install options, refer to install(1).
The file postgresql.conf in your database cluster is patched during the upgrade process. If you have modified it manually, create a backup copy before upgrading and verify that the migrated file still contains your modifications.
Before upgrading from a pre-16.0 version, ensure that you have as much free space on your disk as the size of your current database, as reported on Administration > Projects.
If you are a local PostgreSQL cluster as your database, ensure that the server and the database are shut down before continuing. In all other scenarios (an Oracle database or a remote PostgreSQL cluster not managed by Squore) ensure that Squore Server is stopped and that the database is accessible and accepting connections.
No progress information is displayed on screen during the database upgrade phase, which may take a while to complete.
Follow these steps to upgrade your Windows installation.
Run the Windows installer.
Click the Next button to get to the Licence Agreement screen.
Click the Next button to get to the Destination Folder screen.
Browse for the folder containing the old installation and click the Next button.
On the Upgrade Choice screen, select Override to delete the existing installation and start from scratch (all your data is lost) or Upgrade to upgrade your existing installation to the new version, then click the Next button.
The Upgrade Choice screen
Clicking the the Next button button on this screen checks that the version of java configured to run Squore Server is supported. If you are running an unsupported version, you will see the following error message:
The unsupported Java version message
Edit your Squore Server installation to point to a supported version of Java, as explained in the section called “Changing the path to the Java Installation”, and click the Next button again the installer to continue the upgrade.
Wait while the installer retrieves the settings to apply to the upgrade and displays them on the Summary screen, and click Install.
The Summary screen
Wait for the upgrade process to complete and close the wizard by clicking on Finish.
The Installation Complete screen
Folders inside the installation directory are deleted during an upgrade, including the default tmp, data, cluster and backup folders. Before you attempt to upgrade Squore, run a full backup of your data (and move it outside <SQUORE_HOME>) using the provided backup scripts described in the section called “Backing-Up the Squore Data”
On Linux, if you used the -x and/or -s parameters in your initial installation or if you manually edited the value of postgreSQL's shared_buffer or java Xmx parameters after installing, you must pass -x and/or -s on the command line for the upgrade as well, as they are not read from the previous installation. For more details on install options, refer to install(1).
The file postgresql.conf in your database cluster is patched during the upgrade process. If you have modified it manually, create a backup copy before upgrading and verify that the migrated file still contains your modifications.
Before upgrading from a pre-16.0 version, ensure that you have as much free space on your disk as the size of your current database, as reported on Administration > Projects.
If you are a local PostgreSQL cluster as your database, ensure that the server and the database are shut down before continuing. In all other scenarios (an Oracle database or a remote PostgreSQL cluster not managed by Squore) ensure that Squore Server is stopped and that the database is accessible and accepting connections.
No progress information is displayed on screen during the database upgrade phase, which may take a while to complete.
Follow these steps to upgrade your Linux installation.
Download the Linux installation package.
Extract the archive by running the command:
cd
/tmp
/usr/bin/tar
xjf
squore-server-linux-*.tar.bz2
<SQUORE_HOME>/server/bin/standalone.confRun the upgrade by executing:
cd
/tmp/squore-server/bin
./install
-U
/path/to/old/installation
[options...]
<SQUORE_HOME>/server/bin/standalone.conf if necessary to reapply your custom configurations.Ensure that the minimum permissions described in the section called “Installing the Master Squore Server” still apply.
When upgrading NFS-Mounted installations, follow this procedure:
Stop all Squore Server Instances
Stop the Master Squore Server
Upgrade the Master Squore Server installation following the standard upgrade procedure described in the section called “On Linux”.
Verify that the permissions defined in the section called “Installing the Master Squore Server” still apply on the upgraded Master Squore Server.
Upgrade the data on each Squore Server Instance with these steps:
# ./bin/pgctl start # ./bin/sqadm upgrade-db --from 15A.9
In the example above, the from parameter takes a version number formatted as
major_version.minor_version. Use
15.9 when upgrading from Squore 15-A-SP9 or
16.1.2 when upgrading from Squore 16.1.2.
Start each Squore Server Instance after the upgrade completes