4 incredibly useful steps to better backups

Love backups? Didn't think so. To make the process less painful, consider the following steps when creating or changing backup environment

In all my years in IT, I can't think of an everyday task that is more universally loathed than maintaining good backups. Depending upon what size environment you're running, setting them up in the first place can be a massive investment in capital and manpower, but that's just the tip of the iceberg. Daily monitoring and troubleshooting often end up making the initial deployment look like a walk in the park.

But it doesn't need to be that way. Backups can be almost a set-it-and-forget-it affair, although reaching that utopia requires careful planning and a solid understanding of what you want to accomplish. Here are some design tips to help you avoid the most common backup pitfalls.

Step No. 1: Set expectations

As is often the case, the first step is the most important. Before you even begin to think about what kind of hardware and software you'll use to back up your environment, sit down with your business stakeholders and come to a consensus on what RTO (recovery time objective) and RPO (recovery point objective) you're trying to achieve. The RTO is the time it will take you to recover a given resource; the RPO is the maximum age of the data that you'll be able to recover at any given time.

In my experience, IT pros who take the time to have this discussion with management discover that what management finds important bears little resemblance to their pre-conceptions. Either management has nearly impossible RTO/RPO objectives or -- surprisingly enough -- cares far less than you might think about how quickly you can get certain services back in production.

To continue reading this article register now

How to choose a low-code development platform