Redundant storage solution

1. A method of switching between a first node and a second node, each located within a virtual private cloud and the first node being located within a first zone and the second node being located within a second zone that is separate from the first zone, the nodes each comprising pools and volumes, the method comprising:

determining, at the second node, that the first node has experienced a failure to send or receive data, wherein the failure is determined based on a heartbeat;

creating a new route table at the second node for a virtual private cloud controller, wherein the new route table comprises an internet protocol address of the second node;

flushing a previous route table on the virtual private cloud controller;

updating the new route table on the virtual private cloud controller; and

receiving, at the second node, data from the virtual private cloud controller.

2. The method according to claim 1 , further comprising automatically discovering the information present on both nodes necessary to achieve replication, including at least determining which storage pools and volumes need to be replicated, the determination including:

automatically discovering storage pools on the nodes that have a same name;

automatically discovering the volumes in each such storage pool;

automatically configuring tasks necessary for each volume to be replicated;

automatically determining whether a full back-up or synchronization from the first node to the second node of all storage pools and volumes in the source node is necessary; and

upon such determination, executing the full back-up or synchronization from the first node to the second node of all storage pools and volumes in the source node.

3. The method of claim 1 , further comprising:

performing a snap replication once per a first predetermined period, the snap replication comprising synchronizing data on the first node to the second node which has changed within a second predetermined period.

4. The method of claim 1 , further comprising:

providing access to the first node or the second node via a user-interface.

5. The method of claim 4 , wherein the user-interface is an application programming interface.

6. The method of claim 4 , wherein the user-interface is a complete packet inspection interface.

7. The method of claim 1 , further comprising:

authorizing two-way communication between the nodes via at least one secure shell.

8. The method of claim 1 , further comprising:

authorizing two-way communication between the nodes via at least one secure network connection.

9. The method of claim 8 , wherein the secure network connection is via TCP/IP.

10. The method of claim 8 , wherein the secure network connection is via secure shell.

11. The method of claim 1 , wherein the request to a virtual private cloud controller to update an internet protocol address information utilizes a load balancer.

12. The method of claim 1 , wherein the second zone is physically separate from first zone.

13. The method of claim 1 , wherein the second zone is logically separate from first zone.

14. The method of claim 1 , further comprising:

enabling a second port on the second node;

transmitting the request to a virtual private cloud controller to update the new route table with the internet protocol address and with the second port information;

receiving, via the second port, data from the virtual private cloud controller.

15. The method of claim 1 , further comprising:

automatically discovering the pools and volumes need to be replicated; and

configuring replication based on the automatic discovery.

16. A method of switching between a first node and a second node, each located within a virtual private cloud and the first node being located within a first zone and the second node being located within a second zone that is physically separate from the first zone, the nodes each comprising pools and volumes, the method comprising:

determining, at the second node, that the first node has experienced a failure to send or receive data, wherein the failure is determined based on a heartbeat;

transmitting, via the second node, a request to a load balancer to update a private non-routable internet protocol address, wherein the update of the private non-routable internet protocol address redirects data to the second node; and

receiving, via the second node, the data from the load balancer.

17. A virtual private cloud configured to be connected to the internet via a hypertext transfer protocol server, the virtual private cloud comprising:

a first server comprising a first network interface card and a second network interface card;

a second server comprising a first network interface card and a second network interface card, the second server configured to be communicatively coupled to the first server to provide for a redundant file system;

the first network interface card on the first server configured to be coupled to the first network interface card on the second server;

the second server configured to:

determine that the first server has experienced a failure to send or receive data by a heartbeat;

create a new route table at the second server for a virtual private cloud controller, wherein the new route table comprises an elastic internet protocol address of the second server;

flush a previous route table on the virtual private cloud controller;

update the new route table on the virtual private cloud controller; and

receive, via the second server, data from the virtual private cloud controller.