Veeam released the Backup & Replication V10 on July 23, Veeam Backup & Replication 10a is the newer build of version 10 that addresses issues reported by customers on the original build and adds the following new features and enhancements. e.g. Fully integrated AWS-native backup, Microsoft Windows 10 version 2004 and Microsoft Windows Server SAC version 2004, Linux Kernel version 5.7 support for guest VMs, RHEL 8.2, CentOS 8.2, Oracle Linux 8.2 (RHCK) and VMware Photon OS, Ubuntu 20.04, Debian 10.4, openSUSE Leap 15.2, Oracle Linux 8 (up to UEK R6) and Fedora 32 (up to kernel 5.7.7), VMware vCloud Director 10.1, Recent Azure Stack versions, Azure File Sync support. In addition, version 10a introduces over 1200 minor enhancements and fixes based on v10, the details as link https://www.veeam.com/kb3228.
Veeam released the Backup & Replication v10 on February, and with it comes over 150+ anticipated new features and enhancements. Veeam now also have support for the option “Copy backups to object storage as soon as they are created” at SOBR Repositories settings, it will create additional copy of your backups for added redundancy by having all backups copied to the capacity tier as soon as they are created on the performance tier. Let’s follow steps to configure it.
Veeam released the Backup & Replication V10 on Feb 18, Veeam Backup & Replication V10 with more than 150 new features and enhancements – including modern NAS support, Multi-VM Instant Recovery and heightened ransomware protection – v10 includes data protection capabilities that increase availability, portability, and extensibility for Cloud Data Management.
Our customer moved the VMs from Windows 2012 Hyper-V host server to 2019 Hyper-V host server, I tried to backup the Exchange 2010 servers via Veeam application-aware function (because we would like to use it for truncate logs) and it failed, the error message show failed to create production checkpoint.
As we know, Veeam Backup and Replication 9.5 Update 4a supports lots of new features, I showed you how to step by step to install it at my previously Blog.
Today, I tried to upgrade Veeam Backup and Replication from 9.5 update 3a to 4a, it showed Unable to detect database action error message, it has never happened this error before, I got a solution to solve this issues after contact with Veeam support engineer, let’s follow steps to solve this issue.
Veeam released the Backup & Replication 9.5 service pack 4a today, Veeam Backup & Replication 9.5 Update 4a is a cumulative hotfix rollup that addresses issues reported by customers on the original build of Update 4, as well as minor platform support enhancements –
VMware vSphere 6.7 U2 readiness, Microsoft System Center Virtual Machine Manager 2019, Dell EMC Data Domain DD OS 6.2. In addition, Update 4a addresses over 300 minor bugs reported by customers and found during the internal testing.
The details information you can check from Veeam website https://www.veeam.com/kb2926
The Installation steps are straightforward, but you need to confirm that you are running version 188.8.131.5215 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrade, your build number will be 184.108.40.20653.
Veeam released the service pack 3a on July, it includes to fix some support issues and it also add to support some current platforms – Microsoft Windows Server 1803, Microsoft Windows Server Hyper-V 1803, Microsoft System Center Virtual Machine Manager 1801, Microsoft Windows 10 April 2018 Update, VMware vSphere 6.7, VMware vCloud Director 9.1…. and added support for Direct Restore to Microsoft Azure for environments with ExpressRoute or site-to-site VPN connectivity to Azure.
when we tried to use Veeam backup and replication 9.5 with Update 3 to Back and replica VMs, all VMs are happy except two Windows Server 2012 R2 Active Directory Servers, they showed error message “Failed to create VM recovery checkpoint (mode: Veeam application-aware processing) Details: Job failed (”). Error code: ‘32768’. Failed to create VM recovery snapshot, VM ID ‘d2936ee7-3444-419e-82d9-01d45e5370f8’.Retrying snapshot creation attempt (Failed to create production checkpoint.)Task has been rescheduled”.