Export (0) Print
Expand All

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.

Steps Reference

Ensure that each host has an instance running on at least two physical BizTalk servers (reliability check).

High Availability for BizTalk Hosts

Ensure that each receive location is redundant (reliability check).

Scaling Out Receiving Hosts

Ensure that the SQL Server Agent service is running on the SQL server (administration check).

Ensure that all SQL Server jobs related to BizTalk Server are working properly (administration check).

Monitoring SQL Server Agent Jobs

If the SQL Server Agent jobs are not running, system performance will degrade over time. For more information about the SQL Server Agent jobs that BizTalk Server provides to help manage the BizTalk Server databases, see Database Structure and Jobs (http://go.microsoft.com/fwlink/?LinkID=153451).

Ensure that the SQL Server jobs responsible for backing up BizTalk Server databases are running normally (administration check).

Ensure that the latest security updates are installed (security check).

Microsoft Update site at http://update.microsoft.com/microsoftupdate/v6/default.aspx

Analyze weekly performance monitoring logs against baseline and thresholds (performance check).

Ensure that the system is not experiencing frequent auto-growth of BizTalk Server databases (performance check).

Run SQL Server Profiler during high load to check for long response times and high resource usage (performance check).

Using SQL Server Profiler (http://go.microsoft.com/fwlink/?LinkID=106720).

Ensure that message batching for all adapters is appropriate for resource consumption or latency (performance check).

Ensure that the large message threshold is appropriate for resource consumption (performance check).

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 (http://go.microsoft.com/fwlink/?LinkID=151391).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft