Search results

Just to report : even local restore is boosted. PBS alongside PVE , Restore to Datacenter SATA SSD from Datacenter SATA SSD 170G used data of 400G virtual disk Speeds are over SATA speeds because writing zeroes seems accounted/ PVE 8.4.0 restore was 630MB/s ( ~11 minutes) ( so real speed was...

GC job must be set on each PBS. Prune should be set on each PBS, Snapshot sync deletions called "Remove vanished" isn't safe from my point of view. See : https://forum.proxmox.com/threads/garbage-collection-on-synced-targets-necessary-if-remove-vanished-is-checked-eom.158266/

another way, with nowadays systemd versions, shipped with pve 9 , is to use MAC based altname, like enx123456789012 where 123456789012 is the MAC address.

just to clarify, MDF files as SQL backups by PVE/PBS are valid, because rely on SQL VSS agent within Windows guest. Only granular restore is missing. Full MDF need to be downloaded/restored, attached as temporary to recovery specific DB.

edit : myself test with a PBS v3. 2 grant user permission is required to allow API token Read Datastore for Sync job. (perhaps fixed in newer version) https://pbs.proxmox.com/docs/user-management.html#api-tokens

no, if compression not used. As PBS deduplication does not rewrite existing data.

it should work, but as you have a problem, the idea is to do a new install in BIOS.

once Legacy BIOS selected, don't forget to set Boot order too. VirtIO v285 does not support 2012 r2, use older version like v173.

"SharedFolder" in your screenshot is actually *local* because mount failed due to typo

missing "a" in ShredDir ? To fix the missing iso ? edit: double check your keyboard, If letters are missing or mixing in configuration as in this thread, errors will be excepted.

Run tailscale status and examine the connection information for the peer device. If the output contains "direct", the connection is direct. If the output includes "relay", the connection is relayed through a DERP server. If the output includes "peer-relay", the connection is relayed through a...

we can't confirm each step neither detail each step. backup as safety , always. but restore can be skipped : from Node \ Shell , you can zpool detach one 1.8TB , this breaks ZFS mirror , but will continue to work , no interruption. then "Wipe disk" from PVE UI \ Node \ Disks , the correct disk...

of course. it's not really a migrate.

no, changing FS ( zfs / Lvmthin / btrfs) implies formatting.

ZFS is slower than vmware FS (as it does raid, checksum integrity...) . Try with Lvmthin

https://web.archive.org/web/20250809215052/https://blog.jeff-media.com/solution-creating-a-datastore-on-proxmox-backup-server-fails-at-chunkstore-create/

Have you checked I/O per VM ? Have you rebooted host to run the latest kernel ? No backups running ?

VM#1 speeds are not the real one as it's RAM speed thanks to ZFS ARC. test for longer like CDM 1 x 16 GiB. or reboot host to reset ZFS ARC cache.

What about the SSD exact model ? is ZFS used ?

https://forum.proxmox.com/threads/windows-server-2025-unattended-iso-issues-known.164463/post-805659