Canonical: https://molo17.com/blog/gluesync-backup-restore/ Markdown mirror: https://molo17.com/blog/gluesync-backup-restore/index.md Title: Gluesync backup and restore Description: Learn how Gluesync handles backup and restore operations and how you can use them to protect and replicate your platform state. [← All articles](/blog/) Article # Gluesync backup and restore: protecting your data integration platform 21 Jan 2026 [Gluesync integrates](/blog/?category=gluesync-integrates) 2 min read Learn how Gluesync handles backup and restore operations and how to use them to protect and replicate your platform state.  In enterprise-grade data integration environments, reliability does not stop at real-time replication and orchestration. Safely preserving and restoring pipeline configurations and metadata is a critical part of platform lifecycle management. Within the [**Gluesync**](https://molo17.com/gluesync/) **modular ecosystem,** where modules like [Automator](https://molo17.com/blog/gluesync-automator-module/) streamline operational workflows—backup and restore capabilities play a foundational role in guaranteeing continuity, disaster recovery and controlled environment replication across stages. This article outlines how Gluesync handles backup and restore operations and how teams can use them to protect and replicate their platform state with confidence. ## What Gluesync backup includes Gluesync backups capture the logical state of the platform rather than raw replicated data. A backup includes: - Core Hub configuration and metadata - defined pipelines, schemas and mappings - platform-level objects and settings you need to reconstruct the environment This approach allows teams to restore the **operational setup** of Gluesync without reconfiguring pipelines manually, while keeping source and target databases fully independent. Gluesync stores backups as structured files. Consequently, you can reuse them across development, staging, or production environments. ## Backup strategies and use cases Gluesync backup and restore features support several common operational scenarios: - **disaster recovery** In case of infrastructure failure, backups allow the Core Hub and its configurations to be restored quickly, minimizing downtime and operational risk. - **environment cloning** Teams can replicate a Gluesync setup from one environment to another, enabling consistent testing, validation or rollout across multiple stages. - **change control and rollback** Before applying major configuration changes, a backup provides a safe rollback point, allowing teams to revert to a known-good state if needed. ## How backup and restore work in Gluesync Backups and restores are orchestrated through **Gluesync Automator**, which provides a web interface over the Core Hub’s import/export features. - **Backup** exports the current Core Hub configuration to YAML or a ZIP archive containing pipelines, agent metadata, schedules and UDF files. - **Restore** re‑imports these files into a target Core Hub cluster, recreating pipelines and their configurations. Restore actions are explicit, logged and designed to avoid conflicts with existing entities. ## Automating backups with Gluesync Automator While backups can be triggered manually, **Automator** streamlines the process through a **browser‑based UI**. Teams can execute on‑demand or scripted backups, standardize export formats across environments and integrate backup steps into broader deployment workflows. This approach makes configuration protection **repeatable, auditable and aligned with enterprise operational practices.** ## Backup and restore as part of operational resilience Backup and restore are integral components of Gluesync’s operational resilience. Together with modular automation and orchestration, they ensure that your integration architecture remains portable, recoverable, and easily reproducible. For step‑by‑step procedures and configuration options, visit the official [**Gluesync Backup and Restore documentation.**](https://docs.molo17.com/gluesync/v2.1/deploy-and-run/backup-and-restore.html) [← Older article Gluesync Whisperer module: controlled database workloads for testing and validation](/blog/gluesync-whisperer-module/) [Newer article → Oracle LogMiner agent for Gluesync: real-time CDC for Oracle databases](/blog/oracle-logminer-agent-for-gluesync/) ## Keep reading 1. [Mentioned in this article Gluesync Automator module: simplifying pipeline setup and lifecycle operations Gluesync Automator module for platform automation and bulk data operations 19 Jan 2026](/blog/gluesync-automator-module/) 2. [Gluesync integrates GridGain target connector: expand your data integration capabilities with Gluesync The GridGain target connector for Gluesync is now live for all users. In fact, this addition expands Gluesync’s portfolio of supported databases. Specifically, it enables businesses to synchronize data \[…\] 28 Jul 2025](/blog/gridgain-target-connector-high-performance-data-integration-with-gluesync/) 3. [Gluesync integrates Redis Agent for Gluesync: seamless integration for target Redis deployments Redis Agent for Gluesync is now available, offering a powerful solution for integrating data into Redis environments. Whether you’re using Redis on-premises, in the cloud, or through managed services \[…\] 13 Dec 2024](/blog/redis-agent-for-gluesync-seamless-integration-for-target-redis-deployments/) [Back to all articles](/blog/) [More in Gluesync integrates →](/blog/?category=gluesync-integrates)