![]() Microsoft Exchange Issues and FailuresĪdditionally, in the event of an issue, the solution isn’t always to restore from backup. You should always have a full working backup, especially before performing any type of maintenance, updates, or upgrades to your environment. There’s no excuse for not having a backup, especially if you call yourself a professional. It’s perfect for special migration and upgrade jobs, homelabs, and small/micro sized businesses.įor larger organizations, I’ve used, setup, implemented, and managed the following backup applications: If you’re looking for something free and easy, you could use the built-in Windows Server Backup function on Microsoft Windows Server. There are plenty of options to perform Microsoft Exchange-aware backups. Restoring the Exchange Server to a previous snapshot will cause a configuration synchronization gap between the Active Directory configuration and the mailbox database on the Exchange Server. Note that the configuration for Microsoft Exchange is stored inside of Active Directory, and not on the actual Exchange Server. ![]() Simply performing a VM snapshot is not supported and can break your Exchange installation. Not only do they backup the mailbox database and the VM running Exchange, but they also backup the system state and configuration of Microsoft Exchange. ![]() These applications are aware of Exchange and designed to perform proper backups of Exchange, the mailboxes, and configuration. You must use an Exchange-aware backup and/or disaster recovery application/software suite. To back up and restore Exchange Server, you must use an Exchange-aware application that supports the VSS writer for Exchange Server, such as Windows Server Backup (with the VSS plug-in), Microsoft System Center 2012 – Data Protection Manager, or a third-party Exchange-aware VSS-based application. ![]() Exchange Server includes a plug-in for Windows Server Backup that enables you to make and restore VSS-based backups of Exchange data. Microsoft Exchange Aware BackupsĮxchange Server supports only Exchange-aware, VSS-based backups. The above example is what you DO NOT want to do. This completely broke their Exchange install and possibly made it unrecoverable. In all of these cases the admins took a snapshot of their Exchange virtual machine (in Hyper-V or ESXi/VMware), and then restored it to the previous point when the failure occurred. In the past week I’ve had over 30 people reach out to me via chat looking for help and advice in situations where: Today I wanted to do a brief post addressing Microsoft Exchange Backup and Disaster Recovery. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |