I am currently in the process of moving my storage drives to a new separate 24-bay enclosure. My original plan was to have Drivepool running in that storage box, and map the pool as a network drive to my new machine that I am building. However, I've realized that mapped drives have some limitations for my particular scenario. It would work, but it would be BETTER if the drives appeared as physical drives to the new machine instead of mapped. (Plex Media Server has a partial scan feature that can run a mini scan based on seeing if the contents of a folder changed. Works on normal drives, but not mapped network drives).
So I did some research into iSCSI as a solution. I've seen posts that say I should have no trouble adding iSCSI disks to a pool. At the same time, what I've learned about creating an iSCSI Target using Windows Server requires VHD's. Which I take to mean I will need to make a drive sized VHD on each physical drive, add those to the VHD target, then connect to the target from my new machine and add those iscsi connected drives to Drivepool running on the new machine. Am I correct with that course of action?
If I am correct, I will need to do this drive by drive in order to preserve my data. Basically my plan is:
1) Empty a drive from old pool.
2) Create VHD on empty drive that is the size of the whole drive.
3) Add VHD to iSCSI Target.
4) Connect to Target using new machine as Initiator, and add drive to new Pool on new machine.
5) Empty another drive from old pool onto the NEW pool and repeat the process.
END RESULT: -All drives reside in large enclosure
-All drives mapped to new machine via iSCSI
-New Drivepool running on New machine see's all drives as physically attached
Does that sound like a correct plan, or am I needlessly complicating things?
I assume the following:
A. I cannot add a drive with existing data to iSCSI Target, because it needs VHD's, which is not how the drives are currently setup.
B. I cannot make a single VHD for the Target from the pool itself because a pool sized VHD is impossible; cannot have a VHD be bigger than the individual drives in the pool.
gamechld got a reaction from Christopher (Drashna) in Drivepool apperantly causing BSOD after 1803 update
gamechld got a reaction from Thronic in Drivepool apperantly causing BSOD after 1803 update
gamechld got a reaction from vapedrib in iSCSI Migration Questions