{
    "api_version": "1",
    "kind": "dse_post",
    "self": "https://update.dsesecurity.com/api/v1/posts/proxmox-backup-prune-garbage-collection-space/",
    "item": {
        "id": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/",
        "slug": "proxmox-backup-prune-garbage-collection-space",
        "url": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/",
        "alternate_urls": {
            "markdown": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space.md",
            "json": "https://update.dsesecurity.com/api/v1/posts/proxmox-backup-prune-garbage-collection-space/"
        },
        "title": "Explain pending space after Proxmox Backup pruning",
        "summary": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.",
        "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/"
            }
        ],
        "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-15T00:43:22+00:00",
        "modified_at": "2026-10-15T00:44:33+00:00",
        "reviewed_on": "2026-10-14",
        "reading_minutes": 2,
        "word_count": 243,
        "potentially_affected": "Use this guide for the Proxmox Backup datastore behavior described in the maintenance documentation. Pruning alone is also not evidence that all underlying sensitive data has been removed.",
        "dse_recommendation": "DSE recommends reviewing retention intent before pruning additional recovery points to solve a capacity alert.",
        "primary_source": {
            "name": "Proxmox — Maintenance Tasks, Backup Server documentation",
            "url": "https://pbs.proxmox.com/docs/maintenance.html",
            "published_on": null,
            "authority": "pbs.proxmox.com"
        },
        "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>Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.</p>\n<h2>Source facts</h2>\n<p>Proxmox documents pruning as removing snapshot metadata rather than immediately deleting its data chunks. Other snapshots may still reference those chunks. Garbage collection identifies unused chunks through mark and sweep phases, with a cutoff affected by active backup writers and a grace period. Chunks within that period appear as pending removals. Consequently, deleting a snapshot and reclaiming its storage are different events.</p>\n<p>Source: <a href=\"https://pbs.proxmox.com/docs/maintenance.html\">Proxmox — Maintenance Tasks, Backup Server documentation</a>.</p>\n<h2>Applicability</h2>\n<p>Use this guide for the Proxmox Backup datastore behavior described in the maintenance documentation. Pruning alone is also not evidence that all underlying sensitive data has been removed.</p>\n<h2>DSE recommendation</h2>\n<p>DSE recommends reviewing retention intent before pruning additional recovery points to solve a capacity alert. Record datastore use, the last prune result, garbage-collection status, pending removals, and active writers together. Use the prune simulator when evaluating a retention change. Assign a capacity escalation owner so urgent space pressure does not become repeated deletion without a recovery decision. Keep filesystem-level chunk deletion outside the troubleshooting procedure and use the product’s supported maintenance operations.</p>\n<h2>Verification</h2>\n<p>Compare datastore use and garbage-collection reports across the relevant grace period, noting active jobs and references that remain. Confirm required recovery points are still present and follow the approved restore-test process. Close the capacity issue on measured reclaimed space and retained recovery coverage.</p>\n<h2>Official reference</h2>\n<p><a href=\"https://pbs.proxmox.com/docs/maintenance.html\">Proxmox — Maintenance Tasks, Backup Server documentation</a>. Reviewed October 14, 2026.</p>",
        "content_text": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.\nSource facts\nProxmox documents pruning as removing snapshot metadata rather than immediately deleting its data chunks. Other snapshots may still reference those chunks. Garbage collection identifies unused chunks through mark and sweep phases, with a cutoff affected by active backup writers and a grace period. Chunks within that period appear as pending removals. Consequently, deleting a snapshot and reclaiming its storage are different events.\nSource: Proxmox — Maintenance Tasks, Backup Server documentation.\nApplicability\nUse this guide for the Proxmox Backup datastore behavior described in the maintenance documentation. Pruning alone is also not evidence that all underlying sensitive data has been removed.\nDSE recommendation\nDSE recommends reviewing retention intent before pruning additional recovery points to solve a capacity alert. Record datastore use, the last prune result, garbage-collection status, pending removals, and active writers together. Use the prune simulator when evaluating a retention change. Assign a capacity escalation owner so urgent space pressure does not become repeated deletion without a recovery decision. Keep filesystem-level chunk deletion outside the troubleshooting procedure and use the product’s supported maintenance operations.\nVerification\nCompare datastore use and garbage-collection reports across the relevant grace period, noting active jobs and references that remain. Confirm required recovery points are still present and follow the approved restore-test process. Close the capacity issue on measured reclaimed space and retained recovery coverage.\nOfficial reference\nProxmox — Maintenance Tasks, Backup Server documentation. Reviewed October 14, 2026.",
        "content_markdown": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.\n\n## Source facts\n\nProxmox documents pruning as removing snapshot metadata rather than immediately deleting its data chunks. Other snapshots may still reference those chunks. Garbage collection identifies unused chunks through mark and sweep phases, with a cutoff affected by active backup writers and a grace period. Chunks within that period appear as pending removals. Consequently, deleting a snapshot and reclaiming its storage are different events.\n\nSource: [Proxmox — Maintenance Tasks, Backup Server documentation](https://pbs.proxmox.com/docs/maintenance.html).\n\n## Applicability\n\nUse this guide for the Proxmox Backup datastore behavior described in the maintenance documentation. Pruning alone is also not evidence that all underlying sensitive data has been removed.\n\n## DSE recommendation\n\nDSE recommends reviewing retention intent before pruning additional recovery points to solve a capacity alert. Record datastore use, the last prune result, garbage-collection status, pending removals, and active writers together. Use the prune simulator when evaluating a retention change. Assign a capacity escalation owner so urgent space pressure does not become repeated deletion without a recovery decision. Keep filesystem-level chunk deletion outside the troubleshooting procedure and use the product’s supported maintenance operations.\n\n## Verification\n\nCompare datastore use and garbage-collection reports across the relevant grace period, noting active jobs and references that remain. Confirm required recovery points are still present and follow the approved restore-test process. Close the capacity issue on measured reclaimed space and retained recovery coverage.\n\n## Official reference\n\n[Proxmox — Maintenance Tasks, Backup Server documentation](https://pbs.proxmox.com/docs/maintenance.html). Reviewed October 14, 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/proxmox-backup-prune-garbage-collection-space/",
                "url": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/",
                "isPartOf": {
                    "@id": "https://update.dsesecurity.com/#website"
                },
                "lastReviewed": "2026-10-14"
            },
            {
                "@type": "BreadcrumbList",
                "@id": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/#breadcrumbs",
                "itemListElement": [
                    {
                        "@type": "ListItem",
                        "position": 1,
                        "name": "DSE Updates",
                        "item": "https://update.dsesecurity.com/"
                    },
                    {
                        "@type": "ListItem",
                        "position": 2,
                        "name": "Explain pending space after Proxmox Backup pruning",
                        "item": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/"
                    }
                ]
            },
            {
                "@type": [
                    "Article",
                    "TechArticle"
                ],
                "@id": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/#article",
                "identifier": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/",
                "url": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/",
                "headline": "Explain pending space after Proxmox Backup pruning",
                "description": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.",
                "abstract": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.",
                "articleBody": "Distinguish snapshot removal from chunk reclamation when a Proxmox Backup datastore still looks full.\nSource facts\nProxmox documents pruning as removing snapshot metadata rather than immediately deleting its data chunks. Other snapshots may still reference those chunks. Garbage collection identifies unused chunks through mark and sweep phases, with a cutoff affected by active backup writers and a grace period. Chunks within that period appear as pending removals. Consequently, deleting a snapshot and reclaiming its storage are different events.\nSource: Proxmox — Maintenance Tasks, Backup Server documentation.\nApplicability\nUse this guide for the Proxmox Backup datastore behavior described in the maintenance documentation. Pruning alone is also not evidence that all underlying sensitive data has been removed.\nDSE recommendation\nDSE recommends reviewing retention intent before pruning additional recovery points to solve a capacity alert. Record datastore use, the last prune result, garbage-collection status, pending removals, and active writers together. Use the prune simulator when evaluating a retention change. Assign a capacity escalation owner so urgent space pressure does not become repeated deletion without a recovery decision. Keep filesystem-level chunk deletion outside the troubleshooting procedure and use the product’s supported maintenance operations.\nVerification\nCompare datastore use and garbage-collection reports across the relevant grace period, noting active jobs and references that remain. Confirm required recovery points are still present and follow the approved restore-test process. Close the capacity issue on measured reclaimed space and retained recovery coverage.\nOfficial reference\nProxmox — Maintenance Tasks, Backup Server documentation. Reviewed October 14, 2026.",
                "datePublished": "2026-10-15T00:43:22+00:00",
                "dateModified": "2026-10-15T00:44:33+00:00",
                "mainEntityOfPage": {
                    "@id": "https://update.dsesecurity.com/updates/proxmox-backup-prune-garbage-collection-space/"
                },
                "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/proxmox-backup-prune-garbage-collection-space/#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": "Explain pending space after Proxmox Backup pruning"
                },
                "articleSection": [
                    "Business Continuity"
                ],
                "keywords": [
                    "Business Continuity",
                    "Guide",
                    "Information priority"
                ],
                "genre": "Guide",
                "about": [
                    {
                        "@type": "Thing",
                        "name": "Business Continuity",
                        "url": "https://update.dsesecurity.com/topic/business-continuity/"
                    }
                ],
                "wordCount": 243,
                "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": "Proxmox — Maintenance Tasks, Backup Server documentation",
                    "url": "https://pbs.proxmox.com/docs/maintenance.html"
                }
            }
        ]
    }
}