Article ID: 117833, created on Oct 10, 2013, last review on Apr 27, 2014

  • Applies to:
  • Virtual Automation 6.0

Symptoms

  1. When you select Infrastructure > HW node > Backups, existing backups are not shown;
  2. PVA agent restart helps temporarily:

    # pvaagent restart
    
  3. The backups from all servers are stored in the same folder on the same NFS share mounted to the same location as backups are stored, for example on the server with IP address 10.20.30.40 it is /vz/backups/:

    ># vzabackup --view-folder localhost
     path = /vz/backups/
     login =
    ># mount
    /dev/sda1 on / type ext4 (rw)
    proc on /proc type proc (rw)
    ...
    10.20.30.40:/mnt/share/nfs/PSBM on /vz/backups type nfs (rw,addr=10.20.30.40) 
    

Cause

In such setup, servers consider backups to be stored locally, because NFS share is considered to be a local resource.

When PVA Agent is restarted, or a backup task is run on the server for some virtual environment, the list of stored backups is sent to the PVA Management Node (all accessible backups on PVA Agent restart, or all container's backups on successful backup creation). PVA MN updates the list of backups for each container basing on its EID, and it considers backups to be stored on that server where the backups were created last time or where PVA Agent was recently restarted.

Resolution

Create a separate folder for each connected server, for example:

  • for node1:

    ># mount
    /dev/sda1 on / type ext4 (rw)
    proc on /proc type proc (rw)
    ...
    10.20.30.40:/mnt/share/nfs/PSBM/node1 on /vz/backups type nfs (rw,addr=10.20.30.40)
    
  • for node2:

    ># mount
    /dev/sda1 on / type ext4 (rw)
    proc on /proc type proc (rw)
    ...
    10.20.30.40:/mnt/share/nfs/PSBM/node2 on /vz/backups type nfs (rw,addr=10.20.30.40) 
    

Search Words

backups are not shown

nfs backups share

319940068c5fa20655215d590b7be29b 2897d76d56d2010f4e3a28f864d69223 0889ab60fa6494de107aa7338c3c38b6

Email subscription for changes to this article
Save as PDF