Checklist: Performing Weekly Maintenance Checks
This topic describes the steps involved in performing weekly maintenance checks of the reliability, administration, security, and performance of a BizTalk Server system.
Ensure that each host has an instance running on at least two physical BizTalk servers (reliability check). For more information, go to High Availability for BizTalk Hosts.
Ensure that each receive location is redundant (reliability check). For more information, go to Scaling Out Receiving Hosts.
Ensure that the SQL Server Agent service is running on the SQL server (administration check). For more information, go to:
Ensure that all SQL Server jobs related to BizTalk Server are working properly (administration check). If the SQL Server Agent jobs are not running, system performance will degrade over time. For more information, go to:
Ensure that the SQL Server jobs responsible for backing up BizTalk Server databases are running normally (administration check). For more information, go to:
Ensure that the latest security updates are installed (security check). For more information, go to the Windows Update: FAQ.
Analyze weekly performance monitoring logs against baseline and thresholds (performance check). For more information, go to:
Ensure that the system is not experiencing frequent auto-growth of BizTalk Server databases (performance check). For more information, go to:
Run SQL Server Profiler during high load to check for long response times and high resource usage (performance check). For more information, go to Using SQL Server Profiler.
Ensure that message batching for all adapters is appropriate for resource consumption or latency (performance check). For more information, go to:
Ensure that the large message threshold is appropriate for resource consumption (performance check). For more information, go to How BizTalk Server Processes Large Messages.
Archive backup files and specify appropriate computers for backup.
To avoid potential data loss, you should specify a computer for your backup that is different from the computer with the original data, and for <destination path> you should specify a computer to store the database logs that is different from the computer with the original database logs.
For more information about best practices for backup, see Best Practices for Backing Up and Restoring Databases.