We have already
dedicated couple of articles related to Nakivo Backup and Replication
v6.1 wherein we have seen the architectural components and
also talked about new features available in Nakivo
Backup and Replication v6.1 here is a link for your quick
reference Demystifying Nakivo Backup and Replication v6.1
We also discussed about Backup/Recovery of Active Directory Objects with Nakivo Backup and Replication v6.1 in case you missed it here is the link for your quick reference Backup/Recover Active Directory Objects with Nakivo
Apart from testing the backup and recovery related functionalities using Nakivo Backup and Replication v6.1 we also had a detailed discussion on Replicating Virtual Machines here is the link for your reference Replicate VM's with Nakivo Backup & Replication
We also talked
about working with Nakivo Backup and replication
appliance and what's new withNakivo Backup and replication 6.2 which
was announced by NAKIVO on october 13th
2016 which help us by providing backup, replication,
and recovery of paid EC2 instances sold
through AWS Marketplace we also discussed about What's New - Nakivo Backup and Replication v7 Part 1 wherein
we have seen some highlights about Hyper-v support which has been added for
Hyper-v 2016 and 2012 with Nakivo v7.
In Our last
articles related to Nakivo Backup and Replication series we
discussed about
What’s New- Nakivo Backup and Replication v7 Part2 and
we have seen some of features released with Nakivo Backup and Replication v7 also
talked about Active Directory Integration - Nakivo Backup and
Replication v7 and discussed about
Dedicated this article to talk about another feature available with Nakivo Backup and Replication Appliance which help us to protect our backup by creating a backup copy.
When looking this feature from an enterprise perspective the feature is quite important to consider as your backups can lost because of accidental backup deletion, backup file corruption or any other unwanted reason, Therefore creating more than one copy of your business-critical
backups is vital which ensure that your data can be recovered in case of a
disaster.
Another reason to think about the backup copy if we have primary backups which are store in the same location as your production machines and any issues in the production machine can also affect the backups which clearly is a single point of failure.
When working with Nakivo Backup and Replication we can create an additional layer protection by enabling the backup copy feature let's have a look how this feature works behind the covers.
First thing First create a Backup Copy Job and select the backup for which we are creating an additional copy and specify the destination repository details which would be running in a different site as the intention is to avoid any single point of failures and configure the schedule for the Backup Copy Job (Daily, Weekly).
First thing First create a Backup Copy Job and select the backup for which we are creating an additional copy and specify the destination repository details which would be running in a different site as the intention is to avoid any single point of failures and configure the schedule for the Backup Copy Job (Daily, Weekly).
Next task on the list to configure retention which gives us couple of flexible options to configure starting with default option wherein we can maintain the exact copy of the source backup and the recovery point retention of the source backups would be applied,or we can choose the recovery point retention (Week,Day, Month and Year).
Next option in the list is Encryption which can be selected when transferring data over WAN without making use of VPN, and the last option is Screenshot Verification which perform screenshot verification for all backups after the jobs has been executed and requires VMware tools to be running inside the Virtual Machine.
Before we finish and run this job it's time we specify the name of this Job and couple of other options including Network Acceleration (Can be enabled when both the source and destination site should have at least one transporter for transferring data over slow WAN,)
No comments:
Post a Comment