With NAKIVO Backup & Replication, you have several options to place a Backup Repository for storing backups or backup copies.
Backing Up to Local Hard Drive
Choose this location to create a Backup Repository locally on the machine where the assigned Transporter is installed.
A local SSD/HDD-based backup repository is often used for storing initial backups. An HDD-based backup repository might be the right option if you need a lot of local storage capacity (up to 15 TB), and you don’t require your computer to work fast. If you aren’t concerned about storage capacity but need faster performance, choose an SSD-based backup repository.
Backing Up to Shared Folder
Choose one of the options below to create a Backup Repository in a remote shared location:
It's recommended that you use the latest version of the network/file sharing protocol.
If a Backup Repository is located on a NAS CIFS share and mounted to a host under a previous Linux OS, make sure you upgrade the host to the latest Linux release. Also, deploy a NAKIVO Transporter on the NAS and use the Backup Repository as a local folder instead. This can eliminate the impact of network issues on the Backup Repository and improve its stability. To store backups on a specialized deduplication appliance, create an incremental-with-full-backups repository and select a corresponding CIFS shared folder or an NFS shared folder in case you use the product with EMC Data Domain Boost.
Backing Up to Cloud
If you want to back up machines to a cloud or keep backup copies there, you will need to create a Backup Repository within your Amazon Web Services or Microsoft Azure account and then add it to the NAKIVO Backup & Replication inventory. When creating a Backup Repository and connecting it with your Amazon EC2 instance, make sure you select the Amazon EBS backup repository type. If you are using Microsoft Azure, choose a remote CIFS share location for the backup repository. Also, keep in mind, that you will be charged for the space you will use for Backup Repository by a cloud service provider. For details, refer to AWS Pricing and Azure Pricing. To fulfill your disaster recovery requirements, utilize shared folders or clouds to create a Backup Repository for storing copies of your primary backups. You can also use a RAID array for placing a Backup Repository. This way you can increase data integrity and optimize server performance.