# Preserve Genetec Directory changes before returning to the master database > Security Center 5.14 does not automatically restore backup-database configuration edits to the master. Decide how to preserve those edits before Directory failback. - Canonical URL: https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/ - Publisher: Detection Systems & Engineering (DSE Security) - Author: DSE Security Editorial Team - Published: 2026-10-28T23:23:30+00:00 - Modified: 2026-10-28T23:23:38+00:00 - Last reviewed by DSE: 2026-10-28 - Resource type: Playbook - DSE priority: Advisory - Topics: Business Continuity, IT - Reading time: 3 minutes ## What you need to know Security Center 5.14 does not automatically restore backup-database configuration edits to the master. Decide how to preserve those edits before Directory failback. ## Potentially affected Security Center 5.14 Directory systems using Backup and restore database failover mode. ## DSE recommendation Identify the authoritative configuration and rehearse the documented contingency-backup preservation path before enabling automatic return. ## Article Bottom line: Decide which configuration changes must survive before returning a Genetec Directory from its backup database to the master. ## Source fact: documented behavior The [Setting up Directory database failover through backup and restore](https://techdocs.genetec.com/r/en-US/Security-Center-Administrator-Guide-5.14/Setting-up-Directory-database-failover-through-backup-and-restore) topic is the primary reference for this Security Center 5.14 discussion. The Security Center 5.14 procedure says configuration edits made while using the backup database are not automatically restored to the master when it returns. It describes a contingency backup created each time Directory reconnects to the master, and directs restoration of the latest contingency backup after reactivating the master to preserve those changes. The automatic reconnection option works only when the primary Directory server is online. The procedure cautions that switching the active database causes a short service disruption and loses configuration changes made while the master was offline. ## What the source does not establish This is the documented Backup and restore failover mode, not a general database merge promise. The contingency backup is a preservation mechanism requiring the described recovery work. The topic does not prove that an installation has a usable backup or establish a customer recovery time. ## Applicability questions - Is this the configured Directory database failover mode and deployed release? - Which configuration changes were made while the backup database was active? - Who will decide which database contents are authoritative? - Where is the required contingency backup, and who can perform an authorized restoration? ## DSE recommendation: controlled next steps The following steps are DSE recommendations based on the cited source. DSE recommends preparing this decision before an incident. For a rehearsal, use an isolated representative system and a harmless, identifiable configuration edit. - Record the active database, designated master and last known backup before the exercise. Keep a sanitized edit ledger during the backup-database period, including the change, owner, time and expected final state. - Choose the return route with the system and database owners. Resolve how the documented contingency backup will be retained and restored. Keep automatic reconnection under explicit change approval until that preservation and verification work has been demonstrated. - Rehearse the selected route and compare the resulting configuration with the edit ledger. Record any discrepancy and restore the approved test state. Use the result to write a site-specific recovery runbook rather than assuming a successful connection resolves the configuration question. ## Verification and evidence Retain database identities, relevant versions, the edit ledger, backup identifiers, restoration evidence and before/after configuration comparisons. Record who approved the authoritative state and when the required service checks passed. Keep this record about Directory configuration. Assess video archive consolidation through its own media-recovery procedure. The proposed rehearsal does not claim that configuration recovery has been tested for a customer or that the return can occur without interruption. ## Official references - [Setting up Directory database failover through backup and restore](https://techdocs.genetec.com/r/en-US/Security-Center-Administrator-Guide-5.14/Setting-up-Directory-database-failover-through-backup-and-restore) — Genetec; Security Center 5.14. Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change. ## Primary reference - Name: Genetec — Setting up Directory database failover through backup and restore (Security Center 5.14) - Authority: Genetec - URL: https://techdocs.genetec.com/r/en-US/Security-Center-Administrator-Guide-5.14/Setting-up-Directory-database-failover-through-backup-and-restore - Source publication date: Not stated by the source ## Citation and use Preferred citation: “Preserve Genetec Directory changes before returning to the master database,” DSE Security, https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/ Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/ Usage and citation policy: https://update.dsesecurity.com/usage/ Copyright © 2026 Detection Systems & Engineering. All rights reserved.