Umbria Database Maintenance Plan Requirements

Follow the recommended action plan below to maintain your Umbria installation.

SQL Server:

1. Backup- all tables, full backup with verify (daily)
2. Transaction log backup and shrink (every 15 minutes) (Production only)
3. Check database integrity (daily)
4. Reorganize index (daily)
5. Update statistics (daily)
6. Rebuild index (weekly)
7. Maintenance cleanup (daily)

8. Reorganize full text indexes weekly (for queries and more help on this, see the Appendix folder for Full Text Indexing)

Backup Retention

Client-determined.

Email Notifications

Upon completion.

Email notification for database size on threshold.

Recovery Mode

Ensure Production databases are set to full recovery mode once imported.

Dev and Testing on simple mode.

Backup Scheduling

No backups or maintenance during import process on both Time and Billing server and Umbria. Also ensure it is out of the timeframe of VMWare/HyperV hosting server backups.

Prod 9 p.m. EST for example

Test or Development or UAT 11 p.m. EST for example

Memory

Memory maximum, set limit.

Example:

• 32 GB system
  • 4 GB for Windows (TBD on additional applications) (Min 2 GB)
  • 28 GB for SQL
• 25-50 percent memory/size of database

Disk

Separate Data/Logs/Temp onto separate disks.

Temp Database

Grow by 1 GB; confirm it is not growing all the time.

Size is by largest transaction, may need to be tested for default allocation based on initial import.

Service Monitoring

It is strongly recommended, to have system monitoring on the system, for services. Sometimes with system updates, server failures and reboots, services for umbria might not start.

For monitoring, you can use the SCOM Windows Server monitoring platform, or another third party tool.

 

Web Server (Web Service):

This can be monitored from the Umbria admin panel under Service Agents or the Welcome tab. A line appears for Web Server.

Additionally a monitoring alert can be placed on IIS (Internet Information Services) panel on the server if the Application Pool stops.

 

Agent Server (App/Windows Service):

A monitoring alert can be set on this server against the Umbria Agent Service in the Windows Services panel in Windows Server. Additionally, the service should set to start the service if a failure occurs.

This can be also monitored from the Umbria admin panel under Service Agents or the Welcome tab. A line appears for Agent Server.

 

Elastic Search:

A monitoring alert can be set on this server against the Elastic Search Service in the Windows Services panel in Windows Server. Additionally, the service should set to start the service if a failure occurs. That service will be on the server where Elastic is installed which typically is the Umbria Agent Server. Also the Umbria Agent service would need to be restarted after an Elastic Service restart.

In addition, typically if the Umbria Agent Service is stopped, elastic capabilities in Umbria may be non functional. Restart the Agent service.

 

SQL:

SQL can be configured to notify if the SQL services are stopped. If these are stopped and the database is unaccessible, the Umbria login will bring the user to the install page.