# Archiving and synchronization of data along with time stamp with MQTT broker after failure of internet connection in IOT gateway

**URL:** <https://discourse.nodered.org/t/archiving-and-synchronization-of-data-along-with-time-stamp-with-mqtt-broker-after-failure-of-internet-connection-in-iot-gateway/12770>\
**Category:** General\
**Created:** [1 July 2019 06:22 UTC](https://discourse.nodered.org/t/archiving-and-synchronization-of-data-along-with-time-stamp-with-mqtt-broker-after-failure-of-internet-connection-in-iot-gateway/12770 "2019-07-01T06:22:43Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![ukmoose](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/ukmoose/32/13_2.png) [@ukmoose](https://discourse.nodered.org/u/ukmoose)\
**Post date:** [1 July 2019 07:22 UTC](https://discourse.nodered.org/t/archiving-and-synchronization-of-data-along-with-time-stamp-with-mqtt-broker-after-failure-of-internet-connection-in-iot-gateway/12770/3 "2019-07-01T07:22:02Z")

</div>

A good first step is always to search this forum to see if the question has come up before.

> [@MQTT - Storing data when disconnected](https://discourse.nodered.org/t/mqtt-storing-data-when-disconnected/9306/9):
>
> So the Node-RED mqtt node has made qos 1 and 2 redundant by having a connection check around publish. The underlying mqtt client lib already manages messages correctly based on qos. In fact the mqtt client can be configured with a storage policy. The default policy is es6-map. If Node-RED is running in a constrained environment where qos\>0 can not be supported. Then I would expect qos to be set to 0 in that environment.

Which while not giving an answer, will give you lots of things to think about...

---

_[View the full topic](https://discourse.nodered.org/t/archiving-and-synchronization-of-data-along-with-time-stamp-with-mqtt-broker-after-failure-of-internet-connection-in-iot-gateway/12770)._