Hi,
We recovered all our customers backups old restore points before upgrade.
What we done:
- Tunning PostgresSQL main configuration is not good for setup, we upgraded a lot of setting , sometimes we hitted 30K -100kTPS.
- Created a pool of 2 servers with total 36 cores and 128 gb ram. This server are just VBO Proxy , not other role.
- Optimize proxy.xml in VBO Proxys for allow more current task because psql get exausted so fast.
- Create a Temp Object storage and move all task to this temp object storage.
- Delete the Production Object Storage and re-join production Object selecting as Proxy the new Pool of Servers.
- Move all task back to the new production object that got the new pool of servers as proxys.
- Do a re-index of the object storage. In our case 100TB took a whole day.
As note, Index status task are show in Veeam.Archiver.Proxy_*** with lines like:
Mailbox backup dates were updated (mailbox ID: 56d98941-2f7d-420f-874f-59316413e193, last backup attempt: 5/24/2024 10:20:04 PM, last archive: 5/24/2024 10:20:04 PM)
One of the most important thing we found in this issue is the Postgress generate by default a lot of timeouts and pool exausted.
Right now we're able to do restores from Jobs and from Organization without lost any restore points.
We recovered all our customers backups old restore points before upgrade.
What we done:
- Tunning PostgresSQL main configuration is not good for setup, we upgraded a lot of setting , sometimes we hitted 30K -100kTPS.
- Created a pool of 2 servers with total 36 cores and 128 gb ram. This server are just VBO Proxy , not other role.
- Optimize proxy.xml in VBO Proxys for allow more current task because psql get exausted so fast.
- Create a Temp Object storage and move all task to this temp object storage.
- Delete the Production Object Storage and re-join production Object selecting as Proxy the new Pool of Servers.
- Move all task back to the new production object that got the new pool of servers as proxys.
- Do a re-index of the object storage. In our case 100TB took a whole day.
As note, Index status task are show in Veeam.Archiver.Proxy_*** with lines like:
Mailbox backup dates were updated (mailbox ID: 56d98941-2f7d-420f-874f-59316413e193, last backup attempt: 5/24/2024 10:20:04 PM, last archive: 5/24/2024 10:20:04 PM)
One of the most important thing we found in this issue is the Postgress generate by default a lot of timeouts and pool exausted.
Right now we're able to do restores from Jobs and from Organization without lost any restore points.
Statistics: Posted by edh — Sep 08, 2024 10:51 pm
