Last year I was tapped to spearhead a new project here at Veeam: launch a global influencer program. This honestly was something I was a bit timid about as I have no experience operating a program like this. I’ve happily been nominated as a VMware vExpert and a Cisco Champion for a number of years. Additionally on my team, Doug Hazelman, Luca Dell’Oca and Clint Wyckoff have been nominated as current and prior vExperts and Mike Resseler as a Microsoft MVP. We feel we have a good background on how these types of programs should operate and now we are happy to publically announce the Veeam Vanguard Program.

In previous posts we talked about recovery methods that can be used with Veeam Endpoint Backup. While discussing volume recovery we mentioned a few limitations and how these limitations can be avoided via Veeam Recovery Media. Let’s take a closer look at the Veeam Recovery Media and how to start the Bare Metal Recovery process.

The physical (and mental!) process of migrating from legacy to virtual can be sometimes a difficult job for admin because the virtual sphere terms and features are sometimes different from what was learned earlier. For those of you who are learning about the many aspects of virtualization and Hyper-V, we will continue to publish helpful posts that explain various Hyper-V features.

In our previous post we discussed file-level recoveries. Besides recovering individual files, you also have the ability to recover entire volumes. Note that this only works when you have chosen the Entire PC or the Volume Level Backup methods. When you perform volume-level recovery, Veeam Endpoint Backup FREE restores the entire content of the volume.

It probably has been said ten million times before but it’s worth saying again… Backup always leads to recovery and recovery should be easy. In previous posts we looked at the integration of Veeam Backup & Replication with Veeam Endpoint Backup FREE and already gave you some recovery options that you get with the integration. Today we are going to review the recovery options available for any end user.

Before we dive in to this, keep in mind that recovery options highly rely on the backup mode you used. For example, it not possible to recover the entire computer from your personal files backup.

In the previous Veeam Endpoint Backup FREE blog post we discussed the integration between Veeam Endpoint Backup FREE and Veeam Backup & Replication. Besides the minimum requirements (Veeam Backup & Replication v8 with update 2) and the configuration, we also looked at addition data protection possibilities such as backup copy jobs and backup to tape jobs. Finally we looked at additional administration tasks like reviewing statistics, deleting and / or removing endpoint backup jobs and more.

Today we continue and look at probably the most important additional functionality… Additional restore options

I'll wrap up my “Replication 101 series” with an overview of recovery options from VMware VM replicas available in Veeam Backup & Replication v8 (a part of Veeam Availability Suite v8). I'm going to walk you through failover basics, including planned failover and failover plans, which can help you automate disaster recovery (DR). Keep reading to learn how to safeguard your critical applications from failures and downtime.

Some time ago, we released Veeam Backup & Replication v8 Update 2. Why is this update important for Veeam Endpoint Backup FREE? The answer is pretty simple – starting from Update 2 you can use a Veeam Backup & Replication repository as a backup destination. Besides using a Veeam Backup & Replication repository as a backup destination (target) you receive many more possibilities. Let’s start today with the integration, data protection tasks and the additional administration possibilities that you get.

Scheduling is an important part of your backup strategy. Whether you run your backup at noon or in the middle of the night can be an important decision for you. When is your computer running and available for backup? Do you want to run it after a long day of work or before the day starts? Do you want to run it whenever you attach your backup storage or connected to the network? And how many time need to be minimum between different backups? Those of you that work with servers know that it isn’t always easy to find the right timing to perform your backups and with endpoints such as laptops and desktops it even gets more difficult.