Hyper-V Server 2012 R2 joining multiple datastores to present as one volume
Hi,
I am coming from a VMware background and have been presented with a Hyper-V 2012 R2 setup.
Using Hyper-V replication to the Disaster Recovery "DR" site, the EMC VNXe3150 SAN at that site can have datastores only at 2TB max each .. I need to be able to present a larger than 2TB datastore to the DR Hyper-V hosts to allow a server to replicate properly. (The SAN at the production site is a HP which has ~6TB datastores defined).
In VMware I would have tried to join an extent onto the datastore but cannot find this functionality on Hyper-V.
For example:
Server 1 total size = 2.0TB + replication overhead = 2.14TB
-Hosts on production, this is no problem as datastores of 6TB exist
-Hosts at DR have multiple datastores but limited to 2TB each... hence cannot replicate Server 1 successfully.
-Hosts are using clustered storage (CSV)
-Would like to join 2x2TB datastores together to make a single 4TB one at DR site
Any help appreciated.
Note this is on the host level, not storage for an individual VM.
I am coming from a VMware background and have been presented with a Hyper-V 2012 R2 setup.
Using Hyper-V replication to the Disaster Recovery "DR" site, the EMC VNXe3150 SAN at that site can have datastores only at 2TB max each .. I need to be able to present a larger than 2TB datastore to the DR Hyper-V hosts to allow a server to replicate properly. (The SAN at the production site is a HP which has ~6TB datastores defined).
In VMware I would have tried to join an extent onto the datastore but cannot find this functionality on Hyper-V.
For example:
Server 1 total size = 2.0TB + replication overhead = 2.14TB
-Hosts on production, this is no problem as datastores of 6TB exist
-Hosts at DR have multiple datastores but limited to 2TB each... hence cannot replicate Server 1 successfully.
-Hosts are using clustered storage (CSV)
-Would like to join 2x2TB datastores together to make a single 4TB one at DR site
Any help appreciated.
Note this is on the host level, not storage for an individual VM.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Aaron Tomosky
Storage spaces on the hyperv host to combine the disks?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you all for your comments.
kevinhsieh - I see where you're coming from but I don't want to add a 3rd party product into the mix. Agree 2TB is way off.. it seems to be the limit of EMC - probably the model of SAN we have more than anything.
Aaron Tomosky - I can't do that unfortunately as it seems to work only with physical disks.. good thought though.
Philip Elder - This one got me thinking but not quite for the reason posted - in the failover manager you can move storage.. you can manually select different stores to put the vhdx files onto.. I've put the data drive on it's own separate store with the OS, config etc on another... maybe this will let this work..
I've kicked off the replication again, will post back results later.
Again, thank you all for your advise.
kevinhsieh - I see where you're coming from but I don't want to add a 3rd party product into the mix. Agree 2TB is way off.. it seems to be the limit of EMC - probably the model of SAN we have more than anything.
Aaron Tomosky - I can't do that unfortunately as it seems to work only with physical disks.. good thought though.
Philip Elder - This one got me thinking but not quite for the reason posted - in the failover manager you can move storage.. you can manually select different stores to put the vhdx files onto.. I've put the data drive on it's own separate store with the OS, config etc on another... maybe this will let this work..
I've kicked off the replication again, will post back results later.
Again, thank you all for your advise.
If the in-VM experience is such that the services can work with separate partitions then go for it.
ASKER
I ended up using a Qnap NAS which allowed me to create a 4TB datastore without problem.. It's a Disaster Recovery site so any performance difference shouldn't matter if it is ever needed. Disappointed Hyper-V doesn't make this as easy as VMware does.
Thank you all for your suggestions - whilst I didn't get a resolution from them, they were helpful.
Thank you all for your suggestions - whilst I didn't get a resolution from them, they were helpful.
Be sure that the Qnap can actually run your VMs acceptably. When I had my most recent disaster the storage was seriously underperforming and Outlook was unusable, and OWA wasn't much better. It was a major disaster until I could move back to better performing storage. That's not even counting that it could take hours to reboot a VM. Performance of DR storage matters.
You got the ssd option or added an ssd right? Only way those things perform well.