3-2-1 backup strategy

3-2-1 backup rules

The 3-2-1 backup strategy is made up of three rules:

• Three data copies. Three copies of all critical data should be made on a regular basis -- daily or more frequently -- including the original data and at least two backups.
• Two types of storage. Two different storage types should be used to store the data. Both copies of the backed-up data should be kept on two separate storage types to minimize the chance of failure. Storage device types could include an internal hard drive, external hard drive, removable storage drive, a tape library, a secondary storage array or a cloud backup environment.
• One off-site location. One copy of the data should be shipped to an off-site storage facility. At least one data copy should be stored in an off-site or remote location to ensure that natural or geographical disasters cannot affect all data copies. This copy can be physically delivered to the off-site location, as with tape-based backups, or it can be replicated to the secondary site via telecommunications facilities.

Importance of the 3-2-1 rule

The 3-2-1 backup strategy is recognized as a best practice for information security and data protection professionals. Although the process doesn't guarantee that all data will never be compromised in some manner, the strategy eliminates some of the risks involved in backup procedures. The 3-2-1 methodology is important in ensuring that there is no single point of failure for data. Not only is an organization covered if one copy is corrupted or a technology fails, but also if a natural disaster or theft occurs that wipes out the physical storage types.

The data recovery process employing the 3-2-1 methodology would be as follows:

• Original (active) data is corrupted, damaged or lost. If the production copy of data is unavailable, the first alternative is to recover the necessary data from the backup copy stored in-house on another medium or secondary storage system.
• Second data copy is unavailable or unusable. If the system -- tape or drive -- used to store the second data copy is unavailable or the data copy is damaged, out-of-date or otherwise unusable, the off-site copy should be recovered back to the in-house servers.
• Restart the 3-2-1 process ASAP. Once a suitable data copy has been mounted and operations have been restored, the backup process should begin again as soon as possible to ensure that data continues to be adequately protected.

Variation on the 3-2-1 backup methodology

There are a number of ways to achieve a workable 3-2-1 backup system, and the variations on the basic theme will depend largely on the following:

• the amount of data to be protected;
• currently installed and available storage equipment; and
• the type of off-site repository resources that are available and easily accessed.

For example, the first step of making the three copies of the backup data can be accomplished in a variety of ways.

The simplest method would be for the backup software to create the primary backup copy and then the same backup software or a replication utility would be used to make the two additional copies, storing the two copies on different types of media. Note that if a storage vendor's replication or storage snapshot function is used, the target storage system might need to be identical -- or very similar -- to the originating system.

Alternatively, mirroring could be used to create the first two copies simultaneously with the third spun off from one of those copies. Since one copy has to reside on a different medium, the process of making that copy is often the final step in the process. This is because copying to a different media type is likely to occur at a different rate than that of making the first two disk or solid-state drive-based copies. Alternatively, a split mirror approach can be used to create two copies residing on the same media, followed by copying one of those copies to another medium.

For the second copy that is maintained in-house for quick or operational recoveries, companies should store that copy on another server or storage system separate from the originating equipment. Ideally, the secondary storage device should be located on a separate network -- or network segment -- to help ensure that both copies aren't likely to be contaminated in the event of a malicious attack. The target gear for the second copy should allow easy access to the backup data in case it's needed, such as if the original data is lost or damaged. Storing copy number two on equipment similar to the original system should facilitate recoveries.

However, the in-house copy doesn't necessarily have to be stored on the same or similar media. In some cases, an organization might make the primary copy and then copy that data to two tape drives, simultaneously or sequentially. One tape cartridge would be retained on site and the other would be sent to the off-site facility. The drawback to this approach is that recovering data from the on-site tape might take some time -- certainly longer than recovering from a hard disk or solid-state drive. This would also be true if other types of removable media were used, such as optical disks or removable drives, although recovery times will vary. Still, recovery from any form of removable media, including tape, is likely to be faster than recovering from a cloud storage service.

Some backup software applications will handle the multiple-copy aspect automatically, possibly even creating the second or third copy. Data duplication or replication applications can also handle this chore. In very small environments, the second and third copies can be triggered manually; this method is less reliable, as it depends on manual procedures and can quickly become untenable as data stores grow.

Getting the third copy off-site

In the traditional approach to 3-2-1 backup, satisfying the requirement that one copy of data must go off-site was typically accomplished by sending a tape to another location. Usually, a company would contract with a tape vaulting service, which would pick up and store the tape cartridge. Data copied to non-tape portable media, such as optical disks or removable drives, would similarly be handled by an off-site vaulting service.

Today, many companies still rely on tape and outside vaulting services, such as Iron Mountain. Some companies that have their own remote facilities -- such as satellite offices, secondary data centers or disaster recovery installations -- can use ordinary courier services to pick up and deliver their off-site copies. Depending on the nature and location of the remote storage facility, some environmental issues (e.g., HVAC) might need to be resolved to ensure that the tape media is stored safely.

