Service Pack 3 (SP3) and later for Exchange Server includes several security and performance enhancing improvements that offer the user more customized experience. It is recommended to always perform a full database backup before the update on your Exchange database computer. This is due to install the update and upgrade of Exchange mailbox server can make unmountable the database. In such cases you have to change your current use> Database Backup to restore them or run effective Exchange Server Recovery with third-party tools.
To examples of this that you have Exchange Server 2000 SP2 and try to update it using Exchange Server 2003. If you try to mount the database, you may come across the below entry in the Application log of Event Viewer:
Type: Error
Source: ESE
Category: General
Event ID: 505
Description: Information StoreFailed (2028) An attempt to open the compressed file Drive: \ Exchsrvr \ MDBDATA \ priv1.edb "for read / write access, because they are not converted to a normal file. The opened file will fail with error -4005 (0xfffff05b). To prevent this error, that in the future, you can manually unzip the file and change the compression state of the folder to uncompressed. Writing to this file when it is compressed is not supported.
Possibly an event with ID 9519, thesuggests that failure to attach to Jet DB.
CAUSE
Can not deploy Exchange Server SP3 and later compressed information store databases. This is because the database files compress sector independence, which is required by ESE to log-based recovery is invalid. So, if contains Exchange Server prior to SP3 NTFS compressed database, it will not be loaded. Even such a compressed database can be damaged
Solution
To isolate the given problem, use thefollowing steps:
Dismount all databases
You can then unzip the folder of logs and databases
Use eseutil / d to perform offline defragmentation of databases
However, if you damage your database by the NTFS compression, you should recover from the available backup. If this does not give the desired result, you need to repair an Exchange software and the database. Exchange recovery tools use high-end restorationHow to repair database algorithms, which also reliable and safe.
