Tech Tip: CMMS Database Backup and Disaster Recovery

Challenge: Protecting Your CMMS Data From Disaster

Many Mainsaver customers have been using our software on-premise for over 20 years.  Their CMMS database is a rich resource for asset history, material usage, and purchasing data.  It is standard practice for mission-critical systems to be backed up daily and to have a disaster recovery plan in place for events affecting the IT infrastructure.  Yet with IT departments increasingly focused on the ERP package, there have been incidents where vital CMMS data has been lost due to ineffective backups. 

Solution: Prevent Loss of Data and Service Interruptions with CMMS Database Backups

Customers that use Mainsaver Core hosted in the Cloud can rest assured that the database is backed up every day and the application server network is distributed over multiple sites which provide continuous service in the event of one site being down. However, local installations require meticulous steps to prevent data loss and minimize interruptions.

Methodology For Protecting Your On-Premise Mainsaver Database

Customers that have the Mainsaver database and application products installed locally should follow these CMMS database backup and recovery steps. 

Backup Strategy:

  • Back up the Mainsaver database daily, preferably during off-peak hours, utilizing Microsoft SQL Server management tools for unattended backups. Regularly verify the existence of backup files with the Database Administrator.

File Redundancy:

  • Copy database backup files from the server hard drive to an alternate location, reducing the risk of simultaneous hard drive and backup losses. Automation tools can streamline this process.

Disaster Recovery Options:

  • Explore advanced disaster recovery options in Microsoft SQL Server, such as real-time ‘mirroring’ of the Mainsaver database onto another server. If the primary server fails, redirect workstations to the mirrored server.

Backup Server Identification:

  • In the event of a primary database server failure, identify a backup server. Conduct drills by restoring a current backup, setting up user logins, and testing access from a workstation. Document the entire procedure.

Documented Install Procedures:

  • Store all Mainsaver install images, Custom BIN Files (if applicable), and Serial Number files on a file server.
  • Ensure documented install procedures are readily available in case of workstation or web server failures.

Benefits of Proper CMMS Database Backup and Recovery Planning:

While server failures are uncommon, proactive preparation is indispensable to ensure uninterrupted MRO operations with your on-premise Mainsaver CMMS installation. Adopting these practices minimizes risks and enhances the reliability of your CMMS solution, safeguarding decades’ worth of critical data.

Learn more about Mainsaver’s maintenance management solutions

Mainsaver Cloud

CMMS

Mainsaver Cloud is the new web-based SaaS version of our CMMS platform that’s easy to use and implement, accessible anywhere, and affordable for small and medium-sized businesses.

Mainsaver Core

EAM

Mainsaver Core offers comprehensive enterprise asset management capabilities in a customizable on-premise or web-based solution that meets the needs of the largest and most complex organizations.

Learn more about Mainsaver’s maintenance management solutions

Mainsaver Cloud

CMMS

Mainsaver Cloud is the new web-based SaaS version of our CMMS platform that’s easy to use and implement, accessible anywhere, and affordable for small and medium-sized businesses.

Mainsaver Core

EAM

Mainsaver Core offers comprehensive enterprise asset management capabilities in a customizable on-premise or web-based solution that meets the needs of the largest and most complex organizations.