If PVA Agent is configured to create TAR-based backups for containers, you may hit a timeout different from described in KB #8133.
~# time vzabackup localhost -e 1305 Starting backup operation for node 'host.server.net'... * Operation with the Container ct1305 is started * Backing up environment ct1305 locally * Operation with the Container ct1305 is finished with errors: The request was timed out. Backup operation for node 'vzlin02' failed: The request was timed out Backup failed real 30m30.999s user 0m0.223s sys 0m0.198s
PVA Agent configuration might contains the following settings with
backend set to 1 and no custom configuration for
~# echo 'cat //backend/../..|//processm' | xmllint --shell /var/opt/pva/agent/etc/vzagent.conf | grep '^<' <vzlin_backup_serializer> <configuration> <backend>1</backend> <enable_snapshot>1</enable_snapshot> <custom> <queue>0</queue> <heavy_timeout_limit>36000</heavy_timeout_limit> </custom> </configuration> </vzlin_backup_serializer> <vzlin_backup_serializer11> <configuration> <backend>1</backend> <enable_snapshot>1</enable_snapshot> <custom> <pool>0</pool> <queue>0</queue> <heavy_timeout_limit>82800</heavy_timeout_limit> </custom> </configuration> </vzlin_backup_serializer11> <processm> <configuration/> </processm>
30 minutes - it is 1800 seconds, the default timeout for commands execution with "processm" operator of PVA Agent.
Edit the PVA Agent configuration file to increase timeout. The configuration file can be found in the following locations:
- check KB #112499 if in doubts.
Initially the section for
processm does not specify any timeout:
<processm> <configuration/> </processm>
Change it to something like:
<processm> <configuration> <custom> <default_timeout>36000</default_timeout> </custom> </configuration> </processm>
Restart PVA agent on node:
#service pvaagentd restart