When using System Center Data Protection Manager 2010 to protect an Exchange Server 2010 solution there are four essential steps that need to occur in order for the backup to be successful.
1) Volume shadow copy is made of the Exchange data on the host where the backup is initiated.
2) The data on the shadow copies is transferred to the Data Protection Manager server.
3) All Exchange log files and database files in the backup set have an optional consistency check performed.
4) Backup complete is performed allowing for log truncation activities (if applicable).
Step #1: Create shadow copies
Data Protection Manager 2010 performs three different types of shadow copy backup operations against an Exchange 2010 server. The type of shadow copy performed is dependent both on the job settings and the configuration of the Exchange installation.
The three types of shadow copies performed:
1) Full Shadow Copy
The full shadow copy is performed as part of initial replica creation and during each express full backup. The full shadow copy will include all Exchange log files and all Exchange database files and includes a call for log truncation to occur upon successful backup completion. Full shadow copies will occur on all standalone databases, and on selected database copies if the Exchange Server is in a Database Availability Group configuration. (Only a single copy of a database in a DAG may be enabled for full shadow copy).
2) Incremental Shadow Copy
The incremental shadow copy will as part of continuous protection of the mailbox database. The incremental shadow copy will include all Exchange log files and includes a call for log truncation to occur upon successful backup completion. Incremental shadow copies can occur on all standalone databases and on selected database copies if the Exchange Server is in a Database Availability Group configuration. (Only a single copy of a database in a DAG may be enabled for incremental shadow copy – selection is inherited by the copy enabled for full shadow copy and cannot be specified separately).
3) Copy Shadow Copy
The copy shadow copy is performed on selected database copies if the Exchange Server is in a Database Availability Group configuration. The copy shadow copy will be performed on initial replica creation and during each express full backup. A copy backup includes all Exchange log files and all Exchange database files but does not call for log truncation to occur upon successful full backup. (The databases selected for this operation could be all or none of the copies not enabled for full shadow copy).
The creation of shadow copies is the first part of an Exchange backup using DPM 2010. An administrator would expect the shadow copy process to complete quickly. The creation of the shadow copies must be successful in order for the backup process to continue.
For a Full Shadow Copy (standalone) the administrator may note the following events in the application log :
Index: 1 Time: 11/29/2010 8:28:04 AM ID: 9606 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7a595f8f-2a18-4f1a-a68d-aa3757ba6c3e) has prepared for backup successfully.
Index: 2 Time: 11/29/2010 8:28:07 AM ID: 2005 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 4 starting. This will be a Full shadow copy.
For more information, click http://www.microsoft.com/contentredirect.asp.
Index: 3 Time: 11/29/2010 8:28:07 AM ID: 9811 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 4) has successfully prepared the database engine for a full or copy backup of database 'MBX-1-DB0'.
Index: 4 Time: 11/29/2010 8:28:07 AM ID: 9608 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7a595f8f-2a18-4f1a-a68d-aa3757ba6c3e:4) has prepared for Snapshot successfully.
Index: 5 Time: 11/29/2010 8:28:07 AM ID: 2001 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 4 freeze started.
Index: 6 Time: 11/29/2010 8:28:07 AM ID: 2001 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) MBX-1-DB0: Shadow copy instance 4 freeze started.
Index: 7 Time: 11/29/2010 8:28:07 AM ID: 9610 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7a595f8f-2a18-4f1a-a68d-aa3757ba6c3e:4) has frozen the database(s) successfully.
Index: 8 Time: 11/29/2010 8:28:07 AM ID: 2003 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 4 freeze ended.
Index: 9 Time: 11/29/2010 8:28:07 AM ID: 9612 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7a595f8f-2a18-4f1a-a68d-aa3757ba6c3e:4) has thawed the database(s) successfully.
Index: 10 Time: 11/29/2010 8:28:08 AM ID: 9622 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7a595f8f-2a18-4f1a-a68d-aa3757ba6c3e:4) has processed the post-snapshot event successfully.
For an Incremental Shadow Copy (standalone) the administrator may note the following events in the application log:
Index: 0 Time: 11/29/2010 8:49:39 AM ID: 9606 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7d3e1a06-76ce-4b12-a313-98edd703705a) has prepared for backup successfully.
Index: 1 Time: 11/29/2010 8:49:42 AM ID: 2008 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 8 starting. This will be an Incremental shadow copy.
Index: 2 Time: 11/29/2010 8:49:42 AM ID: 9812 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 8) has successfully prepared the database engine for an incremental or differential backup of database 'MBX-1-DB0'.
Index: 3 Time: 11/29/2010 8:49:42 AM ID: 9608 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7d3e1a06-76ce-4b12-a313-98edd703705a:8) has prepared for Snapshot successfully.
Index: 4 Time: 11/29/2010 8:49:42 AM ID: 2001 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 8 freeze started.
Index: 5 Time: 11/29/2010 8:49:42 AM ID: 2001 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) MBX-1-DB0: Shadow copy instance 8 freeze started.
Index: 6 Time: 11/29/2010 8:49:42 AM ID: 9610 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7d3e1a06-76ce-4b12-a313-98edd703705a:8) has frozen the database(s) successfully.
Index: 7 Time: 11/29/2010 8:49:43 AM ID: 2003 Level: Information Source: ESE Machine: MBX-1.exchange.msft Message: Information Store (3596) Shadow copy instance 8 freeze ended.
Index: 8 Time: 11/29/2010 8:49:43 AM ID: 9612 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7d3e1a06-76ce-4b12-a313-98edd703705a:8) has thawed the database(s) successfully.
Index: 9 Time: 11/29/2010 8:49:44 AM ID: 9622 Level: Information Source: MSExchangeIS Machine: MBX-1.exchange.msft Message: Exchange VSS Writer (instance 7d3e1a06-76ce-4b12-a313-98edd703705a:8) has processed the post-snapshot event successfully.
For a Full Shadow Copy (Database Availability Group / Active Mailbox Database Copy hosted on server MBX-2) the administrator may note the following events in the application log:
Index: 20 Time: 11/29/2010 9:04:39 AM ID: 2021 Level: Information Source: MSExchangeRepl Machine: MBX-2.exchange.msft Message: The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.
Index: 21 Time: 11/29/2010 9:04:40 AM ID: 9606 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 714e46f9-22ee-4b8a-a1d6-92bc6c84083c) has prepared for backup successfully.
Index: 22 Time: 11/29/2010 9:04:43 AM ID: 2005 Level: Information Source: ESE Machine: MBX-2.exchange.msft Message: Information Store (3360) Shadow copy instance 2 starting. This will be a Full shadow copy.
Index: 23 Time: 11/29/2010 9:04:43 AM ID: 9811 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 2) has successfully prepared the database engine for a full or copy backup of database 'DAG-DB0'.
Index: 24 Time: 11/29/2010 9:04:43 AM ID: 9608 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 714e46f9-22ee-4b8a-a1d6-92bc6c84083c:2) has prepared for Snapshot successfully.
Index: 25 Time: 11/29/2010 9:04:43 AM ID: 2001 Level: Information Source: ESE Machine: MBX-2.exchange.msft Message: Information Store (3360) Shadow copy instance 2 freeze started.
Index: 26 Time: 11/29/2010 9:04:43 AM ID: 2001 Level: Information Source: ESE Machine: MBX-2.exchange.msft Message: Information Store (3360) DAG-DB0: Shadow copy instance 2 freeze started.
Index: 27 Time: 11/29/2010 9:04:43 AM ID: 9610 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 714e46f9-22ee-4b8a-a1d6-92bc6c84083c:2) has frozen the database(s) successfully.
Index: 28 Time: 11/29/2010 9:04:44 AM ID: 2003 Level: Information Source: ESE Machine: MBX-2.exchange.msft Message: Information Store (3360) Shadow copy instance 2 freeze ended.
Index: 29 Time: 11/29/2010 9:04:44 AM ID: 9612 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 714e46f9-22ee-4b8a-a1d6-92bc6c84083c:2) has thawed the database(s) successfully.
Index: 30 Time: 11/29/2010 9:04:45 AM ID: 9622 Level: Information Source: MSExchangeIS Machine: MBX-2.exchange.msft Message: Exchange VSS Writer (instance 714e46f9-22ee-4b8a-a1d6-92bc6c84083c:2) has processed the post-snapshot event successfully.
For a Copy Shadow Copy (Database Availability Group / Passive Mailbox Database Copy hosted on server MBX-3) the administrator may note the following events in the application log:
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:21 AM Event ID: 2021 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:25 AM Event ID: 2110 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange VSS Writer instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa has successfully prepared for a full or a copy backup of database 'DAG-DB0'. The following database will be backed up: DAG-DB0.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:25 AM Event ID: 2023 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa) successfully prepared for backup.
Log Name: Application Source: MSExchangeIS Mailbox Store Date: 11/29/2010 6:01:35 AM Event ID: 9539 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange Information Store database "09067c7d-64f6-4b2a-aa91-aca0229c2025: /o=Exchange/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MBX-1/cn=Microsoft Private MDB" was stopped.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:35 AM Event ID: 2027 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange VSS Writer instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa has successfully frozen the databases.
Log Name: Application Source: ESE BACKUP Date: 11/29/2010 6:01:35 AM Event ID: 960 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: msexchangerepl (2228) This computer is performing a surrogate backup. The master server is MBX-2.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:35 AM Event ID: 2025 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa) successfully prepared for a snapshot.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:36 AM Event ID: 2029 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange VSS Writer instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa has successfully thawed the databases.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:01:37 AM Event ID: 2035 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 95661579-1ddb-4826-9e0a-a0ceed92a2aa) has successfully processed the post-snapshot event.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:03:37 AM Event ID: 2114 Task Category: Service Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The replication instance for database DAG-DB0 has started copying log files. The first log file copied was generation 187.
Log Name: Application Source: MSExchangeIS Mailbox Store Date: 11/29/2010 6:03:37 AM Event ID: 1000 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Attempting to start the Information Store "DAG-DB0".
Log Name: Application Source: ESE BACKUP Date: 11/29/2010 6:03:41 AM Event ID: 963 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: msexchangerepl (2228) The surrogate backup procedure to MBX-2 has been successfully completed.
For a Full Shadow Copy (Database Availability Group / Passive Mailbox Database Copy hosted on server MBX-2) the administrator may note the following events in the application log:
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:18:17 AM Event ID: 2021 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:26 AM Event ID: 2110 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange VSS Writer instance 06f76857-2e99-436a-baa1-c0336c7f918c has successfully prepared for a full or a copy backup of database 'DAG-DB1'. The following database will be backed up: DAG-DB1.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:26 AM Event ID: 2023 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 06f76857-2e99-436a-baa1-c0336c7f918c) successfully prepared for backup.
Log Name: Application Source: MSExchangeIS Mailbox Store Date: 11/29/2010 6:21:29 AM Event ID: 9539 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange Information Store database "8c319775-6c8b-4780-b90f-81a6ac63714d: /o=Exchange/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=MBX-1/cn=Microsoft Private MDB" was stopped.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:29 AM Event ID: 2027 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange VSS Writer instance 06f76857-2e99-436a-baa1-c0336c7f918c has successfully frozen the databases.
Log Name: Application Source: ESE BACKUP Date: 11/29/2010 6:21:29 AM Event ID: 960 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: msexchangerepl (2356) This computer is performing a surrogate backup. The master server is MBX-3.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:30 AM Event ID: 2025 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 06f76857-2e99-436a-baa1-c0336c7f918c) successfully prepared for a snapshot.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:30 AM Event ID: 2027 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange VSS Writer instance 06f76857-2e99-436a-baa1-c0336c7f918c has successfully frozen the databases.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:31 AM Event ID: 2029 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange VSS Writer instance 06f76857-2e99-436a-baa1-c0336c7f918c has successfully thawed the databases.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:31 AM Event ID: 2035 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The Microsoft Exchange Replication service VSS Writer (Instance 06f76857-2e99-436a-baa1-c0336c7f918c) has successfully processed the post-snapshot event.
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:21:34 AM Event ID: 2114 Task Category: Service Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: The replication instance for database DAG-DB1 has started copying log files. The first log file copied was generation 194.
Log Name: Application Source: MSExchangeIS Mailbox Store Date: 11/29/2010 6:21:34 AM Event ID: 1000 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Attempting to start the Information Store "DAG-DB1".
Log Name: Application Source: ESE BACKUP Date: 11/29/2010 6:23:35 AM Event ID: 963 Task Category: General Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: msexchangerepl (2356) The surrogate backup procedure to MBX-3 has been successfully completed.
For a Copy Shadow Copy (Database Availability Group / Active Mailbox Database Copy hosted on server MBX-3) the administrator may not the following events in the application log:
Log Name: Application Source: MSExchangeRepl Date: 11/29/2010 6:56:39 AM Event ID: 2021 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: The Microsoft Exchange VSS Writer has successfully collected the metadata document in preparation for backup.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:40 AM Event ID: 9606 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 266b4cbc-3c4f-4e0d-891f-ad18193b80f4) has prepared for backup successfully.
Log Name: Application Source: ESE Date: 11/29/2010 6:56:42 AM Event ID: 2009 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Information Store (3220) Shadow copy instance 2 starting. This will be a Copy shadow copy.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:42 AM Event ID: 9811 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 2) has successfully prepared the database engine for a full or copy backup of database 'DAG-DB1'.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:42 AM Event ID: 9608 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 266b4cbc-3c4f-4e0d-891f-ad18193b80f4:2) has prepared for Snapshot successfully.
Log Name: Application Source: ESE Date: 11/29/2010 6:56:43 AM Event ID: 2001 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Information Store (3220) Shadow copy instance 2 freeze started.
Log Name: Application Source: ESE Date: 11/29/2010 6:56:43 AM Event ID: 2001 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Information Store (3220) DAG-DB1: Shadow copy instance 2 freeze started.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:43 AM Event ID: 9610 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 266b4cbc-3c4f-4e0d-891f-ad18193b80f4:2) has frozen the database(s) successfully.
Log Name: Application Source: ESE Date: 11/29/2010 6:56:43 AM Event ID: 2003 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Information Store (3220) Shadow copy instance 2 freeze ended.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:43 AM Event ID: 9612 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 266b4cbc-3c4f-4e0d-891f-ad18193b80f4:2) has thawed the database(s) successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 6:56:44 AM Event ID: 9622 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-3.exchange.msft Description: Exchange VSS Writer (instance 266b4cbc-3c4f-4e0d-891f-ad18193b80f4:2) has processed the post-snapshot event successfully.
Step #2: Transferring shadow copy data to the DPM 2010 server
After the successful creation of shadow copies the data in the shadow copy volume is transferred to the DPM 2010 server. (Note: If the protection method is to tape instead of to disk – Step #2 and Step #3 are reversed). The data is transferred via the network connection between the Exchange server hosting the shadow copy data and the DPM 2010 server.
The amount of data to be copied to the DPM server depends on the type of backup performed.
For a Full Shadow Copy <or> a Copy Shadow Copy that is the initial replica creation the data transfer to the DPM server will include all log files at the time of backup initiation and the full database.
For a Full Shadow Copy <or> a Copy Shadow Copy that is an express full backup the data transfer to the DPM server will include all log files and delta changes to the database from the initial replica creation or previous express full backup.
For an Incremental Shadow Copy the data transfer to the DPM server will include all log files.
The amount of time that the transfer to the DPM server takes is largely dependent on the size of the data set to be transferred, performance of the hosts involved, and performance of the network.
DPM 2010 does allow the administrator to optimize the performance of the protection group by enabling a setting to allow on the wire compression. This setting is not enabled by default.
Once the data has been successfully transmitted to the DPM 2010 server the backup can proceed to the next step.
Step #3: Running consistency check
After the data has been streamed to the DPM 2010 server the process of consistency checking can begin. (Note: If the protection method is to tape instead of disk – Step #2 and Step #3 are reversed. Consistency checking is then performed on the Exchange Server hosting the shadow copy storage rather then the DPM 2010 server).
Consistency checking in DPM is completely optional and can have the following three settings:
Disabled
Enabled – Log Files Only
Enabled – Database and Log Files
We do have some recommendations on how consistency checking is utilized. If the Exchange Server 2010 mailbox database is standalone, it is recommended that both log file consistency check and database consistency check be performed. This assumes that DPM 2010 is the primary recovery method for this database. If the Exchange Server 2010 mailbox database is hosted in a Database Availability Group, it is recommended that only the log files be consistency checked. This assumes that the DAG is the primary recovery method for this database.
The consistency check will verify the integrity of the log files and the database files that reside on the DPM server. Should a consistency check be performed, and a corruption be identified, the backup will be considered failed.
By copying delta data sets to the DPM 2010 server, and performing consistency check on the DPM 2010 server itself, the performance impacts associated with consistency checking are offloaded from the Exchange Server itself. (Note that this assumes protection to disk rather then protection to tape). The consistency check on the DPM 2010 server is achieved by using eseutil.exe and ese.dll from your Exchange installations. It is important that administrators ensure that the highest version of these two binaries exists on the DPM 2010 server. For example, if when DPM was originally installed the administrator was using Exchange Server 2010 RTM and a single mailbox server is upgraded to Exchange Server 2010 SP1 – the binaries for eseutil.exe and ese.dll on the DPM server should be replaced with the Exchange Server 2010 SP1 binaries, since this is the highest revision in use in the protected environment.
The length of time the consistency check takes is largely dependent on the size of the database and the number of log files included in the backup set. Recently we have encountered some customers that have reported DPM backups not completing or not completing in a timely fashion. After reviewing the environments, consistency check was enabled for log files as recommended. In these cases there was a significant number of delta log files due to migrations (circa 100 gig in my reference scenario). In this case we simply worked around this by temporarily disabling consistency checking and allowing the express full backup to complete. Once these logs were truncated and we were back to a “normal” log generation cycle, consistency checking was re-enabled as recommended.
Step #4: Backup complete
At this stage the shadow copies, consistency check, and data transfer have completed successfully. At this time the Exchange writer can be informed that the backup completed successfully. It is also at this time that if a full shadow copy <or> incremental shadow copy was performed that log truncation can occur for logs that are eligible for truncation. This is a very important step, if backup complete is not called by the application future backups are subject to fail with an error that a backup is already in progress. (This may necessitate restarting the Information Store service on order to clear this condition). Please note that log truncation no longer occurs as a part of the backup process, therefore it is not necessary for logs to truncate in order for the backup to be completed successfully. It may be several minutes until the log file truncation is actually processed on the hosts.
A note regarding log truncation…
On a Database Availability Group server there is a 225 event indicating that no log files can be truncated. If careful attention is paid to the event it will be noticed that the source of the event is ESE. This event is expected on a DAG member, since ESE is not responsible for determining which log files in a replicated environment should be truncated.
The following events may be found in the application log regarding the Exchange backup when a Full Shadow Copy <or> Incremental Shadow Copy are performed of a Database Availability Group:
Log Name: Application Source: ESE Date: 11/29/2010 7:34:30 AM Event ID: 225 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Information Store (3360) DAG-DB0: No log files can be truncated.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:34:30 AM Event ID: 9827 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance 10105fe3-5935-46dc-8aa8-4edb9ca0cb48:4) has successfully completed the full or incremental backup of replicated database 'DAG-DB0'. The log files will be truncated after they have been replayed.
Log Name: Application Source: ESE Date: 11/29/2010 7:34:30 AM Event ID: 2006 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Information Store (3360) Shadow copy instance 4 completed successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:34:30 AM Event ID: 9616 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance 10105fe3-5935-46dc-8aa8-4edb9ca0cb48:4) has processed the backup completion event successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:34:31 AM Event ID: 9648 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance 10105fe3-5935-46dc-8aa8-4edb9ca0cb48:4) has processed the backup shutdown event successfully.
The following events may be found in the application log regarding the Exchange backup when a Full Shadow Copy <or> Incremental Shadow Copy is performed of a Standalone Server:
Log Name: Application Source: ESE Date: 11/29/2010 7:39:36 AM Event ID: 224 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-1.exchange.msft Description: Information Store (3596) MBX-1-DB0: Deleting log files c:\MBX-1\MBX-1-DB0\E00000000DF.log to c:\MBX-1\MBX-1-DB0\E00000000E5.log.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:39:36 AM Event ID: 9780 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-1.exchange.msft Description: Exchange VSS Writer (instance 7f301ea2-f4ee-4521-b386-31c159293dcd:11) has successfully completed the full or incremental backup of database 'MBX-1-DB0'.
The database engine has also successfully executed log file truncation procedures for this database. (Note that this may or may not have resulted in the actual truncation of log files, depending on whether any log files existed that were candidates for truncation.)
Log Name: Application Source: ESE Date: 11/29/2010 7:39:36 AM Event ID: 2006 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-1.exchange.msft Description: Information Store (3596) Shadow copy instance 11 completed successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:39:36 AM Event ID: 9616 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-1.exchange.msft Description: Exchange VSS Writer (instance 7f301ea2-f4ee-4521-b386-31c159293dcd:11) has processed the backup completion event successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:39:38 AM Event ID: 9648 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-1.exchange.msft Description: Exchange VSS Writer (instance 7f301ea2-f4ee-4521-b386-31c159293dcd:11) has processed the backup shutdown event successfully.
The following events may be found in the application log regarding the Exchange backup when a Copy Shadow Copy is performed:
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:49:23 AM Event ID: 9781 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance b7990a10-5077-49f7-ad9b-f40e6a92019e:5) has successfully completed the copy or differential backup of database 'DAG-DB0'. No logfiles were truncated for this database.
Log Name: Application Source: ESE Date: 11/29/2010 7:49:23 AM Event ID: 2006 Task Category: ShadowCopy Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Information Store (3360) Shadow copy instance 5 completed successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:49:23 AM Event ID: 9616 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance b7990a10-5077-49f7-ad9b-f40e6a92019e:5) has processed the backup completion event successfully.
Log Name: Application Source: MSExchangeIS Date: 11/29/2010 7:49:25 AM Event ID: 9648 Task Category: Exchange VSS Writer Level: Information Keywords: Classic User: N/A Computer: MBX-2.exchange.msft Description: Exchange VSS Writer (instance b7990a10-5077-49f7-ad9b-f40e6a92019e:5) has processed the backup shutdown event successfully.