What is the right thing to do today to prepare for leveraging Windows Server 2019? I’m convinced there is no single answer on the best way to address these systems; rather the right approach is to identify options that are suitable for each workload. This may also match some questions you may have. Should I move the workload to Azure? How do I safely upgrade my domain functional level? Should I use Azure SQL? Should I take physical Windows Server 2008 R2 systems and virtualize them or move to Azure? Should I migrate to the latest Hyper-V platform? What do I do if I don’t have the source code? These are all indeed natural questions to have now.

Unfortunately, bad patches are something everyone has experienced at one point or another. Just take the most recent example of the Microsoft Windows October 2018 Update that impacted both desktop and server versions of Windows. Unfortunately, this update resulted in missing files for impacted systems, and has temporarily been paused as Microsoft investigates.

Because of incidents like this, organizations are often seldom to quickly adopt patches. This is one of the reasons the WannaCry ransomware was so impactful. Unpatched systems introduce risk into environments, as new exploits for old problems are on the rise. In order to patch a system, organizations must first do two things, back up the systems to be patched, and perform patch testing.

With the infrastructure world in constant flux, more and more businesses are adopting a multi-cloud deployment model. The challenges from this are becoming more complex and, in some cases, cumbersome.

Welcome to even more tips and tricks for a smooth Veeam Availability Orchestrator deployment.

Having been hands-on in service provider land for the entirety of my career prior to joining Veeam, I understand the pain points that come with offering backup and recovery services. I’ve spent countless hours working on getting the best combination of hardware and software for those services. I also know firsthand the challenges that storage platforms pose for architecture, engineering and operations teams who design, implement and manage these platforms.

The Scale-Out Backup Repository (SOBR) is a very powerful management technology that has been in Veeam Backup & Replication since v9, but I recently had a situation in our lab that made me remember how powerful this technology is, and I thought it appropriate to re-introduce this feature.

Recently we announced a new joint solution, Veeam Availability on Cisco HyperFlex. This new solution brings together the power of Veeam Hyper-Availability Platform and Cisco's industry-leading Hyperconverged Infrastructure (HCI) solution, HyperFlex to deliver an enterprise-grade, highly available Intelligent Data Management platform. So, what’s different?

Veeam Backup & Replication is known for ease of installation and a moderate learning curve. It is something that we take as a great achievement, but as we see in our support practice, it can sometimes lead to a “deploy and forget” approach, without fine-tuning the software or learning the nuances of its work. In our previous blog posts, we examined tape configuration considerations and some common misconfigurations. This time, the blog post is aimed at giving the reader some insight on a Veeam Backup & Replication infrastructure, how data flows between the components, and most importantly, how to properly load-balance backup components so that the system can work stably and efficiently.

The end of general support for vSphere 5.5 was on September 19, 2018. There may be a number of questions for those customers that are still sitting on vSphere 5.5, like what version do I upgrade to? And what considerations do I need to make as part of the support upgrade path?

Today is End of General Support for vSphere 5.5! There have been lots of articles and walkthroughs on how to make that upgrade work for you, and how to get to a supported level of vSphere. But we wanted to touch on making sure your data is protected prior, during and after the upgrade events.