locked
Controlling Storage and Shares RRS feed

  • Question

  • Hi all,

    Thanks for taking the time to read this, and possibly assist. I am a brand new WHS user. I have an external enclosure that has a 5 drive RAID5 array, and another 3 drive RAID5 array. So, WHS will see it's internal drive, and those 2 virtual drives. Is there an easy way to control which shares are on which drives?

    I initially setup WHS with no drives attached. So, it partitioned the system drive and made 90% of the drive DATA, that contains the shares. When I attached the external enclosure and built the 2 arrays, it did not assign them drive letters, but rather added them to the volume, as designed to make WHS simple and easy to use.

    However, I do not want to use any space on the internal drive, and would like to restrict the shares to utilize a specific raid array. I'd rather not enable the duplication feature across multiple drives. Is there an easy way to force the shares to use a specific drive?

    I can manually mount the arrays to drive letters, make shared directories on those arrays, but I want to know what the best practice is without screwing anything up.

    I'll be storing primarily music, digital photos, and avchd video on the shares.

    Thanks in advance!
    -Ed
    Tuesday, December 9, 2008 6:19 AM

Answers

  • Hi Ed,
    the tombstones on drive D: are pointers indeed. If you have at least Power Pack 1 installed, drive D: should not be used for any data at all, as long, as there is enough space on the other disks.
    If there is historical data, this will not be relocated automatically. To perform such a move, you can use the tool LZreallocator, which seems to work only before you have installed the November patch for Windows Home Server.
    Your understanding of duplication is right.
    What exactly do you mean with removing one of those drives - one of the RAIDs or a single disk?
    I'm not sure, if the data remains on a disk, if it is removed from storage pool. If not, recovery software may still have access unless the disk has been rewritten with some wiping tool or new data.
    In case you plug a normal WHS data disk into another PC, the data stored on this drive can be found in the hidden folder DE in subfolder shares.

    Some more details how WHS Drive Extender works you can find in this whitepaper.
    Best greetings from Germany
    Olaf
    Tuesday, December 9, 2008 7:38 AM
    Moderator

All replies

  • So, I think I answered my own question with more searching on this forum that pointed me to a Drive Extender doc, and in it I see...

    "It is highly recommended that you not use hardware RAID technologies for your home server. Recovering from hard-drive failures becomes increasingly complex when hardware RAID systems are used. The recommended and supported approach is to use multiple hard drives that are configured as Just a Bunch of Disks (JBOD)."

    I guess the best practice is to kill the raid arrays, add the individual drives and enable folder duplication.   This would guarantee my data resides on 2 physical disks.   The primary drive is a 200GB, split into a 20GB and 180GB partition.   The 180GB primary data partition is obviously D:.   So I guess the individual secondary external drives, (5) 500 GB and (3) 1000 GB, will be added to the storage volume.   Will that work ok?  Are the "tombstone" files on the 180GB partition truly pointers?  The way I understand it, i I store a 100MB video file on the Videos Share, and folder duplication is enabled, the 100MB file will be placed on 2 of the 8 secondary external disks, and a small tombstone file much smaller than 100MB I hope is created on the 180GB primary data partition right?

    Also, if I were to remove one of those drives from WHS, would I be able to view the data on another Windows PC?  How about with a forensics tool such as Encase?

    Thanks in advance,
    -Ed


    Tuesday, December 9, 2008 6:41 AM
  • Hi Ed,
    the tombstones on drive D: are pointers indeed. If you have at least Power Pack 1 installed, drive D: should not be used for any data at all, as long, as there is enough space on the other disks.
    If there is historical data, this will not be relocated automatically. To perform such a move, you can use the tool LZreallocator, which seems to work only before you have installed the November patch for Windows Home Server.
    Your understanding of duplication is right.
    What exactly do you mean with removing one of those drives - one of the RAIDs or a single disk?
    I'm not sure, if the data remains on a disk, if it is removed from storage pool. If not, recovery software may still have access unless the disk has been rewritten with some wiping tool or new data.
    In case you plug a normal WHS data disk into another PC, the data stored on this drive can be found in the hidden folder DE in subfolder shares.

    Some more details how WHS Drive Extender works you can find in this whitepaper.
    Best greetings from Germany
    Olaf
    Tuesday, December 9, 2008 7:38 AM
    Moderator
  • Thank you for the reply and your answer.  It is greatly appreciated.    I should have prefaced my post with, this is a truly fresh install.  All drives involved (internal to WHS and in the external enclosure) are empty.   So I originally had 2 raid arrays (5) 500GB drives in RAID5 and (3) 1000GB drives in RAID5.  I will delete those arrays so that I'll have 8 individual external drives, and let WHS manage my data with the folder duplication.   Further, WHS will have 180GB worth of space to place its tombstones, which should be enough.   So I have no data at risk at this point.  I will be reinstalling WHS from scratch with this new setup to ensure a smooth setup and operation.

    Kind regards,
    -Ed
    Tuesday, December 9, 2008 1:43 PM
  • One thing I would recommend is to do your installation with all drives connected. That will give you a feel for how easy a server reinstallation will be, and where you'll have problems. If you can't get the drives in one of your external enclosures to register at all on the hardware discovery screen, for example, a server reinstallation will fail (it won't even be presented as an option, most likely).
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, December 9, 2008 4:06 PM
    Moderator
  • Thank you all for taking the time to read and respond.  It is much appreciated and I hope to learn a great deal about WHS so I too can help others.

    Kind regards,
    -Ed
    Wednesday, December 10, 2008 2:39 AM