From: Tom Weber <pve@junkyard.4t2.com>
To: PVE development discussion <pve-devel@pve.proxmox.com>
Subject: [pve-devel] Race with PBS Backup of GW running as VM in PVE
Date: Tue, 27 Jul 2021 14:35:53 +0200 [thread overview]
Message-ID: <3fe0a1fb-1184-554b-c464-96915c987a24@junkyard.4t2.com> (raw)
Hi,
with a Setup like
PBS <--->| GW VM |<--> PVE Host
where the GW VM is running on the PVE Host and connecting the PVE Host with
the PBSever, I seem to run into a race condition when trying to
snapshot-backup the GW VM to the PBS Server.
The snapshot appears to freeze the GW VM just the moment the PVE Host tries
to establish the connection to the PBS:
INFO: starting new backup job: vzdump 121001254 --storage pbs-XXX --remove 0
--node XXX-01 --mode snapshot
INFO: Starting Backup of VM 121001254 (qemu)
INFO: Backup started at 2021-07-27 13:48:12
INFO: status = running
INFO: VM Name: XXX.gw-XXX
INFO: backup mode: snapshot
INFO: ionice priority: 7
INFO: creating Proxmox Backup Server archive 'vm/121001254/2021-07-27T11:48:12Z'
ERROR: VM 121001254 qmp command 'backup' failed - backup connect failed:
command error: error trying to connect: tcp connect error: No route to host
(os error 113)
ERROR: Backup of VM 121001254 failed - VM 121001254 qmp command 'backup'
failed - backup connect failed: command error: error trying to connect: tcp
connect error: No route to host (os error 113)
INFO: Failed at 2021-07-27 13:48:47
INFO: Backup job finished with errors
TASK ERROR: job errors
on a "Fast" Setup meaning fast Hosts and LAN, it works sometimes, sometimes
it fails.
on a "Slow" Setup meaning non powerfull Host Hardware and VPNs via LTE, this
always fails.
This is with PVE 6 and PBS 1.1
Any ideas to work around this? Not sure if I'd consider this a bug.
Regards,
Tom
reply other threads:[~2021-07-27 12:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3fe0a1fb-1184-554b-c464-96915c987a24@junkyard.4t2.com \
--to=pve@junkyard.4t2.com \
--cc=pve-devel@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.