I'll pre-face this by saying that I think I already know the answers to this, but I want to ask to be sure.
Current environment consists of several direct attached storage volumes (all 15K SAS) and several fiber attached storage volumes with mixed 4-7TB 15k SAS volumes, and three 20TB 7200k SATA volumes. In total there are 11 separate volumes with associated shares that are used for backup.
My thoughts were to implement DrivePool and combine all volumes into a single drivepool to create a "performance disk" that will have smaller retention sets (3 days) and then longer term "capacity disk" copied to our DataDomain (yuck!) for long term archiving. We have a few backup sets that have primary full VBK files around 6TB with incrementals of around 100gb each, which could have several sets of those depending on retention policy.
1) Is there a way to write files to the disk with the most available space in the pool?
2) File sizes are unknown until the backup is finished. My assumption is that this will be a problem for DrivePool, in that, if it's writing to a disk that only has 4TB free and it ends up being a 6TB backup, then it will fail. Correct?
3) I'm assuming there's no way to allow "write continuation" to another disk if the current disk fills or hits the % max.
4) If a disk starts to fill can I set a lower max % , say 50%, and set the balance plugin to run every X minutes? My intent would be that if a disk would start to "balance" other data off the disk and make room for additional write capacity as the current backup being written grows.
5) I would anticipate that we'll use 70-80TB of the almost 100TB that we'll have available to us. We will have headroom, but I'm concerned about managing/maximizing write space. Depending on above answers. I would assume Veeam will start having write failures for larger backup files if there's not enough room on the volumes.
6) Can I configure a non-SSD as a cache point, say one of the 20TB SATA volumes, that would then write out to the pool? I'd used it purely as a staging point, rather than for performance. At this point, ANYTHING is faster than our DataDomain's
Has Stablebit worked with any Enterprise customers on a JBOD solution like this that will help manage this type of scenario? Or, is there a better SOFTWARE (not hardware) product that you would suggest that could do a better job? We're probably another year out from purchasing proper backup storage so I'm stuck using what I have for now.
Question
zim2323
I'll pre-face this by saying that I think I already know the answers to this, but I want to ask to be sure.
Current environment consists of several direct attached storage volumes (all 15K SAS) and several fiber attached storage volumes with mixed 4-7TB 15k SAS volumes, and three 20TB 7200k SATA volumes. In total there are 11 separate volumes with associated shares that are used for backup.
My thoughts were to implement DrivePool and combine all volumes into a single drivepool to create a "performance disk" that will have smaller retention sets (3 days) and then longer term "capacity disk" copied to our DataDomain (yuck!) for long term archiving. We have a few backup sets that have primary full VBK files around 6TB with incrementals of around 100gb each, which could have several sets of those depending on retention policy.
1) Is there a way to write files to the disk with the most available space in the pool?
2) File sizes are unknown until the backup is finished. My assumption is that this will be a problem for DrivePool, in that, if it's writing to a disk that only has 4TB free and it ends up being a 6TB backup, then it will fail. Correct?
3) I'm assuming there's no way to allow "write continuation" to another disk if the current disk fills or hits the % max.
4) If a disk starts to fill can I set a lower max % , say 50%, and set the balance plugin to run every X minutes? My intent would be that if a disk would start to "balance" other data off the disk and make room for additional write capacity as the current backup being written grows.
5) I would anticipate that we'll use 70-80TB of the almost 100TB that we'll have available to us. We will have headroom, but I'm concerned about managing/maximizing write space. Depending on above answers. I would assume Veeam will start having write failures for larger backup files if there's not enough room on the volumes.
6) Can I configure a non-SSD as a cache point, say one of the 20TB SATA volumes, that would then write out to the pool? I'd used it purely as a staging point, rather than for performance. At this point, ANYTHING is faster than our DataDomain's
Has Stablebit worked with any Enterprise customers on a JBOD solution like this that will help manage this type of scenario? Or, is there a better SOFTWARE (not hardware) product that you would suggest that could do a better job? We're probably another year out from purchasing proper backup storage so I'm stuck using what I have for now.
Thanks,
Chris
Link to comment
Share on other sites
3 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.