Veeam Backup And Replication Tutorial

[Emmaline]

VeeamBackup & Replication is a software solution that protects your data by performing backup, replication, and recovery operations. With this product, you can recover your data fast from all types of infrastructure: virtual, physical, and cloud.

Note: Make sure to run the installation by mounting the image or running the Setup.exe file to avoid missing crucial components. Do not run the installation using the executables from other folders.

The Ready to Install step shows the default installation configuration. To start the installation without custom settings, select Install and wait for the process to complete. The wizard goes through eight steps. Once done, click Finish to exit the wizard.

The Data Locations step appears in the manual configuration mode and if you selected to install a new instance of the database server. This screen lets you specify the installation folder and the write cache and the indexing data storage location.

This guide guided you through the installation steps for Veeam Backup & Replication version 12. You should now be able to successfully connect to your backup servers and perform any necessary operations necessary to implement your data backup strategy.

Currently the Veeam Backup & Replication instance is running in Production Site and all the VMs are replicated over to DR site. We have Re-IP features in DR plan, so when failover happens the VMs get IPs for DR site subnet.

Side Track - The backup repository for replication, can it be on local drive of Veeam instance? I understand the backup repository in case of replication only holds the meta data of replication, so should this also be protected? Or if I have High/Available instance of Veeam Backup & Replication in DR site, will this also be addressed?

First I have to state that the migration of VBR server on the DR site is not an option, as the DR site could be shutdown / unrechable for administrative reasons: during those periods the replication/bckcopy jobs would be interrupted, but backup/bckcopy jobs on HQ do have to continue: if the VBR server would be moved to DR site, no Backup jobs would be possible at HQ during DR un-reachability.

Having two VBRsrv (one at DR for replication, one at HQ for BCK/BCKCPY) yes would be a fine option, but it would require to have VEEAM Enterprise Manager in order to distribute the license, unless we want to duplicate the licensing cost.

-vsphere-f24/managing-licenses-with-two-veeam-server-t76265.html

Either way, server at each site, control replication from DR so if main site goes down, you can flip the switch at that side and bring things up. Keep Storage/ proxy / Veeam server for backups at main site.

The EM server will track workloads between both VBR server and recognize that the same vm was processed by replica and backup jobs. So only 1x instance will be used even if two backup servers are doing the jobs.

The offsite server is a Physical 2008 R2 Standard (64-Bit) Dual Xeon box with 4GB RAM , 2x 500GB RAID 1 for OS and 2x 2TB RAID 1 for the Backup Repository. (This is an old system) . Will I be able to run Veeam on this box using the local drives for the repository along with it being the AD?

im not really sure you need a dc though. if you are just trying to store the backups offsite i dont think that is necessary and its over complicating it. if you need the ability to run the vms at the remote site it might be necessary.

Edit the settings of the original copy job you used to seed the backup. In the target drop down, pick the repository you just created. Then click the map backup link. Once that is all done, run a sync. It will then sync all the changes that have taken place since the original seed.

That was what I was looking at setting up until the last video I watched. In that video they started talking about the RTPO and mentioned that having an AD server off site would be better to be able to recover faster. But I guess there are different levels, they were talking about a DR site and failing over where right now I just need to be able to get the backups off site, which your solution provides.

What you are doing here is simply creating a second copy of your current backup. This way if there is a fire or worse, and you can not, or do not want to run out of the building cradling your SAN, you can recover from the off site backup copy.

As to Veeam implementation, it might be worth deploying either primary or additional backup server at DR location and letting it manage replication jobs. Should something happen with production site, all required procedures, like Failover, Failback can be executed smoothly via DR backup server.

Do I establish a VPN connection from the office to the house or vice versa? Ryan mentioned it would be a different subnet, but I thought if I was connecting from the house to the office,then the server would be on the same subnet as the office.

I was thinking about a site to site vpn, but i guess a client vpn connection would work and would put you on the same subnet and to be on the same subnet you would connect to a vpn at the office from a client at the remote site.

Third-party backup solutions are also available for QNAP ES NAS (including Symantec BE, Veeam, and NAKIVO). Veeam Backup & Replication provides backup, restore and replication functionality for virtual machines that use VMware vSphere and Microsoft Hyper-V hypervisors.

Veeam Backup & Replication is positioned as a part of the Veeam Availability Suite bundle (which includes Veeam ONE for monitoring, reporting and capacity planning), but can also be installed as a standalone product. It is available in three editions based on the level of provided functionality. The product is licensed by the number of CPU sockets purchased.

You need a client PC to install Veeam BR (Veeam BR Server). We created a virtual machine based on VMware vSphere ESXi (the configuration of the Veeam BR server is in the below table). The BR services on the Windows server must run with the same domain user account used for the shared folder on the NAS, with administrative privileges on that server.

You can add VMware vCenter Servers and ESX(i) hosts. If an ESX(i) host is managed by a VMware vCenter Server, it is recommended that you add the VMware vCenter Server, not a standalone ESX(i) host. If you move VMs between ESX(i) hosts managed by the VMware vCenter Server, you will not have to re-configure jobs in Veeam Backup & Replication. Veeam Backup & Replication will automatically locate migrated VMs and continue processing them as usual.

Veeam BR can backup many types of server or computer (including Windows, Linux, macOS, and VMware server). Veeam BR can also back up virtual machines, disks, and files.

This section will assist you in backing up data to a QNAP ES NAS.

In 2021 began selling their latest release, Veeam Backup and Replication Version 11. This is a feature rich release with capabilities such as direct ONTAP API integrations for NAS backup with ThinkSystem DM Series to streamline, simplify and automate data protection.

Lenovo has proven experience in developing and delivering Veeam-based solutions that help customers modernize and simplify their IT infrastructure to dramatically improve backup and recovery for physical and virtual workloads both on-prem and cloud based.

The Veeam Data Platform combined with best-in-class data center infrastructure and software-defined solutions from Lenovo, enables businesses of all sizes to accelerate digital transformation, simplify IT, reduce risk, lower costs and enhance business agility.

Lenovo offers various types and forms of Veeam products including perpetual licenses and annual subscriptions so organizations and partners can leverage best in class Lenovo servers to build agile IT infrastructure that is reliable, secure, and high performing with payment flexibility. Choosing a Veeam OEM subscription from Lenovo for most customers is the simplest and most cost-effective approach.

Align with V12 release, Veeam rebranded portfolio comes with enhanced features and flexible options. Veeam Universal License (VUL) is a portable license that allows the customer the flexibility to protect cloud, virtual and physical workloads interchangeably whether it be on-premises or in hybrid- or multi-cloud deployments, including full-feature capabilities for all workload types. (Including VMware, AWS, Azure, Google Cloud, Windows between others).

VUL is required for many features, so Veeam strongly recommend to migrate current licenses to VUL for full capability. A VUL is always required for NAS, all physical agents, Nutanix AHV virtual machines (VMs), cloud-native workloads and more.

Customers can quote Veeam subscriptions or licenses from Lenovo through the Data Center Solution Configurator (DCSC) using either guided configurations (CTO) or by selecting standalone part numbers (BTO).

This section provides information on Veeam licenses and subscriptions for management tools such as Veeam ONE and the Veeam Disaster Recovery Orchestrator (DRO), formerly known as Veeam Availability Orchestrator.

Lenovo and Veeam have partnered to integrate support for Lenovo storage snapshot technology into the Veeam Availability Suite. This integration provides customers with a deeper level of protection and availability across Lenovo ThinkSystem DM Series, and Lenovo ThinkSystem DE Series storage platforms. Integration of Veeam Backup & Recovery with Lenovo storage snapshot technology allows you to achieve:

Lenovo DE-Series storage provides simple and reliable SAN storage that integrates seamlessly with most application environments. Its modular design helps decrease operating expenses while offering many options for connectivity, capacity, and performance that easily scale to meet the demands of a growing backup environment.

3a8082e126