From TIE 3.0.0 onward, database maintenance tasks are managed via an ePolicy Orchestrator (ePO) Server task TIE Server Data Management and TIE Server Database Maintenance.
This article has been updated to reflect that no manual action is needed for these tasks.
Backup and restore the TIE Server database
Each TIE Server instance holds a full copy of the database, so any secondary TIE Servers run as a backup of the TIE Server Primary instance.
We recommend that you use a Storage Area Network (SAN) to store each TIE Server virtual appliance disk. With the SAN, you can also have periodic snapshots against unexpected failure events at the database level.
To manually backup data, run the following command on your 3.0.x TIE Server Primary instance as root:
/opt/McAfee/tieserver/postgresql/bin/pg_dump -d tie -U mfetie > /data/tie-backup.sql
To manually backup data, run the following command on your 4.0.x TIE Server Primary instance as root:
/opt/Trellix/tieserver/postgresql/bin/pg_dump -d tie -U mfetie > /data/tie-backup.sql
To later manually restore data from the backup, perform the following steps on your 3.0.x TIE Server Primary instance as root:
WARNING: The following steps delete
all database data. The previous
/opt/McAfee/tieserver/postgresql/bin/pg_dump -d tie -U mfetie > /data/tie-backup.sql command must run without errors before you continue with these steps.
# service tieserver stop
# service tieserver pg_start
# /opt/McAfee/tieserver/postgresql/bin/psql -Umfetie tie
tie# update pg_database set datallowconn = true where datname like 'template%';
tie# \q
# vi /data/tieserver_pg/pg_hba.conf
Replace "local tie mfetie" with "local all mfetie".
# service tieserver pg_stop
# service tieserver pg_start
# /opt/McAfee/tieserver/postgresql/bin/psql -Umfetie template0
template0# DROP DATABASE IF EXISTS tie;
template0# CREATE DATABASE tie
WITH OWNER mfetie
ENCODING 'UTF8'
TEMPLATE template0
LC_COLLATE = 'en_US.UTF-8'
LC_CTYPE = 'en_US.UTF-8'
CONNECTION LIMIT = 1024;
template0# \q
# /opt/McAfee/tieserver/postgresql/bin/psql -U mfetie tie < /data/tie-backup.sql
# /opt/McAfee/tieserver/postgresql/bin/psql -Umfetie tie
tie# update pg_database set datallowconn = false where datname like 'template%';
tie# \q
# vi /data/tieserver_pg/pg_hba.conf
Replace "local all mfetie" with "local tie mfetie".
# service tieserver pg_stop
# service tieserver start
To later manually restore data from the backup, perform the following steps on your 4.0.x TIE Server Primary instance as root:
WARNING: The following steps delete
all database data. The previous
/opt/Trellix/tieserver/postgresql/bin/pg_dump -d tie -U mfetie > /data/tie-backup.sql command must run without errors before you continue with these steps.
# service tieserver stop
# service tieserver pg_start
# /opt/Trellix/tieserver/postgresql/bin/psql -Umfetie tie
tie# update pg_database set datallowconn = true where datname like 'template%';
tie# \q
# vi /data/tieserver_pg/pg_hba.conf
Replace "local tie mfetie" with "local all mfetie".
# service tieserver pg_stop
# service tieserver pg_start
# /opt/Trellix/tieserver/postgresql/bin/psql -Umfetie template0
template0# DROP DATABASE IF EXISTS tie;
template0# CREATE DATABASE tie
WITH OWNER mfetie
ENCODING 'UTF8'
TEMPLATE template0
LC_COLLATE = 'en_US.UTF-8'
LC_CTYPE = 'en_US.UTF-8'
CONNECTION LIMIT = 1024;
template0# \q
# /opt/Trellix/tieserver/postgresql/bin/psql -U mfetie tie < /data/tie-backup.sql
# /opt/Trellix/tieserver/postgresql/bin/psql -Umfetie tie
tie# update pg_database set datallowconn = false where datname like 'template%';
tie# \q
# vi /data/tieserver_pg/pg_hba.conf
Replace "local all mfetie" with "local tie mfetie".
# service tieserver pg_stop
If you have one or more secondary TIE Servers, restart the database connection. Run the following command on each secondary server:
# replication-monitoring.sh –c reset
For more information about available options, see the
PostgreSQL documentation.
Access control to the TIE Server database
By default, read-only external database access is restricted between TIE Server instances. The reason is that the secondary TIE Server reads from the TIE Server primary instance. You can use the reconfig-pghba tool to allow other hosts to connect to the database:
# sudo /usr/sbin/reconfig-pghba
