Recent content by s_sasha

Hi @t.lamprecht That fully answers my question - thank you.

Hi guys, So the question is: are the incremental backups "windows active directory aware" - customer had asked us this question today because apparently there's an old issue with AD, that caused USN rollback errors when a virtual active directory server was restored from an image and we are...

Hi @aaron , thank you very much for your time - this is satisfactory and you may mark thread as resolved (or am I able to do so myself ?)

Yeah, That's the best I could come with in y head as well and it's better than what we have, however other than making our own rules around these sub volumes how do I know which once should be 'added' to the calculation from the /hodes/{node}/storage as there's no pool info coming along ...

Hi, Thanks for the reply, so what I mean is total space allocated to the pool - that can't change/expand unless is reconfigured ? Now, our configuration: 1. Is thin provisioned 2. There are two pools, one is for OS etc, second is for the guests. But to clarify once again, I don't need to know...

Hi everyone :) We' re looking for a reliable way to read zfs pool 'usable capacity' total via the API ? Please note that it's not the 'available', but the total, for example we've got two sub volumes in the pool: vmdata-16k vmdata-32k when we use /nodes/{node}/storage we get the 'total'...

No problem, thanks - I'll monitor the thread :cool:

That makes sense, to answer your questions 1) Load isn't any different between when requests are successful and when they fail and general node load on average is not higher than 49% 2) ZFS Yeah, think async endpoints would solve this. Any work around you could suggest in the interim?

Hi, thanks for the prompt reply. Endpoint: /nodes/xxx.xxx.xxx/qemu/0000/resize Request data: {:disk \"scsi0\" :size \"+10G\"} Request type: PUT

Hi everyone, We're in need for some help here please. In short, some of the API requests return with 500, but complete anyway. We're on proxmox-ve: 6.2-1 There are no errors in /var/log/syslog in fact here is one of the successful attempts: Jan 7 15:47:45 xxx.xxx.xxx pvedaemon[42603]...