{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "item": { "id": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "slug": "inventory-linux-mount-points-before-proxmox-backup-host-file-backups", "url": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups.md", "json": "https://update.dsesecurity.com/api/v1/posts/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/" }, "title": "Inventory Linux mount points before Proxmox Backup host file backups", "summary": "Compare the actual Linux mount layout with the file archives included in a host backup.", "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:32:58+00:00", "modified_at": "2026-10-15T13:36:16+00:00", "reviewed_on": "2026-10-15", "reading_minutes": 2, "word_count": 262, "potentially_affected": "This applies to host file archives created with proxmox-backup-client as documented for Proxmox Backup Server. It does not describe Proxmox VE's separate virtual-machine backup integration.", "dse_recommendation": "DSE recommends comparing the Linux mount inventory with the intended recovery scope before approving the host-backup command.", "primary_source": { "name": "Proxmox Backup Server — Backup Client Usage", "url": "https://pbs.proxmox.com/docs/backup-client.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": "

Compare the actual Linux mount layout with the file archives included in a host backup.

\n

Source facts

\n

Proxmox Backup Server’s documented host backup client does not automatically cross mounted filesystem boundaries. A backup rooted at the filesystem root can therefore emit skipped-mount messages for mounted paths. The client supports explicitly including devices with include-dev, including more than one such path, and a single backup can contain multiple separately named file archives. The guide’s approach is to create a separate archive for each mounted disk. Backup scope must therefore follow the actual mount layout.

\n

Source: Proxmox Backup Server — Backup Client Usage.

\n

Applicability

\n

This applies to host file archives created with proxmox-backup-client as documented for Proxmox Backup Server. It does not describe Proxmox VE’s separate virtual-machine backup integration.

\n

DSE recommendation

\n

DSE recommends comparing the Linux mount inventory with the intended recovery scope before approving the host-backup command. Record each important mounted filesystem and whether it is included explicitly, represented by another archive, or intentionally excluded. Retain skipped-mount output in the job review so a successful upload cannot hide missing application data. Recheck the plan whenever storage is added or remounted. Keep application-consistency requirements separate from filesystem inclusion; capturing a directory does not by itself define a database recovery procedure.

\n

Verification

\n

Place harmless marker files in each intended test filesystem, run the proposed backup, and inspect its archive inventory. Restore those markers to a separate test location and compare included paths with the reviewed mount list. Document deliberate exclusions and investigate every unexplained skipped mount.

\n

Official reference

\n

Proxmox Backup Server — Backup Client Usage. Reviewed October 15, 2026.

", "content_text": "Compare the actual Linux mount layout with the file archives included in a host backup.\nSource facts\nProxmox Backup Server’s documented host backup client does not automatically cross mounted filesystem boundaries. A backup rooted at the filesystem root can therefore emit skipped-mount messages for mounted paths. The client supports explicitly including devices with include-dev, including more than one such path, and a single backup can contain multiple separately named file archives. The guide’s approach is to create a separate archive for each mounted disk. Backup scope must therefore follow the actual mount layout.\nSource: Proxmox Backup Server — Backup Client Usage.\nApplicability\nThis applies to host file archives created with proxmox-backup-client as documented for Proxmox Backup Server. It does not describe Proxmox VE’s separate virtual-machine backup integration.\nDSE recommendation\nDSE recommends comparing the Linux mount inventory with the intended recovery scope before approving the host-backup command. Record each important mounted filesystem and whether it is included explicitly, represented by another archive, or intentionally excluded. Retain skipped-mount output in the job review so a successful upload cannot hide missing application data. Recheck the plan whenever storage is added or remounted. Keep application-consistency requirements separate from filesystem inclusion; capturing a directory does not by itself define a database recovery procedure.\nVerification\nPlace harmless marker files in each intended test filesystem, run the proposed backup, and inspect its archive inventory. Restore those markers to a separate test location and compare included paths with the reviewed mount list. Document deliberate exclusions and investigate every unexplained skipped mount.\nOfficial reference\nProxmox Backup Server — Backup Client Usage. Reviewed October 15, 2026.", "content_markdown": "Compare the actual Linux mount layout with the file archives included in a host backup.\n\n## Source facts\n\nProxmox Backup Server’s documented host backup client does not automatically cross mounted filesystem boundaries. A backup rooted at the filesystem root can therefore emit skipped-mount messages for mounted paths. The client supports explicitly including devices with include-dev, including more than one such path, and a single backup can contain multiple separately named file archives. The guide’s approach is to create a separate archive for each mounted disk. Backup scope must therefore follow the actual mount layout.\n\nSource: [Proxmox Backup Server — Backup Client Usage](https://pbs.proxmox.com/docs/backup-client.html).\n\n## Applicability\n\nThis applies to host file archives created with proxmox-backup-client as documented for Proxmox Backup Server. It does not describe Proxmox VE’s separate virtual-machine backup integration.\n\n## DSE recommendation\n\nDSE recommends comparing the Linux mount inventory with the intended recovery scope before approving the host-backup command. Record each important mounted filesystem and whether it is included explicitly, represented by another archive, or intentionally excluded. Retain skipped-mount output in the job review so a successful upload cannot hide missing application data. Recheck the plan whenever storage is added or remounted. Keep application-consistency requirements separate from filesystem inclusion; capturing a directory does not by itself define a database recovery procedure.\n\n## Verification\n\nPlace harmless marker files in each intended test filesystem, run the proposed backup, and inspect its archive inventory. Restore those markers to a separate test location and compare included paths with the reviewed mount list. Document deliberate exclusions and investigate every unexplained skipped mount.\n\n## Official reference\n\n[Proxmox Backup Server — Backup Client Usage](https://pbs.proxmox.com/docs/backup-client.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/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "url": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-15" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Inventory Linux mount points before Proxmox Backup host file backups", "item": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/#article", "identifier": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "url": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/", "headline": "Inventory Linux mount points before Proxmox Backup host file backups", "description": "Compare the actual Linux mount layout with the file archives included in a host backup.", "abstract": "Compare the actual Linux mount layout with the file archives included in a host backup.", "articleBody": "Compare the actual Linux mount layout with the file archives included in a host backup.\nSource facts\nProxmox Backup Server’s documented host backup client does not automatically cross mounted filesystem boundaries. A backup rooted at the filesystem root can therefore emit skipped-mount messages for mounted paths. The client supports explicitly including devices with include-dev, including more than one such path, and a single backup can contain multiple separately named file archives. The guide’s approach is to create a separate archive for each mounted disk. Backup scope must therefore follow the actual mount layout.\nSource: Proxmox Backup Server — Backup Client Usage.\nApplicability\nThis applies to host file archives created with proxmox-backup-client as documented for Proxmox Backup Server. It does not describe Proxmox VE’s separate virtual-machine backup integration.\nDSE recommendation\nDSE recommends comparing the Linux mount inventory with the intended recovery scope before approving the host-backup command. Record each important mounted filesystem and whether it is included explicitly, represented by another archive, or intentionally excluded. Retain skipped-mount output in the job review so a successful upload cannot hide missing application data. Recheck the plan whenever storage is added or remounted. Keep application-consistency requirements separate from filesystem inclusion; capturing a directory does not by itself define a database recovery procedure.\nVerification\nPlace harmless marker files in each intended test filesystem, run the proposed backup, and inspect its archive inventory. Restore those markers to a separate test location and compare included paths with the reviewed mount list. Document deliberate exclusions and investigate every unexplained skipped mount.\nOfficial reference\nProxmox Backup Server — Backup Client Usage. Reviewed October 15, 2026.", "datePublished": "2026-10-15T13:32:58+00:00", "dateModified": "2026-10-15T13:36:16+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/" }, "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/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/#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": "Inventory Linux mount points before Proxmox Backup host file backups" }, "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": 262, "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 Backup Server — Backup Client Usage", "url": "https://pbs.proxmox.com/docs/backup-client.html" } } ] } }