Garbage Collection on synced targets necessary if "remove vanished" is checked? (EOM)
- Thread starter mhert
- Start date
Yes, garbage collection is required to free up unused chunks, also in the case of removal of vanished snapshots by a sync job. Please let me refer you to https://pbs.proxmox.com/docs/maintenance.html#garbage-collection
as i understand there's no 1:1 sync to a remote target (without processing the data afterwards) as known from "normal" backups (sync new files and delete old ones)?
so a sync copies the content (chunks) of (new) snaphots und without a garbage collection on remote it runs out of memory at a point in time?
which effect has a prune job on the source to followings sync jobs (to the target)?
so a sync copies the content (chunks) of (new) snaphots und without a garbage collection on remote it runs out of memory at a point in time?
which effect has a prune job on the source to followings sync jobs (to the target)?
Last edited:
Not sure if I understand your question, but if you have enabled the removed vanished flag for sync jobs, backup snapshots, groups and namespaces are removed from the target when no longer present on the source side. But since the remove snapshots might have referenced chunks on the target datastore, which are now not in use anymore, you will have to run a garbage collection on the target datastore to free these chunks.
Hope this makes it more clear.
No, the snapshots must exist on the source, otherwise they will not be synced. And the sync job will only ever transfer chunks indexed by one of the snapshots to sync, never unused or unrelated chunks. It is therefore independent from the garbage collection on the source.