# Redundancy database configuration

**URL:** <https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381>\
**Category:** Ignition\
**Tags:** perspective, ignition81, database\
**Created:** [May 8, 2023, 4:41am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381 "2023-05-08T04:41:52Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![KIM\_SUNG\_HOO](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@KIM\_SUNG\_HOO](https://forum.inductiveautomation.com/u/KIM_SUNG_HOO)\
**Post date:** [May 8, 2023, 4:41am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/1 "2023-05-08T04:41:53Z")

</div>

hi, I have some questions about database redundancy.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/1/e183bdc54641aff5e6692aae1eb4ef141def3d5e.png)

If configured as in the picture, is this different from the case of master and backup (warm)?

If it is different, should all gateways be configured as a single gateway rather than gateway redundancy?

thanks for reading!

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 8, 2023, 11:33am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/2 "2023-05-08T11:33:23Z")

</div>

> [@KIM\_SUNG\_HOO](#):
>
> is this different

Yes, this diagram has no redundancy. If a server crashes, nothing takes its place. Redundant pairs don't do extra work for performance, they are doubled to handle a server crash. The scale-out layouts are **orthogonal** to redundancy setups.

---

<div class="post-metadata">

**Author:** ![KIM\_SUNG\_HOO](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@KIM\_SUNG\_HOO](https://forum.inductiveautomation.com/u/KIM_SUNG_HOO)\
**Post date:** [May 8, 2023, 11:25pm UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/3 "2023-05-08T23:25:31Z")

</div>

> [@pturmel](#):
>
> The scale-out layouts are **orthogonal** to redundancy setups.

what does it mean?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 9, 2023, 12:05am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/4 "2023-05-09T00:05:17Z")

</div>

It means that in any non-Edge non-Maker organization of Ignition servers, where an Independent (non-redundant) Gateway is shown, a redundant pair could be used instead.

---

<div class="post-metadata">

**Author:** ![KIM\_SUNG\_HOO](https://avatars.discourse-cdn.com/v4/letter/k/977dab/32.png) [@KIM\_SUNG\_HOO](https://forum.inductiveautomation.com/u/KIM_SUNG_HOO)\
**Post date:** [May 9, 2023, 1:37am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/5 "2023-05-09T01:37:22Z")

</div>

i have some question.

When configured as above, is it not necessary to install the tag historian module in the master gateway?

and Do I need to install perspective module for database gateway?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 9, 2023, 1:40am UTC](https://forum.inductiveautomation.com/t/redundancy-database-configuration/73381/6 "2023-05-09T01:40:39Z")

</div>

There are so many possibilities that I can't really answer that. Perhaps you should share some real-world application specifications with IA sales engineering. So you an get an official answer for your **actual** situation.
