Backup auf ext. SSD - Anzahl der Backups stimmt nicht

N

Netzblicker

Member
Mar 13, 2022
48
4
13
59
Regensburg, Germany
Hallo,
ich finde meinen Fehler nicht - ich hab hier ein Cluster und einen eigenen Backupserver - der macht auch brav seine Backups. Dann wird per Skript jede Nacht eine SSD gemountet und ein Backup draufkopiert - aber irgendwie stimmt die Anzahl nicht - siehe Screenshots. Er soll eigentlich 4 Backups je VM aufheben, hat aber bei manchen mehr - warum?
 

Attachments

  • Bildschirmfoto 2024-02-28 um 09.38.17.png
    Bildschirmfoto 2024-02-28 um 09.38.17.png
    33.1 KB · Views: 8
  • Bildschirmfoto 2024-02-28 um 09.38.37.png
    Bildschirmfoto 2024-02-28 um 09.38.37.png
    42.1 KB · Views: 8
Netzblicker said:
Hallo,
ich finde meinen Fehler nicht - ich hab hier ein Cluster und einen eigenen Backupserver - der macht auch brav seine Backups. Dann wird per Skript jede Nacht eine SSD gemountet und ein Backup draufkopiert - aber irgendwie stimmt die Anzahl nicht - siehe Screenshots. Er soll eigentlich 4 Backups je VM aufheben, hat aber bei manchen mehr - warum?
Click to expand...
Hi,
was macht das Skript denn genau, wie werden die snapshots gesynched? Local sync job? Wurde der prune job bereits ausgeführt seitdem die snapshots gesynched wurden? Eventuell gibt der task log des prune jobs aufschluss weshalb diese snapshots nicht entfernt werden.
 
Hey,
das Skript mountet nur die SSD und schmeisst sie nach einer definierten Zeit wieder aus, mehr nicht. Gesynct wird lokal, die SSDs werden einmal pro Woche gewechselt und mit nach Hause genommen.
Die Garbage Collection läuft vorher durch - meinst du das? Der Output ist dieser hier:

Datastore: usb-rotation-grey
Task ID: UPID:pbs:0001EB26:1A4E6A65:00000010:65DE5B60:garbage_collection:usb\x2drotation\x2dgrey:root@pam:
Index file count: 74

Removed garbage: 0 B
Removed chunks: 0
Removed bad chunks: 0

Leftover bad chunks: 0
Pending removals: 396.425 GiB (in 190405 chunks)

Original Data usage: 9.945 TiB
On-Disk usage: 1.31 TiB (13.17%)
On-Disk chunks: 472383

Deduplication Factor: 7.59

Garbage collection successful.
 
der Output vom Prune:

