Protecting Your Backups with Backup Copy
Brandon Lee, posted on May 3, 2017
In thinking about making an enterprise environment resilient against a disaster whether natural, malware, or self-imposed, we need to think very carefully about our backups. It is extremely important to not only make sure we have good onsite backups but also copies of those backups elsewhere. Malware and other ransomware infections these days are making organizations scrutinize where backup data may live and how many copies of that backup data we might need to have. In today’s age of always available business services, organizations have to make sure copies of data are sent offsite to provide an alternative option to restore data in case backed up data onsite is damaged by any number of causes including the aforementioned ransomware infection. Having a backup copy process can provide means to copy backed up data offsite to another DR/alternative location physically separated from the primary location.
Backup Copy – Necessary to Ensure Successful DR Strategy and Business Continuity
Why is having a backup copy essential? It keeps an additional copy of your backup files at another location which can be located either on or off site. This creates an additional layer of securing your backups. If we think about a disaster scenario that involves either a ransomware infection or possibly a natural disaster that affects your primary location that also houses all the backups for your production environment – what happens if our backups at that location are destroyed? This would be disastrous and possibly in a worst-case scenario, may even mean the end of your business.
However, if we have an additional copy of our backup data taken from production to another offsite or DR location, we have a way to recover from the disaster scenario mentioned above. In the case of NAKIVO Backup & Replication, we can utilize the backup copy job to save a copy offsite as well as in the cloud.
Let’s take a look at how the Backup Copy functionality in NAKIVO Backup & Replication v7 can be set up to maintain a backup copy of your VM backups. The process is extremely easy to set up and creates the additional layer of data protection that ultimately can save a business from the perfect storm disaster – losing production data AND backup data!
In our test setup, we have (2) NAKIVO appliances. We will use one as the primary backup appliance and the other as the target for our backup copy job which we will schedule to run after a successful backup job completes.
To set up the Backup Copy job, we simply navigate to the Create job action in the Web interface.
In the New Backup Copy Job Wizard we select the backups for which we would like to create a backup copy job.
Next, we want to select the Destination for the backup copy job. Here is where we want to design out our implementation of our backup copy job. We can think about how and where we want data to be copied. Ideally, you may want to have a copy job that copies data to a secondary repository and then another backup copy job that copies the data offsite for the best resiliency.
In the Schedule configuration, we can set up our backup copy job to Run after another job. Having it set this way ensures that immediately after we have a good primary backup job run, we will kick off our backup copy job. This ensures we have the most up to date production backup in our DR repository.
In our retention settings, we can leave the default Maintain exact copy of the source backup or we can select different options depending on how many recovery points we want to have available in the copy repository.
In our Backup Copy Job Wizard, “options” configuration, we name the job, setup other job options such as network acceleration, encryption, and also screenshot verification for extra checks on the validity of the copied backup of the VM. Also, we can set up any “pre” and “post” actions to run as well.
As we see now, our backup data has been successfully copied to our backup copy repository that is offsite. In this case, we are protected in the situation where our primary backups are corrupted or destroyed by some means. We can still use the backups that are stored in our offsite location.
In today’s world, a copy of our backup data is no longer a “nice to have” but is becoming essential. Most enterprise environments live and die by their ability to be resilient and “always on” due to a web-centric world that drives most businesses today. Utilizing a backup copy job, such as those found in NAKIVO Backup & Replication, allows a secondary copy of mission and business critical data to live offsite and most likely out of harm’s way when disaster strikes in a primary production location.