Oh. Thank you so much. No, I didn't post it to BZ because, PBS or just online backup is wrong by design and there is some info about that in the proxmox wiki. Just don't use it, or upgrade to pve 8.2 and use local SSD for temp cache. But I don't know what will be happening if local SSD out of...
Sad but no. It happened because my PBS server stopped write any new data during try to get a new backup data. And after several hours my Proxmox VMs just hangs. I logged in into those and all of my VMs which had a some write during backup switched to read only with a lot of errors. I fixed that...
Yes. If I will have that possibility, I test that, but I'm sure that problem still here because design. You need fast and robust backup server to make any kind online backup. I use proxmox PVE from v 4.0 and problem still here. It's design. I hoped that PBS uses other design but not, I've...
If backup process hangs for any reasons, there is a lot of problem after that... You can see that. It's my production. Thank for you did not answer me in that topic. Hope that proxmox stuff will answer me.
That problem is common (and still here) and described in wiki: https://pve.proxmox.com/wiki/Backup_and_Restore see section VM Backup Fleecing
If you can answer for my other topic witch is related to that problem I will be glad -...
Dear all, could you tell me what will happen if my backup fleecing device out of space? - For example, if my PBS will go offline during any network issues and so on.
No. I realized that problem comes from bad design of proxmox at all. For try to mitigate impact of my problem I need to have consider use PVE v 8.2 with use of Backup fleecing (advanced feature) or switch to pve-zsync
Dear all!
I use proxmox VE v 7.3-4 with PBS v 3.2-2 for a long time.
I missed out space on my pbs and after that my backup job stacked with error msg:
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task...
If you have fsync writes from a VM you absolutle need to use killer feature of zfs - zlog ssd cache (enterprise level with a capacitor). If you have many read you can use l2arc with tune to write any data on it and make it persistence! - That is another killer feature of zfs. If you have many...
oh... I think you are right. I have problem with totally hangs of my vm during backup, with message of guest vm like: i/o timeout... I have so slow backup storage... :(
I have the same problem. I have a solution just move client_max_body_size 5120m; to top of file, please see my confing file:
client_max_body_size 5120m;
upstream proxmox {
server "bve-01.company.ru";
}
server {
listen 80 default_server;
rewrite ^(.*) https://$host$1 permanent;
}...
There is another moment: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/sect-guest_virtual_machine_device_configuration-random_number_generator_device
I'm not deep in this, but I suppose if you use program urandom...
Did you understand for zlog at all? zlog works only with a database, the zlog may tell you db engine I'm write your data when a real data is on RAM and SSD cache, after that zfs will write your data to disk from RAM. zlog SSD will have only if power cut situation. zlog is very good for exmaple...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.