Recent content by hefferbub

Perfect. Thanks so much. PBS is a great piece of technology!

Thank you so much. I thought I had seen documentation on that, but could not find it.

I love PBS, and I'm using it for a multi-tiered backup strategy. I have a 2 node PVE 6.3 cluster where one is the primary that normally runs all VMS and the other is a backup that receives replicated VMs and also runs PBS. I also have a Synology NAS located in another building where I sync the...

I have a 2 node cluster running 6.3 where I have a primary server than normally runs all the VMs and a smaller backup server intended to be ready to run those VMs in case of planned or unplanned downtime on the primary. I do a regular replication (every 2 hours) of all critical VMs to the...

I used these excellent instructions to sync a datastore to a shared folder on a Synology NAS using the following command to mount it on the PBS server: mount -t cifs "//172.16.0.66/foobar" -o username=MYUSER,password=MYPASS,vers=2\.0 /mnt/foobar. I then followed the rest of your instructions...

I love the replication feature with non-shared ZFS storage! It is a thing of beauty to watch these rapid offline migrations which only need to transfer a modest differential of data. It is just what I hoped for to allow for quick failover I manage myself (and avoid the sometimes-arcane...

Thanks Spirit. I was able to test your suggestion, and it does work to use pve-zsync outside of a cluster to a new 6.2 machine. Here is what I did: Create a new Zvol (volume) in the default zpool on the target server: zfs create rpool/mybackups On source server ensure that there is a...

Thanks. That makes a lot of sense, although I still need to shutdown and backup the VMs on the original server in case the update goes south. If I have the new server up, non clustered, I could back up more quickly to it somehow. Perhaps using PVE-Zsync? What makes sense to you?

I have a stand-alone server running v4.4 with ZFS and I would like to move it to 6.2 with minimal downtime, as well as set things up for easier future maintenance and upgrades. It has a number of VMs totaling less than 500 GB of storage, but my backup times (to a Synology NAS) are running close...

I disabled that on a subsequent test, (and also changed ionice to 5) and it seemed to make no difference. And isn't that limit equal to 50 megabytes per second? I'm getting 12. Any other thoughts? Thanks!

I have a fairly lightly loaded server running Proxmox 4.4-5. It is a Dual Intel Xeon E5645 Six core/12 thread with 96GB, with a 4 drive ZFS RAID. My PVEPerf numbers are: CPU BOGOMIPS: 116252.16 REGEX/SECOND: 1143709 HD SIZE: 3280.12 GB (rpool/ROOT/pve-1) FSYNCS/SECOND...

I finally did the server switchover, and it all worked beautifully. ZFS rocks! The one minor glitch was that the system at first failed to bring up any of the network interfaces. The ports would not even light up. It turned out, I needed to delete the contents of this file...

Ah, I finally figured it out! On the hp 1920 switch, when I created the "Link Aggregation", I created it as "static". It should have been "dynamic" which enables the LACP protocol. Seems fine now. Thanks for all suggestions.

Thanks for those excellent diagnostic suggestions. I attached the results, which look OK to me: The weird thing is, I can ping this IP from the switch it is connected to. The weirder thing is, I can connect to the Proxmox web interface at this IP from my iPad, but not from a Mac or Windows...