As organizations drive toward getting every bit of performance out of Exchange and Notes, there are more questions and concerns than ever before about email management.
In my recent presentation at Commvault GO, Commvault’s inaugural customer conference, I opened the session on a bit of a soap-box discussing the differences between availability and recovery. The lines between availability and recovery have been blurred for some, and I worked to sharpen them by pointing out where replication and availability fall short. For example, things like ransomware attacks, accidental or intentional deletion and misconfiguration, or moving to someone else’s server (cloud), all highlight scenarios where only a robust data protection and recovery solution could provide recourse.
We discussed IntelliSnap technology as still the fastest possible way to create RPOs and meet demanding RTO as well as the flexibility it provides for on-demand data access from snapshots. Commvault’s replication support for HDS and EMC storage allows administrators to configure storage array native replication with Commvault awareness for snapshot management. Also new in V11 is multi-streaming, block level and application aware backup techniques for Exchange. All of these dramatically improve performance, access and simplicity for database level protection with granular recovery. The block level technologies are bringing the snapshot feature set down to a streaming backup approach with mount directly from Commvault’s open storage platform as if it were a proprietary hardware array.
On the virtualization front, I presented four ways to protect your virtualized Exchange server. Why four? Why not one? In the industry, we are seeing virtualization-focused competitors forcing their virtualization-focused backup approach where it doesn’t necessarily belong. Understandably so. If you are a hammer, everything starts to look like a nail. I get it. But this is somewhere that Commvault really shines: Flexibility and completeness of vision.
We’re not a hammer; we are a tool box containing the right tool for any job. One point I tried to drive home is that while there is a solution for every design, there is no one solution for every design. The bottom line here is the best way to protect Exchange will flesh out based on server and storage design and the desired outcomes.
On the archiving front, I presented Commvault’s new SMTP daemon. While I don’t think I can get marketing to agree to that as a product name, ContentStore Mailbox, as it’s currently known, it is certainly worth mentioning. By implementing the ContentStore Mailbox feature and a single Exchange journal policy, your journal email is now sent directly to a Commvault system either on-premises or in the cloud where it is instantly archived, protected, copied and indexed.
Additionally, this isn’t just for administrators and compliance officers for search and eDiscovery. End users can also access their data securely and easily in Commvault for viewing, download, even forward and reply. So it’s not just an awesome e-Discovery solution; it’s a data continuity solution for your users should their production email services ever become unavailable or if they are just looking for something that is no longer in their mailbox.
Other cool topics we discussed were around email portability between Notes, Exchange and Gmail to help customers with migration.
In summary, we left the audience with a message to use the right tools for the right job and to mitigate risk in computing environments, both on-premises and in the cloud. Until the machines become self-aware, humans will be in charge, and as long as humans are running the show there will be risk to your data. Grant yourself control over eDiscovery scale and performance. Ensure you can access data during and after application migration, and retirement, without having to maintain legacy systems. Take control and have confidence in this rapidly changing world of compute and storage.