- Windows server with local or direct attached storage - local disk, USB drive, iSCSI/FC LUN
- Linux server with local, direct attached storage or mounted NFS - local disk, USB drive, iSCSI/FC LUN, NFS mounts
- CIFS (SMB) share
- deduplicating storage appliance - only the following three are supported EMC Data Domain, ExaGrid and HPE StoreOnce and there is also Enterprise license required.
For the current implementation, the chosen solution is implemented in a VMware environment across two vCenter Servers. VBR Server and main repository are located in the primary site. In the secondary site a backup repository has been installed on top of a Windows VM. Data mover service is installed in both sites.
Having a data mover service in secondary site also enables backups directly to secondary site. Now, let's see how to configure the offsite repository.
First we need to deploy the Windows VM. The process is "standard" procedure: reserve an IP address, deploy from template, select VM name, compute resource and storage, customize the guest OS (including joining to AD).
After the VM has been deployed, configure the VM hardware if necessary: repository space depending on the size of the backups and RAM (4GB for OS and up to 4GB for each concurrent backup job).
Once the Windows VM is up, go to VBR management console, backup infrastructure tab and start repository configuration wizard by right clicking on Backup Repository -> Add backup repository.
Add a name and a description for the new repository:
Select the type of repository (Windows, Linux, CIFS, Appliance):
On the repository server list page press "Add new"
This will open a new wizard that configures a new windows server repository. Add DNS name or IP address of the repository server (optionally a description):
Add the credentials to use for connecting to the VM. If you've saved them in the credential manager select them from the drop down list, otherwise click Add button and enter the username and password.
Review the components to be installed and press Apply. The wizard will install VBR components on the repository server and it displays the progress in the window:
A summary page is displayed with info about the target server:
Once server is configured the new backup repository is displayed in the list of servers. Press Populate button to retrieve all the available storage locations. Select the appropriate storage, press Next.
Configure the repository parameters: backup folder path, maximum number of concurrent tasks, read and write data rates (if necessary).
Advanced configuration features are realated mostly to storage appliances. Pressing Advanced button allows to select the following:
- Align backup file data blocks - useful for better deduplication ratios on storage appliances that use constant block size deduplication
- decompress backup data before storing - achieves better deduplication ratio on most storage appliances at the cost of performance
- this repository is backed by rotated hard drives - if hard drives are rotated and removed from the server
- user per-VM backup files - multiple I/O streams per VM will improve performance with storage appliances
Next, select the mount server and whether to enable vPower NFS or not. Default TCP ports for mount server and vPower NFS could be changed if necessary (press Ports button).
Review the configuration page of the server and press Apply.
The summary page will display the tasks, the progress and their status - creating repository folder, installing components (mount server, vPower NFS), configuring components.
The following services are installed on the repository server:
- Veeam Data Mover Service - sends and receives data
- Veeam Mount Server - mounts backups and replicas for file-level access
- Veeam Installer Service - installs, updates and configures VBR components
- Veeam vPower NFS Service - enables running VMs directly from backup files by "publishing" VM vdmk's from backup files to vPower NFS datastore. The datastore is then mounted on the ESXi host.
Once the process finishes, the new repository appears in the repository list of the VBR console and it is ready to use. Use it as a destination for a copy job or as an offsite backup job.