Hi,
I recently started the Veeam backup adventures. I have a Windows Xeon Workstation with system on SSD and backup repositories on fast HDDs.
I am now for two weeks doing initial backups (and have the usual throtteling issues as well, but never mind).
My question: Being throttled does not keep Veeam from constantly writing on the HDD. As the throtteling causes the jobs to run into days or weeks, this feels like an experiement about how much 24/7 write activity the hdd will accept before burning, while the actual data amount written is minimal.
Is this my fault? What would be the recommended setup? Would Veeam write less if I had more memory (currrently only 8 GB), or should an SSD be the initial repository?
(After the Office 365 backup my next step goes to LTO tape installed to the same workstation, but as the jobs are so much delayed I did not arrive there yet..)
Thank you for the wonderful product!
Mike
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Jan 17, 2022 8:40 am
- Full Name: Mike Haeseleer
- Contact:
-
- Veeam Software
- Posts: 3191
- Liked: 774 times
- Joined: Oct 21, 2011 11:22 am
- Full Name: Polina Vasileva
- Contact:
Re: My fault for hardware setup? Suggestions for hardware?
Hi Mike,
When you use local repositories, Veeam writes data to a Jet database and on SSD you'll see better performance.
During the backup, it writes constantly or as often as the new data is received. To speed up the backup and distribute the load, Veeam uses multiple threads for read/write, and even if throttling occurs for one object another may still be accessible and processed.
For bigger shops, we always recommend using object storage as a target. It gives less load on your local drive, plus better backup performance.
For more hints, you can check out our Best Practice guide.
Thanks!
When you use local repositories, Veeam writes data to a Jet database and on SSD you'll see better performance.
During the backup, it writes constantly or as often as the new data is received. To speed up the backup and distribute the load, Veeam uses multiple threads for read/write, and even if throttling occurs for one object another may still be accessible and processed.
For bigger shops, we always recommend using object storage as a target. It gives less load on your local drive, plus better backup performance.
For more hints, you can check out our Best Practice guide.
Thanks!
Who is online
Users browsing this forum: Google [Bot] and 3 guests