Vaulting or other off-site scenarios come with their own caveats. Backup tapes can get lost between the loading dock, the delivery van or the off-site service. And natural elements -- heat, cold, rain or snow -- can wreak havoc with tape cartridges, causing data loss. For these reasons, off-site copies on any medium should be tested to ensure their integrity soon after they arrive at the remote facility.

Increasingly, however, companies avoid some of the pitfalls of manually handling copies of their data by transmitting their off-site copies electronically. So instead of physically shipping tapes, disks or drives, off-site copies can be sent over the internet or private communication lines to a cloud storage service. Often, the backup software or hardware will handle transmitting the off-site copy automatically, but compatibility between the backup system and cloud service can be an issue.

If the off-site copy also represents the second media type (the "2" of 3-2-1), sending it to a cloud service adds a wrinkle to the 3-2-1 backup method, as the service is likely to store the copy on the same type of media that is used in-house. Although this deserves some consideration, it might not be an issue: Cloud storage is often considered more of a storage medium than an alternative storage location.

Universality of the 3-2-1 backup rule

Data protection technologies and techniques have evolved considerably since the 3-2-1 backup methodology was first conceived, but it can still be applied to the various forms of modern data backup and recovery.

Snapshotting and replication are two widely used data protection technologies that help overcome some of the obstacles of adequately backing up very large data stores. Using snapshots plus replication fits nicely within the 3-2-1 model as the methods used to make the original copy of the data as well as the two duplicates. But it's important to understand the target system requirements of storage vendors' snapshot and replication applications; already installed storage systems might not be appropriate targets for some vendors' products.

Backup appliances are relatively new fixtures in some data centers that combine backup software with dedicated hardware. These devices simplify initial backups and can usually connect seamlessly with a cloud backup service to stash an off-site copy of the data. In most cases, these systems can be used to hold one of the on-site copies, making it easy to recover individual files or entire data sets.

Similarly, data protection processes such as continuous data protection (CDP) alter the 3-2-1 model a bit, but with proper management these newer approaches can support 3-2-1 effectively. True CDP copies new and modified data to a target system immediately -- or in frequent batches -- so it can be a good upgrade to a 3-2-1 system that needs to back up voluminous data. Because CDP backups are far more frequent than daily or weekly backups, the risk of losing data is considerably reduced.

New uses of backup data and the 3-2-1 rule

There are other developments in modern data protection that don't eliminate the possibility of using a 3-2-1 backup scheme, but they might make it a little more complicated to manage. The following are among the more impactful developments related to 3-2-1 backup processes:

• using backup data for other purposes, such as populating data warehouses and big data analyses;
• the evolving rules regarding personal information and data integrity; and
• operational resiliency.

Today, backups are not just insurance policies tucked away until something goes awry. Companies are extracting more value from their backup data stores by using that data for things like developing and testing new applications. Contemporary approaches to programming, such as DevOps, require easy access to data that is as close to live application data as possible to ensure that applications are developed properly in a real-world environment. Backup data fills that bill very nicely, as it's likely to be freshly generated on a regular and frequent basis.

Analytical applications might also need access to large amounts of current data. By using fresh backup data, the results of the analytic process are likely to be more reliable and accurate. Tighter controls and management of data companies are required to ensure that these applications get the best data possible while maintaining the primary concepts of 3-2-1 backup. Note that if one of the backup copies is used for application development or for analytics, it can be altered or unavailable, making one of the requisite three copies unusable if recovery is required.

Data integrity has always been a key concern of data protection activities. It is not enough to simply back up data and lock away the copies; it is imperative to ensure that backups are complete, uncorrupted and recoverable. Recovery testing helps in this regard, as well as employing some of the more advanced features that backup apps offer to detect ransomware and other threats. Again, these concerns don't necessarily derail a 3-2-1 backup approach, but they might add some steps to the process, such a regularly scheduled recovery testing.

The General Data Protection Regulation (GDPR) is another contemporary wrinkle that could affect data protection practices. The GDPR is European Union legislation that defines the steps organizations must take to protect the personal data of their users. For 3-2-1 backup practitioners, this means ensuring that wherever those three copies of data are stored, security measures -- both physical and digital -- are adequate to ensure against data theft or loss and to avoid potentially crippling EU fines as well as negative publicity.

Another directive of the GDPR says that a company's customers or users have the right to have their names and all data related to them expunged from the company's storage systems and media. In a 3-2-1 environment, this means that the information must be removed from all three copies of the data, so it's necessary to be able to search stored data on a granular level to discover the specific pieces of data that must be deleted.

