Change default backup folder

[Kanze]

Hello Proxmox expert,

I need some suggestion how to resolve my problem, this is my situation.
I tried to do a backup of my Eve-ng VM that have 1Tb of dedicated HDD. When it was running I had this messages on the logs:

INFO: starting new backup job: vzdump 105 --remove 0 --node proxmox --mode snapshot --storage local --notes-template '{{guestname}}' --compress zstd
INFO: Starting Backup of VM 105 (qemu)
INFO: Backup started at 2023-06-02 12:23:11
INFO: status = running
INFO: VM Name: Eve-ng
INFO: include disk 'scsi0' 'local-lvm:vm-105-disk-0' 1T
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating vzdump archive '/var/lib/vz/dump/vzdump-qemu-105-2023_06_02-12_23_11.vma.zst'
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '77e8744c-b9a6-4b08-9dda-46c187524520'
INFO: resuming VM again
INFO:   0% (355.2 MiB of 1.0 TiB) in 3s, read: 118.4 MiB/s, write: 70.7 MiB/s
INFO:   1% (12.1 GiB of 1.0 TiB) in 35s, read: 375.0 MiB/s, write: 60.4 MiB/s
INFO:   2% (20.5 GiB of 1.0 TiB) in 2m 4s, read: 96.8 MiB/s, write: 68.4 MiB/s
INFO:   3% (30.8 GiB of 1.0 TiB) in 4m 9s, read: 84.5 MiB/s, write: 78.0 MiB/s
INFO:   4% (41.0 GiB of 1.0 TiB) in 6m 10s, read: 86.3 MiB/s, write: 79.5 MiB/s
INFO:   5% (51.2 GiB of 1.0 TiB) in 8m 7s, read: 89.6 MiB/s, write: 81.3 MiB/s
INFO:   6% (61.4 GiB of 1.0 TiB) in 10m 6s, read: 87.9 MiB/s, write: 81.1 MiB/s
INFO:   7% (71.7 GiB of 1.0 TiB) in 12m 1s, read: 91.2 MiB/s, write: 84.2 MiB/s
INFO:   8% (82.0 GiB of 1.0 TiB) in 13m 59s, read: 89.4 MiB/s, write: 83.4 MiB/s
INFO:   9% (92.2 GiB of 1.0 TiB) in 16m 2s, read: 84.7 MiB/s, write: 77.1 MiB/s
INFO:  10% (102.6 GiB of 1.0 TiB) in 16m 38s, read: 295.5 MiB/s, write: 72.4 MiB/s
INFO:  11% (112.9 GiB of 1.0 TiB) in 16m 43s, read: 2.1 GiB/s, write: 3.8 MiB/s
INFO:  12% (126.0 GiB of 1.0 TiB) in 16m 51s, read: 1.6 GiB/s, write: 46.6 MiB/s
INFO:  13% (133.7 GiB of 1.0 TiB) in 16m 58s, read: 1.1 GiB/s, write: 54.7 MiB/s
INFO:  14% (145.1 GiB of 1.0 TiB) in 17m 2s, read: 2.9 GiB/s, write: 9.0 KiB/s
INFO:  15% (154.5 GiB of 1.0 TiB) in 17m 10s, read: 1.2 GiB/s, write: 47.8 MiB/s
INFO:  16% (164.3 GiB of 1.0 TiB) in 17m 20s, read: 1005.2 MiB/s, write: 38.2 MiB/s
INFO:  17% (175.0 GiB of 1.0 TiB) in 17m 27s, read: 1.5 GiB/s, write: 2.9 KiB/s
INFO:  18% (185.8 GiB of 1.0 TiB) in 17m 38s, read: 1004.9 MiB/s, write: 34.3 MiB/s
INFO:  19% (195.7 GiB of 1.0 TiB) in 17m 48s, read: 1011.6 MiB/s, write: 38.2 MiB/s
INFO:  20% (205.8 GiB of 1.0 TiB) in 17m 54s, read: 1.7 GiB/s, write: 16.7 KiB/s
INFO:  21% (215.5 GiB of 1.0 TiB) in 18m 4s, read: 997.2 MiB/s, write: 38.3 MiB/s
INFO:  22% (225.4 GiB of 1.0 TiB) in 18m 10s, read: 1.6 GiB/s, write: 5.3 KiB/s
INFO:  23% (236.6 GiB of 1.0 TiB) in 18m 21s, read: 1.0 GiB/s, write: 34.8 MiB/s
INFO:  24% (246.0 GiB of 1.0 TiB) in 18m 31s, read: 960.7 MiB/s, write: 38.2 MiB/s
INFO:  25% (257.2 GiB of 1.0 TiB) in 18m 38s, read: 1.6 GiB/s, write: 14.9 KiB/s
INFO:  26% (266.3 GiB of 1.0 TiB) in 18m 48s, read: 934.5 MiB/s, write: 27.5 MiB/s
INFO:  27% (277.1 GiB of 1.0 TiB) in 18m 57s, read: 1.2 GiB/s, write: 12.5 MiB/s
INFO:  28% (287.3 GiB of 1.0 TiB) in 19m 3s, read: 1.7 GiB/s, write: 3.3 KiB/s
INFO:  29% (297.5 GiB of 1.0 TiB) in 19m 12s, read: 1.1 GiB/s, write: 25.8 MiB/s
INFO:  30% (307.9 GiB of 1.0 TiB) in 19m 21s, read: 1.2 GiB/s, write: 12.1 MiB/s
INFO:  31% (317.7 GiB of 1.0 TiB) in 19m 27s, read: 1.6 GiB/s, write: 3.3 KiB/s
INFO:  32% (329.1 GiB of 1.0 TiB) in 19m 38s, read: 1.0 GiB/s, write: 34.7 MiB/s
INFO:  33% (338.0 GiB of 1.0 TiB) in 19m 47s, read: 1006.8 MiB/s, write: 38.3 MiB/s
INFO:  34% (349.9 GiB of 1.0 TiB) in 19m 54s, read: 1.7 GiB/s, write: 4.6 MiB/s
INFO:  35% (359.7 GiB of 1.0 TiB) in 20m 3s, read: 1.1 GiB/s, write: 41.4 MiB/s
INFO:  36% (369.5 GiB of 1.0 TiB) in 20m 7s, read: 2.5 GiB/s, write: 7.4 MiB/s
INFO:  37% (380.0 GiB of 1.0 TiB) in 20m 16s, read: 1.2 GiB/s, write: 24.3 MiB/s
INFO:  38% (390.0 GiB of 1.0 TiB) in 20m 26s, read: 1.0 GiB/s, write: 47.3 MiB/s
INFO:  39% (399.7 GiB of 1.0 TiB) in 20m 32s, read: 1.6 GiB/s, write: 88.7 KiB/s
INFO:  40% (409.7 GiB of 1.0 TiB) in 20m 44s, read: 848.5 MiB/s, write: 39.9 MiB/s
INFO:  41% (420.2 GiB of 1.0 TiB) in 20m 55s, read: 983.9 MiB/s, write: 44.1 MiB/s
INFO:  42% (430.6 GiB of 1.0 TiB) in 20m 58s, read: 3.5 GiB/s, write: 6.7 KiB/s
INFO:  43% (441.1 GiB of 1.0 TiB) in 21m 16s, read: 597.3 MiB/s, write: 27.8 MiB/s
INFO:  44% (454.0 GiB of 1.0 TiB) in 21m 45s, read: 455.2 MiB/s, write: 12.8 MiB/s
INFO:  45% (464.5 GiB of 1.0 TiB) in 21m 48s, read: 3.5 GiB/s, write: 12.0 KiB/s
zstd: error 25 : Write error : No space left on device (cannot write compressed block)
INFO:  45% (465.5 GiB of 1.0 TiB) in 21m 49s, read: 1.1 GiB/s, write: 27.6 MiB/s
ERROR: vma_queue_write: write error - Broken pipe
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 105 failed - vma_queue_write: write error - Broken pipe
INFO: Failed at 2023-06-02 12:45:14
INFO: Backup job finished with errors
TASK ERROR: job errors

As you can see I had this error:

zstd: error 25 : Write error : No space left on device (cannot write compressed block)

So I was thinking if there's a way to set a custom path to create the backup files outside the server itself and pointing to another one.
Is it possible do something like that?

I was thinking to modify vzdump.conf but before do something stupid I want to understand if it's feasable and how

Thanks!

 

[Dunuin]

Mount an internal/external disk or a NFS/SMB Share by creating a entry in the /etc/fstab. Then, in the PVE webUI at Datacenter -> Storage -> Add, create a new "Directory" storage with content type "VZDump backups" and point its path to the mountpoint you used in the fstab. Then run a pvesm set YourStorageID --is_mountpoint /path/to/your/mountpoint so a failed mount won't fill up your root filesystem until PVE crashes. UID 0 and 100000 need rights to read+write to that folder.

 

[Kanze]

@Dunuin that amazing, work like a charm! I'll add your reply to my bookmark