Search results

  1. T

    [SOLVED] unable to create an Linux VM with VirtIO drive since update

    Hello, the same issues at my side .... With virtio disks Ubuntu/Mint distros are failing at fresh install (one way or another) ... With IDE devices no issues at all .... No matter Enterprise or No-Subscription .... Prox 7.1 latest update ....
  2. T

    [SOLVED] dirty/new bitmaps

    OK .... it will transfer only the changed blocks ... understood ! but if it has to make dirty-bitmaps again , how does he do that ? What does it compare ? source<>destination or source<>previous-dirty-bitmap ? If destination has been moved over to another location and connected with...
  3. T

    missing replicate feature on volume 'local-lvm:vm-1001-disk-1' (500)

    @adaptation, lvm volumes do not have replication feature as the system told you ... VM that you want to replicate has to be put on zfs type of storage ... Since you have just one drive (per server) you will have to reinstall proxmox and choose zfs for your boot filesystem type ... or you...
  4. T

    file-level restore

    Yessss .. thank you , now I see where I checked it ... completely forgot ... Thank you , everything works now ... map --keyfile (path-to-file) BR Tonci
  5. T

    file-level restore

    [{"backup-id":"500","backup-time":1614971114,"backup-type":"ct","files":[{"crypt-mode":"encrypt","filename":"pct.conf.blob","size":295},{"crypt-mode":"encrypt","filename":"root.pxar.didx","size":4011809993},{"crypt-mode":"encrypt","filename":"catalog.pcat1.didx","size":905637},{"crypt-mode":"sign...
  6. T

    file-level restore

    Here it is : .. did not understand "code/tags" root@pbs03:~# proxmox-backup-client snapshots --output-format json --repository root@pam@localhost:8007:rn102...
  7. T

    file-level restore

    vm-301 is windows server
  8. T

    file-level restore

    Here it goes: ... if this was what you meant ... proxmox-backup-client snapshots --repository root@pam@localhost:8007:rn102 Password for "root@pam": ********** ┌─────────────────────────────┬───────────┬───────────────────────────────────── │ snapshot │ size │ files...
  9. T

    file-level restore

    Problem !!! On the other PBS setup I tried to ntfs mount drive but got this error message : root@pbs03:~# proxmox-backup-client map vm/301/2021-01-19T19:00:24Z drive-virtio0.img --repository root@pam@localhos t:8007:rn102 root@pbs03:~# Error: unable to decrypt blob - missing CryptConfig...
  10. T

    PBS backup faster than restore

    I noticed little strange (for me) disk activity on PBS: 1. I made vm backup and it lasts till 20h30. 2. at 20h35 I started garbage collection in order to free PBS from everything but this one vm backup. 3. I waited till 21h08 because of this blue "write" activity and assumed this belongs to...
  11. T

    PBS backup faster than restore

    I've setup new environment : baremetal PBS , and store consists of 4x2T (zfs raid10) 7k2 rpm :
  12. T

    PBS backup faster than restore

    Thank you for your explanation ... How can we "influence" chunk size ? What kind of setup would be best practice (optimal)? Can this chunk size be managed or it depends on the hardware (hard disk spinn/ssd) I od have server with 4 sata ports available and 4x8T sata hdds ... What would be...
  13. T

    PBS backup faster than restore

    I'm sure things are not trivial at all ... I can only presume that maybe number of snapshots affects restore time ... we are not talking of one archive vma file that is being read continuously ... here we have kind of "kaothic mosaic" spread overall the datastore (more than 65000 data-chunk...
  14. T

    PBS backup faster than restore

    Here is another try/compare : 1. this 20 Mbs restore is from PBS (virtualized on hostX) and it stretches through whole picture. 2. from 13h15 to 13h20 happens restore from netgear nfs server , so it's much faster than from PBS 3. from 13h40 to 13h50 vzdump archiveX is being copied from...
  15. T

    PBS backup faster than restore

    I installed PBS in VM and attached one virtio drive for datastore ... added datastore through GUI (storage(disks/...) etc. Everything works fine except that backup is cca 20% faster than restore (?!) ... and (traditional) restore from nfs-backup server (vzdump) is cca 3x faster and on...
  16. T

    backup register image failed: command error: unable to get shared lock

    Hello, I installed PBS in vm and attached NFS (ubuntu1804) as datastore. (mounted on /mnt/nfs1) Everything went straight forward, chunk-folders generated correctly, PBS attached to PVE, but backup failed like this: INFO: starting new backup job: vzdump 104 --storage PBS01 --mode snapshot...
  17. T

    [SOLVED] dirty/new bitmaps

    Thank you ... all clear !!! ... so shutting down VM and powering it on again "resets" bitmaps ? ... but restart not ? Ok it makes sense ... it would be ideal if bitmaps were always up-to-date with VM but this is also Ok
  18. T

    file-level restore

    Hi Lars, thank you very much for your hint that looks very promising and that's exactly what I needed ... a kind of gui-upgrade would help in the future of course :) 1. list snapshots ( that can be seen in gui , but cannot be copy-pasted) : proxmox-backup-client snapshots --repository...
  19. T

    file-level restore

    Unlike "aplication" VM's, file-storage VM's could have large images. My first experiences with PBS tell me that this actual concept seems to fit more for disaster-recovery scenarios than for file-level restore. Finally we have incremental backup out-of-the-box and that is what we were missing...
  20. T

    [SOLVED] dirty/new bitmaps

    I installed PBS and TrueNas as nfs-datastore. Setup went well w/o any issues. But after 1st full backup , the second/incremental one started with "creating new bitmaps": INFO: virtio0: dirty-bitmap status: created new INFO: virtio1: dirty-bitmap status: created new Fullbackup lasted 16h and...