From Technet Docs: " If you restore an older file copy of the database, the checkpoint will be too far ahead, and Exchange Server tries to start log file replay from a log file that is too new.You can solve this problem by removing the checkpoint file; thus forcing Exchange Server to scan all available logs." My question: When we restore a backup, the check point file is restored from the tape which is the check point file with the database and transaction log files in the tape. Then why is the checkpoint file pointing to a new log file. ( If the check point file was not backed up , then the new checkpoint file would be too ahead) Really appreciate any comments. Thanks Raj

Well, when you restore a backup the idea is that you restore the database and not the database AND logs. If you follow process and restore the database then the logs will be in another directory (volume) and the act of mounting the store will cause Exchange to put 2 and 2 together, then play the logs. If you restore everything you are only going to get a restore to the point of that backup. Properly laying the data out solves all of your problems. "raj_nair" wrote in message news:622b61d5-d458-4bf9-aa50-9bc4a08b155e... From Technet Docs: " If you restore an older file copy of the database, the checkpoint will be too far ahead, and Exchange Server tries to start log file replay from a log file that is too new.You can solve this problem by removing the checkpoint file; thus forcing Exchange Server to scan all available logs." My question: When we restore a backup, the check point file is restored from the tape which is the check point file with the database and transaction log files in the tape. Then why is the checkpoint file pointing to a new log file. ( If the check point file was not backed up , then the new checkpoint file would be too ahead) Really appreciate any comments. Thanks Raj Mark Arnold, Exchange MVP.

When you restore from an online backup , the checkpoint file is ignored.

Mark, Thanks for yur comment. But you put me in a little confusion. You said "Well, when you restore a backup the idea is that you restore the database and not the database AND logs." In online backups, what i know is the databases and transaction logs are backed up and then the transaction logs are truncated from exchange server. And in a normal restore process from an online backup, first the database is restored, and follwoing that the transaction logs from temporary directory is played and then the transaction logs from the production directory is played by the hard recovery process. At this point the database can be mounted. PS : what do you meant by another directory? Is it the temporary directory for log files ( where restore.env file is also there).