Upgrade on new hardware: Create a single cluster for both Database and Datamart

The ability to run separate PostgreSQL instances for TeamForge database and datamart on the same server is being deprecated in TeamForge 17.11. If you have the TeamForge database and datamart on separate PostgreSQL instances on the same server and if you are upgrading on a new hardware, follow these instructions to create a dump of both the database and datamart and load them into one PostgreSQL instance on the same server.

During TeamForge installation, the REPORTS_DATABASE_PORT token should no longer be used to assign a separate port for datamart on the server that also runs the TeamForge database. The following warning shows up if you use the REPORTS_DATABASE_PORT token with a custom port number (other than the default value, which is 5432).
Using two separate Postgres clusters for database and datamart on the same machine is deprecated. Consider deploying the two clusters on two machines or using a single cluster for both databases.
If you have TeamForge database and datamart running on separate PostgreSQL instances on the same server:
- New hardware upgrade: If you are upgrading on a new hardware, you must create a dump of both the database and datamart and load them into the same PostgreSQL instance.
- Same hardware upgrade: If you are upgrading on the same hardware, you may still choose to use the REPORTS_DATABASE_PORT and have the database and datamart running on two separate PostgreSQL instances. However, support for REPORTS_DATABASE_PORT token may end in one of the future TeamForge releases, when you may have to dump and load both the database and datamart on the same PostgreSQL instance anyway.

It is assumed that you are upgrading from TeamForge 17.8 (with database and datamart on separate ports) to TeamForge 17.11 (or later) on a new hardware.

Do this on the existing TeamForge Application Server where the database and datamart runs on two separate ports.
1. Make a dump file of your site database.
  - su - postgres
  - /usr/bin/pg_dumpall > /var/lib/pgsql/9.x/backups/teamforge_data_backup.dmp
  - exit
  - mkdir /tmp/backup_dir
  - cp /var/lib/pgsql/9.x/backups/teamforge_data_backup.dmp /tmp/backup_dir/
2. Make a dump of your datamart.
  - /usr/bin/pg_dumpall -p <reports_database_port> > /var/lib/pgsql/9.x/backups/teamforge_reporting_data_backup.dmp
Do this on the new TeamForge server.
1. Recreate the runtime environment (do not provision TeamForge directly).
  - teamforge deploy
2. Reload the site database.
  - su - postgres
  - /usr/bin/psql < /tmp/backup_dir/teamforge_data_backup.dmp
  - exit
3. Reload the datamart.
  - su - postgres -c "/usr/bin/psql -p <reports_database_port> < /tmp/backup_dir/teamforge_reporting_data_backup.dmp"
Provision services.
- teamforge provision
Note:
TeamForge 17.4 (and later) installer expects the system locale to be LANG=en_US.UTF-8. TeamForge "provision" command fails otherwise.