Backup failed

Mabel

New Member
Mar 1, 2010
3
0
1
SORRY - WRONG FORUM

Hi,
We are working with 2 Proxmox installations and 6 machines on it.
Every night we do backups of all machines and over weeks it worked
without any errors.
Since two weeks some backups failed with the same error.
And it's different machines, not the same from day to day.
Now we created separate jobs for every machine, but it
didn't solve the problem.
Here the detailed backup log:
vzdump --quiet --snapshot --compress --storage Backup-Store_sh-vm11 --mailto qsysopr@revell.de 103
103: Feb 26 22:20:08 INFO: Starting Backup of VM 103 (qemu)
103: Feb 26 22:20:08 INFO: running
103: Feb 26 22:20:08 INFO: status = running
103: Feb 26 22:20:08 INFO: backup mode: snapshot
103: Feb 26 22:20:08 INFO: bandwidth limit: 10240 KB/s
103: Feb 26 22:20:09 INFO: Logical volume "vzsnap-sh-vm11-0" created
103: Feb 26 22:20:09 INFO: Logical volume "vzsnap-sh-vm11-0" successfully removed
103: Feb 26 22:20:09 ERROR: Backup of VM 103 failed - unable to open '/srv/backup-store/kvm-server-backup/sh-vm11/vzdump-qemu-103-2010_02_26-22_20_08.tmp/qemu-server.conf' at /usr/share/perl5/PVE/VZDump/QemuServer.pm line 373.

Can somebody help us?

Thanks a lot.

Kind regards,,

Mabel
 
Last edited:
moved to the right forum.
 
Hi,
has nobody any idea to this error?
We do the backup to the disk of another machine. Some month it
worked without any error.
Then this error comes every night on different machines.
Also the change to a NAS system didn't solve the problem.
We checked the network system, changed switches and cables.
No positive response.

So please give us an idea to how to find the reason of the problem.

Kind regards,

Mabel
 
the error message points you the right direction - check your backup target.
 
Hi,

none of the hints worked.

After trying different connections cifs and iSCSI and different backup systems, Ubuntu server and separate NAS system,
we found one workaround which is working.

We connect a Windows 2000 server via iSCSI to a NAS system. The Proxmox system is connected via cifs to
the share of the Windows server.
This solution is now working since 5 days without any error.

Thank you for your help.

Regards,

Mabel