[PVE-User] Backup error not reported
lorenzo.quatrini at gmail.com
Wed Nov 9 12:56:52 CET 2011
Il 09/11/2011 09:24, Eneko Lacunza ha scritto:
> Hi all,
> Last night we had a problem with a scheduled backup; the destination
> storage was not correctly mounted (due to a reboot in the NAS) and the
> backups failed.
> The problems is that no report was sent to the configured email. When
> the backup is ok the report is sent correctly.
> Syslog only says the following:
> Nov 9 03:00:01 camelot /USR/SBIN/CRON: (root) CMD (test
> -x /usr/lib/atsar/atsa1 && /usr/lib/atsar/atsa1)
> Nov 9 03:00:01 camelot /USR/SBIN/CRON: (root) CMD (vzdump --quiet
> --node 2 --snapshot --compress --storage NAS_backup_vm --maxfiles 1
> --mailto sistemas at binovo.es 106^I108^I111^I112^I113^I114^I115^I120)
> PVE versions:
> camelot:~# pveversion --verbose
> pve-manager: 1.9-24 (pve-manager/1.9/6542)
> running kernel: 2.6.35-2-pve
> proxmox-ve-2.6.35: 1.8-13
> pve-kernel-2.6.32-4-pve: 2.6.32-33
> pve-kernel-2.6.35-2-pve: 2.6.35-13
> qemu-server: 1.1-32
> pve-firmware: 1.0-13
> libpve-storage-perl: 1.0-19
> vncterm: 0.9-2
> vzctl: 3.0.28-1pve5
> vzdump: 1.2-15
> vzprocps: 2.0.11-2
> vzquota: 3.0.11-1
> pve-qemu-kvm: 0.15.0-1
> ksm-control-daemon: 1.0-6
> Any hint?
the backup job is stuck waiting for the nfs share; as soon as you restore the
share all the pending jobs should start flowing again.
Watch the processes on the proxmox server (vzdump and/or tar jobs); maybe the
backups are running right now.
I guess that a timeout on the backup job and a check for the avaibility of the
nfs share could avoid this situation, but I think it is better to wait for 2.0
before making any request about.
More information about the pve-user