Creating a better "Daily/Weekly/Monthly System Maintenance Tasks" list.

[Ryan_Wakefield]

Hello everyone,

So I have been working on putting together a list of all of the different System Maintenance Tasks that should be and can be performed on the OnBase system. Now yes, I am well aware of the items that are in the System Administration MRG. However, I want to go beyond that and get a more detailed list.

GENERAL Maintenance

Daily

• Confirm Successful Daily Backups
• Confirm Successful Database Backup
• Confirm Successful Database Transaction Log Backups
• Check Source Directories
• View SYS Unidentified Items
• Check Windows Event Viewer
• Check Document Locks
• Check Process Locks

Weekly

• Confirm Successful Weekly Backups
• Confirm Removable Media to Off-Site Location
• Record the Size and Free Space of the SQL Transaction Log Table
• Record the Size and Free Space of the OnBase Database
• Record the Size and Free Space of All Disk Groups
• Record All Free Space on Remaining Drives
• Run All System Configuration Reports
• Capture Performance Metrics
• Rebuild Database Indexes

Monthly

• Purge OnBase Transaction Log
• Confirm Successful Monthly Backups
• Confirm Tape Rotation to Off-Site Location
• Test Ability to Restore Files from Backups
• Test Ability to Restore OnBase Database
• Consider Rebooting All Servers
• Communicate with Local IT Staff
• Communicate with OnBase Users
• Communicate with Your Solution Provider

So what System Maintenance tasks do you perform? As well, are those maintenance tasks specific to your industry or are they more general like the ones above?

[Thomas_Reu]

Besides a scheduled iireset every night, I've found it useful to restart the onbase services every night or at least before work starts Monday.  For example: your database team makes a DB mod and schedules it in the middle of the night over the weekend.  Then, they reboot the DB server.  At that point, all of the onbase services will still have a status = running.  However, in real life, services like the distribution service are completely out to lunch.  Note: I couldn't find an easy way for a program to determine this.  Then I thought, why do I need a complex program to determine this.  So, I just created a quick bat file to stop and start the appropriate services.  This has saved me a lot of grief.  And as for long term code maintenance, there is almost nothing to maintain.

[Eliki_Damuni]

Great topic, Ryan!  Is anyone periodically resetting database statistics?

[Corinthia_Lill1]

Hi Eliki!  We update database statistics weekly.