Article ID: 123975, created on Dec 18, 2014, last review on Jun 17, 2016

  • Applies to:
  • Virtuozzo
  • Virtuozzo containers
  • Virtuozzo hypervisor
  • Virtual Automation

The first recommendation when dealing with any kind of backup/restore problems - update Parallels Virtual Automation Agent (and PVA Management node if it is configured) to the latest version.

The available versions (and installation instructions) can be tracked using the following knowledgebase article:

Parallels Virtual Automation builds, releases, and supported virtualization products

Table of contents

General Troubleshooting steps

  1. Update PVA Agent (and PVA Management node if it is present) to the latest build;
  2. In case the node is registered in PVA Management node, unregister it and attempt the backup/restore process while the node is a stand-alone host;
  3. In case the container is backed up to (restored from) some remote location, attempt to create a local backup (move the backup to the local node and attempt a local restore);
  4. Try to backup (restore) some other containers on the node to confirm whether the issue happens for all containers on the node or a particular container (ideally, create a small empty test container and test the backup/restore on it);
  5. Confirm which backend is configured for the backup procedure - check the "<backend>" tag in the PVA Agent configuration file (default location is "/var/opt/pva/agent/etc/vzagent.conf" or "/vz/pva/agent/etc/vzagent.conf"). Value "0" stands for Acronis backend, "1" - for "tar"-based backups. If "tar" is chosen, it is recommended to switch the backend to Acronis (change the configured "<backend>" value to "0" and restart the PVA Agent: "# pvaagent restart");
  6. Run the failing task using "time" utility (e.g "time vzabackup localhost -e 101"). If it fails after some round time resembling a default timeout (e.g 36000 seconds) - find and increase the configured timeout value (in the configuration of the PVA Agent or PVA Management node if it exists. Increase all related timeouts. Locations of the configuration files can be found using this article).
  7. Disable snapshot creation in the PVA configuration and try the backup operation again. Instructions on disabling snapshots can be found in the 'Resolution' section of this article. (Note: if helps, disabling snapshots should be considered as a workaround and not the permanent solution.)
  8. Check if there are any recent core dump files in "/var/opt/pva/agent/dumps" folder, correlating with the time of the failing backup/restore task (if there are any, it is recommended to contact Parallels Technical Support for further investigation);
  9. Check the log files on the node ("/var/log/messages" and "dmesg" output for Linux and EventViewer logs for Windows). If there are any NTFS or I/O error messages (any messages indicating hard disk or filesystem corruption), - fix the problems on the node side before proceeding with the backup/restore;
  10. Increase PVA Agent log level, analyze the error messages collected with increased logging.

Check the obtained error messages against the list of know problems/misconfigurations that can be found below

Back-end (Acronis) problems

The majority of Acronis-related problems are represented by a similar error message:

Backup operation for node "host.server.com" failed: Failed to perform the file backup 
 Acronis Error: Module=0 Code=0, Tag=0, 
 Backup failed 

The "Acronis Error: Module=0 Code=0, Tag=0" error can be caused by several different issues/misconfigurations. Additionally, it can conceal the original error.

To confirm the actual error, increase the PVA Agent log level to 5 and reproduce the issue. Instructions on changing the log level (along with instructions on locating the PVA Agent log files) can be found in "Parallels Virtual Automation troubleshooting" article. After getting the necessary information do not forget to decrease the PVA Agent log level back to the default value (3).

