I'm setting up a new backup job and am not sure what the best option would be for storage optimization.
I'm using a scale-out repository with the performance tier as an iSCSI target on a Synology NAS, and the capacity tier is S3 compatible on Wasabi. I'll be backing up 4 Hyper-V virtual machines (all Windows Server) totalling about 1.8TB.
I'm not sure if it would be best to use local or LAN. Can anyone advise?
Thanks
-
- Influencer
- Posts: 18
- Liked: never
- Joined: Jan 11, 2022 2:53 pm
- Full Name: Josh Marchant
- Contact:
-
- Veeam Software
- Posts: 3625
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Recommended 'Storage optimization' for iSCSI on Synology NAS
Hi Josh,
I'd suggest to stick with the default values but you can also have a look at this section of the best practices and this page on our help center.
Thanks!
I'd suggest to stick with the default values but you can also have a look at this section of the best practices and this page on our help center.
Thanks!
-
- Service Provider
- Posts: 3
- Liked: never
- Joined: Mar 29, 2021 7:03 am
- Full Name: Yoni Blieck
- Contact:
Re: Recommended 'Storage optimization' for iSCSI on Synology NAS
Hello,
Why would we stick to the defaults and use local torget as block size?
Why not using the WAN target, as with Wasabi the number of API requests are not billed. And so with smaller blocks, the changes are less big?
Why would we stick to the defaults and use local torget as block size?
Why not using the WAN target, as with Wasabi the number of API requests are not billed. And so with smaller blocks, the changes are less big?
-
- Veeam Software
- Posts: 3625
- Liked: 608 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Recommended 'Storage optimization' for iSCSI on Synology NAS
Hi Yoni,
You should leverage the default size if there are no specific reasons to use a block of another size. Long story short, read and synthetic operations of the backup files having a smaller block can be much slower depending on storage type because more data blocks must be processed. The table on this page provides recommendations for block size selection depending on backup files size.
Thanks!
You should leverage the default size if there are no specific reasons to use a block of another size. Long story short, read and synthetic operations of the backup files having a smaller block can be much slower depending on storage type because more data blocks must be processed. The table on this page provides recommendations for block size selection depending on backup files size.
Thanks!
Who is online
Users browsing this forum: 00ricbjo, Baidu [Spider], m.levisson, Semrush [Bot] and 174 guests