An introduction to serverless backups

Taking production servers out of the backup process can increase backup efficiency. This tip outlines how serverless backups are performed today.

Today, many data centers operate on a 24-hour schedule, and setting aside a designated backup window is simply no longer an option. As such, backups must be performed in a way that prevents them from becoming disruptive to the workloads that are running on the production servers. One way of accomplishing this is through a serverless backup.

A serverless backup is a general term for a backup in which a production server is not involved (or is minimally involved) in the backup process. To see why this is important, think about how a normal backup works. Typically, a backup agent is installed on the server that needs to be backed up. A centralized backup server communicates with the agent and orchestrates the entire backup process. When the server is backed up, the backup process consumes network bandwidth, disk I/O and CPU resources. These are resources that would normally be used by the production workloads. As such, the backup process robs system resources from the production servers.

The goal of a serverless backup is to remove the backup process from production servers, so that those servers are not impacted by the backup process. There are several different ways in which this can be accomplished. One of the most common methods involves the use of snapshots.

Although some vendors describe snapshots as a backup replacement technology, snapshots cannot replace backups by themselves because they are not an actual copy of data. However, snapshots can augment the backup process in a way that helps to minimize the impact on the production servers.

Creating a snapshot involves one of two processes. One of these processes is the creation of a differencing disk. When a differencing disk is created, all write operations are directed to the differencing disk so that the original disk remains unmodified. The other snapshot creation process involves using pointers to keep track of disk storage blocks.

Regardless of which snapshot creation method is used, the first step in performing a serverless backup is creating the snapshot. Once the snapshot has been created, the snapshot is used to assist in the backup process. The actual method that is used varies from one vendor to the next. One common technique involves creating a differencing disk snapshot so that the data that is being backed up remains in a pristine state. After doing so, the data is replicated across the SAN to a dedicated LUN. When the replication process completes, the LUN contains an exact replica of the production LUN as it existed at the time that the snapshot was created.

Although the data has been replicated, it still needs to be backed up. One option is to copy the contents of the replica LUN to tape. In the case of virtual data centers, however, it is common to replicate the volumes containing virtual machines and then mount the virtual machine replicas within an isolated environment. That way, server-level backups can be performed against replicas of production servers without impacting the production environment in the process. Figure A shows how this process works.

Some serverless backup solutions perform the backup process against replica VMs running on isolated host servers
Figure A: Some serverless backup solutions perform the backup process against replica VMs running on isolated host servers.

Another method that is sometimes used for performing serverless backups involves using a protocol called E-copy (or extended copy). The E-copy protocol is part of the SCSI command set and is used to facilitate device to device communications.

In the case of E-copy based backups, the backup server initiates and manages the backup process, but is not directly involved in the actual backup. In a normal backup, data from the protected resource passes through the backup server in route to the backup target (usually a tape drive or a disk based backup). When E-copy is used, the backup software simply tells the underlying storage to copy data from one device to another. The copy process occurs at the storage level without the data ever having to pass through the backup server.

Conclusion

As you can see, serverless backups offload the backup overhead from production servers while also helping to expedite the backup process. It is important to realize, however, that serverless backups are not unique to one specific backup technology. There are a number of different backup technologies that can produce serverless backups.

About the author: Brien M. Posey, MCSE, has received Microsoft’s MVP award for Exchange Server, Windows Server and Internet Information Server (IIS). Brien has served as CIO for a nationwide chain of hospitals and has been responsible for the Department of Information Management at Fort Knox. You can visit Brien's personal website at www.brienposey.com.

This was first published in June 2012

Dig deeper on Disk-based backup

Pro+

Features

Enjoy the benefits of Pro+ membership, learn more and join.

0 comments

Oldest 

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

-ADS BY GOOGLE

SearchSolidStateStorage

SearchVirtualStorage

SearchCloudStorage

SearchDisasterRecovery

SearchStorage

SearchITChannel

Close