Ongoing Operations approaches disaster recovery in two main ways with regard to backup servers.
The traditional way (as we call it) would be through our Rep V3 product, which is an agent-based backup solution that goes on any type of server, whether physical or virtual. This product will backup the file system and the system state over a period of time, using roughly 15-30 minute snapshots. We can keep that data for as little as 2 weeks or as long as a year. With this method, if you need to backup a physical server or archive that data regardless of the server type, you can recall data from 6, 8, or 10 months ago.
The second method uses our Rep V4 product, which is more of a replication tool. It requires VMware, and it uses the VMware journals to report all the changes that are happening to that virtual machine in real time. The big advantages of this product are that the recovery time objective and recovery point objectives are much lower – usually it’s a matter of under a minute to recover the server and have very little data loss. Two of the disadvantages, though, is that it has to be a virtual machine (so physical servers are out of luck), and we keep a record of those changes for only 5 days. So this approach works well if a patch blows up, or a server goes down – we can bring it back up much more quickly than if we were to use Rep V3. But if you’re looking for a way to recall data from months ago, RepV4 isn’t the best solution.
A lot of our credit unions use a combination of V3 and V4 in order to fully protect their environment: one for archival and one for server protection. What’s the best answer for your credit union? It really depends on what your credit union’s needs are and how you want to approach DR.
Want to find out more? Please fill out the short form here and we will be in touch!