Enterprise ERP Backup Guidance

What objects should be backed for EEEP (Munis) to reduce the risk of data loss?

• Enterprise ERP

• Server

• Network

• On-Premise

• SQL

• Backup plans

Backup plans should be in place to reduce the risk of data loss due to a variety of causes. 

SQL Backups:

• A nightly backup of all production databases.  Default EERP database maintenance plans are scheduled to execute a full database backup on the local database server for the production databases at 10:00 pm local time; differential backups are scheduled to execute for the munprod and tylercmprod database every two hours from 10:30 am to 6:30 pm local time.

• There is an on-demand backup job that can be used to manually execute a full database backup of the Production EERP database (munprod).

• Databases can be manually backed up if the nightly backup is not feasible for the use-case. Users will need administrative access to the SQL server, typically an IT department task. A user can then connect to SQL Server Management Studio (SSMS) to take a manual backup of the database in question. Microsoft instructions for taking a manual database backup via SSMS or T-SQL can be found here.

File backups:

• EERP and other products have specific directories that store application-level settings and other important files. It is important to have a good backup of these directories in case a file is modified or there is a loss of file(s) in these directories.

• The following directories should be backed up at or after 2:00AM:

  • Application Server:

    • DATA_DRIVE\dbexport

    • DATA_DRIVE\musys

    • DATA_DRIVE\cmd

  • *Database Server:

    • *DATA_DRIVE\dbexport

  • Infrastructure Server:

    • Nothing

  • TCM Server:

    • DATA_DRIVE\ApacheCerts

    • DATA_DRIVE\TylerForms

  • Time & Attendance Server:

    • DATA_DRIVE\ET_Prod

  • External Web Server:

    • DATA_DRIVE\MSSCustom

    • DATA_DRIVE\inetpub\tylerroot\