# Database backup

**URL:** <https://forum.inductiveautomation.com/t/database-backup/5242>\
**Category:** Ignition\
**Created:** [October 6, 2012, 5:35am UTC](https://forum.inductiveautomation.com/t/database-backup/5242 "2012-10-06T05:35:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![hazey](https://avatars.discourse-cdn.com/v4/letter/h/a587f6/32.png) [@hazey](https://forum.inductiveautomation.com/u/hazey)\
**Post date:** [October 6, 2012, 5:35am UTC](https://forum.inductiveautomation.com/t/database-backup/5242/1 "2012-10-06T05:35:13Z")

</div>

Hi guys, I have a problem with transaction groups. The IT staff currently do a schedule backup of the database in the early hours of the morning. The database sits on another machine. When they do the backup they are closing the connection to Ignition, when the backup is finished all of the last values that were in the transaction groups are being triggered to write in the database again, so I end up with double transactions when the backup is finished.

Any ideas on a cure for this?

thanks

hazey

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [October 8, 2012, 9:40pm UTC](https://forum.inductiveautomation.com/t/database-backup/5242/2 "2012-10-08T21:40:50Z")

</div>

What version of Ignition are you using?

What type of transaction group are you using?

---

<div class="post-metadata">

**Author:** ![hazey](https://avatars.discourse-cdn.com/v4/letter/h/a587f6/32.png) [@hazey](https://forum.inductiveautomation.com/u/hazey)\
**Post date:** [October 9, 2012, 2:49am UTC](https://forum.inductiveautomation.com/t/database-backup/5242/3 "2012-10-09T02:49:43Z")

</div>

Greg it is version 7.2.11 and standard Transaction groups.

I have attached log file the backup is at 1.15am every day.  
[logs.bin.gz](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/df0455a0d77b0a67d62d361e687c5ef14c5f9fec.gz) (650 KB)

---

<div class="post-metadata">

**Author:** ![greg.simpson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/greg.simpson/32/3135_2.png) [@greg.simpson](https://forum.inductiveautomation.com/u/greg.simpson)\
**Post date:** [October 10, 2012, 4:19pm UTC](https://forum.inductiveautomation.com/t/database-backup/5242/4 "2012-10-10T16:19:43Z")

</div>

Has this always occurred when they do the database backup?

---

<div class="post-metadata">

**Author:** ![hazey](https://avatars.discourse-cdn.com/v4/letter/h/a587f6/32.png) [@hazey](https://forum.inductiveautomation.com/u/hazey)\
**Post date:** [October 11, 2012, 12:30am UTC](https://forum.inductiveautomation.com/t/database-backup/5242/5 "2012-10-11T00:30:00Z")

</div>

Greg Yes it has.

---

<div class="post-metadata">

**Author:** ![Michael.Stofan](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.stofan/32/3342_2.png) [@Michael.Stofan](https://forum.inductiveautomation.com/u/Michael.Stofan)\
**Post date:** [October 11, 2012, 10:49pm UTC](https://forum.inductiveautomation.com/t/database-backup/5242/6 "2012-10-11T22:49:12Z")

</div>

If your transaction groups are set to use a trigger, you could try selected the “Prevent trigger caused by group start” check box. It may help you out in this situation.