These are additional components, plug-ins and proxy options that are available to you in the Veeam Data Platform.
Additional Proxy Options
- VMware CDP proxy receives VM data, prepares data for short-term restore points, compresses and deduplicates data, encrypts and decrypts data, sends data to the storage in the disaster recovery site or another VMware CDP proxy. You can assign the role of a VMware CDP proxy to any Windows-based or Linux-based virtual or physical server added to your Veeam Backup & Replication infrastructure which operates as a data mover and transfers data between the source and target hosts.
In this video we will describe the progress of having a new VMware CDP Proxy server:
- Hyper-V Off Host: You can deploy an off-host backup proxy to remove unwanted overhead on the production Hyper-V host. In this case, the off-host backup proxy will retrieve VM data from the source datastore, process it and transfer it to the destination.
- General-purpose Backup Proxies (NAS, filers, file shares and off-host backups of physical servers.): you can specify proxies for other backup operations as well.
In this video we will describe the progress of having a new File Proxy server:
- Guest Interaction Proxy is a backup infrastructure component that sits between the backup server and processed VM. This component is needed if the backup or replication jobs perform the following processing of VMs: application-aware processing, guest file system indexing or transaction logs processing. To interact with the VM guest OS, Veeam Backup & Replication needs either to install non-persistent runtime components or use (if necessary, install) persistent agent components in each VM. The task of deploying these components in a VM is performed by the guest interaction proxy.
- Azure Restore Proxy Appliance (former Azure proxy): The Azure restore proxy appliance is a small auxiliary machine in Microsoft Azure over which Veeam Backup & Replication transports VM disk data to Blob storage. Veeam components installed on the Azure restore proxy appliance compress and deduplicate disk data, which helps reduce network traffic. Continue reading on Native Azure Backup and Recovery.
Additional Transport Concepts
- WAN Accelerators: WAN accelerators are responsible for global data caching and data deduplication. One WAN accelerator is deployed on the source site, closer to the source backup repository or source host. The other WAN accelerator is deployed on the target site, closer to the target backup repository or target host.
- Log Shipping Servers: Log shipping servers are dedicated components that Veeam Backup & Replication uses for backup of Microsoft SQL Server transaction logs and Oracle archive logs.
Veeam Backup & Replication prioritizes log shipping servers by how close the log shipping server is to the Microsoft SQL Server VM.
Additional Repositories
- REFS/XFS VS NTFS (BLOCK CLONE)
ReFS and XFS Block Cloning will create synthetic backups without moving the data blocks between files and instead references backup file blocks already present on the volume. This means all manipulations associated with synthetic full backups are limited to metadata updates and require no actual I/O operations on backed up data.
Watch this quick animation comparing ReFS to NTFS:
Suggested resources:
- Deduplication Appliances
When backing up to a deduplication storage appliance from Veeam Backup & Replication, performance or deduplication ratio is low without using best practice settings.
Watch this demo to learn more about deduplication, compression and encryption, as well as how these play into your disaster recovery plan.
An external repository is a read-only repository. You can use Veeam Backup & Replication to copy, import and/or restore backups created by Veeam native cloud appliances from external to on-premises repositories. This way, you can perform data migration between cloud, on-premises, and virtual infrastructures.
A repository housed in a cloud solution or an S3 compatible storage solution.
In the following demo we'll take a look at how you can set up an object storage repository, as well as how it can be used as part of the backup job.
Suggested resources:
Veeam Linux Hardened Repository
To protect your backup files from loss because of malware activity or unplanned actions, you can add a hardened repository based on a Linux server. The hardened repository supports immutability and single-use credentials.
Let's take a quick look on how to set up Veeam Hardened Repository:
Suggested resources:
- Linux Hardened Repository Overview
- Selecting Hardware and Setting Up Environment for Veeam Hardened Repository
- Securing Linux Hardened Repository
Scale-Out Backup Repository
A scale-out backup repository consists of one or more backup repositories or object storage repositories called performance tier, and can be expanded with object storage repositories for long-term and archive storage: capacity tier and archive tier.
Let's take a quick look at how to adjust Scale-Out Backup Repository:
Suggested resources:
Additional Transport Modes
- Direct NFS Access
The Direct NFS access is a recommended transport mode for VMs whose disks are located on NFS datastores.
In the Direct NFS access mode, Veeam Backup & Replication bypasses the ESXi host and reads/writes data directly from/to NFS datastores. To do this, Veeam Backup & Replication deploys its native NFS client on the VMware backup proxy and uses it for VM data transport. VM data still travels over LAN but there is no load on the ESXi host.
The Direct NFS access mode cannot be used for VMs that have at least one snapshot.
- Storage Integrations
You can back up VMware vSphere VMs by creating snapshots of storage volumes where the VMs reside and using the snapshots as data source for the backup.
Veeam Console Server
The main consideration for a separate Veeam Console server is for additional security, accessing the Veeam Backup & Replication console from a different machine. It is recommended to install the Veeam Console Server on a central managed server that is position in a DMZ and protected with 2-factor authentication.
Check out this short visual MFA setup in the User Guide
A machine on which you install the Veeam Backup & Replication console must meet the following requirements:
- The console is a portal into the Veeam Backup and replication server and provides additional security.
- The machine must meet the system requirements. For more information, see System Requirements.
- The remote console can be installed on a Microsoft Windows machine (physical or virtual).
- If you install the console remotely, you can deploy it behind NAT. However, the backup server must be outside NAT. The opposite type of deployment is not supported: if the backup server is deployed behind NAT and the remote console is deployed outside NAT, you will not be able to connect to the backup server.
The Veeam Backup & Replication console has the following limitations:
- You cannot perform restore from the configuration backup using the remote console.
- The machines on which the remote console is installed are not added to the list of managed servers automatically. For this reason, you cannot perform some operations, for example, import backup files that reside on the remote console machine or assign roles of backup infrastructure components to this machine. To perform these operations, you must add the remote console machine as a managed server to Veeam Backup & Replication. For more information, see Managing Servers.
If you need more help getting started, you can post your question in the comments section below or contact us at any time and someone from the Customer Success team will be there to assist you.