# Inventory Linux mount points before Proxmox Backup host file backups

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

- Canonical URL: https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-15T13:32:58+00:00
- Modified: 2026-10-15T13:36:16+00:00
- Last reviewed by DSE: 2026-10-15
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

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

## 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.

## Article

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

## Source facts

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.

Source: [Proxmox Backup Server — Backup Client Usage](https://pbs.proxmox.com/docs/backup-client.html).

## Applicability

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. 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.

## Verification

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.

## Official reference

[Proxmox Backup Server — Backup Client Usage](https://pbs.proxmox.com/docs/backup-client.html). Reviewed October 15, 2026.

## Primary reference

- Name: Proxmox Backup Server — Backup Client Usage
- Authority: pbs.proxmox.com
- URL: https://pbs.proxmox.com/docs/backup-client.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Inventory Linux mount points before Proxmox Backup host file backups,” DSE Security, https://update.dsesecurity.com/updates/inventory-linux-mount-points-before-proxmox-backup-host-file-backups/
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.