Search results

PBS is up and running since 17-10-2020. It does however have some big tasks to do, and it seems that the webservice becomes unresponsive every now and then while running those tasks (verify, garbage collect, prune). I don't know why. Maybe there is a limit on the amount of threads, maybe the...

There are chunks being marked bad for a reason unknown to me. I'm trying to find out why, but can't think of anything. Please do remember that this is a beta product and service. Do not rely on it as your primary backup (yet!)!

https://bugzilla.proxmox.com/show_bug.cgi?id=3078

Yes. According to the PBS verify, your backups are bad. A verify has renamed the chunks that are bad, and thus you get 'No such file or directory'. It's kinda weird that you are able to start restoring from a failed backup. I'll create a bug for that.

No, I did not (obviously).

This is a datastore that has not existed on ZFS. So a simple ext4 on LVM. If you want, I can grant you access to the machine so you can investigate. I'm pretty sure there's nothing special, but maybe I'm missing something completely.

I have a lot of backups failing on the beta PBS. The verify complains that the CRC checksum is incorrect. Is there a way I can check this myself?

Ok. So I still do not have a clue why things with rsync went south. But I do find something that's curious about the verify-logic. So lets take chunk 16fde23122afe9559c9f6d3109f693fa85574d8d758123010b2e83c88f863db9 (and disregard HOW this got broken, but only look at steps afterwards). During a...

This is a known issue and is pending decisions from Proxmox whether or not they want to use _ as a delimiter. Because we use _ in the datastore, the timestamp-parser gets confused. https://bugzilla.proxmox.com/show_bug.cgi?id=2889

Ok, so I missed some messages.. :) For starters, sorry about the corruption. I did not expect that. I finished the last rsync this afternoon (which explains @Felix. his downtime this afternoon). Indeed, the PBS is much snappier. The file @eider is missing indeed is not there. @fabian which...

So, syncing is done. Somehow (never seen this in my life) with rsync not all files properly synced. Which wasn't intentional, but might serve as a nice test to see how PBS handles failed verification... Performance seems better, but there are still two datastores syncing from ZFS which might...

Yes, very cool. Please note though that the log-device is mostly unused due to the way PBS writes. Caching for these amounts of data that is rarely read is not very useful. By the time that you need the data again, some other data has probably pushed the old data out of the cache. The special...

ZFS on local storage will probably perform comparable to LVM/ext4. I think syncjobs is just http over port 8007, so no zfs-requirements there, I think? It would be cool if LVM management would be included in PBS as well.

No. :) The cool (and risky) thing of PBS is the Proxmox' choice for chunks. This make dedup and compression pretty easy and also makes sure that you don't need to rely on any filesystem. (We are also planning on testing towards CephFS directly, e.g.)

It's still syncing... A few new users on the lvm, but they're not really busy yet. It does seem LVM/ext3 is less efficient in terms of usage, so I need to expand the thin-pool later this morning..

root@pbs:/lvm_pbs# rsync -av /pbs/ ./ sending incremental file list ...

Testing LVM instead of ZFS is a good tip! If I switch the current datastores to LVM/EXT4, would an rsync be sufficient?

I like ZFS for it's simplicity in growing, the possibility of fast disks in front of a slow disk, the filesystem per user, including quota, compression (although not very useful in this case indeed). Also, the way PBS is built, I don't think anyone will be happy of you have a lot of...

Hmm. Restarted the proxmox-backup services (upgraded this morning to 0.9-0).

PBS has a 'verify' of the datastore. How often are we supposed to run that? Daily? Weekly?