| NowSMS - SQLLite DB |  Search
|
|
NowSMS Support Forums ⬆ NowSMS Support - SMS Issues ⬆ Archive through June 03, 2020 ⬆ |
◄ ► |
| Author | Message | |||
| Jose Mosquera New member Username: Jmosquera Post Number: 2 Registered: 04-2019 |
Hello Can you provide more information regarding the following details around the SQLlite DB(s) and other configuration files? 1) With SQLLite DB, is there any administration we need to perform to maintain its speed? Is data held indefinitely or purged regularly? 2) Should we back up the SQLite DB in case of the node going down permanently? If so where is it? 3) Is it advisable to copy this DB over to a new install of NowSMS when recovering/rebuilding a node? 4) In the event of corruption, are there any steps we should take to safeguard the node/cluster and other data? 5) In a cluster setup, how does each node keep track of delivery and receipt msgs? Is the DB stored on shared storage? 6) If not on shared storage how does each node access other nodes SQLLite DB, how is this achieved (TCP, Named Pipes)? 6) How does a new node register itself within an existing cluster? Many Thanks Jose | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5991 Registered: 08-2008 |
Hi, Please refer to my reply to your related post: https://support.nowsms.com/discus/messages/1/74303.html Specifically, the MessageIDPrefix setting. Assigning a unique prefix to each Front-end server is recommended. The SQLite DBs are used only to track upstream message ID assignments. Each node will create one and add entries as messages are routed upstream. Assuming shared storage, other nodes can read from each other’s database to correlate message ids for delivery reports. A new database is created daily per node to minimize corruption issues. The length of retention is described here: https://support.nowsms.com/discus/messages/1/59932.html — Does NowSMS Support | |||
| Jose Mosquera New member Username: Jmosquera Post Number: 6 Registered: 04-2019 |
So to clarify 1) SQLLite DB lives in shared storage but each node creates it's own DB 2) This is how other nodes are able to read the DB's of other nodes to correlate msg ids 3) As long as this shared storage is reliable and backed up we should be ok So would I be correct in assuming that if a node has to be rebuilt, 1) a new DB is built 2) the Msg ID assignment can still be read from the old DB - which is retained for up to 2 weeks 3) therefore no data is stored on the local node apart from some logs.. | |||
| Des - NowSMS Support Board Administrator Username: Desosms Post Number: 5997 Registered: 08-2008 |
Correct | |||