02-28T05:00:00+01:00: Starting datastore sync job 'localhost:backups:usb-rotation-grey::s-e737e5e0-7771'
2024-02-28T05:00:00+01:00: task triggered by schedule '05:00'
2024-02-28T05:00:00+01:00: sync datastore 'usb-rotation-grey' from 'localhost/backups'
2024-02-28T05:00:00+01:00: ----
2024-02-28T05:00:00+01:00: Syncing datastore 'backups', root namespace into datastore 'usb-rotation-grey', root namespace
2024-02-28T05:00:00+01:00: found 7 groups to sync (out of 8 total)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:10:08Z .. 2024-02-25T21:10:04Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/101/2024-02-26T21:10:02Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 7.14% (0/7 groups, 1/2 snapshots in group #1)
2024-02-28T05:00:00+01:00: sync snapshot vm/101/2024-02-27T21:10:07Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 14.29% (1/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/101 failed - inserting chunk on store 'usb-rotation-grey' failed for 3d16f9aa672ca57114548f6838b943abd8d6dc7fe9b503a25258126b30730a4d - write failed: No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:15:47Z .. 2024-02-25T21:17:07Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/103/2024-02-26T21:14:46Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 21.43% (1/7 groups, 1/2 snapshots in group #2)
2024-02-28T05:00:00+01:00: sync snapshot vm/103/2024-02-27T21:14:46Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 28.57% (2/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/103 failed - No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:26:57Z .. 2024-02-25T21:38:56Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/104/2024-02-26T21:27:48Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 35.71% (2/7 groups, 1/2 snapshots in group #3)
2024-02-28T05:00:00+01:00: sync snapshot vm/104/2024-02-27T21:27:17Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 42.86% (3/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/104 failed - No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:10:07Z .. 2024-02-25T21:10:10Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/201/2024-02-26T21:10:02Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 50.00% (3/7 groups, 1/2 snapshots in group #4)
2024-02-28T05:00:00+01:00: sync snapshot vm/201/2024-02-27T21:10:09Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 57.14% (4/7 groups)
2024-02-28T05:00:01+01:00: sync group vm/201 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 4 snapshot(s) (2024-01-31T21:38:18Z .. 2024-02-23T21:49:53Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: re-sync snapshot vm/202/2024-02-24T21:27:01Z
2024-02-28T05:00:01+01:00: no data changes
2024-02-28T05:00:01+01:00: percentage done: 60.71% (4/7 groups, 1/4 snapshots in group #5)
2024-02-28T05:00:01+01:00: sync snapshot vm/202/2024-02-25T21:38:57Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:01+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:01+01:00: sync archive drive-scsi0.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 64.29% (4/7 groups, 2/4 snapshots in group #5)
2024-02-28T05:00:01+01:00: sync group vm/202 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 1 snapshot(s) (2024-01-31T21:10:09Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: sync snapshot vm/302/2024-02-21T21:10:13Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 73.47% (5/7 groups, 1/7 snapshots in group #6)
2024-02-28T05:00:01+01:00: sync group vm/302 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 1 snapshot(s) (2024-01-31T21:12:03Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: sync snapshot vm/304/2024-02-21T21:11:53Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 87.76% (6/7 groups, 1/7 snapshots in group #7)
2024-02-28T05:00:01+01:00: sync group vm/304 failed - inserting chunk on store 'usb-rotation-grey' failed for 7a1568a40be60a3d2fa1dc61ce7f55dc0c9ef449b966eb001aa8dcb8ffe0854e - write failed: No space left on device (os error 28)
2024-02-28T05:00:01+01:00: Finished syncing namespace , current progress: 6 groups, 1 snapshots
2024-02-28T05:00:01+01:00: TASK ERROR: sync failed with some errors.

No space left is klar, hat ja nix gelöscht
 
Netzblicker said:
der Output vom Prune:

02-28T05:00:00+01:00: Starting datastore sync job 'localhost:backups:usb-rotation-grey::s-e737e5e0-7771'
2024-02-28T05:00:00+01:00: task triggered by schedule '05:00'
2024-02-28T05:00:00+01:00: sync datastore 'usb-rotation-grey' from 'localhost/backups'
2024-02-28T05:00:00+01:00: ----
2024-02-28T05:00:00+01:00: Syncing datastore 'backups', root namespace into datastore 'usb-rotation-grey', root namespace
2024-02-28T05:00:00+01:00: found 7 groups to sync (out of 8 total)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:10:08Z .. 2024-02-25T21:10:04Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/101/2024-02-26T21:10:02Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 7.14% (0/7 groups, 1/2 snapshots in group #1)
2024-02-28T05:00:00+01:00: sync snapshot vm/101/2024-02-27T21:10:07Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 14.29% (1/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/101 failed - inserting chunk on store 'usb-rotation-grey' failed for 3d16f9aa672ca57114548f6838b943abd8d6dc7fe9b503a25258126b30730a4d - write failed: No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:15:47Z .. 2024-02-25T21:17:07Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/103/2024-02-26T21:14:46Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 21.43% (1/7 groups, 1/2 snapshots in group #2)
2024-02-28T05:00:00+01:00: sync snapshot vm/103/2024-02-27T21:14:46Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 28.57% (2/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/103 failed - No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:26:57Z .. 2024-02-25T21:38:56Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/104/2024-02-26T21:27:48Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 35.71% (2/7 groups, 1/2 snapshots in group #3)
2024-02-28T05:00:00+01:00: sync snapshot vm/104/2024-02-27T21:27:17Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-ide0.img.fidx
2024-02-28T05:00:00+01:00: percentage done: 42.86% (3/7 groups)
2024-02-28T05:00:00+01:00: sync group vm/104 failed - No space left on device (os error 28)
2024-02-28T05:00:00+01:00: skipped: 6 snapshot(s) (2024-01-31T21:10:07Z .. 2024-02-25T21:10:10Z) - older than the newest local snapshot
2024-02-28T05:00:00+01:00: re-sync snapshot vm/201/2024-02-26T21:10:02Z
2024-02-28T05:00:00+01:00: no data changes
2024-02-28T05:00:00+01:00: percentage done: 50.00% (3/7 groups, 1/2 snapshots in group #4)
2024-02-28T05:00:00+01:00: sync snapshot vm/201/2024-02-27T21:10:09Z
2024-02-28T05:00:00+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:00+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:00+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:00+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 57.14% (4/7 groups)
2024-02-28T05:00:01+01:00: sync group vm/201 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 4 snapshot(s) (2024-01-31T21:38:18Z .. 2024-02-23T21:49:53Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: re-sync snapshot vm/202/2024-02-24T21:27:01Z
2024-02-28T05:00:01+01:00: no data changes
2024-02-28T05:00:01+01:00: percentage done: 60.71% (4/7 groups, 1/4 snapshots in group #5)
2024-02-28T05:00:01+01:00: sync snapshot vm/202/2024-02-25T21:38:57Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-tpmstate0-backup.img.fidx
2024-02-28T05:00:01+01:00: downloaded 0 bytes (0.00 MiB/s)
2024-02-28T05:00:01+01:00: sync archive drive-scsi0.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 64.29% (4/7 groups, 2/4 snapshots in group #5)
2024-02-28T05:00:01+01:00: sync group vm/202 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 1 snapshot(s) (2024-01-31T21:10:09Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: sync snapshot vm/302/2024-02-21T21:10:13Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 73.47% (5/7 groups, 1/7 snapshots in group #6)
2024-02-28T05:00:01+01:00: sync group vm/302 failed - No space left on device (os error 28)
2024-02-28T05:00:01+01:00: skipped: 1 snapshot(s) (2024-01-31T21:12:03Z) - older than the newest local snapshot
2024-02-28T05:00:01+01:00: sync snapshot vm/304/2024-02-21T21:11:53Z
2024-02-28T05:00:01+01:00: sync archive qemu-server.conf.blob
2024-02-28T05:00:01+01:00: sync archive drive-scsi1.img.fidx
2024-02-28T05:00:01+01:00: percentage done: 87.76% (6/7 groups, 1/7 snapshots in group #7)
2024-02-28T05:00:01+01:00: sync group vm/304 failed - inserting chunk on store 'usb-rotation-grey' failed for 7a1568a40be60a3d2fa1dc61ce7f55dc0c9ef449b966eb001aa8dcb8ffe0854e - write failed: No space left on device (os error 28)
2024-02-28T05:00:01+01:00: Finished syncing namespace , current progress: 6 groups, 1 snapshots
2024-02-28T05:00:01+01:00: TASK ERROR: sync failed with some errors.

No space left is klar, hat ja nix gelöscht
Click to expand...
Das ist aber das log vom sync job, nicht vom prune job?

Damit die garbage collection etwas aufräumen kann, muss der prune job vorher snapshots entfernen, laut deinem garbage collection output sind da Pending removals: 396.425 GiB (in 190405 chunks), welche nach etwas mehr als 24h gelöscht werden können. Sie für Details auch https://pbs.proxmox.com/docs/backup-client.html#garbage-collection
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back