I saw you wrote that, but I don't really want to dist-upgrade... why are you suggesting it?
My intent was simply to get updates to any packages (like openssl) but it seems to have triggered a much bigger thing!
I'm afraid this was text book case of "impatience" - there is already a thread where dietmar suggestes
Seems you did not correctly upgrade - you miss package 'libpve-guest-common-perl'.
I did
]# apt-get install libpve-guest-common-perl
and apt-get update a few times and things are looking...
Hi All,
I've just done an apt-get upgrade and ended up with this
Job for pvedaemon.service failed. See 'systemctl status pvedaemon.service' and 'journalctl -xn' for details.
dpkg: error processing package pve-manager (--unpack):
subprocess installed post-installation script returned error...
Right, so if I change "agent: 1" to "agent: 0" and run "vzdump 102 --mode snapshot --storage mnt_backup_daily" (this is what I originally did before starting this thread) do you beleive the guest OS will lock or not? This is with the VM Running. No Agent.
This is such a time waste, scroll up to Tom writing "our qemu backup does NOT need a special guest OS tool".
So now we're agreed: ZFS and Suspend does NOT work (unless you install the agent on the guest os) ?
How do we establish that the guest did or did not lock... ? In the example below I could open a console to the 2008r2 VPS, but could not set the focus on any of the windows using the console.
If you feel the storage is relevant state how, I've tried both the options given above. My own...
It's not that I don't want to it's that it doesn't work as a replacement for the previous vzdump
Please be more specific about what exactly "our qemu backup and restore" is. I.e. A CLI command as requested. Using english words leaves too much room for ambigutity. A CLI copy an paste is both...
If anyone else hits this issue below is my current work around, if it transpires that I am right I'll document and post a link. It also shows (as proof of concept) that the issue is not resource constraint and shows clearly what I'm trying to acheive...
For each host in "qm list"
zfs snapshot...
The host has dual quad core procs > 2Ghz and you can see the drive info above... there is 48GB RAM.
Perhaps it would be more helpful to step through this. With the links you provided so far I have to repeat that the evidence (and my experience) is against what you say. I hope you're right...
PS: an interface graph says the iSCSI target is sustaining 500mbit/s (seq. read / write) - this isn't during the backup, but during a seperate operation on the same target.
This same hardware was perfectly good with 10X the load only a few hrs ago. It's not CPU / RAM / Harddisks when the VPS Guest locks up during a backup and that is the ONLY activity happening...
This is the source:
# pveperf /pmx01zfs
CPU BOGOMIPS: 34136.04
REGEX/SECOND: 893209
HD SIZE...
Hmm, well I'd like to beleive you, but my guests are locking... is there some debug information I can provide? It's a new install (today) following the howto for installing above Debian...
# pveversion -v
proxmox-ve: 4.2-64 (running kernel: 4.4.16-1-pve)
pve-manager: 4.2-18 (running version...
Well not really, they're all related... in the previous (as I used it) vzdump used LVM snapshots to get a consistent backup without causing lock on the guest OS. No special tool was needed on the guest OS.
It seem there is no equivalent for this in proxmox 4 on ZFS?
vzdump doesn't use ZFS...
OK, so it seems that whilst in theory this works, in practice it doesn't. The Guest OS need non trivial modification (qemu-ga) so there is no usable migration path to v4.... is there any way to get a ZFS snapshot backup working (I don't mind having to script it myself, but I'm sure I'm not the...
Ah - ok, this is beginning to make sense now... I ticked the "Qemu Agent" box and rebooted (power cycled) 2 VPSs and started the back up again. I can now console in to the VPS, but the mouse doesn't track and still seem hung (but I do get a console).
Am I again missing something? Does the...
This is an excerpt from the log...
INFO: starting new backup job: vzdump --quiet 1 --mailnotification always --compress 0 --all 1 --mode snapshot --storage mnt_backup_daily
INFO: Starting Backup of VM 102 (qemu)
INFO: status = running
INFO: update VM 102: -lock backup
INFO: VM Name: XXXXXXXXXXX...
I'm using the UI defined backup and found the KVM hosts are unresponsive during a backup run... I tested this a few days ago and thought it worked, but on my limited IOPS test set up things were a little dicey...
I've installed PMX4 on a node that was 3 before (new install, not upgrade) and the...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.