Problem with local backups

Alternativende

Renowned Member
Aug 27, 2015
30
1
73
Hi,
im in trouble with backing up two VM´s on a small Proxmox server. Backup should be done locally and works for one machine every time.

But the second one fails on every try with the following message:

Code:
  103: Aug 23 02:29:18 INFO: status: 15% (114359533568/751619276800), sparse 0% (5045145600), duration 5587, 16/16 MB/s
  103: Aug 23 02:29:18 ERROR: vma_queue_write: write error - Broken pipe
  103: Aug 23 02:29:18 INFO: aborting backup job
  103: Aug 23 02:29:20 INFO: resume vm
  103: Aug 23 02:29:21 INFO: vm is online again after 5590 seconds
  103: Aug 23 02:29:24 ERROR: Backup of VM 103 failed - vma_queue_write: write error - Broken pipe

Here are some things that may be useful.

Code:
~# df -h
Filesystem            Size  Used Avail Use% Mounted on
udev                   10M     0   10M   0% /dev
tmpfs                 3.2G  396K  3.2G   1% /run
/dev/mapper/pve-root   95G  1.6G   89G   2% /
tmpfs                 5.0M     0  5.0M   0% /run/lock
tmpfs                 6.3G   38M  6.3G   1% /run/shm
/dev/mapper/pve-data  776G  217G  560G  28% /var/lib/vz
/dev/sdb1             917G   72M  871G   1% /media/backup
/dev/fuse              30M   16K   30M   1% /etc/pve

fstab
Code:
/dev/sdb1 /media/backup ext4 defaults,errors=remount-ro 0 1

An important thing to mention could be that he always fails at 15%. Both disks are 1TB.

I don´t know which logs could be useful, if you miss anything please give me a hint.

Thanks!
 
Hi,

can you post the output of the following command:

Code:
cat /etc/pve/storage.cfg

If using the CLI, can you post also the used command?
 
Hi,
yes sure, here you go:

Code:
dir: local
    path /var/lib/vz
    shared
    content images,iso,vztmpl,rootdir
    maxfiles 0

dir: Backup
    path /media/backup
    shared
    content images
    maxfiles 100

dir: BackupVM
    path /media/backup
    shared
    content images,backup
    maxfiles 4

No currently im not using the CLI to start the backups. Just the webinterface.
 
OK, now please post the output of the following command, so I can see which options are you using:

Code:
cat /var/log/syslog | grep "starting new backup job"

and possibly the whole system log part regarding the failed (and the successful) backup.
 
Last edited:
Hey,
im sorry but unfortunately it works now... I have no idea why but there were two runs successful without changing anything. So i think it´s ok now somehow.

Thanks!
 

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!

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!