Can Enkompass use multiple volumes on NAS storage ?

[webhostireland]

Hi,

I understand Enkompass is designed to use centralised storage.

Is it possible to use different volumes on the NAS for website home folder files ?

\\server\volume1
\\server\volume2
\\server\volume3
\\server\volume4
\\server\volume5

We want to be able to use different volumes to keep each volume small in size.

So if you had 500GB hard drive you could make 5 x 100GB data volumes.

the reason behind using small volumes is if you need to run chkdsk you only need to take the effected volume offline instead of the entire 500GB volume which would take a long time to run chkdsk resulting in many hours of downtime.

Thanks,
Dave

[cPanelEric]

Howdy,

Enkompass can do this, but not in the interface at this time. There are functions that support this already in the core but no means to make use of them. We're working out the "Rearrange accounts" style functions, but we also have to be able to move data from one server to another too. The only way to do this now would be manually hacking at AD and having to setup permissions manually, not a good way of doing it just yet.

Thanks!

[webhostireland]

Hi Eric,

That is excellent news that sometime in the future it will be able to support multiple volumes to store website content on the NAS / SAN device.

thanks
Dave

[cpanelbox]

I'm a bit concerned regarding enkompass scalability when using remote storage.

The way I see it, Enkompass should support creating pools of web servers each with their own storage point.

This way it's really scalable as you add, let's say, 4 or 5 web servers to the same pool and assign a shared remote storage to them.

Then, when it fills up, you close that pool and create another one of 4 or 5 web servers and assign another shared storage to them.

There are many advantages to this approach specially:
- Scalability
- Maintenance
- Performance

Sites failover would only be possible inside the same pool but even I see this as a benefit.

In a 50.000 user scenario, considering you put 500 users per server and each user uses 2GB average, without the pool feature you would need 100 web servers sharing the same 100TB storage with a over exaggerated failover farm and each domain would also have 100 A record entries for each of the webservers.

With the pool feature, you would have the same 100 web servers, but split in smaller farms of 5 servers each with a shared storage of 5TB per farm where each domain would have at max 5 A records in their DNS.

Update:

Anyway, I just got an update from Cpanel in which they're planning to introduce later on multiple farms (pools as I described it).