There has been a lot of discussions in the Exchange ecosystem (see comments on this post and other posts on our blog for example) about the fact that Windows Server 2008 built-in backup application (Windows Server Backup) is not Exchange-aware. Even though we have also clarified that the limitation does not apply to Windows Small Business Server 2008, we still kept getting a lot of open and honest feedback on the subject, which we greatly appreciate. Background About 2 years ago, when the Exchange team started testing Exchange 2007 on Windows 2008, we found that the built-in backup application had changed dramatically. Decisions that drove that change by the Windows team are not the subject of this post, but it is fair to say that the Windows team did not make the decision lightly. When we evaluated the features of Windows Server Backup, it was clear that the backup and restore experience on Windows 2008 would not be the experience that existing Exchange customers have been used to for so long. Because we had feedback from several customers who told us they would rather get a more full-featured backup solution for their Exchange servers, a decision was made not to provide an Exchange-aware backup solution for Windows 2008 in Exchange 2007 Service Pack 1. Exchange 2007 Service Pack 1 Ships... Right after we shipped Service Pack 1, we started hearing from customers who were upset with the fact that they cannot take Exchange-aware online backups with Windows Server Backup. These customers had enjoyed the integration of Exchange and Windows Backup (NTBackup) for many years, and for many versions of Exchange and Windows. We also saw quite a but of discussion activity on this issue in various Exchange communities (this blog, internal discussion groups, MVP and MCT communities, etc.). We then published a blog post on this issue, which prompted more comments from customers who told us that they were unhappy about this and why. Now - the next question you have must be: What are we doing about this? Although we can't share all of the details now, we thought that this issue was important enough to announce a decision we recently made. We have decided to develop and release a VSS-based plug-in for Windows Server Backup that will enable you to properly backup and restore Exchange 2007 with a built-in Windows 2008 backup application. While you will be able to backup and restore Exchange 2007 on Windows 2008, you should not expect feature parity with the Windows 2003 NTBackup experience. There will not be the same level granularity and control that NTBackup provides and backups will be limited to the local server only. However, you will be able to perform a VSS backup of Exchange to a separate disc or a network share. If the backup completes successfully, it will (depending on options chosen) truncate Exchange transaction log files, and you'll be able to restore Exchange data when needed. We will cover all of the details in updated documentation when the time comes. We realize that this may not be an ideal solution for all organizations, but we are quite confident that this is a good solution for many, especially our smaller customer segment. When can you expect this? We do not have a release date to announce yet. Our Customer Experience team is working out the details, and because we are still relatively early in this process, we cannot commit to a specific date yet. Rest assured - we'll announce it when it becomes available! Finally, I think it is in order to thank all of you for all the feedback that you have provided us. As we mentioned before, we want your feedback. We are lucky to have people passionate enough to let us know and explain why what we did was not ideal. - Nino Bilic
Blog Post
Exchange Team Blog
3 MIN READ
To Backup or Not to Backup? Yes! To backup!!
The_Exchange_Team
Jun 18, 2008Platinum Contributor
32 Comments
Sort By
- AnonymousNTBackup still works when loaded in Windows Server 2008, and backing up Exchange 2008 SP1. I've tested backups and restores of the storage groups. Here's how I did it:
Copy ntbackup.exe, ntmsapi.dll, and vssapi.dll from Windows 2003
into a folder on your Windows 2008 server. Make sure to match x32 or x64 binaries! Once these 3 files are in the same folder, ntbackup.exe will
run just fine on Windows 2008, and even allow the Exchange services to be backed up. Life goes on for Windows admins.
Of course, this is NOT a supported configuration by Microsoft. - AnonymousThanks for listening to your customers.
I had to resort to an alternate solution for doing my exchange
backups. There are a number of VSS aware solutions on the market
but not all of them are exchange aware in that the log files get
trunct after a good backup.
I think having this Plugin for the windows server 2008 backup will
be a god send to alot of people deploying exchange on windows server 2008.
Thanks. - AnonymousThank god you do listen.
Today a company directory Moved (instead of copying)3 public folders in his contacts, because he was travelling and wanted a copy.
They do not have a 3rd party backup solution...this type of stuff up is common. Microsoft must product sensible backup solutions to Exchange and especially SharePoint...and all it's configurations.
Otherwise we will be exmerg and exporting to more solutions.
SBS 2008 and EBS will need all the backup options they can get.
- AnonymousI think the Exchange teams and Windows teams need to get together to put the functionallity back into the NTBackup solution that was there before. Selling new product to management with less features is less than an easy job. If they were able to do an Exchange backup in the last three versions of Windows why can't they do it now!
- AnonymousJust today I ran into a situation that is exactly the reason we need a native backup of Exchange.
For a still unknown reason my third-party Exchange 2003 backup application wasn't running properly. The logs weren't being cleared and the log drive filled up. I don't have to tell you what happened next. Rather than spend the time diagnosing the actual problem, I was able to run an NT backup, clear the logs and get everyone working again.
If I was running Exchange 2007, this would have been a much more serious problem that would have resulted in much more downtime. - AnonymousThis is really a great achievement (no doubt) in compare with the traditional API based backup when you consider quick restore. However, there are some real time scenario with the examples start to finish would help a lot for the customer who would like to proceed now with the technology.
- AnonymousEven if it's more then a day late and a dollar short still better to be late then never.
- AnonymousGreat work guys!! I have a lot of SMB customers that use NTBackup exclusively for backing up Exchange 2003. It's always hard to explain to a customer why their "upgrade" has less features that they consider essential.
I added some more thoughts here: http://www.networkworld.com/community/node/29130 - AnonymousHi folks. Great news on a plugin. Will the plugin allow us to schedule backups to save to remote network locations or will we still be bound to only being able to schedule backups to local storage? Thank you.
- AnonymousI found this Guide to online backup on Wikipedia! I thought it was extremely helpful so I put it here to share! (http://memopal.clickmeter.com/891931.html)! I just discovered online backup and I think it’s a good way to protect data! Can anyone confirm this???