UtopiaSync Maintenance
A brief overview of why, how and where to deal with Maintenance in your UtopiaSync Instance
PreviousUtopiaSync Custom ConfigurationNextHow Moditar drove efficiency for Meridian Wine Merchants using Utopia iPaaS
Last updated
A brief overview of why, how and where to deal with Maintenance in your UtopiaSync Instance
Last updated
If you have been using Utopia for a while you might have noticed that the data base sizes tend to grow! What is the cause?
For one, the more you use it the greater the data being held, but secondly one of the features of Utopia is the extensive logging it create. This logging has a large impact on the space used. Take a look at our which describes the logs and where you can find logging.
Utopia has a built in maintenance process which will keep the mongoDB under control, with separate maintenance functions for documents and logs, for example you can keep documents for 3 months but logs for 1 week. These maintenance features can also be excluded from data by not selecting the maintenance toggle on the collections in the Utopia UI.
In order to allow this process to happen you have to connect an S3 database to the cluster, the configs can be found in microservices deployment and the secrets area of your cluster.
The MySQL tables (SQL) will have to be maintained externally. Other external maintenance recommendations include Compacting and reindexing for MongoDB collections. Setting up the retention time in S3 buckets will help maintain those.