Backup job finished with errors ?

Discussion in 'Proxmox VE (Deutsch)' started by fpausp, May 11, 2019.

  1. fpausp

    fpausp Member

    Joined:
    Aug 31, 2010
    Messages:
    247
    Likes Received:
    6
    Bekomme zum zweiten mal den Fehler nachdem die letzte Maschine VM 129 via NFS auf den Backupserver (Proxmox NFS Server) geschrieben wurde...

    Code:
    INFO: status: 85% (110040776704/128853213184), sparse 71% (91862376448), duration 281, read/write 1580/0 MB/s
    INFO: status: 89% (114896273408/128853213184), sparse 75% (96717873152), duration 284, read/write 1618/0 MB/s
    INFO: status: 92% (119747182592/128853213184), sparse 78% (101568782336), duration 287, read/write 1616/0 MB/s
    INFO: status: 96% (124709961728/128853213184), sparse 82% (106531561472), duration 290, read/write 1654/0 MB/s
    INFO: status: 100% (128853213184/128853213184), sparse 85% (110674800640), duration 293, read/write 1381/0 MB/s
    INFO: transferred 128853 MB in 293 seconds (439 MB/s)
    INFO: stopping kvm after backup task
    INFO: archive file size: 13.74GB
    INFO: delete old backup '/mnt/pve/pvestor01/dump/vzdump-qemu-129-2019_05_04-03_24_20.vma.lzo'
    INFO: Finished Backup of VM 129 (00:05:00)
    INFO: Backup finished at 2019-05-11 02:23:02
    INFO: Backup job finished with errors
    
    TASK ERROR: job errors


    Die vzdump-qemu-129-2019_05_04-03_24_20.vma.lzo wurde offensichtlich gelöscht:

    Code:
    root@pvestor01:/data/pvestor01/dump# ls -alih vzdump-qemu-129-2019_0*
    187 -rw-r--r-- 1 root root 5.8K May  5 03:43 vzdump-qemu-129-2019_05_05-03_38_08.log
    199 -rw-r--r-- 1 root root  14G May  5 03:43 vzdump-qemu-129-2019_05_05-03_38_08.vma.lzo
    368 -rw-r--r-- 1 root root 6.1K May  6 03:54 vzdump-qemu-129-2019_05_06-03_49_37.log
    363 -rw-r--r-- 1 root root  14G May  6 03:54 vzdump-qemu-129-2019_05_06-03_49_37.vma.lzo
    343 -rw-r--r-- 1 root root 6.1K May  7 03:48 vzdump-qemu-129-2019_05_07-03_43_01.log
    340 -rw-r--r-- 1 root root  14G May  7 03:48 vzdump-qemu-129-2019_05_07-03_43_01.vma.lzo
    540 -rw-r--r-- 1 root root 6.1K May  8 03:48 vzdump-qemu-129-2019_05_08-03_43_28.log
    538 -rw-r--r-- 1 root root  14G May  8 03:48 vzdump-qemu-129-2019_05_08-03_43_28.vma.lzo
    604 -rw-r--r-- 1 root root 6.0K May  9 03:47 vzdump-qemu-129-2019_05_09-03_42_13.log
    757 -rw-r--r-- 1 root root  14G May  9 03:47 vzdump-qemu-129-2019_05_09-03_42_13.vma.lzo
    386 -rw-r--r-- 1 root root 6.1K May 10 02:24 vzdump-qemu-129-2019_05_10-02_19_48.log
    385 -rw-r--r-- 1 root root  14G May 10 02:24 vzdump-qemu-129-2019_05_10-02_19_48.vma.lzo
    560 -rw-r--r-- 1 root root 6.0K May 11 02:23 vzdump-qemu-129-2019_05_11-02_18_02.log
    559 -rw-r--r-- 1 root root  14G May 11 02:23 vzdump-qemu-129-2019_05_11-02_18_02.vma.lzo
    
    Hat jemand einen Vorschlag?
     
  2. dietmar

    dietmar Proxmox Staff Member
    Staff Member

    Joined:
    Apr 28, 2005
    Messages:
    16,445
    Likes Received:
    304
    Das log is nicht komplett und enthält keine Fehler ...
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    Leon Gaultier likes this.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice