I have ran into an issue recently that I haven't been able so find a solution on (Google seems to turn up no results).
My node has 4 VM's (2 Windows, 2 Linux) that are on an LVM storage made up of a raid 10 array. One of my drives had failed and I replaced it, rebuilding went fine and...
vzdump doesn't correctly handle sparse files.
I have 459G sparse file, that happens because I've implemented SSO based on FreeIPA, and users usually have high user id, and lastlog creates sparse file which gets as big as 459G.
ipadmin@proxy:/var/log$ ls -slh lastlog
16K -rw-r--r-- 1 root root...
wir haben zwei Server:
Quellserver: Proxmox 4.1
Zielserver: Proxmox 4.2
Wir wollten die VMs vom Quellserver auf den Zielserver übernehmen, den Quellserver updaten und anschließend zu einem Cluster hinzufügen.
Bei den wiederhergestellten Daten (LXC VMs) auf dem Zielserver wurden aber...
I first noticed this when using VZDump to backup a VM sitting on a ZFS filesystem to an NFS share on a different host. I am at the moment trying to migrate a 1 TB virtual disk from a Zpool that I wish to destroy and rebuild. The NFS target is backed by a ZFS file system on a fast SSD...
Sometimes the VM stops right after the backup is started.
VM is Windows 2003 Web Edition SP2 x86
- Windows's system.log just says about unexpected shutdown
- Proxmox logs show nothing but vzdump error about not running VM
What else can I check? Any help is appreciated.
We actually face a problem for scheduling backups of lxc containers with a second raw disk as a mountpoint (mp0).
vzdump seems to ignore this and only backup the raw rootfs. Even with options like backup=1 or backup=yes specified.
Here is the container conf:
It seems to me that backing up a lxc excludes some paths per default as mentioned, but not explicit called, in . But in my opinion excluding /var/log/* MAY be a bad idea as this excludes everything - although some programs are expecting existing log paths after restoring, apache2 for example...
I installed vzdump and suddendly the proxmox web interface disappeared :
( this is the source code of what I can see now)
<meta http-equiv="/pve2/ext4/resources/css/ext-all.css" />
<link rel="/pve2/css/ext-pve.css" />...
I have a proxmox 3 node cluster running version 3.4.10.
A few days ago certain VMs started to fail Vzdump backup with the error:
vma_queue_write: write error - Broken pipe
I pulled the affected VM out of HA and did a shutdown and startup and put them back into HA which fixed one of...
I'm having some troubles using the backup system (vzdump) with a remote location. Currently I'm trying to backup 5 virtual machines to my remote location. Two of them succeeded, three of them failed.
The errors are all the same 'vma_queue_write: write error - Broken pipe'...