{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
        "slug": "preview-restic-restore-deletion-before-reconciling-a-populated-target",
        "url": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/preview-restic-restore-deletion-before-reconciling-a-populated-target/"
        },
        "title": "Preview restic restore deletion before reconciling a populated target",
        "summary": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.",
        "format": {
            "slug": "guide",
            "name": "Guide"
        },
        "priority": {
            "slug": "info",
            "name": "Information"
        },
        "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-15T13:33:10+00:00",
        "modified_at": "2026-10-15T13:36:16+00:00",
        "reviewed_on": "2026-10-15",
        "reading_minutes": 2,
        "word_count": 261,
        "potentially_affected": "This applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.",
        "dse_recommendation": "DSE recommends restoring to a separate empty staging location for ordinary file recovery.",
        "primary_source": {
            "name": "restic — Restoring from Backup",
            "url": "https://restic.readthedocs.io/en/stable/050_restore.html",
            "published_on": null,
            "authority": "restic.readthedocs.io"
        },
        "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": "<p>Review every proposed target deletion before reconciling an existing directory from a restic snapshot.</p>\n<h2>Source facts</h2>\n<p>Restic restore can remove target files that are absent from the selected snapshot when its delete option is used. Include and exclude selections also affect which paths are eligible for that removal. Dry-run mode can report intended restore changes without performing them and checks existing file contents according to the selected overwrite behavior. Directories and symbolic links are always reported as restored in the dry-run listing. A populated target therefore needs a reviewed reconciliation scope.</p>\n<p>Source: <a href=\"https://restic.readthedocs.io/en/stable/050_restore.html\">restic — Restoring from Backup</a>.</p>\n<h2>Applicability</h2>\n<p>This applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends restoring to a separate empty staging location for ordinary file recovery. If reconciliation of an existing target is required, capture its present state and review a dry-run listing with the owner before enabling deletion. Keep the selected snapshot, target path, filters, and overwrite policy in one request. Stop the process if any path is ambiguous. Do not make delete a standard recovery wrapper default merely to produce a directory that looks identical to the archive.</p>\n<h2>Verification</h2>\n<p>Use a disposable populated target containing both snapshot files and intentional extras. Preview the exact proposed restore and inspect every planned deletion, then compare the actual result in the test copy. Retain the reviewed selection and verify unrelated paths remain untouched before considering an equivalent production change.</p>\n<h2>Official reference</h2>\n<p><a href=\"https://restic.readthedocs.io/en/stable/050_restore.html\">restic — Restoring from Backup</a>. Reviewed October 15, 2026.</p>",
        "content_text": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.\nSource facts\nRestic restore can remove target files that are absent from the selected snapshot when its delete option is used. Include and exclude selections also affect which paths are eligible for that removal. Dry-run mode can report intended restore changes without performing them and checks existing file contents according to the selected overwrite behavior. Directories and symbolic links are always reported as restored in the dry-run listing. A populated target therefore needs a reviewed reconciliation scope.\nSource: restic — Restoring from Backup.\nApplicability\nThis applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.\nDSE recommendation\nDSE recommends restoring to a separate empty staging location for ordinary file recovery. If reconciliation of an existing target is required, capture its present state and review a dry-run listing with the owner before enabling deletion. Keep the selected snapshot, target path, filters, and overwrite policy in one request. Stop the process if any path is ambiguous. Do not make delete a standard recovery wrapper default merely to produce a directory that looks identical to the archive.\nVerification\nUse a disposable populated target containing both snapshot files and intentional extras. Preview the exact proposed restore and inspect every planned deletion, then compare the actual result in the test copy. Retain the reviewed selection and verify unrelated paths remain untouched before considering an equivalent production change.\nOfficial reference\nrestic — Restoring from Backup. Reviewed October 15, 2026.",
        "content_markdown": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.\n\n## Source facts\n\nRestic restore can remove target files that are absent from the selected snapshot when its delete option is used. Include and exclude selections also affect which paths are eligible for that removal. Dry-run mode can report intended restore changes without performing them and checks existing file contents according to the selected overwrite behavior. Directories and symbolic links are always reported as restored in the dry-run listing. A populated target therefore needs a reviewed reconciliation scope.\n\nSource: [restic — Restoring from Backup](https://restic.readthedocs.io/en/stable/050_restore.html).\n\n## Applicability\n\nThis applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.\n\n## DSE recommendation\n\nDSE recommends restoring to a separate empty staging location for ordinary file recovery. If reconciliation of an existing target is required, capture its present state and review a dry-run listing with the owner before enabling deletion. Keep the selected snapshot, target path, filters, and overwrite policy in one request. Stop the process if any path is ambiguous. Do not make delete a standard recovery wrapper default merely to produce a directory that looks identical to the archive.\n\n## Verification\n\nUse a disposable populated target containing both snapshot files and intentional extras. Preview the exact proposed restore and inspect every planned deletion, then compare the actual result in the test copy. Retain the reviewed selection and verify unrelated paths remain untouched before considering an equivalent production change.\n\n## Official reference\n\n[restic — Restoring from Backup](https://restic.readthedocs.io/en/stable/050_restore.html). Reviewed October 15, 2026."
    },
    "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/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
                "url": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-15"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Preview restic restore deletion before reconciling a populated target",
                        "item": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/#article",
                "identifier": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
                "url": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/",
                "headline": "Preview restic restore deletion before reconciling a populated target",
                "description": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.",
                "abstract": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.",
                "articleBody": "Review every proposed target deletion before reconciling an existing directory from a restic snapshot.\nSource facts\nRestic restore can remove target files that are absent from the selected snapshot when its delete option is used. Include and exclude selections also affect which paths are eligible for that removal. Dry-run mode can report intended restore changes without performing them and checks existing file contents according to the selected overwrite behavior. Directories and symbolic links are always reported as restored in the dry-run listing. A populated target therefore needs a reviewed reconciliation scope.\nSource: restic — Restoring from Backup.\nApplicability\nThis applies to the stable restic restore behavior documented here. It addresses optional deletion while restoring into existing content, not permission to replace a live application directory without coordination.\nDSE recommendation\nDSE recommends restoring to a separate empty staging location for ordinary file recovery. If reconciliation of an existing target is required, capture its present state and review a dry-run listing with the owner before enabling deletion. Keep the selected snapshot, target path, filters, and overwrite policy in one request. Stop the process if any path is ambiguous. Do not make delete a standard recovery wrapper default merely to produce a directory that looks identical to the archive.\nVerification\nUse a disposable populated target containing both snapshot files and intentional extras. Preview the exact proposed restore and inspect every planned deletion, then compare the actual result in the test copy. Retain the reviewed selection and verify unrelated paths remain untouched before considering an equivalent production change.\nOfficial reference\nrestic — Restoring from Backup. Reviewed October 15, 2026.",
                "datePublished": "2026-10-15T13:33:10+00:00",
                "dateModified": "2026-10-15T13:36:16+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/preview-restic-restore-deletion-before-reconciling-a-populated-target/"
                },
                "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/preview-restic-restore-deletion-before-reconciling-a-populated-target/#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": "Preview restic restore deletion before reconciling a populated target"
                },
                "articleSection": [
                    "Business Continuity",
                    "IT"
                ],
                "keywords": [
                    "Business Continuity",
                    "IT",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "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": 261,
                "timeRequired": "PT2M",
                "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": "restic — Restoring from Backup",
                    "url": "https://restic.readthedocs.io/en/stable/050_restore.html"
                }
            }
        ]
    }
}