# Clustering and Resilience

**URL:** <https://forums.interworx.com/t/clustering-and-resilience/12349>\
**Category:** General Inquries\
**Created:** [April 20, 2009, 7:12am UTC](https://forums.interworx.com/t/clustering-and-resilience/12349 "2009-04-20T07:12:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://forums.interworx.com/uploads/default/original/2X/4/40ab17cc34b792a0172b48ad1333b9ba9299a9a1.png) [@system](https://forums.interworx.com/u/system)\
**Post date:** [April 20, 2009, 7:12am UTC](https://forums.interworx.com/t/clustering-and-resilience/12349/1 "2009-04-20T07:12:45Z")

</div>

What have you guys used to make a fully failure proof Interworx deployment?

In other words everytime I deploy a new server with Interworx I’d have to have a new control panel for customers on that server.

If their domain DNS has not resolved they would have to access it by IP, which is a pain.

I prefer them to login through the siteworx login box on our homepage. So clustering is a good solution. If a node fails, doesn’t matter right?

However the master server, if that fails, game over.

So whats the best way to create a fully disaster proof solution?

Also do you guys save data on the servers local HDDs or do you use SANs / NAS / iSCSI? I am thinking about a SAN solution but heard performance is not that great and I’m better with local disks or iSCSI.

---

<div class="post-metadata">

**Author:** ![Fr3d](https://forums.interworx.com/user_avatar/forums.interworx.com/fr3d/32/27_2.png) [@Fr3d](https://forums.interworx.com/u/Fr3d)\
**Post date:** [April 20, 2009, 9:30am UTC](https://forums.interworx.com/t/clustering-and-resilience/12349/2 "2009-04-20T09:30:04Z")

</div>

> [@gareth25;16116](#):
>
> Also do you guys save data on the servers local HDDs or do you use SANs / NAS / iSCSI? I am thinking about a SAN solution but heard performance is not that great and I’m better with local disks or iSCSI.

I would recommend learning more about SAN and NAS technology before investing in either - iSCSI is not a storage medium, it’s how a system communicates with one 😉

---

<div class="post-metadata">

**Author:** ![system](https://forums.interworx.com/uploads/default/original/2X/4/40ab17cc34b792a0172b48ad1333b9ba9299a9a1.png) [@system](https://forums.interworx.com/u/system)\
**Post date:** [April 20, 2009, 9:51am UTC](https://forums.interworx.com/t/clustering-and-resilience/12349/3 "2009-04-20T09:51:15Z")

</div>

I understand that, but it’s like NFS - iSCSI is supposed to be faster than NFS which is what Iworx uses to talk to a NAS.

I am looking at Synology RackStation as they have high performance at a nice price, and with RAID 6 should be pretty reliable.