PostgreSQL Sync and Backup Tool

For developers and operators maintaining several business databases, this console brings synchronization, backup planning and execution records together. Review databases and their sizes across servers, select the objects to maintain, then follow each task's steps and results, reducing the work of repeatedly locating settings, running commands and collecting logs across environments.

Check the direction before synchronizing

• Source and destination: Synchronization tasks specify a source, a destination and the corresponding databases, with choices for processing structure and data.
• Creation and execution records: A missing destination database can be created as part of the task, and each step retains its status and logs.

This supports preparing a one-way data copy for a business environment, with direction and scope visible for checking before execution.

Scope backups and follow results

• Databases or selected tables: Backups can cover a whole database or selected tables, with several databases included in one job.
• Item-level progress: Each item records its status, file size, completion time and result location. The job page presents overall progress and failure reasons.
• Retry one item: Eligible failed full-database items can be retried separately without repeating every successful item.

Schedule recurring maintenance

Recurring maintenance supports daily, interval-based and weekly schedules, showing the next run, the latest job and whether the schedule is enabled. Existing schedules can have databases or selected tables added as services are introduced or environments change. Both manual and scheduled work leave records for handover and review.

Synchronization and recovery scope

The practical value is a continuous maintenance workflow with a defined scope, visible progress and results that can be checked: select the objects, execute the work, identify failures and follow up. The project provides configured one-way synchronization and backups; it does not promise two-way merging, zero-downtime migration or automatic recovery. Recovery procedures and actual recoverability require separate validation.