XADM: Exchange 2000 Server Attempts to Restore Copy Backup Instead of Full Backup (265145)
The information in this article applies to:
- Microsoft Exchange 2000 Server
This article was previously published under Q265145 SYMPTOMS
When you attempt to restore a database, you expect Exchange 2000 Server to indicate that a full backup that you previously created is needed to complete the restore operation, but it indicates that a copy backup is needed instead. If you did not save the copy backup, you are unable to restore the database.
This problem typically occurs after you create a full backup of more than one database. If you create a copy backup of one of the databases at a later time, and then create a full backup of a different database, the copy backup and the second full backup are used during the restore operation instead of the original full backup.
CAUSE
After you create a copy backup, the Extensible Storage Engine (ESE) may not be able to distinguish between the copy backup and a full backup. Therefore, if you create a full backup of part of the storage group after you create the copy backup, some of the log files that are needed to restore the previous full backup may be deleted. As a result, you must restore the copy backup to obtain the most recent version of the database.
WORKAROUND
To work around this problem, always save copy backups that you create, and protect them in the same manner that you would protect a full backup.
STATUSMicrosoft has confirmed that this is a problem in Microsoft Exchange 2000 Server.
| Modification Type: | Minor | Last Reviewed: | 4/21/2005 |
|---|
| Keywords: | kbbug kbnofix KB265145 |
|---|
|