Search Engine: Elastic

Article ID: 128672, created on Apr 14, 2016, last review on Jul 14, 2018

  • Applies to:
  • Operations Automation 6.0


Diskspace usage on VZ Backup node in OA under Services > Cloud Infrastructure > VPS Hardware Nodes > Backup Node > Stored VPS Backups shows:


While current usage is:

[root@vzlinbuckup01 ~]# df -h | grep vz
/dev/sda3       7.2T  6.4T  400G  95% /vz


There are a lot of corrupted backups without 'info' and 'metadata' files that cannot be managed by VZ Agent on the backup node.


  1. Synchronize VZ agent database to collect actual data of managed backups:

    # /opt/pva/agent/bin/vzbackupsync
  2. Acquire the list of corrupted backups by withdrawing (line-by-line) the list of 'good' backups (have 'info' file inside) from the list of all backups:

    # find /vz/backups/ -name info | sort > goodbackups
    # sed -r 's/.{5}$//' goodbackups > goodbackups_trimmed
    # ls -d /vz/backups/*/* | sort > allbackups
    # comm -3 allbackups goodbackups_trimmed > corrupt_backups
  3. Remove corrupted backups:

    # rm -rf `cat corrupt_backups`

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0

Email subscription for changes to this article
Save as PDF