Key Tech Terms to Know: Archives, Backups, Disaster Recovery and “as-a-Service”

Backups: A snapshot, point-in-time copy of your current on-premises data that you use to restore original file-level data if it's ever damaged or lost. This refers to the practice of copying computer files to another storage device, with additional copies being added to an external storage location as those files change. Backup data can be located online in to-disk format or offline in to-tape format.

Backup-as-a-Service (BaaS): An approach where instead of performing backup on-premises, BaaS connects systems and data to a second datacenter, private, public or hybrid cloud managed by an outside provider. This outsourced method offloads the duties of managing tapes or hard disks and keeps data accessible or restorable from a remote location.

Some people also refer to this form of data protection as Backup Recovery-as-a-Service (BRaaS), which is meant to place more emphasis on its purpose: to be able to recover using these backups.

IT Disaster Recovery (DR): A type of data protection that is usually implemented with the goal of returning systems to normal. Depending on the approach, recovery could be within hours, but is typically much longer (days or weeks). It is typically accomplished using a combination of backups, SAN-to-SAN hardware-based replication, database replication or even software-based replication. With traditional IT-DR, the DR site requires the same amount of physical hardware and capacity as what is being used in the production or primary site, or this hardware must be procured before recovery can begin.

Disaster Recovery as a Service (DRaaS): Emphasizes fast recovery from a technology disruption, restoring applications and networking often within minutes-to-hours so users can return to work again quickly. It is like BaaS but instead of protecting individual files, it involves protecting the entire system or environment. On-premises datacenters or cloud-based datacenters are replicated to a second datacenter, private, public or hybrid cloud managed by an outside provider, removing the need for organizations to manage and maintain their own DR site. It also eliminates the need for capacity planning because the service allows for scaling of hardware resources when a declaration occurs, reducing costs.

Disaster Recovery on Infrastructure-as-a-Service (IaaS): References when an organization builds a recovery solution using replication or migration tools with an IaaS provider such as Azure, AWS or Google. In many cases this solution is set up with the intent of reducing overall costs for DR, but the firm's IT team is responsible for the implementation, management, testing and recovery of the applications. It's important to note that failover and failback capabilities should be tested on a small dataset if you are protecting workloads from outside of that same cloud family, because in some cases the failback doesn't exist or requires a large effort.

Putting It All Together

On a high level, the key difference between each of these terms comes down to their intended purpose. Oftentimes, a firm's budget has an impact on what solution is chosen, but knowing every solution option will aid in good decision-making, flexibility and transformation for the future. Selecting a BaaS provider, for example, that also offers DRaaS solutions, may mean an easier transition later on.

As a rule of thumb, small firms need to have archive and backups at a minimum. Mid-size and larger firms are likely expected by clients and partners to not only archive and backup their data, but also have the ability to recover from disruptions within a moment's notice.

In each of the “as-a-Service” offerings noted in this article, it's important to also understand that three different service models exist within them:

1. Managed – the provider is responsible for performing and managing the solution (backups, replication, storage, etc.). In scenarios when the client's IT team is unavailable, the provider can even execute the recovery process on their own.
2. Assisted – the provider gives the client expert advice on building a robust recovery strategy and setup, while also helping during a recovery event when needed.
3. Self-Service – the client receives the necessary tools for the solution, but is on their own for everything else.

Anytime you are using the cloud, there are shared responsibilities. For this reason, know how much responsibility you want to take on. Firms should consider each of these “as-a-Service” service models and their associated responsibilities to ensure proper alignment with their needs.

*****

Jeff Ton is executive vice president of product and service development for Bluelock where he is responsible for driving the company's product strategy and service vision and strategy. Ton has over 30 years of experience in business and information technology and previously served as CIO for Goodwill Industries of Central Indiana and Lauth Property Group. To learn more about DRaaS specifically, read Bluelock's free & ungated beginner's resource, “The Practical Guide to Disaster Recovery-as-a-Service.”