A Backup and Recovery strategy is more than simply performing backups. A true backup and recovery strategy must be based on both standard recovery model components and business needs. We are well versed in defining and implementing multifaceted recovery models that work.

Once the Backup and Recovery Strategy is defined, agreed upon and implemented then we will execute test recovery 'spot checks' on a regular basis in order to validate that we have recoverable backup components. This allows us to flag corruption or other recovery issues early.

There are numerous methods to performing PostgreSQL upgrades. In some cases data migrations are part of the upgrade, and in all cases we need a rollback strategy. Our staff of Professional PostgreSQL DBA's approach PostgreSQL upgrades in a methodical manner including definition of upgrade strategies, rollback plans and effective implementation of those plans.

PostgreSQL table bloat, MVCC management and transaction ID management must be managed via VACUUM and autovacuum processing. Vacuum processes must be carefully managed so we get maximum system performance while making continual progress per vacuuming the tables in the system on a regular basis. As part of the Admin-Maintenance Service we manage the PostgreSQL vacuum and autovacuum processes on an ongoing basis. We tune the autovacuum processes, tune individual tables, and recommend tables for rebuilds/bloat reduction as needed.

Regular REINDEXing is something that needs to be managed on all PostgreSQL databases. REINDEX removes bloat, corrects missing/incorrect entries, etc. However REINDEX is not free so the process of REINDEXing the cluster / system indexes must be carefully managed. Our staff will manage REINDEX runs in a structured manner while at the same time maintaining a low impact on day to day database operations.

We generate and deliver query reports on a regular basis. We also tune the logging parameters to ensure that the query reports are capturing the level of detail appropriate to tuning the system based on system activity and usage profiles. Clients can leverage the ticketing system to have the CS DBA staff perform query analysis and tuning via the included monthly hours and/or via additional Admin-Pack hours.

PostgreSQL logging is managed continuously. We ensure that the appropriate activity and level of detail are being logged while maintaining maximum system performance. We also manage archiving of the logs, plus archive retention and removal in order to minimize disk space needs while maintaining an appropriate available log history.

Each client is given a login to our ticketing system as part of the service. We use Jira and leverage its features to manage ongoing tasks, client interaction, information & action requests, etc. Our staff will file tickets for the client in cases where we need the client to take action, or where we need approval to expend additional time. Clients can update tickets with comments, direction and approvals. Clients can also create new tickets for issues, needed action from or staff, etc.

The client receives a monthly activity report with details about what we've done for the month including ticket status updates, admin activity, outstanding recommendations and outstanding “waiting on client” issues. The Monthly Activity Report presents a summary monthly snapshot of where we're at overall and presents a high level look at our progress. Additional details can always be found in the audit trails within the individual tickets.

Admin-Packs are recurring monthly blocks of consulting/admin hours from our DBA staff for use by our clients. These hours can be used to implement our recommendations, tune queries, research performance issues, etc. - anything related to the client PostgreSQL database clusters. Admin-Packs work like a cell phone plan; a specific number of hours are available each month, for a fixed cost, additional hours are billed at our standard rate. Packages are increasingly discounted as the number of monthly hours increases.