In case backup fails with the "Acronis Error: Module=0 Code=0, Tag=0" error message, narrow down the problem using the additional symptoms and use the appropriate solution:

  • 8133 The backup fails after a long time (for example, in 10 hours). The VZFS container which is being backed up has a huge amount of inodes (> 1000000. The amount of inodes can be checked using "vzquota stat CTID" command)
  • 113801 Container in question uses old (pre PVC 4.0) layout:

    # ls -al /vz/privae/101/
    total 28 
    drwxr-xr-x 7  root root 4096 Feb 20 2011  .
    drwxr-xr-x 55 root root 4096 Apr 23 11:36 ..
    drwxrwxrwx 2  root root 4096 Aug 31 2007  cow
    drwxr-xr-x 22 root root 4096 Apr 2  20:39 root
    drwxr-xr-x 6  root root 4096 Aug 31 2007  templates
    lrwxrwxrwx 1  root root 7    Jul 13 2007  VERSION -> 005.003
    drwxr-xr-x 2  root root 4096 Feb 7  2011  .vza
    drwxr-xr-x 2  root root 4096 Feb 20 2011  vzagent
    

    example of new layout:

    # ls -al /vz/private/101
    total 36
    drwxr-xr-x 6  root root 4096 Apr 23 12:50 .
    drwxr-xr-x 55 root root 4096 Apr 23 11:36 ..
    drwxr-xr-x 2  root root 4096 Feb 13 20:57 dump
    drwx------ 6  root root 4096 Sep 21 2011  fs
    -rw-r--r-- 1  root root 0    Feb 13 20:57 .lck
    -rw-r--r-- 1  root root 22   Apr 11 20:15 .owner
    -rw------- 1  root root 3408 Apr 25 05:10 quota.fs
    drwxr-xr-x 2  root root 4096 Feb 13 20:57 scripts
    lrwxrwxrwx 1  root root 12   Apr 11 20:14 templates -> fs/templates
    -rw-r--r-- 1  root root 768  Apr 23 12:50 ve.conf
    lrwxrwxrwx 1  root root 1    Apr 11 20:14 .ve.layout -> 4
    drwxr-xr-x 2  root root 4096 Feb 13 20:57 .vza
    
  • 113802 "/tmp" folder/partition does not have enough free space to store the B-tree data for the container's filesystem.

  • 118500 Backup folder in located on NFS share. Increasing PVA log level to 4 shows the following errors in "/var/log/pva/agent/yyyy-mm-dd-vzagent.log":

    Acronis Error: Module=4 Code=20, "Access to the file is denied."{$module="ERROR_MODULE_NAME"}, Tag=4440164880728584274,K:/574/file/unix/posixsp.cpp:Open:468
    Acronis Error: Module=4 Code=23, "Failed to lock the file."{$module="ERROR_MODULE_NAME"}, Tag=4440164880728583947,K:/574/file/unix/posixsp.cpp:DoLockFileHandle:141
    Acronis Error: Module=0 Code=65521, "Input/output error"{code=5}{$module="ERROR_MODULE_NAME"}, Tag=bd28fdbd64edb900,K:/574/common/error.cpp:AddPosixError:142
    /opt/pva/agent/lib/libVZLBackup.so.6.0 (VZL::setAcronisErrorMessage(char const*, Common::Error const&) + 0x589) [0x7ff256b24bcf]
    T=15:37:14:333; L=(dbg); PID=36294; TID=7ff249094700; P=VZLBackup [translateAcronisErrorCode] Calling [int VZL::<unnamed>::translateAcronisErrorCode(unsigned int)]
    T=15:37:14:333; L=(dbg); PID=36294; TID=7ff249094700; P=VZLBackup [endCommand] [VZLClientDataExchange::endCommand] Got Acronis Error.
    Acronis Error: Module=4 Code=20, "Access to the file is denied."{$module="ERROR_MODULE_NAME"}, Tag=4440164880728584274,K:/574/file/unix/posixsp
    
  • 113794 "/vz" volume is located on an iSCSI partition:

    # mount | grep vz | grep mapper
    /dev/mapper/mypvcserver on /vz type ext3 (rw,_netdev,noatime)
    

    ("_netdev_" mount option is the indicator of an iSCSI drive)

  • 122274 "/vz/" partition is located on a multipath device:

    # dmsetup table
    storage01-data01: 0 1363169280 multipath 1 queue_if_no_path 0 1 1 round-robin 0 1 1 8:16 10
    storage01-data01p1: 0 1363163382 linear 253:2 63
    VolGroup00-LogVol01: 0 69992448 linear 8:2 215220608
    VolGroup00-LogVol00: 0 215220224 linear 8:2 384
    
    # df -h /vz
    Filesystem            Size  Used Avail Use% Mounted on
    /dev/mapper/storage01-data01p1
                          640G  455G  154G  75% /vz
    
  • 123962 The similar messages can be found in "/var/log/pva/agent/yyyy.mm.dd-vzagent.log" after increasing PVA Agent log level:

    Acronis Error: Module=4 Code=14{$module="ERROR_MODULE_NAME"}, Tag=17448149215251209819,/usr/include/acronis/file/dir.h:IOCTL:185
    
    T=18:54:31:233; L=(udf); PID=62402; TID=7f5a3c786740; P=VZLBackup [onAcronisEvent] Acronis reports: module 4, error 25
    

Other Acronis error codes:

  • 119930 Backup restoration fails with "Acronis Error: Module=4 Code=13" message
  • 120659 "Acronis Error: Module=4 Code=17". Backup restoration fails with a "Restore failed: Can't open archive" error message. Similar messages can be found in "/var/log/pva/agent/yyyy.mm.dd-vzagent.log" log:

    T=09:30:48:294; L=(err); PID=50855; TID=7f6772d40760; P=VZLBackup [setAcronisErrorMessage] [VZLClientDataExchange::endCommand] Got Acronis Error.
    Acronis Error: Module=4 Code=17, "Specified file does not exist."{$module="ERROR_MODULE_NAME"}, Tag=4440164880728584258,K:/569/file/unix/posixsp.cpp:Open:452
    Acronis Error: Module=0 Code=65521, "No such file or directory"{code=2}{$module="ERROR_MODULE_NAME"}, Tag=bd28fdbd64edb900,K:/569/common/error.cpp:AddPosixError:142
    ...
    T=09:30:48:309; L=(udf); PID=50855; TID=7f6772d40760; P=VZLBackup [onAcronisEvent] Acronis says: Failed to open the file private.tib for read: 262,162.
    T=09:30:48:310; L=(wrn); PID=50855; TID=7f6772d40760; P=VZLBackup [open] Can't open archive
    

