Skip to content

Disaster Recovery Management #22

Open

Description

@ChakshuGautam
  • Define DR Management strategy for this.
  • Implementation.

References:

  1. https://github.com/EnterpriseDB/barman
  2. https://github.com/pgbackrest/pgbackrest

Activity

  1. PiyushRaj927 commented on May 29, 2023

    @PiyushRaj927
    Collaborator

    Hi @ChakshuGautam, could you please provide more information on this issue? Thank you!

  2. nitishmalang commented on May 29, 2023

    @nitishmalang

    Hi @ChakshuGautam, could you please provide more information on this issue? Thank you!

    yes @ChakshuGautam please

  3. PiyushRaj927 commented on Jun 5, 2023

    @PiyushRaj927
    Collaborator

    @ChakshuGautam, I would like your input on this suggestion. My suggestion is to use pgBarman (https://pgbarman.org/) in a separate container alongside our PostgreSQL installation. It enables Point-in-Time Recovery (PITR) for efficient data restoration during emergencies. Do you think this solution meets our requirements?

    cc: @jayanth-kumar-morem @singhalkarun

  4. ChakshuGautam commented on Jun 5, 2023

    @ChakshuGautam
    CollaboratorAuthor

    @PiyushRaj927 This is exactly what I was looking for. We have used Barman before and it works as expected. The wal logs are a bit too much in size so look for compression.

  5. jayanth-kumar-morem commented on Jun 19, 2023

    @jayanth-kumar-morem
    Collaborator

    Hey @ChakshuGautam ,

    PGSQL has built-in support for compressing WAL.
    We can control this using the wal_compression configuration parameter in the postgresql.conf file. When this parameter is set to on, PostgreSQL will try to compress WAL data when a full page image is written to the WAL. This can significantly reduce the amount of WAL data.

  6. jayanth-kumar-morem commented on Jun 19, 2023

    @jayanth-kumar-morem
    Collaborator

    @PiyushRaj927 Have you started working on this? If not I can take this one up.

  7. PiyushRaj927 commented on Jun 19, 2023

    @PiyushRaj927
    Collaborator

    No @jayanth-kumar-morem, I have not started working on the issue.

  8. jayanth-kumar-morem commented on Jun 19, 2023

    @jayanth-kumar-morem
    Collaborator

    Alright, I'll get on this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions