Proxmox Backup Server 3.3 released!

[Chris]

Would be nice if we can test if it still works with ntfs, my UUID is a simple string with 16 characters/digits in uppercase.

NTFS is currently not supported as the UUID format is enforced by the api schema. Please do open a feature request at bugzilla.proxmox.com for this.

 

[t.lamprecht]

Ok thats the problem, I tried to use my existing datastore which is a ntfs partition. In past I had a script to mount / unmount and edit datastore.cfg to make it possible use removable datastores. NTFS UUIDs looks different.


Would be nice if we can test if it still works with ntfs, my UUID is a simple string with 16 characters/digits in uppercase.

NTFS is not a modern file system, and it's hard to get supported correctly as it's a proprietary file system.
The Linux kernel implementation works somewhat OK for reading, but I'd not rely on writing critical data like backups to NTFS from Linux.
And UUIDs are standardized, they are 128 bits and coming out as 32 hex chars, if NTFS has a different format then it's not a UUID.
While we could deviate from that, which itself I would really like to avoid, it's not 100% clear that Windows based FS can be supported as they have some quite different design choices and do not support everything that Linux/Unix/POSIX file systems do.

Edit: Can be still worth a try and could work out fine, but I wanted to manage the expectations here a bit.

 

[hernicus]

This looks wrong, with 3.3.0 the version in the header is also not separated with a minus sign anymore, in your screenshot it still is.

Either something went wrong with the upgrade, some old daemon is still running or your browser has an issue, unlikely after you tried different on

This looks wrong, with 3.3.0 the version in the header is also not separated with a minus sign anymore, in your screenshot it still is.

Either something went wrong with the upgrade, some old daemon is still running or your browser has an issue, unlikely after you tried different ones.

Just wanted to follow up here and thank you! I was able to resolve my issue and you were right - it was cache, but not browser cache. It was Cloudflare cache, which I put in front of my instance. Thank you again!