{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/preserve-genetec-directory-changes-before-returning-to-master-database/", "item": { "id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "slug": "preserve-genetec-directory-changes-before-returning-to-master-database", "url": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database.md", "json": "https://update.dsesecurity.com/api/v1/posts/preserve-genetec-directory-changes-before-returning-to-master-database/" }, "title": "Preserve Genetec Directory changes before returning to the master database", "summary": "Security Center 5.14 does not automatically restore backup-database configuration edits to the master. Decide how to preserve those edits before Directory failback.", "format": { "slug": "playbook", "name": "Playbook" }, "priority": { "slug": "advisory", "name": "Advisory" }, "featured": false, "image": { "theme": "continuity-recovery", "label": "Continuity & recovery", "alt": "Paired infrastructure paths converging on a stable recovered service.", "card_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "business-continuity", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-28T23:23:30+00:00", "modified_at": "2026-10-28T23:23:38+00:00", "reviewed_on": "2026-10-28", "reading_minutes": 3, "word_count": 475, "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.", "primary_source": { "name": "Genetec — Setting up Directory database failover through backup and restore (Security Center 5.14)", "url": "https://techdocs.genetec.com/r/en-US/Security-Center-Administrator-Guide-5.14/Setting-up-Directory-database-failover-through-backup-and-restore", "published_on": null, "authority": "Genetec" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

Bottom line: Decide which configuration changes must survive before returning a Genetec Directory from its backup database to the master.

\n

Source fact: documented behavior

\n

The Setting up Directory database failover through backup and restore topic is the primary reference for this Security Center 5.14 discussion.

\n

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.

\n

What the source does not establish

\n

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.

\n

Applicability questions

\n\n

DSE recommendation: controlled next steps

\n

The following steps are DSE recommendations based on the cited source.

\n

DSE recommends preparing this decision before an incident. For a rehearsal, use an isolated representative system and a harmless, identifiable configuration edit.

\n
    \n
  1. 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.
    2. \n
  2. 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.
    3. \n
  3. 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.
    4. \n
\n

Verification and evidence

\n

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.

\n

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.

\n

Official references

\n\n

Source review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.

\n", "content_text": "Bottom line: Decide which configuration changes must survive before returning a Genetec Directory from its backup database to the master.\nSource fact: documented behavior\nThe Setting up Directory database failover through backup and restore topic is the primary reference for this Security Center 5.14 discussion.\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nIs this the configured Directory database failover mode and deployed release?\nWhich configuration changes were made while the backup database was active?\nWho will decide which database contents are authoritative?\nWhere is the required contingency backup, and who can perform an authorized restoration?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends preparing this decision before an incident. For a rehearsal, use an isolated representative system and a harmless, identifiable configuration edit.\n\nRecord 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.\nChoose 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.\nRehearse 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.\n\nVerification and evidence\nRetain 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.\nKeep 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.\nOfficial references\n\nSetting up Directory database failover through backup and restore — Genetec; Security Center 5.14.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "content_markdown": "Bottom line: Decide which configuration changes must survive before returning a Genetec Directory from its backup database to the master.\n\n## Source fact: documented behavior\n\nThe [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.\n\nThe 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.\n\n## What the source does not establish\n\nThis 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.\n\n## Applicability questions\n\n- Is this the configured Directory database failover mode and deployed release?\n\n- Which configuration changes were made while the backup database was active?\n\n- Who will decide which database contents are authoritative?\n\n- Where is the required contingency backup, and who can perform an authorized restoration?\n\n## DSE recommendation: controlled next steps\n\nThe following steps are DSE recommendations based on the cited source.\n\nDSE recommends preparing this decision before an incident. For a rehearsal, use an isolated representative system and a harmless, identifiable configuration edit.\n\n- 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.\n\n- 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.\n\n- 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.\n\n## Verification and evidence\n\nRetain 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.\n\nKeep 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.\n\n## Official references\n\n- [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.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "url": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-28" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Business Continuity", "item": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "ListItem", "position": 3, "name": "Preserve Genetec Directory changes before returning to the master database", "item": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/#article", "identifier": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "url": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/", "headline": "Preserve Genetec Directory changes before returning to the master database", "description": "Security Center 5.14 does not automatically restore backup-database configuration edits to the master.", "abstract": "Security Center 5.14 does not automatically restore backup-database configuration edits to the master. Decide how to preserve those edits before Directory failback.", "articleBody": "Bottom line: Decide which configuration changes must survive before returning a Genetec Directory from its backup database to the master.\nSource fact: documented behavior\nThe Setting up Directory database failover through backup and restore topic is the primary reference for this Security Center 5.14 discussion.\nThe 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.\nWhat the source does not establish\nThis 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.\nApplicability questions\n\nIs this the configured Directory database failover mode and deployed release?\nWhich configuration changes were made while the backup database was active?\nWho will decide which database contents are authoritative?\nWhere is the required contingency backup, and who can perform an authorized restoration?\n\nDSE recommendation: controlled next steps\nThe following steps are DSE recommendations based on the cited source.\nDSE recommends preparing this decision before an incident. For a rehearsal, use an isolated representative system and a harmless, identifiable configuration edit.\n\nRecord 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.\nChoose 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.\nRehearse 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.\n\nVerification and evidence\nRetain 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.\nKeep 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.\nOfficial references\n\nSetting up Directory database failover through backup and restore — Genetec; Security Center 5.14.\n\nSource review completed October 28, 2026. Recheck the official documentation and deployment-specific applicability before a production change.", "datePublished": "2026-10-28T23:23:30+00:00", "dateModified": "2026-10-28T23:23:38+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/preserve-genetec-directory-changes-before-returning-to-master-database/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/continuity-recovery-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Preserve Genetec Directory changes before returning to the master database" }, "articleSection": [ "Business Continuity", "IT" ], "keywords": [ "Business Continuity", "IT", "Playbook", "Advisory priority" ], "genre": "Playbook", "about": [ { "@type": "Thing", "name": "Business Continuity", "url": "https://update.dsesecurity.com/topic/business-continuity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 475, "timeRequired": "PT3M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "Genetec — Setting up Directory database failover through backup and restore (Security Center 5.14)", "url": "https://techdocs.genetec.com/r/en-US/Security-Center-Administrator-Guide-5.14/Setting-up-Directory-database-failover-through-backup-and-restore" } } ] } }