XAlpha
-
Posts
33 -
Joined
-
Last visited
-
Days Won
1
Posts posted by XAlpha
-
-
Since you brought it up, any plans to implement a balancer by file size? That would allow DP to automatically shift large files to archive-oriented drives...
-
Is there a way to force a consistency check? If not, feature request please. :-)
-
No, a way to manually force a consistency check. There used to be an option with previous versions on WHS 2011.
-
Is there a way to manually trigger a consistency check with DP 432? It was in the old 1x version for WHS 2011, and if nothing else it gave a nice warm fuzzy feeling to press it from time to time.
-
Windows only recognizes drives as fault tolerant if Windows is managing the dynamic volume. RAID controller volumes and drobos both show up to windows as not fault tolerant. So the gui for drive pool would need to have a section that would allow fault tolerant disks to be designated.
For your 2, that would be the downside. As I mentioned, a controller fault would still leave you vulnerable, but while it happens it is extremely rare. Post people would take that chance. To answer your question, no a drobo drive or a drive in a RAID pool cannot be pulled out and read as a standard NTFS volume. However, the drobo drives can be put in a different drobo as long as it's a comparable model, and RAID arrays can be move to a different controller.
I realize it's not a "clean" a solution as having a bundle of a dozen disks in a server, but for instance I have three systems at work that have three drobos plus an internal RAID array, and it'd be nice to be able to pool them all without double duplicating.
-
Thanks, but that designates whether to duplicated and/or unduplicated data on each disk. I'm proposing that if a disk is fault tolerant (an option to designate that would have to be made available), then the data that's on it isn't duplicated even if the folder containing it is set to duplicate. I realize this wouldn't protect against controller failure, but it would still protect against HDD failure, which is what happens most of the time anyways.
-
I have a few systems with a similar hardware configuration - several internal hard drives (up to 10) each with its own drive letter, plus at least one external Drobo disk array. My conundrum has always been - include the Drobo in the pool, or leave it out? I use duplication on all my folders...
Drobo's are great, they're fault tolerant using either single or dual parity; however when coupled with a DrivePool box, adding the Drobo to a pool that has all its contents duplicated would be a waste of drive space that's already protected by duplication.
So it would be great to be able to qualify a disk as "fault tolerant," allowing DrivePool to write files/folders that are enabled for duplication to only the fault tolerant disk (such as a Drobo). I also have had RAID-6 arrays that I had broke up and put each drive in DP; however, it would be nice to be able to mix and match single drives along with RAID arrays without wasting disk space.
Duplication Warnings
in General
Posted
I'm trying to resolve an issue with a "duplication warning" that has come up. "There were problems checking, duplicating or cleaning up one or more files on the pool."
The file is from WHS client computer backup folder on the pool "\client computer backups\data.4096.127.dat."
DP couldn't resolve it, so I moved the folder out of the pool onto an independent drive. The folder and the file are no longer on the pooled drive, but I'm still getting the error, and DP can't seem to fix it. I've rebooted, uninstalled version 561 and installed the latest beta, and went back to 561, but none of that has resolved the duplication warning issue.
Please advise.