Acronis errors on Parallels Virtuozzo Containers for Windows:

  • 113726 A backup of a container with VSS-enabled SCSI disks fails with "Acronis Error: Module=10 Code=0{=0}, Tag=f22447445b0f1eae" and "Acronis Error: Module=7 Code=3, "Read error"{=0}, Tag=0" errors
  • 115737 A backup task over the network to a shared folder fails; at the same time, a local backup completes successfully. In PVA Agent logs, you can find similar errors:

    P=VZLBackupManagerLocal [execute] [VZLEnvBackupOperation::execute] Failed to backup Environmeent 51a60b98-b4da-438e-ae51-e4940558c093, Failed to backup partition
    Acronis Error: Module=7 Code=4, "Write error"{=0}, Tag=0
    Acronis Error: Module=4 Code=3, "Error writing the file."{function="WriteFile"}, Tag=7ceb2cdc9fb1200f
    Acronis Error: Module=0 Code=fff0, "The specified network name is no longer available.
    
  • 10036 Container backup initiated from POA fails with a similar error message:

    -1 : Failed to backup partition
    Acronis Error: Module=7 Code=4, "Write error"{=0}, Tag=0
    Acronis Error: Module=4 Code=e, "Operation is not supported."{=0}, Tag=f22447445b0f1f6a"
    
  • 1401 Backup of a particular container fails with the similar error message:

    Backup operation for node 'vz' failed: Failed to backup partition
    Acronis Error: Module=7 Code=33, "Unable to create volume snapshot"{=0}, Tag=0
    Acronis Error: Module=10 Code=0{=0}, Tag=f22447445b0f1f54
    
  • 115376 Backup fails with the following error:

    Acronis Error: Module=7 Code=4, "Write error"{=0}, Tag=0
    Acronis Error: Module=4 Code=3, "Error writing the file."{function="WriteFile"}, Tag=7ceb2cdc9fb1200f
    Acronis Error: Module=0 Code=fff0, "Not enough server storage is available to process this command."{code=ffffffff8007046a}, Tag=bd28fdbd64edb816`
    
  • 111687 Container backup fails with the following error message:

    ...
    Backup operation for node 'pvcfw-server' failed: Plugin was not loaded
    Backup failed
    

Back-end (tar) problems

  • 122008 Container backup fails with timeout after 30 minutes: "Backup operation for node <...> failed: The request was timed out"
  • 117797 Container cannot be restored with "/bin/vztar: Cannot rename <...> to <...>" error message
  • 111755 Container backup fails with "Unable to resolve Virtuozzo Server hostname" error message

Template-related issues

  • 119874 Container restoration fails with "Failed to check template consistency, code 52" error message.
  • 117136 Container restoration fails with "Failed to check template consistency, code 70" error message.
  • 119308 Container restoration fails with "Failed to check template consistency, code 1" error message.
  • 122296 Container restoration fails with "Application template <...> is not installed" error message

PVA Management node related issues

  • 121861 Container restoration fails with "Restore failed: Access is denied" error message

Backup listing problems

  • 119951 "vzarestore -l" does not show any existing backups on the node after running "vzabackupsync"
  • 123207 "vzarestore -l" does not show the container backup that was manually moved to the node

Miscellaneous

  • 122123 Container restoration fails with "_No suitable backup to restore_" message
  • 118784 Backup creation hangs and the container is inaccessible
  • 120176 Backup (or restore) operation fails with "The request was timed out"
  • 115056 Load average on the node is very high during backup creation

Search Words

パラレルス virtuozzo backup cli 確認

# prlctl backup-delete -t 715ce51d-d657-485e-be04-7cbf4fb0cbad Delete the backup {715ce51d-d657-485e-be04-7cbf4fb0cbad} Failed to delete the backup: Failed to back up the virtual machine due to an internal error. Please try again. If the problem persists, contact your system administrator for assistance.

backup

backup/restore

restore

a26b38f94253cdfbf1028d72cf3a498b 2897d76d56d2010f4e3a28f864d69223 d02f9caf3e11b191a38179103495106f 319940068c5fa20655215d590b7be29b 0dd5b9380c7d4884d77587f3eb0fa8ef

Email subscription for changes to this article
Save as PDF