Umbria Database Maintenance Plan Requirements

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

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 Accounting server and Umbria.

Prod 9 p.m. EST

Test 11 p.m. EST

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.