Save a copy of your TeamForge site's data
to a location from where you can quickly retrieve it to your TeamForge
8.0 site.
- If you are upgrading by installing TeamForge
8.0 on new hardware, then
you'll need the backed-up site data to complete the upgrade.
- If you are upgrading your site on the same hardware, then you won't need the backed-up data
but you should create it anyway, as a precaution.
-
Stop the TeamForge application server and the
Apache server, if they are running.
- RHEL/CentOS: /etc/init.d/httpd stop
- SUSE: /etc/init.d/apache2 stop
- /etc/init.d/collabnet stop
-
Back up your site data.
-
Make a dump file of your site database.
(Do this on your database server in case you
have your DB running on a separate server.)
You have to do a PostgreSQL dump because we are upgrading the
PostgreSQL application as part of this upgrade.
Note: These commands are for a PostgreSQL database,
which is the default. If your site uses an Oracle database, follow
the
Oracle backup procedure
instead.
-
su - postgres
-
/usr/bin/pg_dumpall > /var/lib/pgsql/9.2/backups/teamforge_data_backup.dmp
-
exit
-
mkdir /tmp/backup_dir
-
cp /var/lib/pgsql/9.2/backups/teamforge_data_backup.dmp
/tmp/backup_dir/
Note: If your reporting database is running on a separate port, back up
your reporting database too:
- /usr/bin/pg_dumpall -p
<reports_database_port> > /var/lib/pgsql/9.2/backups/teamforge_reporting_data_backup.dmp
-
Make
an archive file with the following data
directories:
| Directory |
Contents |
| /opt/collabnet/teamforge/var |
User-created data, such as artifact
attachments |
| /svnroot |
Subversion source code repositories |
| /sf-svnroot |
Subversion repository for branding data |
| /cvsroot |
CVS source code repositories (not present on all
sites) |
-
cp -Rpf /svnroot /sf-svnroot /cvsroot
/opt/collabnet/teamforge/var /tmp/backup_dir
-
cd /tmp
-
tar czvf 62backup.tgz backup_dir
-
Back up your SSH keys, if any.
-
Back up your SSL certificates and keys, if any.