# Review Proxmox Backup destination protection after synchronization

> Review destination protection and sync scope independently of source snapshot settings.

- Canonical URL: https://update.dsesecurity.com/updates/review-proxmox-backup-destination-protection-after-synchronization/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-10-15T13:32:59+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

Review destination protection and sync scope independently of source snapshot settings.

## Potentially affected

This applies to the documented Proxmox Backup Server remote sync behavior. It concerns destination policy and scope, rather than the separate prune-and-garbage-collection process already covered in the library.

## DSE recommendation

DSE recommends documenting destination protection expectations independently of source snapshot settings.

## Article

Review destination protection and sync scope independently of source snapshot settings.

## Source facts

Proxmox Backup Server documentation states that a remote backup snapshot’s protected flag is not synchronized. Sync scope also depends on the remote user’s or API token’s readable backup groups and any configured group filters. A job can therefore copy a selected set of snapshots without reproducing that source-side protection flag. The remove-vanished option can remove destination content that no longer exists within the remote scope, and it requires additional local pruning privileges.

Source: [Proxmox Backup Server — Managing Remotes & Sync](https://pbs.proxmox.com/docs/managing-remotes.html).

## Applicability

This applies to the documented Proxmox Backup Server remote sync behavior. It concerns destination policy and scope, rather than the separate prune-and-garbage-collection process already covered in the library.

## DSE recommendation

DSE recommends documenting destination protection expectations independently of source snapshot settings. Compare the intended recovery-point inventory with what the configured remote identity can actually read. Have the backup owner review filtering and removal behavior before enabling automatic disappearance handling. Keep any destination-specific retention or protection step explicit and monitored. Avoid describing synchronization as a full policy clone when the documented flag behavior differs. Preserve a clear record of which administrator owns protection on each side of the relationship.

## Verification

In disposable datastores, synchronize a deliberately protected source snapshot and inspect the destination’s flag and permissions. Compare copied groups with the configured identity and filters. Rehearse any remove-vanished behavior only on expendable snapshots, recording the destination changes and the separate protection policy that should apply.

## Official reference

[Proxmox Backup Server — Managing Remotes & Sync](https://pbs.proxmox.com/docs/managing-remotes.html). Reviewed October 15, 2026.

## Primary reference

- Name: Proxmox Backup Server — Managing Remotes & Sync
- Authority: pbs.proxmox.com
- URL: https://pbs.proxmox.com/docs/managing-remotes.html
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Review Proxmox Backup destination protection after synchronization,” DSE Security, https://update.dsesecurity.com/updates/review-proxmox-backup-destination-protection-after-synchronization/
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.