Search results

I got this error in the backup log INFO: starting new backup job: vzdump 104 103 102 100 106 ... ERROR: Backup of VM 104 failed - unable to find VM '104' I checked the backu settings and vm 104 is not mentioned. I remember I deleted a vm time ago. I guess it was listed in the backup job...

Great, it was missing that. Thank you!

Proxmox 4.2-2/725d76f0 I added 1G SCSI disk and tried to install driver from latest virtio iso (1.2.6). Windows doesn't find the driver. No matter if I select the whole unit D: or select the path as shown below. qm config 100 agent: 1 balloon: 4096 boot: cd bootdisk: ide0 cores: 4 cpu: host...

I opened the bug a suggested. Thank you.

I think it would be nice if it was enabled only when 'VZdump backup file' gets checked. May that be "fixed" on a next release?

Hi all, I wonder if the filed Max Backup has any meaning when adding new storage, if the selected storage type is not 'VZdump backup file'.

Great, it worked also on windows! Thank you all for you support! lvdisplay /dev/pve-big/vm-100-disk-1 --- Logical volume --- LV Path /dev/pve-big/vm-100-disk-1 LV Name vm-100-disk-1 VG Name pve-big LV UUID...

I success with a linux guest and scsi driver scsi0: big:vm-103-disk-1,cache=writeback,discard=on,size=30G scsihw: virtio-scsi-pci I'll try also with windows asap.

I'm using virtio driver. I notice anyway that you config says scsihw: virtio-scsi and mine scsihw: virtio-scsi-pci Any idea about the difference and if it may influence discard?

Hi, I checked the maintenance schedule and it was run last time this morning. I also started it manually as you can see in this image. My server language is set in italian. I used this guide as reference. Mapped size is stll 99% even after running maintenance.

Ops, I forgot to enable options discard the last time I removed and re-added the vdi to be sure it was using virtio controller. Now I checked it twice :-) Anyway, after the stop and restart of the guest with discard option enabled, the "Mapped size" is still 99%. qm config 100 | grep...

Here it is qm config 100 agent: 1 balloon: 2048 boot: c bootdisk: ide0 cores: 8 cpu: host ide2: local:iso/virtio-win.iso,media=cdrom,size=152204K keyboard: it localtime: 1 memory: 6144 name: win2012 net0: e1000=0E:4C:07:AF:81:06,bridge=vmbr0 numa: 1 ostype: win8 scsihw: virtio-scsi-pci smbios1...

I read the documentation and I get confused because pve-admin guide says while shrink qocw2 file guide says . I find it more logic to be virtio-scsi the required controller. Please, help me finding the way to discard the unused blocks from this thin volume: LV Path...

As of now, we are two :-) Let's see if other users will be interested in that. Thank you.

Hi @mmenaz, till now I never tought about a 'selective restore'. This may be a bit more tricky to achieve because it would probably add more complexity. Usually I do the opposite of your: I have a guest vdi with the o.s. and programs and a second vdi storing files. I backup daily the first vdi...

Thank you for your reply. Right now there are no other options that restore everything on a single storage. My question may be changed like this: Would it be possible to add a selective restore as new feature? May this interest other users? I think it would be cool if the restore process, asks...

Hi all, I have a guest with 2 vdi. The first is hosted on a storage name ssd. The second is hosted on a storage named hdd. Not difficult to guess why those names. I made a backup of this guest. When I restore the backup, I can select a single storage as destination. The best thing would be to...

How discard generally work: consider a logical volume (lv) of a thin pool. Once created a lv, the allocated spaced is 0. I create a filesystem on in (i.e. ext4), add some data till it allocates 5G. I remove 2G of files but the allocated space is still 5G. By fstrim, it will de-allocate/discard...

@mbaldini there's no need to unlock the guest. The problem is that the guest got killed by proxmox when I stopped running the backup.

pveversion -v proxmox-ve: 5.0-20 (running kernel: 4.10.17-2-pve) pve-manager: 5.0-30 (running version: 5.0-30/5ab26bc) pve-kernel-4.10.17-2-pve: 4.10.17-20 pve-kernel-4.10.15-1-pve: 4.10.15-15 libpve-http-server-perl: 2.0-6 lvm2: 2.02.168-pve3 corosync: 2.4.2-pve3 libqb0: 1.0.1-1 pve-cluster...