Tag Info

Hot answers tagged

2

Failover clusters require shared storage. Without it, if a machine dies, the data on them is inaccessible and there's no way to failover without the data. I don't believe there is any built in fault tolerant method of using the local drives. For clustered virtual machines, you need shared storage, and internal drives don't qualify. What you can do, ...


2

You should really look at Microsoft DFS to do what you're talking about. It provides a way to abstract the physical location of data by bringing everything together in one place. So, for example you would have: 2 cluster nodes (FSCL1, FSCL2) 2 clustered file services (FS1, FS2), running on the above nodes 2 domain-based DFS namespaces (HOMES, SHARES), ...


1

lvs, openais are both open source. The problem is to use clusters and/or load-balancers properly. That includes deep technical knowledge about what you actually want.


1

StarWind Virtual SAN is pretty much everything you need. Unlike VM-running home-brewed solution GregL was mentioning this particular one is 100% native to Hyper-V as it's Windows app: simple to install and no VM patching mess. + performance. If you're fine with VMs take a look @ HP StoreVirtual VSA. It would be 1TB limited in capacity for their free version ...


1

Not much to add here since StarWind and HP VSA are already mentioned! Both products provide great value and do exactly what you're trying to accomplish. Keep in mind, you won't be able to shuffle the VMs back to local storage if it's already provisioned as storage pool for either HP VSA or StarWind. However, StarWind's storage is always available in ...



Only top voted, non community-wiki answers of a minimum length are eligible