This is a very interesting warning. I migrated many VBR servers, and it’s the first time I’ve encountered this warning.
The detailed warning message is below:
Warning Failed to connect to Red Hat Virtualization plug-in: Failed to login to platform service: The remote certificate is invalid according to the validation procedure.
Cary SunComments Off on How to use QNAP as Object Storage for Veeam Backup and Replication 12.1 with Immutability Backup
QNAP QuObjects application is free and certificated for objects with immutability, which means you can use it as object storage within Veeam for a backup repository that supports their immutability feature.
Cary SunComments Off on Fix Sending e-mail report issue after upgrade to Veeam Backup and Replication 12.1
The email notifications are not working after upgrading from v11 to v12 (v12.1), including sending the test email.
There are warnings on the backup jobs: ” Sending e-mail report Details: The remote certificate is invalid according to the validation procedure. “
Veeam Backup Enterprise Manager is a centralized management and reporting tool designed by Veeam Software for overseeing Veeam Backup & Replication deployments. It allows administrators to control and monitor their backup infrastructure through a web-based interface, making it easier to manage large-scale environments.
When you install Veeam Backup & Replication v12.1, the Veeam Backup & Replication console 12.1 is automatically installed on the backup server. If you want to remotely access Veeam Backup & Replication v12.1, install the Veeam Backup & Replication console 12.1 on a dedicated machine.
When you install Veeam Backup & Replication v12.1, the Veeam Backup & Replication console is automatically installed on the backup server. If you want to access Veeam Backup & Replication remotely, you can install the Veeam Backup & Replication console on a dedicated machine.
Today, I will show you how to install Hyper-V integration services in the Ubuntu Linux VM of Hyper-V. If the Hyper-V integration services are not installed, you cannot restore any data from Veeam Backup.
Veeam Backup for Microsoft 365 has an error in one of the mailboxes. The error message is “There is an error in XML document…The specified type was not recognized: name=’SharingMessage’.
Today, I noticed two fresh vulnerabilities on the VBR12.1 Manager and console servers. Certain .net core requirements are installed when the product is installed. Unfortunately, The .net isn’t patched automatically through Windows updates.
Veeam released version of Veeam Backup for Microsoft 7a on December 5, 2023. The Cumulative patches contain Veeam Backup and replication v12.1 compatibility and the ability to set email notifications with Google and M365 accounts in Veeam Explorers.
Veeam Backup & Replication 12.1 is the newer build of version 12, and the major new features and enhancements were added in Veeam Backup & Replication v12.1. e.g. Detect and identify cyber threats, Respond and recover faster from malware, Ensure security and compliance, Veeam App for ServiceNow, Backup of object storage, Veeam CDP enhancements, Veeam AI Assistant, etc.
You can restore VM files (XML, VMCX, VMRS, VMGS, VHD, VHDX) if they become corrupted. This option is an excellent alternative to restoring the entire VM. You can only restore a single VM file.
Existing jobs do not need to be updated that process the original/recovered VMs if you restore them to the same host and choose to preserve VM UUIDs. If you configure restore differently and want to process the recovered VMs, you must edit existing jobs or create new ones.
If the original VM fails, you can use Veeam Backup & Replication to restore an entire VM from a backup file to the most recent state or a previous point.
VBR v12 guest file restore—happen error message is as below:
Secondary GPT header LBA 209715199 exceeds the size of the disk (86401630720)
Agent failed to process method {Mount.GenericMount)
Because Veeam Backup & Replication only needs to transfer differences between the original/recovered VM and VM replica, the failback to the original virtual machine restored in a different location option helps reduce recovery time and network traffic.
Failback is returning operations to the primary site after a disaster recovery event. It reverses the failover process by replicating any changes made to the virtual machine during the Failover state back to the primary site and then redirecting users and applications back to the primary site.
Planned failover is the smooth manual switching from a primary VM to its replica with minor downtime. Planned failover is proper when you know primary VMs are planning to go offline, and you need to switch the workload from the original VMs to their replicas as soon as possible. For example, you can use planned failover to perform data center migration, maintenance, or software upgrades on primary VMs. You can also perform planned failover if you see signs of an impending disaster.