Jackpot system

1. A jackpot system comprising

at least two jackpot controllers including a first jackpot controller arranged to act at least as a master jackpot controller and a second jackpot controller arranged to act as either a master or a slave jackpot controller,

the first jackpot controller arranged to act as the master jackpot controller by conducting at least one jackpot during which the master jackpot controller aggregates jackpot data and at least periodically communicates the aggregated data to at least the second jackpot controller, and

the second jackpot controller arranged to act initially as the slave jackpot controller and communicate jackpot data to the first jackpot controller for aggregation, the second jackpot controller arranged to store the aggregated data received from the first jackpot controller and to act as the master controller if the master jackpot controller fails by continuing to conduct the at least one jackpot based on the stored aggregated data and by aggregating further jackpot data; and

wherein the jackpot system comprises at least one other jackpot controller arranged to act at least as a slave jackpot controller; and

wherein each other jackpot controller is capable of acting either as a master or a slave jackpot controller and is arranged to receive and store aggregated data and to conduct the at least one jackpot based on the stored aggregated data in a reconfigured jackpot system if necessary; and

wherein each of the jackpot controllers stores a ranking table which specifies the order in which jackpot controllers become the master jackpot controller if there are one or more failures and the jackpot system is reconfigured based on the ranking table.

2. A jackpot system as claimed in claim 1 , comprising at least a third jackpot controller arranged to act as either a master or slave jackpot controller and to receive and store aggregated data from at least one of the first and second jackpot controllers and to continue to conduct the at least one jackpot based on the stored aggregated data in a reconfigured jackpot system in which the third jackpot controller acts as the master controller if the first and second jackpot controllers fail.

3. A jackpot system as claimed in claim 1 , wherein if the current master jackpot controller fails, each jackpot controller checks the ranking table to determine whether to start to act as a master controller.

4. A jackpot system as claimed in claim 3 , wherein the jackpot controller that determines it is now the master jackpot controller establishes the at least one jackpot on itself.

5. A jackpot system as claimed in claim 3 , wherein each jackpot controller that determines that it is still a slave controller establishes communication with the master jackpot controller.

6. A jackpot system as claimed in claim 5 , wherein each jackpot controller that determines that it is still a slave controller communicates any jackpot data not in current aggregated data to the current master jackpot controller.

7. A jackpot system as claimed in claim 1 , wherein the master jackpot controller is arranged to aggregate data for a plurality of separate jackpots and each other jackpot controller is arranged to communicate jackpot data for at least one of the jackpots.

8. A method of conducting a jackpot comprising:

conducting at least one jackpot by aggregating jackpot data received from a plurality of jackpot controllers at a first jackpot controller acting as a master jackpot controller;

at least periodically, communicating the aggregated data to at least a second jackpot controller acting as a slave jackpot controller and also arranged to act as the master jackpot controller;

storing the aggregated data from the first jackpot controller at the second jackpot controller; and

upon the master jackpot controller failing, continuing to conduct each at least one jackpot based on the stored aggregated data with the second jackpot controller acting as the master controller;

at least periodically communicating the aggregated data to a third jackpot controller is arranged to act as either a master or slave jackpot controller;

continuing to conduct the at least one jackpot based on the communicated aggregated data with the third jackpot controller acting as the master controller upon both the first and second jackpot controllers failing;

at least periodically communicating the aggregated data to each jackpot controller in the jackpot system, and continuing to conduct the at least one jackpot based on the communicated aggregated data in a reconfigured jackpot system with one of the jackpot controllers if necessary; and

storing by each of the jackpot controllers a ranking table which specifies the order in which jackpot controllers become the master jackpot controller if there are one or more failures and the jackpot system is reconfigured based on the ranking table.

9. A method as claimed in claim 8 , wherein if the current master jackpot controller fails, the method further comprising checking by each jackpot controller the ranking table to determine whether to start to act as a master controller.

10. A method as claimed in claim 9 , comprising establishing the at least one jackpot on the jackpot controller that determines it is now the master jackpot controller.

11. A jackpot system as claimed in claim 9 , further comprising establishing by each jackpot controller that determines that it is still a slave controller communication with the master jackpot controller.

12. A jackpot system as claimed in claim 11 , further comprising communicating by each jackpot controller that determines that it is still a slave controller any jackpot data not in current aggregated data to the current master jackpot controller.

13. A jackpot system as claimed in claim 8 , comprising aggregating data for a plurality of separate jackpots on the master jackpot controller and each other jackpot controller communicating jackpot data for at least one of the jackpots to the master jackpot controller.