DPM 2006 was the first version of DPM. It focused specifically on the protection of file servers and servers running file-based applications and wasn’t intended to protect Exchange workloads. DPM 2007 was with a high degree of awareness for specific Microsoft applications, such as Exchange Server, SQL Server, and Microsoft Office SharePoint Server read, write and store data on volumes. Hence, DPM 2007 provides tailored, protection and recovery for these key workloads. DPM 2010 provides even more and flexibility in Microsoft application protection and recovery, as well as new capabilities in protecting virtualization platforms and the ability to protect Windows client data.. These features allow systems administrators and IT generalists to develop their own recovery infrastructure, perform their own Exchange Server backups, and perform mailbox database and mailbox recovery operations without relying on backup or storage specialists. Microsoft and Windows-Specific Design As one of the largest IT companies in the world, Microsoft has significant internal data protection requirements. Given that the company uses its own products for its IT infrastructure, it also has one of the biggest deployments of Microsoft products in the world. Several years ago, Microsoft performed an internal investigation to analyze how the third-party data protection tools met the organization’s backup and recovery needs. The investigation found that there were gaps between the protection that Microsoft needed and the protection those products could provide. In parallel with that, Microsoft customers and partners provided feedback on what they needed in data protection and recovery, but weren’t getting in their legacy solutions. The needs across organizations were the same, showing not only the capabilities that were missing but also the requirement that the solution fit equally well for not only large enterprise but all midsized organziations. With this disparity in mind, Microsoft began development of System Center Data Protection Manager.
DPM 2006 was the first version of DPM. It focused specifically on the protection of file servers and servers running file-based applications and wasn’t intended to protect Exchange workloads. DPM 2007 was with a high degree of awareness for specific Microsoft applications, such as Exchange Server, SQL Server, and Microsoft Office SharePoint Server read, write and store data on volumes. Hence, DPM 2007 provides tailored, protection and recovery for these key workloads. DPM 2010 provides even more and flexibility in Microsoft application protection and recovery, as well as new capabilities in protecting virtualization platforms and the ability to protect Windows client data.. These features allow systems administrators and IT generalists to develop their own recovery infrastructure, perform their own Exchange Server backups, and perform mailbox database and mailbox recovery operations without relying on backup or storage specialists. Microsoft and Windows-Specific Design As one of the largest IT companies in the world, Microsoft has significant internal data protection requirements. Given that the company uses its own products for its IT infrastructure, it also has one of the biggest deployments of Microsoft products in the world. Several years ago, Microsoft performed an internal investigation to analyze how the third-party data protection tools met the organization’s backup and recovery needs. The investigation found that there were gaps between the protection that Microsoft needed and the protection those products could provide. In parallel with that, Microsoft customers and partners provided feedback on what they needed in data protection and recovery, but weren’t getting in their legacy solutions. The needs across organizations were the same, showing not only the capabilities that were missing but also the requirement that the solution fit equally well for not only large enterprise but all midsized organziations. With this disparity in mind, Microsoft began development of System Center Data Protection Manager.
DPM2010_Whitepaper_How_to_protect_Exchange.docx