Skip to end of metadata
Go to start of metadata

Only applicable to the BiZZdesign on-premise solution.

This topic provides some pointers for monitoring and backing up your Team Server.

Monitoring

For monitoring the operation of the Team Server, it is recommended to at least monitor the following:

  • Disk usage for all volumes. Whenever the amount of free disk space drops below 20%, you are strongly recommended to extend the volume. These volumes include:
    • The disk volume where the TeamServerHome folder resides (location where the Team Server is installed).

      Disk usage can be lowered by enabling Team Server log rotation.

    • The disk volume where the Team Server Database resides.

  • Memory and CPU usage for both the server hosting the Team Server and the server hosting the Team Server database.
  • That the Team Server Windows service is running on the server hosting the Team Server, and is accepting connections on the HTTP (or HTTPS) port configured in the Team Server's wrapper.conf file.
  • That the Team Server's database continues to accept connections on its listening port (by default 1433 for SQL Server, 5432 for PostgreSQL).
  • That the Team Server's database Service(s) are running on the database server.

Backups

The most important backup to take with regards to the Team Server is of the Team Server database. You are recommended using your organization's best practices for backing up the database, or at a minimum performing snapshots of the entire database server. Also, it would be beneficial to back up at least the following files in the TeamServerHome folder:

  • conf/wrapper.conf
  • teamserver.config.json
  • Any keytabs, SSL certificates or metadata for single sign-on (SSO) configuration. These will be unique to your environment but will likely exist somewhere in the TeamServerHome folder.