Posts about:
Exchange database internals might seem to be a complicated topic, but we’re going to briefly discuss database internals from a very practical perspective.
Despite the recent surge in popularity of the cloud, moving to Office 365 isn't a viable option for every modern-day business. For this reason, enterprise-based Exchange will continue to be a mission-critical platform for many companies, and Microsoft has shown no sign of abandoning the platform anytime soon.
Microsoft recently announced a new DAG copy activation feature that will be available in Exchange 2016 CU2, but before we talk about that, I’d like to do a quick refresher on how database copy activation works currently and will continue to work for Exchange 2013 and 2010.
Spoofing has long been one of the biggest issues with email, and with the move to cloud services in the last few years it has become an ever hotter topic. Although a number of features designed to combat spoofing exist, many of which have been discussed on the blog, no perfect solution is available.
Preservation policies were introduced almost a year ago as part of the Compliance Center in Office 365 (which you might also know as the Protection center, or as Security & Compliance Center after the latest rebranding). In a nutshell, they allow you to preserve content across (almost) all Office 365 workloads. They also provide support for true immutability of the data, such that even the company administrators cannot override.
With the release of Exchange Server 2016 it’s time for on-premises customers to consider their upgrade options. Which means that it’s also a good time to review their Exchange storage strategy.
The best way to learn about Exchange Server is to get hands-on with the product. And the best way to get hands-on without risking a production environment is to build your own test lab.
The following blog post is a trimmed-down excerpt from the eBook "Exchange Server Troubleshooting Companion":
One of the primary talking points of my Storage Configuration Options for Exchange session at IT Dev Connections was around JBOD with Exchange, and what that definition means to various people.
A career-defining moment for many IT professionals is the day that their customer requests some data to be restored from backup, and the backup is found to be not working. Or even worse, the backup doesn’t even exist.
It’s not a situation you ever want to find yourself in, and to help you to avoid it I’m going to tell you about the common (but easily remedied) mistakes that can lead to such an unfortunate position.
The following blog post is a trimmed-down excerpt from the eBook "Exchange Server Troubleshooting Companion":
Mailbox corruption is not a new problem for Exchange Administrators, Support Engineers, and Consultants. Causes of corruption can vary and include: