Tag: Data Protection
Veeam & File Shares: Licensing & Feature Comparison
It’s easy to backup a file share right? Of course it is! But protecting the data in the most useful way can require a bit of extra consideration. In this blog post I’ve compared the ways Veeam can protect file shares, and any licensing considerations or ‘gotchas’ to be aware of.
Veeam Backup for Microsoft 365: Immutability & Backup Copies
Hey everyone, Today I want to talk about not one, but two new features in Veeam Backup for Microsoft 365 (VB365) v7, these are: Immutability, and Backup Copies. Not only do I want to talk about these two features but, most importantly, how they are related to each other. New VB365 Feature: Backup Copies to…
SQL Server 2019 – TDE DB Recovery Errors, Log Shipping & CU16
If you’re using SQL Server 2019, Transparent Data Encryption, and compressing your database backups, you might be in for a shock. Microsoft released a KB detailing a known bug preventing the restores of these backups. Whilst the latest CU addresses this bug, there’s some important caveats to understand and plan for accordingly. Read this blog…
Data Protection Best Practice: Encrypting Backups
Today I want to talk about backups, and the importance of encrypting them, everywhere. When people think of encrypted backups, the usual first thoughts are around portable backups such as tape and USB or backups outside of your trust domain such as cloud storage. This is a great starting point, and if you’re not currently…
New Blog Series: Cloud Object Storage Deep Dive
Hi, Today I’m excited to finally share my blog series that I’ve been working on for some time, a deep dive into the object storage solutions available from the “big three” public cloud hyperscalers (Azure/AWS/GCP). Part one is available now over at the Veeam Blog and I’ll be updating this post as the other sections…
Veeam – Achieving 3-2-1-1-0 Protection for Cloud Native Workloads
Ensuring you protect your public cloud workloads can require you to adapt your approach, but in this post, we’ll discuss how we can still meet and exceed our 3-2-1-1-0 best practice rule.