This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
admin:features:snapshots:scalability [2012/04/03 15:46] doc |
admin:features:snapshots:scalability [2016/06/28 22:38] (current) |
||
|---|---|---|---|
| Line 20: | Line 20: | ||
| Some applications will allow multiple application servers to point to the same location on a SAN to located the files of an Omnidex Snapshot. This works well as long as the data and indexes are accessed in a read-only mode, and as long as there is sufficient I/O bandwidth available on the SAN and the channels to the SAN. | Some applications will allow multiple application servers to point to the same location on a SAN to located the files of an Omnidex Snapshot. This works well as long as the data and indexes are accessed in a read-only mode, and as long as there is sufficient I/O bandwidth available on the SAN and the channels to the SAN. | ||
| + | In more complex situations, an Omnidex Grid can provide additional scalability. An Omnidex Grid can be thought of as a multi-partition Omnidex Snapshot. Each node is like an individual Omnidex Snapshot, while all of the nodes share the same metadata. Additional scalability can be achieved by partitioning the data into a Grid, and then adding more nodes to the grid as the database grows. Consult the section on [[admin:basics:updates:home|Omnidex Grids]] for more information. | ||