# Problem Starting Backup Server After Upgrade Again

**URL:** <https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356>\
**Category:** Ignition\
**Created:** [April 26, 2012, 2:45pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356 "2012-04-26T14:45:07Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\
**Post date:** [April 26, 2012, 2:45pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/1 "2012-04-26T14:45:07Z")

</div>

Hey guys,

I’m having the same problem I had a little while ago with the backup not starting after an upgrade, the issue was resolved before here:

[http://www.inductiveautomation.com/forum/viewtopic.php?f=72&t=7897](http://www.inductiveautomation.com/forum/viewtopic.php?f=72&t=7897)

by copying the module folder from the primary server to the backup server but that is not fixing the issue this time. The only difference is that now I have the SPC module installed on the primary server for testing. Those modules are now on the backup server as well (because I copied the folder over) but according to the wrapper.log file it’s still trying to do a full restore for some reason. Can anyone see anything else that could be wrong?

[wrapper20120426.log](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/c3ff4b57c23825afbcde36aa9c8bfe84f29e6c80.log) (799 KB)

---

<div class="post-metadata">

**Author:** ![Kyle\_Chase](https://avatars.discourse-cdn.com/v4/letter/k/9de0a6/32.png) [@Kyle\_Chase](https://forum.inductiveautomation.com/u/Kyle_Chase)\
**Post date:** [April 26, 2012, 6:16pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/2 "2012-04-26T18:16:58Z")

</div>

Try shutting down the backup server, and delete the contexts of data/db, but keep the folder  
Then edit redundancy.xml and delete the systemstateuid line, then restart

---

<div class="post-metadata">

**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\
**Post date:** [April 26, 2012, 6:56pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/3 "2012-04-26T18:56:15Z")

</div>

I tried that and it still does the same thing.

---

<div class="post-metadata">

**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\
**Post date:** [April 26, 2012, 7:28pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/4 "2012-04-26T19:28:25Z")

</div>

Ok, this is weird… I uninstalled all of the OEE/Downtime modules off of the primary but kept the SPC modules, copied over the modules folder from the primary to the backup and then did everything that Kyle had suggested again and this time it worked. Not sure why that is… apparently it didn’t like something with the OEE modules. FYI.

---

<div class="post-metadata">

**Author:** ![Colby.Clegg](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/colby.clegg/32/3282_2.png) [@Colby.Clegg](https://forum.inductiveautomation.com/u/Colby.Clegg)\
**Post date:** [April 26, 2012, 11:28pm UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/5 "2012-04-26T23:28:18Z")

</div>

On the master node, I believe it should have logged a message along the lines of “Backup node’s module manifest is incompabile with the master’s…” with details of the module versions. If you can locate that in the wrapper.log file, it might help us track down what was going on.

Thanks,

---

<div class="post-metadata">

**Author:** ![Duffanator](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/duffanator/32/3560_2.png) [@Duffanator](https://forum.inductiveautomation.com/u/Duffanator)\
**Post date:** [April 27, 2012, 11:45am UTC](https://forum.inductiveautomation.com/t/problem-starting-backup-server-after-upgrade-again/4356/6 "2012-04-27T11:45:43Z")

</div>

Here is what I found in the log:

[quote]INFO | jvm 1 | 2012/04/26 15:20:27 | WARN [MasterTCPChannel] [15:20:27,564]: The module ‘meshelp’ is missing from the backup system.  
INFO | jvm 1 | 2012/04/26 15:20:27 | INFO [MasterTCPChannel] [15:20:27,565]: Backup node’s module manifest is incompabile with the master’s. A full backup will be performed. Value: [(fpmi/6.4.1 (b505)), (fsql/5.4.1 (b160)), (help/1.4.0 (b212)), (mobile/1.4.0 (b111)), (modbus-driver2/2.4.0 (b207)), (oeedtinstaller/1.4.2 (b120419)), (opccom/1.4.0 (b106)), (productiongateway/1.4.2-rc1 (b120419)), (qualitygateway/1.4.2-rc1 (b120419)), (qualityinstaller/1.4.2-rc1 (b120419)), (rept/1.4.0 (b102)), (schedulegateway/1.4.2 (b120419)), (siemens-drivers/1.4.1 (b149)), (symfact/2.6.0 (b35)), (udp-driver/1.4.0 (b121)), (xopc/1.4.1 (b391)), (xopc-drivers/1.4.1 (b199))]  
INFO | jvm 1 | 2012/04/26 15:20:27 | INFO [MasterTCPChannel] [15:20:27,774]: (id=62) Connected to address ‘/10.2.1.226’  
INFO | jvm 1 | 2012/04/26 15:20:27 | INFO [MasterTCPChannel] [15:20:27,775]: Starting redundancy channel id 62  
INFO | jvm 1 | 2012/04/26 15:20:27 | INFO [MasterStateManager] [15:20:27,778]: Successfully registered new connection to redundant master from ‘/10.2.1.226:50539’  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ProductionGatewayHook] [15:20:27,964]: Redundancy connection status changed: peer id=10.2.1.226, connected=true, last activity=Thu Apr 26 15:20:27 EDT 2012  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [MasterTCPChannel] [15:20:28,377]: System restore initiated by backup node. System will provide a ‘full’ restore file.  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [MasterStateManager] [15:20:28,379]: Backup node has requested a ‘full’ restore.  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,404]: Checkpoint start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,404]: defrag start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,713]: dataFileCache commit start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,768]: dataFileCache open start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,769]: dataFileCache open end  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,781]: defrag end  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,781]: Checkpoint end  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,784]: checkpointClose start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,798]: dataFileCache commit start  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,813]: checkpointClose end  
INFO | jvm 1 | 2012/04/26 15:20:28 | INFO [ENGINE] [15:20:28,813]: Initiating backup of instance[/quote]
