Add the ability to configure a dedicated pgBackRest server #379
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit introduces significant improvements to our backup and recovery capabilities with pgBackRest. The main feature is the ability to configure and manage the dedicated pgBackRest servers. Previously, backup configuration was limited to the database servers only. The primary advantages of this change are: Separation of concerns: It enables administrators to maintain dedicated backup servers, which can increase the robustness and reliability of the backup and recovery process. Flexibility: The backup servers can be configured differently than the database servers, allowing for more tailored backup and recovery scenarios. Backup cron jobs: In addition to these improvements, this commit introduces the ability to manage pgBackRest cron jobs via the "pgbackrest_cron_jobs" variable. Backup Jobs will be automatically configured. Additionally: Docker containers (for Molecule) are configured for ssh interaction. This allows we to test roles for configuring ssh keys.
Updated the pgBackRest configuration template to enable configuration of a single dedicated pgBackRest server for multiple Postgres clusters.
Added support for the include-path option, allowing inclusion of additional configuration files.
Introduced a global section to configure global settings, iterating over the pgbackrest_server_conf.global list for values.
Utilized the include-path directive to include configuration files for stanzas from the specified path ({{ pgbackrest_conf_file | dirname }}/conf.d).
These updates provide the ability to configure a dedicated pgBackRest server for multiple Postgres clusters, enhancing flexibility in managing backup and restore operations across multiple environments.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces significant improvements to our backup and recovery capabilities with pgBackRest.
The main feature is the ability to configure and manage the dedicated pgBackRest servers (
pgbackrest_server_confvariable). Previously, backup configuration was limited to the database servers only.In addition to these improvements, add pgBackRest cron jobs via the "
pgbackrest_cron_jobs" variable. Backup Jobs will be automatically configured. By default, the cron jobs is created on the database server. If 'pgbackrest_repo_host' is defined, the cron jobs will be created on the dedicated pgBackRest server.Updated the pgBackRest configuration template to enable configuration of a single dedicated pgBackRest server for multiple Postgres clusters.