August 2, 2017
When you invest in a great new BDR solution, you can get a lot of guidance from the vendor’s onboarding and support team. At Quorum, we work with new customers every step of the way to ensure their every question is answered and their every move is confident. But there are some questions we (or any vendor) can’t answer – because they’re too dependent on the nuances of your infrastructure.
One of those questions: deciding on the frequency of your snapshots. Functioning as an image of your system at a particular point in time, snapshots can help you improve your Recovery Point Objective (RPO) and accelerate recovery. Teams often wonder which assets deserve which frequency and how to stagger snapshots in a way that ensures data stays protected without wasting resources.
There are no hard and fast rules. Only you know your own data recovery needs. But here are a few things to consider.
Quorum uses onQ for backup and recovery: How We Do It
To explain how this plays out for us, at Quorum we have a 12-hour window of exposure for our Exchange server. In other words, we’re comfortable losing 12 hours of email. And because backing up can slow down systems, we also have our snapshots scheduled for 6 p.m. and 6 a.m. so they don’t have a significant impact on productivity.
You might be wondering - why don’t we make it 4 hours? Well, that would require more storage and resources, and would have a stronger impact on our daily schedule. We decided it’s not worth it. This is the ultimate question your team will need to grapple with: how much you want to invest to protect each resource – and what level of exposure your leadership is comfortable with. Timing the frequency of your snapshots is essentially a balancing act. Weigh your need to protect your data against your need for resources, and you’ll eventually arrive at the right schedule for your needs.