If PE’s databases become sluggish or begins taking up too much disk space, there are several maintenance tasks that can improve their performance.
PE uses PostgreSQL as the backend for its databases.
We recommend that you use PostgreSQL’s native tools to perform database exports and imports. At a minimum, we recommend nightly backups to a remote system, or as dictated by your company policy.
The PE PostgreSQL database includes the following databases:
|pe-activity||Activity data from the Classifier, including who, what and when|
|pe-classifier||Classification data, all Node Group information|
|pe-puppetdb||PuppetDB’s data, including exported resources, catalogs, facts, and reports|
|pe-rbac||RBAC data, including users, permissions, and AD/LDAP info|
|pe-orchestrator||orchestrator data, including details about job runs (users, nodes, and run results)|
In some cases you may find your databases are slow or need general performance enhancements. The PostgreSQL
vacuum command can help optimize your databases.
To vacuum a particular database, run the following command:
su - pe-postgres -s /bin/bash -c "vacuumdb -z --verbose <DATABASE NAME>"
You should perform regular backups of individual Puppet Enterprise databases. There are fundamentally two ways to backup your PE databases. The preferred approach is to backup each database individually for the following reasons:
pg_dump command dumps an individual databases to a compressed binary file on disk, which you can restore at any time.
NOTE: All back up and restore commands must be run as the pe-postgres user.
To backup each PE PostgreSQL database individually, run the following commands:
sudo -u pe-postgres /opt/puppetlabs/server/bin/pg_dump -Fc pe-activity -f /tmp/pe-activity_`date +%m_%d_%y_%H_%M`.bin sudo -u pe-postgres /opt/puppetlabs/server/bin/pg_dump -Fc pe-rbac -f /tmp/pe-rbac_`date +%m_%d_%y_%H_%M`.bin sudo -u pe-postgres /opt/puppetlabs/server/bin/pg_dump -Fc pe-classifier -f /tmp/pe-classifier_`date +%m_%d_%y_%H_%M`.bin sudo -u pe-postgres /opt/puppetlabs/server/bin/pg_dump -Fc pe-puppetdb -f /tmp/pe-puppetdb_`date +%m_%d_%y_%H_%M`.bin sudo -u pe-postgres /opt/puppetlabs/server/bin/pg_dump -Fc pe-orchestrator -f /tmp/pe-orchestrator_`date +%m_%d_%y_%H_%M`.bin
This command creates a binary dump of the database. The
pe-postgres user needs write access to the output destination.
To restore an individual PE PostgreSQL database backup, run the following command:
sudo -u pe-postgres /opt/puppetlabs/server/apps/postgresql/bin/pg_restore -Cc -d template1 <BACKUP_FILE>.bin
This command will connect to the
template1 database and then drop the database indicated in
If you omit the
pg_restore will output the SQL commands needed to restore a database to the console, but it will not perform the actual restoration.
After restoring that database, you fix access privileges for that database with Puppet. Run the following command:
puppet enterprise configure
pg_dumpall command dumps the complete set of PE databases to a SQL file on disk. After you’ve created a back up of your PE databases, you can restore them at any time.
Before beginning, review the following information:
All back up and restore commands must be run as the pe-postgres user.
It isn’t necessary to stop any PE services to perform these steps.
To back up the entire PE PostgreSQL database, run the following command:
sudo -u pe-postgres /opt/puppetlabs/server/apps/postgresql/bin/pg_dumpall -c -f <BACKUP_FILE>.sql
Note: The name and location of your
.sql can be changed as needed.
To begin the restore, stop all PE services except for
pe-postgresql. Run the following commands:
puppet resource service puppet ensure=stopped puppet resource service pe-puppetserver ensure=stopped puppet resource service pe-puppetdb ensure=stopped puppet resource service pe-console-services ensure=stopped puppet resource service pe-orchestration-services ensure=stopped puppet resource service pe-nginx ensure=stopped
When restoring the ‘pe-postgres’ user needs read access to the SQL file created when the database was backed up. Run the following command to perform the restore:
sudo -u pe-postgres /opt/puppetlabs/server/apps/postgresql/bin/psql < <BACKUP_FILE>.sql
This command will import the complete PE PostgreSQL database backup you created in the procedure above.
Start all PE services. Run the following commands:
puppet resource service puppet ensure=running puppet resource service pe-puppetserver ensure=running puppet resource service pe-puppetdb ensure=running puppet resource service pe-console-services ensure=running puppet resource service pe-orchestration-services ensure=running puppet resource service pe-nginx ensure=running
The console uses a database user account to access its PostgreSQL database. If this user’s password is compromised, or if it needs to be changed periodically, do the following:
puppet resource service pe-puppetdb ensure=stopped.
psqlclient, you can do this with
ALTER USER console PASSWORD '<new password>';.
/etc/puppetlabs/puppetdb/conf.d/database.inion the PuppetDB server and change the
password:line under common (or under production, depending on your configuration) to contain the new password.
pe-puppetdbservice on the console server with with
puppet resource service pe-puppetdb ensure=running.
PuppetDB parameters are set in the
jetty.ini file, which is contained in the pe-puppetdb module. Jetty.ini is managed by PE, so if you change any PuppetDB parameters directly in the file, those changes will be overwritten on the next Puppet run.
Instead, you should use the console to make changes to the parameters of the
pe-puppetdb class. For example, the PuppetDB performance dashboard requires the
listen_address parameter to be set to “0.0.0.0”. So, in the console, you would edit the
pe_puppetdb class so that the value of the
listen_address parameter is set to “0.0.0.0”.
Warning: This procedure will enable insecure access to the PuppetDB instance on your server.
If you are unfamiliar with editing class parameters in the console, refer to editing class parameters on nodes.