Instant VM Recovery considerations for modern data center – Part 2
Instant VM Recovery considerations for modern data center – Part 1
Using orchestration to minimize downtime and maximize compliance
It seems like it’s almost every day that the news reports another major company outage and as a result, the massive operational, financial and reputational consequences experienced, both short- and long-term. Widespread systemic outages first come to mind when considering disasters and threats to business and IT service continuity. But oftentimes, it’s the overlooked, “smaller” threats that regularly occur. Human error, equipment failure, power outages, malicious threats and data corruption can too bring an entire organization to a complete standstill.
Read moreBackup Tape Storage Best Practices
Step-by-step guide to deploy different OSes through Windows Deployment Services
Time synchronization in an all virtual environment guide
How to use PowerShell and PowerShell cmdlets
PowerShell has come a long way from a command line interpreter with support of a few commands, to a fully integrated part of every modern Windows OS. Right now, not only is it a cool thing to, but it is also essential in order to achieve better results in Windows tasks’ management, including virtual machine (VM) backup.
This is a two-part article. In the first part, I’m going to talk about PowerShell in general, when you should consider using it for Hyper-V backup and how to get acquainted with PowerShell basics, PowerShell commands (cmdlets) and syntax.
Read moreCluster Group Start Ordering on Windows Server 2016
How to avoid vSAN compatibility issues and be sure your SureBackup is a success
Hello from Veeam Support!
Recently, a customer contacted us with the very curious case. The SureBackup job was failing with the generic error message during snapshot creation phase: “The specified feature is not supported by this version.” There were several VMs included in the SureBackup job, but only one specific VM failed. Moreover, the source backup job itself worked perfectly, including the affected VM.
Read more