Introduction

Post the installation of Dynamics CRM 2011 Server, its maintenance, backup, and finally optimization need to be taken care of. The maintenance of Dynamics CRM 2011 requires familiarity with a wide range of servers, networks, mail systems, and so on.

After installation, the best practice is to back up some of the components. The backup would help to restore the server in the case of a failure of one or more components. A comprehensive backup and recovery mechanism should be in place before the Dynamics CRM 2011 solution is rolled out to end users for use.

The following components of the Dynamics CRM 2011 Server infrastructure need to be backed up (as recommended):

Another part of maintenance activities is to enable tracing when the system encounters errors. Dynamics CRM 2011 provides tracing capabilities. Tracing, by default, is disabled when Dynamics CRM 2011 components are installed. In this chapter, we will learn recipes on how to enable them.

We will also delve into the recipes on how to recover from a failure when it occurs. Recovering from a failure is very important, and we will explore how Dynamics CRM 2011 Server and SQL Server for Dynamics CRM 2011 can be recovered from a failure.

The last phase would be to look into the recipes for optimizing Dynamics CRM 2011 Server's performance. Performance optimization is a standard, nonfunctional requirement in any Dynamics CRM 2011 implementation. Though performance optimization greatly depends on the production network and infrastructure, we would explore the standard Dynamics CRM 2011 Server optimization methods.