To reduce manual system maintenance and downtime, Orbis recommends:

  1. Adjust default log rotation settings to meet the client’s needs.
  2. Provide ample disk space for application, log, and data files.
  3. Configure the client’s system monitoring software to provide sufficient lead time should a system resource exceed predefined thresholds.
  4. Exploit RSuite’s health monitor plugin, if not also a related community RSuite plugin.
  5. Employ the likes of cron jobs to delete obsolete data in temp and workflow data directories.
  6. For RSuite’s MarkLogic and non-XML data stores, employ RSuite version purge policies to avoid retaining a material amount of data that has no remaining business value.
  7. For RSuite’s MySQL database, assess how long workflow and an application’s use of RSuite’s Pubtrack feature (which stores data in this database) has business value, and decide if this should be a manual or automated trim.  Those that do trim this database down typically elect to do this manually.
  8. Assess if any RSuite extensions will be creating additional data, where that data will be stored, when it would no longer be valuable, and whether this data would be covered by another measure.

Clients that do not sufficiently implement recommendations 1 through 3 spend more time maintaining their systems and incur more downtime.

Another source of maintenance is service bulletins.  Orbis occasionally issues service bulletins which recommend system administrators install an update, make a configuration change, etc. when applicable to their deployment.  These have been rare, and are typically in response to a recently exposed issue with RSuite or a sub-component.  Examples include “ImageMagick Security Vulnerability Mitigation” and “Windows Platform Daylight Savings Time Patch Available for MarkLogic 6, 7 and 8”.