RAID 6 in my backup VM host on spinning rust?
-
@beta said in RAID 6 in my backup VM host on spinning rust?:
@dustinb3403 Well I looked up Dell drives and the 3.84 SATA read-intensive drives are going for ~$1800 a piece (before any discounting).
Tier 1 hardware is a particular beast.
Yeah, we can scour the fleabays of the world for caddies, but then comes the firmware fun times and/or question marks.
Our saved search e-mail monitoring shows Tier 1 secondary channel sales as being very expensive even relative to buying direct from the Tier 1 vendor.
At this point, adding a couple of known good SAS spindles and calling it a day is probably going to be the safest bet without having to think about rebuilding that SOBR, or adding a new SOBR and migrating the backups, or just setting up an entirely new array/SOBR and backing up leaving things vulnerable for a while.
Nah, in my mind KISS applies here.
Add the drives, expand the array, and call it a day.
Oh, and make sure to set up a B2 bucket for some immutability.
-
@phlipelder said in RAID 6 in my backup VM host on spinning rust?:
Nah, in my mind KISS applies here.
Add the drives, expand the array, and call it a day.Might not be so simple. Not every perc controller / version can grow a RAID10 array.
I believe the entire array needs to be restriped when doing that.
-
@pete-s said in RAID 6 in my backup VM host on spinning rust?:
@phlipelder said in RAID 6 in my backup VM host on spinning rust?:
Nah, in my mind KISS applies here.
Add the drives, expand the array, and call it a day.Might not be so simple. Not every perc controller / version can grow a RAID10 array.
I believe the entire array needs to be restriped when doing that.
Yeah, brain skipped after a speed bump. ;0)
Verify the current PERC can indeed expand that array and do so keeping things as they are.
You could copy out the contents of the SOBR, blow away the array, add the drives, set up the RAID 6 array, format, copy the data back, and finally get Veeam set up and the backups imported but that kills KISS big time.
Mention of "replacing the server" is there so keep the time cost ($150/Hour minimum here) in mind for any changes to be made relative to the budget for the new rig in the not to distant future.
-
@phlipelder said in RAID 6 in my backup VM host on spinning rust?:
@pete-s said in RAID 6 in my backup VM host on spinning rust?:
@phlipelder said in RAID 6 in my backup VM host on spinning rust?:
Nah, in my mind KISS applies here.
Add the drives, expand the array, and call it a day.Might not be so simple. Not every perc controller / version can grow a RAID10 array.
I believe the entire array needs to be restriped when doing that.
Yeah, brain skipped after a speed bump. ;0)
Verify the current PERC can indeed expand that array and do so keeping things as they are.
You could copy out the contents of the SOBR, blow away the array, add the drives, set up the RAID 6 array, format, copy the data back, and finally get Veeam set up and the backups imported but that kills KISS big time.
Mention of "replacing the server" is there so keep the time cost ($150/Hour minimum here) in mind for any changes to be made relative to the budget for the new rig in the not to distant future.
That's why it faster to just put in two SSDs (we know the server has two bays free). And set up a new array.
You have all the time in the world since both the new and old array are up and running.
As a stop gap measure you could potentially do it with two smaller SSDs and keep both arrays in use.
-
@beta said in RAID 6 in my backup VM host on spinning rust?:
@dashrender Based on what I've seen re:IOPS usage of my current VMs I believe it will.
I guess my other concern with RAID 6 in this case is if the array is getting too big? The individual disks themselves at 600GB I don't think are a problem, but 12 in a single array?
It's always array size, never drive size, that matters primarily. Of course, drive size influences array size, but the two are not exactly the same. Drive size does matter, but is far more trivial and affects a different aspect of the system. Array size is about the chances of failure, drive size influences the time to rebuild after a failure. Both matter, but the first matters way more.
That said 12x600 is 7.2TB which is quite large. Not so large as to be out of the question, but large enough to cause concern.
As a backup target, you have way more flexibility than with other types of storage. I would say that likely if you go with RAID 6 you need to be prepared that if you lose a drive that you will need to run out and buy an 8TB USB drive and copy everything off to it before attempting to replace a failed drive. If that's okay with you, then I'd say RAID 6 is okay assuming the performance remains adequate for your transfer windows.
-
@pete-s said in RAID 6 in my backup VM host on spinning rust?:
@beta said in RAID 6 in my backup VM host on spinning rust?:
Hear me out...I have a Dell server that I use as a Veeam replication target. This host is used as a backup in case my primary server dies - I just turn on the replicas and run from it until primary host is repaired.
This backup host currently has OBR10 comprised of 10 600GB 10K SAS drives. I'm running up against storage capacity limitations and have ordered 2 additional 600GB disks to add to the array, but I was thinking while I am in the process of rebuilding this array, maybe I should change it from OBR10 to RAID 6? My concern is that while I am pretty sure the OBR10 will give me enough space to last until I schedule a complete replacement of the server, the margin will be very slim whereas the RAID 6 I'm sure will give me plenty of extra breathing room until the server is replaced.
Would this be crazy to do? Or should I just stick to OBR10? Thanks!
You know, you only have 10x600/2 = 3TB of storage.
You could replace the entire array with two 3.84TB SATA/SAS SSDs. Run them in RAID1 you'd have better performance and higher reliability.
Buying 2.5" hard drives today is a mistake.
This, definitely. Investing in an ancient system with legacy style drives makes very little sense today.
-
@beta said in RAID 6 in my backup VM host on spinning rust?:
@dustinb3403 Well I looked up Dell drives and the 3.84 SATA read-intensive drives are going for ~$1800 a piece (before any discounting).
Move off of the Dell device. You can get into a Synology or something else with two bays for far less money than the price difference of the drives!
-
@beta said in RAID 6 in my backup VM host on spinning rust?:
@pete-s How much are two 3.84TB enterprise SSDs going to cost me again?
No need, not even recommended, to use enterprise drives. Backup use cases are not good for enterprise drives. Good consumer drives will give you much better value.
-
@jaredbusch said in RAID 6 in my backup VM host on spinning rust?:
@beta said in RAID 6 in my backup VM host on spinning rust?:
Hear me out...I have a Dell server that I use as a Veeam replication target. This host is used as a backup in case my primary server dies - I just turn on the replicas and run from it until primary host is repaired.
This is not a backup. This is a replica. These are completely different things.
Do you actually have a backup?
Oh good point, I missed that. That makes the SSDs that much more important as you want it to be able to perform if it gets used!
-
@scottalanmiller said
It's always array size, never drive size, that matters primarily.
Just so I make sure I understand, array size meaning total TB or total number of disks?
-
@beta said in RAID 6 in my backup VM host on spinning rust?:
@scottalanmiller said
It's always array size, never drive size, that matters primarily.
Just so I make sure I understand, array size meaning total TB or total number of disks?
Total capacity.
