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.
I was trying to configure and test Notification email of Veeam Backup for Microsoft Office 365 V3 function, I received a test notification email consist of unreadable symbols.
Today, I am going to show you how to fix this issue, let follow steps to fix it.
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 9.5.4.2615 prior to installing this update. You can check this under Help | About in Veeam Backup & Replication console. After upgrade, your build number will be 9.5.4.2753.
Veeam released the Backup & Replication 9.5 Update 4 on January, also with this release, Veeam now also have support for Cloud based Object Storage, such as Azure Blob Storage which means that we can have the last 30 days of data stored on a local repository and then move the archive or later up to a Azure Blob but Azure Blob is capacity tier storage, you cannot use it as local backup repository and backup data to it directly. Let’s follow steps to configure it.
As you know, Veeam released the service pack 4 on January 2019, it’s not fix bugs only, it also includes a lot of new features –
Support for Microsoft Windows Server 2019,
Application-level monitoring,
Dedicated view for job and disk-based alarms, Veeam Agents support, Enhanced Cloud Gateway view, Enhanced “Cloud Connect Inventory” report, Microsoft Hyper-V 2019 Support…
The details information you can check from Veeam website https://www.veeam.com/veeam_one_9_5_whats_new_wn.pdf and https://www.veeam.com/veeam_one_9_5_u4_release_notes_rn.pdf.
The steps are straightforward, but you still need to be careful about one thing, the first one is “If you use Veeam ONE to monitor Veeam Backup & Replication or Veeam Cloud Connect, be sure to install Update 4 for Veeam ONE 9.5 first” and the second is “If you are a tenant of a cloud provider, please contact your provider before upgrading to ensure the provider has applied Update 4 on their end”.
Veeam released the service pack 4 on January, it includes to fix some support issues and it also support some current platforms – Microsoft Windows Server 2019, Microsoft Windows Server Hyper-V 2019, Microsoft Active Directory 2019, Exchange 2019 and SharePoint 2019, Microsoft Windows 10 October 2018 Update, Oracle Database 18c, VMware vSphere 6.7 U1 ESXi, vCenter Server and vCenter Server Appliance (VCSA) , VMware vCloud Director 9.5 …. and Expanded restore options to AWS and Azure Stack with Veeam Cloud Mobility, Native Object Storage Support with Veeam Cloud Tier, Improved Security and Compliance with Veeam DataLabs.
Veeam released the service pack 3a on July, it includes to fix some support issues and it also 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.
Today, I received some warning notification emails from Veeam Backup Jobs, they are showing warning as follow:
“Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-0_EB28E537-B0D9-4F9B-80CC-065D6A5E142C.avhdx
Failed to create change tracking time stamp for virtual disk file C:\ClusterStorage\Volume1\PRODVMS\SQL2\SQL2\disk-1_4291495F-31FD-48D8-8621-64516CB1CE6D.avhdx”
We built a new Windows Server 2016 S2D Cluster last week and moved all VMs from Windows 2012 R2 Cluster to new Windows 2016 S2D Cluster and Standalone Windows 2016… Read more »
As we know, Veeam Backup and Replication Software is a powerful and easy-to-use for backup and availability solution, I would like to share a troubleshooting tip with you today. You… Read more »
I helped lots of customers to upgrade Veeam Backup & Replica service from 9.0 to 9.5, most of them are very smooth without issues, but if their server was being… Read more »
Veeam backup copy to Azure After build Site-to-site VPN between Cisco Meraki with Azure, let’s continually settings for Veeam backup copy to Azure. Settings in Azure site Logon to Azure… Read more »
Today, a customer asks me to build a Site-to-Site VPN between their Meraki environment with Azure, they also need Veeam backup copy to Azure, they are using other cloud provider… Read more »
