How to Migrate Veeam Backup and Replication 10a Server from Windows Server 2012R2 to 2019
Today, I am going to show you how to migrate Veeam server from Microsoft server 2012 R2 to Windows server 2019.
Today, I am going to show you how to migrate Veeam server from Microsoft server 2012 R2 to Windows server 2019.
Today, I am going to show you how to configure Veeam Backup for Microsoft Azure 1.0 with auto create service account.
Veeam released Veeam Backup for Microsoft Azure 1.0 on April 28, 2020, Veeam Backup for Microsoft Azure is a solution developed for protection and disaster recovery tasks for Microsoft Azure environments. With Veeam Backup for Microsoft Azure, you can create image-level backups of Microsoft Azure VMs and keep them in Microsoft Azure storage accounts for high availability, cost-effective and long-term storage. In addition to image-level backups, you can protect your data by creating and maintaining a chain of cloud-native snapshots of Microsoft Azure VMs.
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, RHEL 8.2, CentOS 8.2, Oracle Linux 8.2 (RHCK), 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 Cumulative Patch KB3222 for VBO 365 V4c 365 on July 9, there are some Enhancements and Bugs fixed as bellow:
Veeam released Veeam Backup for Microsoft Office 365 on June 4, but the GA build of Veeam Backup for Microsoft Office 365 version 4c (build 4.0.1.519) was recalled due to a backup sync issue identified by Veeam quality assurance.
If you are running build 4.0.1.519 please refer to the KB3194 and install the corresponding patch. The latest 4c Day 0 Update build 4.0.1.531 is now available for download with the link provided below.
Today, I am going to show you how to use Veeam Backup for Microsoft Office 365 V4 with Modern Authentication backup to Azure Blob.
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.
My customer asked me to remove manually added physical server from Veeam Backup and Replication, because the server was be replaced by a new server.
Today, I am going to show you how to remove manually added physical server from Veeam B&R.
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.
I was trying to upgrade VBO 365 from V3 to V4, everything looks fine except upgrading Default Backup Repository, the status shows Upgrade failed “Access is denied”, it has never happed with other customers for upgrading VBO 365 from V3 to V4.
Today, I am going to show you how to use Veeam Backup for Microsoft Office 365 V4 backup to Azure Blob. If you still don’t know how to create Azure Blob, you can reference my previously post as follow link to created it.
Veeam released Veeam Backup for Microsoft Office 365 V3 on November 26 2019, there are lots of function be increased and improved, including Object storage support, Increased Information security, Faster backup performance, Exclude retention for contacts and calendars, Group-based targeting, Enhanced reporting…etc.
eeam released the Backup & Replication 9.5 service pack 4b yesterday, Veeam Backup & Replication 9.5 Update 4b is a cumulative hotfix rollup that addresses issues reported by customers on the original build of Update 4 and Update 4a, as well as add some new feature and platform support enhancements –
Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903, Microsoft Windows 10 May 2019 Update and Microsoft Windows Server version 1903, Linux Kernel version 5.0, Ubuntu 19.04, SLES 15 SP1, RHEL 8, CentOS 8 and openSUSE Leap 15.1, VMware vCloud Director 9.7, VMware vSphere 6.5 U3 readiness, VMware vSphere 6.7 U3 readiness.
In addition, Update 4b addresses over 100 minor bugs reported by customers and found during the internal testing.
Today, I tried to stop a running backup job session, but its status stuck at stopping for 1 hour, there are some jobs are running, I don’t want to impact them, so I decided to force stop the backup job.
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.
You have to very carefully about users License issues before run Veeam Backup for Microsoft Office 365 backup job, because once a license has been given over to a user/site/item, it will aspirate (fall off) 31 days after the last backup. so, you will got the warning message even you removed the user from the backup job settings.
Fortunately, you don’t need to remove backup job or backup repository now because Veeam Backup for Microsoft Office 365 V3.0 added the feature to remove licensed users, but you must remove those unwanted licensed users from backup repository’s database and then remove the license.
Veeam released Veeam Backup for Microsoft Office 365 V3 on April 2, there are lots of function be increased and improved, including increased backup speeds, improved security with multi-factor authentication support, simplified management for larger environments, flexible retention options… etc.
The most import is Veeam release Community Edition version, what is Community Edition? It provides FREE backup and recovery of Office 365 Exchange Online, SharePoint Online and OneDrive for Business, eliminating the risk of losing access and control over your Office 365 data – limited to 10 users and 1 TB of SharePoint data. What are you waiting for? Let’s follow steps to configure it for protecting your Microsoft office 365 data.
Veeam released Veeam Backup for Microsoft Office 365 V3 on April 2, there are lots of function be increased and improved, including increased backup speeds, improved security with multi-factor authentication support, simplified management for larger environments, flexible retention options… etc.
The most import is Veeam release Community Edition version, what is Community Edition? It provides FREE backup and recovery of Office 365 Exchange Online, SharePoint Online and OneDrive for Business, eliminating the risk of losing access and control over your Office 365 data – limited to 10 users and 1 TB of SharePoint data. What are you waiting for? Let’s follow steps to install it for protecting your Microsoft office 365 data.