In my last post, I indicated how easy it was to tell a storage account (particularly the Azure Shell storage account) to use an encryption key. In that example, I brought my own key. That key was an 2048-bit RSA key that Azure Key Vault was happy to use and apply to my storage account. The figure below shows my 2048-bit key:
Read More
I recently had a situation where I started using Azure Shell. The way I look at Azure, and really any cloud service, security should be the first part of the process.
Read More
Veeam 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.
Read More
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, and it showed Unable to detect database action error message, it has never happened this error before, I got a solution to solve this issue 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.