Active archive is another contemporary application that could potentially use backup data. Data that is stored permanently and never accessed can be kept in cold storage, but active archive data is saved data that can be accessed even if its useful life appears to have expired. If one of the backup copies is also designated as an active archive resource, the data should reside on accessible storage and users will likely need search and retrieve tools to tap into the archive.

Shortcomings of 3-2-1 backup

As an effective data protection scheme, 3-2-1 backup has stood the test of time. But, in the context of contemporary storage systems and services, some of the steps and practices might need to be adjusted to meet data protection objectives.

Keeping track of 3-2-1 backup data copies can get complicated depending on the type of backup an organization is using in its 3-2-1 setup. For most companies, doing a full backup daily is not feasible, so other approaches are likely being used, such as incremental or differential backups -- or, as noted earlier, using CDP and eschewing batch backups entirely. Because those types of backups can require some interim actions to produce a full backup copy, the three data copies rule of 3-2-1 might require some added management to ensure that all available copies are up to date and easily accessible.

One such consideration might be how many modern organizations accelerate data backup: deduplicating the source data. With this, the data that has already been backed up and hasn't changed isn't backed up again. This process is typically very granular, operating at a sub-file level. That means when deduped data is recovered, it must be reconstituted by reassembling the portions of files that were copied over the span of several deduped backup operations. The reconstitution process takes time, so recoveries of deduped data will take longer than recovering a full backup.

If a cloud storage service is being used to store the off-site copy, the service provider should be asked to provide details related to its data protection processes. Also, many cloud storage providers will charge customers extra to recover any data that the customer might have accidentally deleted. To avoid additional charges and to add a level of data safety, it's a good idea to copy the cloud-based backup to another cloud storage service -- which effectively duplicates the "1" part of 3-2-1. Additional charges can also be incurred when recovering data from a cloud service, as some providers charge users a fee for retrieving data they have stored at the cloud service.

As noted earlier, using a cloud storage service or transmitting a backup copy to a remote facility requires telecommunications services with ample bandwidth to handle the volume of data that is being sent or retrieved. These costs can also escalate as the amount of data a company has grows. And even with speedy communication lines, it takes time to retrieve data, so that should be considered when developing recovery plans.

If tape or optical libraries are part of the 3-2-1 backup scenario, it is necessary to maintain that equipment to ensure that data can be recovered in a timely manner. Generally, that should not be an issue, but if a company uses tape or optical gear that is older or even has reached end-of-life, maintaining that equipment appropriately can be difficult or costly. Alternatively, the data stored on the obsolete hardware can be recovered and rewritten to up-to-date hardware and media, but that's an expensive and time-consuming process. And if tapes or other media are stored off site at a vaulting service or another remote site, the time it takes to transport them back to a company facility where they can be loaded into a tape library must be considered when determining how long the recovery process is likely to take.

Traditionally, the 3-2-1 has been used to protect data -- but in a disaster recovery situation, more than just data is needed to recover systems and resume operations. Companies should consider disaster recovery as a service (DRaaS) as an enhancement to their 3-2-1 procedures for storing a backup copy off site. DRaaS is enabled by server virtualization, which lets an organization back up its server OSes and environments and applications, along with the data that is typically protected during a backup. When an outage occurs, the virtual servers can be spun up, the applications restarted and the data accessed to allow business operations to resume.

3-2-1 backup management

There are some basic managerial fundamentals for a successful 3-2-1 backup implementation:

• All data copies are identical and up to date.
• The media storing the copies is readable media.
• All copies and equipment are tested and confirmed to be in working order.
• Remote copies are stored safely.
• Recovery of single/multiple files or a full backup is tested on a regular basis.
• Internal data copies are on different storage systems and networks and are not accessible from outside the company.

The backup software used in the 3-2-1 process can be very helpful as it can automatically direct the disposition of backup copies while cataloging all backup activities. Most backup apps have also added features to check for threats, such as malware, ransomware and viruses in backup copies.

If you're using your backup app to spin off the duplicate copies to a cloud backup or storage service, you should ensure that there aren't any compatibility issues with the backup application and the cloud service.

With large volumes of data to protect, new applications that use backup data and the legal implications of maintaining the integrity of stored information, it's no surprise that many backup applications have gone beyond just making copies of data. Today, most backup apps provide built-in or optional data management and security features, such as ransomware protection, data indexing and searching, and extraction, load and transform services so that data can be used in multiple applications.

If your backup application does not provide all the information you need to effectively manage your 3-2-1 backups, a backup reporting application such as Bocada or Veritas NetBackup IT Analytics can provide comprehensive backup management, including monitoring and managing cloud backup activities. These applications go well beyond just tracking backups and can be used for overall storage environment management, even with a mobile device such as an iOS or Android smartphone or tablet.