Safe Database Replication from Production to Test Environment in Confluence Data Center

[Angel Fernando Vazquez Ruiz]

Hi Atlassian Community,

I need guidance on replicating our production database to our test (Beta) environment for Confluence Data Center while preserving test-specific configurations.

Current Setup:

• Confluence Data Center
• PostgreSQL database with following schemas:
  • confluence
  • rdsadmin
  • postgres
• Confluence.> public contains 236 tables
• Access to database is available

Main Concern: I want to avoid overwriting critical configuration settings (like base URL) stored in tables such as BANDANA during the migration process.

Questions:

1. Should I exclude specific tables during pg_dump/pg_restore to maintain test environment configurations?
2. Would it be better to only include certain tables in the migration?
3. Should I focus on dumping a specific schema instead of the entire database?

Specifically, I'm concerned about:

• Maintaining test environment-specific configurations
• Properly handling the BANDANA table which contains crucial configuration
• Determining the correct scope for pg_dump (full database vs specific schema vs selected tables)

Any recommendations on the safest approach to achieve this would be greatly appreciated.

Technical details:

• Using pg_dump and pg_restore for the migration
• Need to preserve test environment configurations

Thank you in advance for your help!

[Fabio Racobaldo _Catworkx_]

Hi @Angel Fernando Vazquez Ruiz ,

for my knowledge you can't do that. You need to backup prod and restore whole application in preprod and then apply your changes (Edit Base URL, Disable Notification, ...)

There is not an automatic procedure to refresh just your data in preprod.

This is the Atlassian official doc https://confluence.atlassian.com/doc/restore-a-test-instance-from-production-127369720.html

Fabio