Quantcast
Channel: Veeam Software Official Blog
Viewing all 1388 articles
Browse latest View live

VeeamON 2015 Call for Presentations now open!

$
0
0

In just over 6 short months, we will be hosting VeeamON 2015, in Las Vegas! If you attended VeeamON 2014, you know this is THE event dedicated to data center Availability. If you weren’t able to join us last year, know that VeeamON has already made quite an impact industry-wide – in a good way! We have more than doubled the amount of technical programs and training for 2015, so NOW is the time join the VeeamON community and participate.

Without further ado, we are pleased to announce that our Call for Presentations (CFP) is now open and live on the VeeamON website! Mark your calendars - The CFP is open now will be closed by July 13, 2015, or earlier if we have reached a sufficient level of excellent content submissions.

vo1

The goal of the CFP is to give the broader Veeam communities an opportunity to share their expertise in technologies related to data center Availability. There are three main content areas that the CFP are aligned to:

  • Availability
  • Virtualization
  • Cloud and storage

These main categories align to various Veeam products, such as Veeam Backup & Replication, Veeam ONE, the Veeam MP for System Center, and now Veeam Endpoint Backup; but also supporting technologies, such as modern storage systems or virtualization platforms. There are also dedicated sessions for our partners who are top-level sponsors at VeeamON, as well as sessions dedicated to our ProPartners for the business of selling Veeam software.

The CFP, however, is YOUR opportunity to present at VeeamON! Be prepared - Just as VeeamON 2015 is expected to be bigger and better, this year’s CFP competition will be tough. The content presented from this year’s programs will derive closely from YOUR CFP submissions! So, be prepared to submit your BEST ideas! After the reviewing process is complete, each selected author will be notified via email.

Maybe you aren’t necessarily interested in submitting to this year’s CFP, but you ARE interested in joining in on the fun, you still can pre-register now to be the first to know when early bird pricing is available. Still not convinced? Watch the preview video for VeeamON 2015.

We hope to see you in Vegas!

If you plan on attending VeeamON 2015, don’t forget to pre-register and be the first to know when registration opens. If you are submitting to CFP, NOW is the time to think about your idea. Remember, this is YOUR opportunity to engage your colleagues by sharing the BEST content related to data center Availability.

Pre-Registration Page

Call for Presentations Page

VeeamON 2015 main page

Like VeeamON on Facebook!


A0 poster – 47 restore scenarios from Veeam Backup & Replication v8

$
0
0

Did you have a chance to print and hang either of our free Veeam posters? If not, you can still get both of these useful posters here: Veeam Backup & Replication v7 for Hyper-V and Veeam Backup & Replication v8 for VMware. Today, we have another poster for you called: 47 restore scenarios from Veeam Backup & Replication v8.

From the very beginning, Veeam Backup & Replication has been consistently popular because of its highly successful recovery procedures. Here at Veeam, we have a saying that, at the end of the day, backup is worthless if you can’t restore your data on demand.

Along with the development of new product versions, Veeam realized that users want to manage recovery in ways that are more flexible, without losing any of the high quality. To respond to these needs, we’ve been including new features to extend Veeam restore capabilities.

We introduced the Veeam Explorers family, which helps system administrators to perform granular recovery operations of Tier-1 applications. vCloud Director support, tape and cloud as backup destinations, Veeam Explorer for Storage Snapshots, etc... — every single feature, what was done for backup, made us taking care about restore as well.

By version 8 of Veeam Backup & Replication, we realized that this solution has 47 different restore scenarios! All of these scenarios are now presented in the new poster below. To be completely honest, it does not mean that you would actually need to restore a backup file every time in 47 different ways, but this poster will definitely give you an idea of the real scope of Veeam capacity.

47 Veeam restore options

Download the poster and use it just like the other two posters: print it in color with decent quality using A0 format and hang it on the wall. Use it as your guide when you want to restore data or need information about how things should work.

Stay tuned, there is yet another free poster coming to you in the very near future!

As always, please share your thoughts about this latest poster, as well as suggestions for future blog topics in comments.

Veeam Availability Suite Update 2: vSphere 6 Support, Endpoint and More!

$
0
0

Today is a key milestone for Veeam Availability Suite v8 (a combination of Veeam Backup & Replication and Veeam ONE) as Update 2 is now generally available. Both products have been updated, and in this blog I’ll showcase what you need to know about the most important features: FULL vSphere 6 Support, Veeam ONE updates and Veeam Endpoint Backup FREE Support.

Veeam FULLY supports vSphere 6!

When I last wrote how vSphere 6 Support is coming soon, we wanted to proactively communicate that support was coming. Since then, our QC has been busy performing our standard extended stress testing of the release candidate builds against vSphere 6 RTM code – and today we are finally making the Update 2 generally available.

As always, we did not settle for basic compatibility and are providing FULL support of vSphere 6 with the following features and enhancements, most not currently available from any other vendor:

  • Support for VMware Virtual Volumes (VVols) and VMware Virtual SAN 2.0
  • Storage Policy-Based Management (SPBM) policy backup and restore
  • Backup and replication of Fault Tolerant (FT) VMs
  • vSphere 6 tags integration
  • Cross-vCenter vMotion awareness
  • Quick Migration to VVols
  • Hot-Add transport mode of SATA virtual disks

Let’s look into this list a little closer. While support for VVols, VMware Virtual SAN 2.0 and Hot-Add transport mode of SATA virtual disks comes easy by simply using the new Virtual Disk Development Kit (VDDK) version, it’s still important to note that our Virtual SAN support remains very advanced on the market as Luca describes. Keep in mind that this smart processing mode provides the most efficient availability technology for any EVO:RAIL and EVO:RACK solutions, as they are built on VMware Virtual SAN. Just put a virtual Veeam proxy on each host.

If you are investing in these next-generation storage technologies from VMware, then you already know that Storage Policy-Based Management (SPBM) is the way to manage VM storage requirements in vSphere going forward. With our support for VM policies backup and restore, we are able to restore VM storage policy associations upon full VM restore. This eliminates manual processes, which directly impacts recovery times. SPBM policies are important to restore because "out of policy” VMs can impact availability of either the restored VM itself, or other VMs sharing the same storage. By default, we will restore the same policies as the backed up VM had – and of course you can choose the desired policy in case of out of place restores:

blog-4-xx-2015-FigX.jpg

Storage Policy-Based Management restores ensure the restored VM gets the same policy, or a new one, it had before the backup.

 

The most intriguing part of our vSphere 6 support to me is having the ability now to backup Fault Tolerant VMs with Veeam Backup & Replication. Among many other enhancements to Fault Tolerance, vSphere 6 includes the ability to snapshot Fault Tolerant VMs through APIs (and this is actually the only way that a snapshot can be created on this type of VM). And thanks to that, Veeam Backup & Replication can finally backup and replicate your Fault Tolerant VMs – just like any other VMs. This, along with other Fault Tolerance enhancements in vSphere 6 removes the remaining barriers of using Fault Tolerance in your data center, providing truly the ultimate in availability for your modern data center.

vSphere 6 also provides new APIs for programmatic access and management of vSphere tags. Tags are really a great way to set backup policies when the infrastructure is mixed and combined for resource optimization. We’ve had support for vSphere 5 tags already (of course, Luca blogged that too) and with our vSphere 6 tag support, you can continue building advanced backup policies around this very flexible infrastructure-centric framework even after you upgrade.

Another key feature that we have support for in vSphere 6 is cross-vCenter vMotion. While Veeam Backup & Replication supported protecting VMs across multiple vCenter Server systems for as long as I remember, the problem this new VMware functionality solves is jobs “losing” explicitly added VMs after they move to another vCenter, where their unique object ID (moRef) will be changed. With added support for cross-vCenter vMotion in our Quick Migration functionality, when migrating a VM to another vCenter Server, the associated entries on backup or replication jobs will be updated automatically, so the availability requirements continue to be met.

The final support for vSphere 6 point I want to cover is the ability to do Quick Migration tasks to a VVol. Quick Migration is still a part of Veeam Backup Free Edition, and is a great way to move VMs around when using vMotion is not an option, including instances when you have an unreliable or slow network links, in scenarios when vMotion is not supported, or even due to something as simple as the lack of the corresponding VMware license. This functionality can help to perform full migrations to new clusters built from the ground up with the latest vSphere 6 features and not inherit any design problems from previous clusters.

For us, fully supporting vSphere 6 means both fully leverage all the new features, and ensure that our customers can confidently run the latest VMware technologies in your data center with the availability levels you demand. You may wonder why we never rush into declaring support, and instead always take a few weeks to perform extended testing of the pre-release code against the final platform code? Because it’s backup (and the protection and availability of your data), and it cannot be rushed. Reducing the time it would take would only include additional risk, this Forums thread explains a bit more on the background of this process. If you are reading Veeam Forums weekly digests, or follow Gostev on Twitter, you likely saw him mentioning us finding a major bug with the Direct SAN access transport with vSphere 6:

blog-4-xx-2015-FigA.jpg

Gostev tells it like it is.

 

Every major vSphere release brings a lot of changes compared to previous releases, which is why we want to take time testing reliability of new versions of every updated vSphere component, and how they interact with our solution. For that reason and for many years now, we have been very consistent with the time frame of releasing support for the new vSphere releases (about 6 weeks from GA on average). And this often pays off big time! Checking out the current version of the VDDK release notes for vSphere 6, the situation that Anton mentioned above has now been added as the top known issue, because it can impact production environments! But worry not: we’ve patched this VDDK issue in our Update 2 until VMware provides a fix, so Veeam users using SAN transport can be confident upgrading to vSphere 6 (unlike those using competing solutions!)

One other thing that is important to note is that while adding vSphere 6 support, we keep support for prior versions of vSphere, which are fairly widely used and still supported by VMware. As such, vSphere 4.0 and newer remain supported with Update 2. Again citing the Veeam Forums; we are very transparent with our customers about our plans for platform support as well as your plans. Did you see the forum poll earlier this year about which version you plan to be on by the end of 2015? This goes directly to the R&D team to help prioritize features and platform support based directly on your feedback. And while the bulk of the respondents (45% as of the time of this blogpost) plan to be on vSphere 6 by the end of 2015, as shown below – we can’t drop the ball on those users who chose to stay on the last “fat” ESX version due to their requirements.

img_blog_3

Support for Veeam Endpoint Backup FREE!

Without a doubt, one of the more exciting new products we’ve had recently is Veeam Endpoint Backup FREE. With Update 2 we now have the ability to see backups inside of a Veeam Backup & Replication console. Additionally, and personally most intriguing, we can put endpoint backups in Veeam repositories. This is excellent news for organizations who have critical endpoint devices or a few remaining non-virtualized systems in the data center.

Here’s a view of a Backup & Replication v8 system with Update 2 and the ability to assign endpoint backup permissions to a repository:

img_blog_4

Endpoint support also includes exporting backed up physical disk contents into various virtual disk formats, performing files and application item restores, as well as using Backup Copy and Backup to Tape jobs for shipping endpoint backups offsite. All paid editions of Backup & Replication will be able to receive Endpoint backups with Update 2. If you haven’t given Endpoint Backup FREE a look yet, I highly encourage you to do so. Endpoint backup should be simple and FREE, and Veeam Endpoint Backup FREE is not one to disappoint.

Veeam ONE v8 Update 2

Also available now is Veeam ONE Update 2, which brings in important settings as well. In discussions with Vitaliy Safarov, Product Manager for Veeam ONE, I asked him what his favorite feature is for this update. His choice is the support to monitor everything in vSphere 6, including VVols. Having the complete visibility for the new features of vSphere 6 are very important; as you can’t run a critical technology without having the visibility you need to support it. Veeam ONE can let you run this new storage practice with the visibility you need to ensure there are no surprises along the way.

Update and Enjoy!

Here are some resources regarding Update 2 for Veeam Backup & Replication 8.0 and Veeam ONE 8.0. Also note that the best place to take it all in will be VeeamON 2015 in Las Vegas, we’ll have expanded content this year focusing on the latest availability strategies as well as the deepest access to the new and existing products. Here’s a rundown of some takeaways for Update 2:

Veeam Endpoint Backup FREE

Release Notes for Veeam Backup & Replication 8.0 Update 2

Release Notes for Veeam ONE 8.0 Update 2

What's new in VMware vSphere 6: Deployment tips and upgrade best practices

Download Update 2 (Veeam Backup & Replication and Veeam ONE)

VeeamON 2015

NOTE! Register for a live webinarVeeam Availability Suite v8 Update 2: FULL vSphere 6 support and More! on May 21 at 1 p.m. AEST (Asia), 2 p.m. CEST (Europe), 12 p.m. ET (North America.)

Veeam Endpoint Backup Architecture & Requirements

$
0
0

Most of you know our Veeam Availability Suite solution and how that suite works. Others might be more familiar with the Veeam Management Pack for System Center. With the release of Veeam Endpoint Backup FREE there is a complete new solution in the Veeam family. In a new series of posts, I am going to highlight a few items of this solution, starting with the architecture today.

Veeam Endpoint Backup is a stand-alone solution. This is completely different from our other solutions and therefore does not require a dedicated server, management suite or something else. It is a windows-based tool that can be installed on any computer that matches the prerequisites.

You install Veeam Endpoint Backup on the computer that you want to protect. This solution has a service-based architecture. When you install the solution, the following three major components are deployed on the computer:

  • Veeam Endpoint Service
  • Veeam Endpoint System Tray Application
  • Microsoft SQL Server 2012 LocalDB

Veeam Endpoint Service

The Veeam Endpoint Service is a Microsoft Windows Service that is responsible for performing the backup and restore tasks on the endpoint. It is started automatically and runs continuously in the background to execute your backups on desired schedule.

Veeam Endpoint System Tray Application

Veeam Endpoint System Tray Service is a tray application that communicates with the Veeam Endpoint service to let you monitor the backup status and gives you the possibility to quickly execute tasks such as performing backup, restores and going to the control panel of the solution.

Microsoft SQL Server 2012 LocalDB

Microsoft SQL Server 2012 LocalDB is a light-weight database that, unlike its “big brother” requires the minimum amount of system resources to run. LocalDB is a Microsoft equivalent of SQLite, which is commonly used to store transactional data for things like web browsers or other end user software. The only difference is that SQLite is usually embedded and runs within the application process, so people don't even notice it - whereas LocalDB is executed as a sub-process that is launched by the Veeam Endpoint Service. Veeam Endpoint Backup uses the LocalDB database to store its configuration data.

As stated, LocalDB is a very light-weight database and uses little resources during your daily work. When Veeam Endpoint Backup FREE is idle, the cost of resources for both the database and the solution itself are little to nothing.

clip_image002

And in the screenshot below you can see the amount of resources consumed while Veeam Endpoint Backup FREE is performing a backup.

clip_image004

System Requirements

Veeam Endpoint Backup can be installed on any computer that meets the minimum system requirements for the following supported Microsoft Windows operating systems:

  • Microsoft Windows 7 SP1
  • Microsoft Windows 8.x
  • Microsoft Windows Server 2008 R2 SP1
  • Microsoft Windows Server 2012
  • Microsoft Windows Server 2012 R2

Integration into Backup & Replication

Veeam Endpoint Backup FREE can (optionally) be integrated into Veeam Backup & Replication v8 (requires update 2). Thanks to this integration, you use backup repositories managed by Veeam Backup & Replication as an additional backup target, with backup repository availability to end users controlled by a flexible permission system.

When you want to configure Veeam Endpoint Backup FREE to use a Veeam Backup & Replication repository as a backup target, you will connect to your Veeam Backup & Replication infrastructure by registering a Veeam backup server – but your backup data will go directly to the repository, bypassing the backup server.

That is all you need to know about the integration in regards to the architecture. We will dive much deeper into actual integration, and additional functionality it enables, in the dedicated blog post later in this series.

Conclusion

Veeam Endpoint Backup doesn’t require a lot to be able to run, and its architecture is rather simple. After downloading, it only takes a few clicks and couple of minutes to install the solution and configure the free protection for your endpoint.

Veeam FastSCP for Microsoft Azure, a new free gift for the IT community

$
0
0

The cloud is everywhere since the last few years and it doesn’t look like it will go away any time soon. More and more businesses are considering infrastructure as a service to extend their current datacenter needs. Spinning up a few virtual machines can be done quickly and efficiently in Microsoft Azure and with the pay-as-you-go model, many CFOs are very happy to see the switch from CAPEX to the OPEX model. Yet, as of today, not that many companies are using these services for their production environment, and if they do, it is only a small part or a state-less part of their infrastructure.

But for other needs within the datacenter, certainly in the development, testing and acceptance cycle it is very easy to use these services.

There is a problem…

In many scenarios, there is a potential problem when using Microsoft Azure VMs. Unless the VMs running in Azure are an extension of your datacenter and are domain-joined and connected through a VPN, it isn’t easy to copy files into those VMs or getting data back out.

As an active Azure user, I know this issue first hand.

There are two ways to do this today.

1. Through RDP

The first method is by copying the files through the RDP protocol. This works for smaller files but there are downsides to this method. A disconnect or time-out of your session will interrupt the data transfer and then you need to start again. A small hiccup in the connectivity can cause the exact same problem. Also, this can be very slow and you need to remember to keep the RDP window open until the transfer finishes.

2. Attach a VM disk

The second method is by creating an empty VHD disk on-premises and copy data onto that disk. Then you can upload that disk to your Microsoft Azure storage account and attach it to your VM. While this is more stable than the RDP method, the method is rather roundabout. You need to create the disk, add the files, upload the disk to Microsoft Azure, attach it, initialize, copy of the data, detach it and remove it from your storage account again. Besides that you are also using additional resources during this procedure so you will pay more for the Microsoft Azure services.

The solution

Veeam® is very proud to introduce the beta of Veeam FastSCP™ for Microsoft Azure which solves exactly this problem. And best of all—it’s FREE! With Veeam FastSCP for Microsoft Azure, you will be able to securely copy your files from on-premises to Azure VMs and from Azure VMs to on-premises.

clip_image002

This solution does not require any VPN or independent encryption at all, as the data is transferred securely over HTTPs. You can manually copy files from and to Azure virtual machines and you don’t need to keep the UI open until the file copy completes.

clip_image004

The job can be followed in the Jobs tab.

clip_image006

And even better, you can also schedule file copy jobs for nightly or weekly copies of files to or from Azure virtual machines.

clip_image007

Scenarios solved…

This solution is a potential time-saver and can solve many scenarios in your environment. Here are a few examples:

  • Customizing VMs running in Microsoft Azure

Developers could use this feature to customize the Virtual Machines to meet their specific needs much easier by uploading customization scripts, configuration files and data to have better testing results.

  • Updating data of applications

Nightly uploads of data (like for example daily CMDB data dumps) will allow the IT Professional or Developer to have current data on Azure VMs, or back on-premises.

  • Download usage data or log files

Developers or IT Professionals can capture usage data or log files and send those on-premises for further analysis and testing.

  • Copy database data

You can use this to get database data on-premises and have a copy of your running database on-premises.

  • Basic periodic file-level backup

You can use this to get certain, specific files (data, config, etc.) on-premises on a regular basis.

And we are sure that you can come up with lots more examples! Share them in the Veeam dedicated forum (coming soon) and interact directly with the Product Management team and other Azure users.

Conclusion

Veeam FastSCP for Microsoft Azure solves the problem of uploading data from on-premises to Azure VMs and vice versa. Through a natively secure file copy, with no VPN needed, you can upload or download your data fast and easy – while built-in compression reduces bandwidth requirements in many cases. You can even schedule download and upload jobs with no scripting skills required – everything is done through a simple wizard-driven UI.

The beta is available at http://go.veeam.com/azure

All feedback, issues or anything else can be posted on our forums: http://forums.veeam.com/veeam-fastscp-for-microsoft-azure-f36/

NOTE! Register for a live webinarFree, secure file copy for Azure VMs with Veeam FastSCP for Microsoft Azure, on May 14 at 12 p.m. ET (North America), 11 a.m. CEST (Europe), or 2 p.m. AEST (Asia.)

Veeam Management Pack v8 for System Center beta is here!

$
0
0

With Veeam® Management Pack™ (MP) v7 R2, Veeam delivered a very solid management pack for monitoring Microsoft Hyper-V, VMware vSphere and Veeam Backup & Replication™. IT never stands still, however, and nor does Veeam! Today, I am pleased to tell you that Veeam Management Pack v8 beta is available. As always, some very exciting new items are included in this release.

This release builds on Veeam MP’s core value of delivering complete visibility of your datacenter. And based on both your feedback and our research, we’ve added many new, high-value features to provide you with actionable data to drive better, more informed business-IT decisions.

Let’s look deeper into five exciting new features and improvements that you’ll find in Veeam MP v8.

1. vSphere 6.0 support

Veeam MP v8 now supports VMware vSphere 6.0. This is in line with Veeam’s release of Update 2 for Veeam Backup & Replication and Veeam ONE™, which also includes vSphere 6.0 support. For those upgrading or deploying vSphere 6.0 and managing it with System Center Operations Manager, you now have full visibility into that environment, including Virtual Volumes (VVols) datastores and other vSphere 6.0 features.

image

2. The Morning Coffee report

This is the new feature that I probably like the most. As a former system administrator, one of my daily-recurring morning tasks was to check the entire environment and ensure that everything was in good shape. Accomplishing this task often required a large cup of coffee. Now, Veeam MP’s new Infrastructure Summary report does the work for you by providing a single overview report to check the status of the entire environment.

image

In this report, which you can schedule to run on a daily basis, you can quickly see your entire infrastructure and important values such as density for hosts, clusters, vCPU and more. You can also see the CPU pressure and memory pressure per host, cluster or datacenter. Finally, you can see the pressure on your over-provisioned datastores.

3. Let’s go Hybrid Cloud

We introduced the Hybrid Cloud Capacity Planning report in our previous Veeam MP version, which allowed you to project the cloud resources you would need to move workloads to the Microsoft and VMware public clouds. Now, we’ve updated these analytics in Veeam MP v8 with the latest options for both Microsoft and VMware. We’ve also added more logic into the report to increase prediction accuracy.

image

4. Checkpoint/vSphere snapshot tracking

Every virtualization admin knows about snapshot problems. Whether it is a Microsoft Hyper-V checkpoint or a VMware vSphere snapshot, the problem is the same: snapshots and checkpoints that stay open too long can increase in size and quickly become performance problems for your storage.

With our detailed checkpoint and snapshot tracking, you can now quickly identify storage-related performance issues across your entire virtual environment. In MP v8, we’ve introduced an updated dashboard using the custom Veeam heatmap widget that we call Snapshot Finder .

image

Once you use this Veeam MP dashboard to quickly locate snapshots, a detailed, new report lists the entire snapshot tree, plus a timestamp and comments. This allows you to identify the snapshot’s owner and justification so you can either quickly remove it or take another appropriate action.

image

5. Support for SMB shares for Hyper-V

If you are using SMB 3.0 file shares for your Hyper-V VMs, Veeam MP adds visibility there too. SMB shares can now be seen in the Storage Topology view, with drill-down to the virtual machine (VM) level. Veeam MP also monitors performance and availability of SMB storage.

image

Is there more?

Of course! Besides the above five added features and improvements, we also added some interesting things to help you make faster and better-informed IT decision-making.

We’ve added additional tuning and optimization to correct over-sized and under-sized VMs and hosts. This means you can now decide on peak or average resource usage for right-sizing advice. You can also leverage data collected from inside a virtualized OS with the System Center Operations Manager agent, so estimates are more application-aware.

Our famous Veeam Task Manager for Hyper-V now comes as a plugin for Microsoft System Center Virtual Machine Manager (VMM). This allows you to see real time performance metrics on your hosts and VMs, embedded in the VMM console.

image

In addition, we have enhanced our vCenter alarm monitoring to track system configuration health, security certificates, hardware components and more.

And last, but not least, there are some new, cool dashboards, widgets, reports and visualizations available.

Conclusion

The new Veeam Management Pack v8 for System Center will support the latest hypervisor versions and Veeam Backup & Replication versions. In addition, it provides additional support for VMware vSphere v6 and it comes with more functionality, logic and actionable data for management, planning, forecasting and making good IT business decisions.

If you are already using Veeam Management Pack for System Center, then please put our Veeam MP v8 beta to the test in your lab and give us feedback! If you are not a customer yet, but are looking for a management pack that delivers complete visibility and brings relevant, timely data with alert management, dashboards, reporting, on-premises and hybrid-cloud capacity planning—then this is a must-try-to-believe-it product!

For all feedback, questions and possible issues with Veeam MP, visit our dedicated MP forum (http://forums.veeam.com/veeam-management-pack-for-microsoft-system-center-f1/).

Download the BETA: http://go.veeam.com/mp-v8-beta

NOTE! Register for a live webinarWhat’s NEW in Veeam Management Pack v8 for System Center, on May 28 at 12 p.m. ET (North America), 2 p.m. CEST (Europe), or 1 p.m. AEST (Asia.)

Veeam Backup Free Edition: Now with PowerShell!

$
0
0

Vladimir EreminThis is a guest post by Vladimir Eremin, a product manager at Veeam. Vladimir is very active on the Veeam Forums, Twitter and in Spiceworks. One of Vladimir’s skills is PowerShell and he walks through this process here in this guest blog post. If you have any question on the PowerShell parts mentioned in this post, use the Veeam Forums to discuss. You an also download the sample script here and discuss this topic in the Veeam Forums.

Our Veeam Backup Free Edition has been the most popular free Veeam tool, mostly thanks to its VeeamZIP functionality: ability to perform interactive full backups of unlimited amount of VMs. However, VeeamZIP has always had one small yet irritating limitation – the inability to schedule performing regular backups. Indeed, due to the fact that VeeamZIP can only be triggered interactively, there is simply no means in UI to schedule it like regular backup jobs. If you have been down this path, you will be happy to know that as of Update 2, this is no longer the case! In areas like the Veeam forums, our engagement on Twitter and other areas; we have recognized the concern and decided to address it by making Start-VBRZip PowerShell cmdlet available in Free Edition.

How it works

As noted earlier, the main functionality Veeam Backup Free Edition is ability to perform VeeamZIP backups of your VMs (and, of course, to recover VMs, guest files and application items from those backups). VeeamZIP always produces a full backup file (.vbk) that acts as an independent restore point. Free Edition allows you to store the backup file on a backup repository, on a local folder or on a network share.

When you perform backup with VeeamZIP, you can start the backup process for selected VM immediately. This type of backup requires minimal settings, and as such is extremely easy to trigger manually.

image

With Update 2, you can now write a simple PowerShell script (download example here) that starts VeeamZIP activity for a selected VM, and sets whatever schedule you want for it via Windows Scheduler. We have even created the following example script for you that will not only trigger VeeamZIP backups of the required VMs, but will also email you a nicely formatted report with backup results!

Script parameters

The script is able to perform ad-hoc backup of selected VMs residing on both standalone host or cluster, or vCenter server. Before executing script, you need to provide three mandatory parameters: names of VMs to backup, host those VMs are located at, and directory where backup files should be stored.

 

##################################################################

#                   User Defined Variables

##################################################################

 

# Names of VMs to backup separated by semicolon (Mandatory)

$VMNames = ""

 

# Name of vCenter or standalone host VMs to backup reside on (Mandatory)

$HostName = ""

 

# Directory that VM backups should go to (Mandatory; for instance, C:\Backup)

$Directory = ""

Optionally, you can change compression level and desired retention, disable VMware quiescence, enable encryption or even notification settings:

# Desired compression level (Optional; Possible values: 0 - None, 4 - Dedupe-friendly, 5 - Optimal, 6 - High, 9 - Extreme)

$CompressionLevel = "5"

# Quiesce VM when taking snapshot (Optional; VMware Tools or Hyper-V Integration Components are required for this in the guest OS; Possible values: $True/$False)

$EnableQuiescence = $True

# Protect resulting backup with encryption key (Optional; $True/$False)

$EnableEncryption = $False

# Encryption Key (Optional; path to a secure string)

$EncryptionKey = ""

# Retention settings (Optional; by default, VeeamZIP files are not removed and kept in the specified location for an indefinite period of time.

# Possible values: Never, Tonight, TomorrowNight, In3days, In1Week, In2Weeks, In1Month)

$Retention = "Never"

If you like to get an email report once the backup is completed, you should additionally fill out the following notification settings.

##################################################################

# Notification Settings

##################################################################

# Enable notification (Optional)

$EnableNotification = $True

# Email SMTP server

$SMTPServer = ""

# Email FROM

$EmailFrom = ""

# Email TO

$EmailTo = ""

# Email subject

$EmailSubject = ""

The resulting email report will look like this:

 

Name Start Time End Time Result Details
CentOS-tiny_2015-03-26T180459 3/26/2015 6:04:59 PM 3/26/2015 6:07:17 PM Warning Processing finished with warnings at 3/26/2015 6:07:13 PM Cannot use VMware Tools quiescence because VMware Tools are not found.
CentOS-tiny_replica_2015-03-26T180720 3/26/2015 6:07:20 PM 3/26/2015 6:11:20 PM Success Processing finished at 3/26/2015 6:11:18 PM

All of the abovementioned settings can be configured by setting certain variables to the corresponding values. For instance, to enable encryption, you should set $True (Boolean) value to $EnableEncryption variable, and provide the encryption key (see the next chapter). Additionally, if you want the backup files to be deleted after two weeks, you should set “In2Weeks” (string) value to $Retention variable, etc. There is no need to remember what each and every variable does and what values are acceptable – for your convenience, the example script include a short description for each variable.

Encryption

Getting back to encryption, data security is a critical part of the backup strategy. Backup data must be protected from unauthorized access, especially when a sensitive VM data is backed up to an offsite location or archived to tapes. To keep your data safe, you can encrypt your VeeamZIP backups. As noted above, this requires choosing a file containing the encryption password.

Of course, you could provide the password to a script as a plain text string. However, regular strings are insecure (to the say the least), since they are stored in memory as plain text. As a result, most PowerShell cmdlets will simply not accept passwords in this form.

A secure string is a better option. This type is like the usual string, but its content is encrypted in memory. It uses reversible encryption so the password can be decrypted when needed, but only by the principal that encrypted it. To create a secure string you need to open the PS console, and type the following two lines. When executed, the code will ask you to prompt a password and, then, save it as a secure string into a file:

$SecurePassword = Read-Host -Prompt "Enter password" -AsSecureString

$SecurePassword | ConvertFrom-SecureString > “Directory where secure string should be stored; C:\SecureString.txt, for instance”

After that, specify the path to the newly-created file in the main script:

# Protect resulting backup with encryption key (Optional; $True/$False)

$EnableEncryption = $True

# Encryption Key (Optional; path to a secure string)

$EncryptionKey = "C:\SecureString.txt"

 

Scheduling the script

Before you schedule the script, be sure to try starting it manually to ensure that it performs as expected.

The easiest way to schedule the script to perform periodic backup automatically is to use Windows Task Scheduler. Simply go to the Task Scheduler tool, and create a new basic task:

image

Assign a name and a description for it, so that you can easily remember what this task does.

The next page is the Task Trigger. It is pretty basic, and self-explanatory. The available options are quite flexible (everything from running backups several times a day or once a month is possible), so set there whatever values that address your RPO requirements. Most people use daily backups:

image

Set the start time for the task for the off hours. In this example, the task runs every evening at 22:00 PM beginning on April 22, 2015.

image

On the subsequent Action page, specify that you want the scheduled task to Start a program, and then click Next.

clip_image002

On the Start a Program pane, you place the following command into Program/script:

Powershell –file “Path to Veeamzip.ps1 file”

clip_image004

That’s it! But we may want to open the task once it is created to make a couple of additional changes. To do so, select the Open the Properties dialog for this task when I click Finish:

clip_image006

Since the task is to be run on a server, where a user might not be logged when the task takes place, it is worth to enable the task to run regardless of whether or not the user is logged on by associating the user’s credentials with the task.

clip_image008

Once you’re done, right-click the job and select Run to ensure that the task completes properly:

clip_image009

PowerShell gives the users what they have always wanted from Veeam Backup Free Edition!

Now that you are armed with this new awesome capability, you now should be able to achieve the long-awaited goal – do scheduled backups with the use of Veeam Backup Free Edition, which provides far more backup and recovery features than script-based free backup solution alternatives.

Check out these other cool resources:

· Veeam whitepaper: The hitchhiker’s guide to Veeam Backup Free Edition

· Veeam blog: What’s new in v8 for Backup Free Edition

· Veeam PowerShell forum

· Download sample Script


 

New poster! Veeam Backup & Replication v8 for Hyper-V: Features overview

$
0
0

We released our first technical poster — Veeam Backup & Replication v7 for Hyper-V: Overview — almost a year ago. It is now time to upgrade that poster with v8 features and enhancements for Hyper-V environments.

This new poster (11MB) is more than just a slight update. It’s completely different material, even though you may see a few similarities at first glance.

A good way to explain this poster is by comparing it to Earth cycles, which has many natural cycles such as water, rock, carbon and more. Just like Earth cycles, there are also many artificial cycles created by people. Data cycles, in particular, are very special to those of us in the IT world.

You process your company’s data with servers. Your colleagues use their laptops to use that data, as well as generate new data. Corporate facilities have data, storage, networks and tapes. And of course, this all needs protection.

In order to protect your data, you back it up and sometimes put it at a remote site and restore it from there when you need it. Solutions are an important part of the data cycle, because they help you manage your data at each stage of the cycle, or they transfer the data in-between some stages. Veeam continues to improve its products so that they are more powerful and provide you with the very best options for data management.

Take a look at the advanced deployment of Veeam Backup & Replication v8 on this new poster (11MB) to see exactly what Veeam offers for each part of your data cycle. Some of these features are well known from previous versions and some are brand new for v8, such as Veeam Cloud Connect or Planned Failover. The bottom line? With Veeam, you never need to worry about the availability of your data. Veeam has it covered!

v8_hyperv_poster_preview

This poster is optimized for printing in A0 format. Place it close to other Veeam technical materials on your wall and impress your boss!

Please let us know which types of materials you’d like to see in the future, and feel free to leave a comment below.


Getting started with Veeam Endpoint Backup

$
0
0

In the previous post we ran quickly through the requirements and architecture of Veeam Endpoint Backup. Now we are going to look on how to start with the product.

I’m not going to run over the installation, which is very easy to do, however, during the installation you need to make a few decisions.

After the installation, the wizard will ask you if you want to configure your backup with the default settings. In order to do so, you need to have a USB drive that is at least half of the selected source (entire PC) in size. For many users, the default settings will be perfect and they can proceed with doing so.

The default options are:

  • Backup scope: entire computer
  • Target Destination: USB device attached to the computer
  • Schedule: 12:30 AM nightly
  • Default exclusions: temporary files folder, Recycle Bin, Microsoft Windows pagefile, hibernate file and VSS snapshot files from the System Volume Information folder

You can easily accept the defaults and change them afterwards as we will see later on. You will also get a question whether you want to change the power settings (depending if it is not yet active in your current power plan). This will allow the computer to wake up from sleep to take the daily backup, and as you will see in other demo recordings put it back to sleep afterwards to save energy.

After that, or when you skipped it you can create the bootable recovery media. This is also one of these tasks that you can skip but I highly advice you to do it immediately during installation or short after. You will need the recovery media when you want to do a bare metal recovery or when you want to restore an active volume.

You can use different devices to create the bootable recovery media such as DVDs, USB flash drives, SD cards or simply save it as an ISO and burn it with another 3rd party tool that you prefer to use.

My advice is to build this recovery media as soon as possible on a USB flash drive or media of your choice and then store it away somewhere safely. Normally, during the lifetime of your endpoint it is not necessary to update it unless you change network or wireless cards and / or storage device.

Recovery media in depth

Let’s have a better look at a few options you have when you create the recovery media. The first window in the window will ask you to specify the media as already explained above. As long as that media is attached to your computer, it will be detected and even if you attach it afterwards, the wizard will detect this and auto-update the possibilities to choose from. One note here, whatever media you are using note that it will be erased completely and formatted as a boot media.
The first window in the window will ask you to specify the media

Very important on this screen is the Include hardware drivers from this computer checkbox. This will make sure that all the specific network, storage and USB drivers are included on the media so that specific hardware will be loaded when booting from the recovery media

The other checkbox (Include the following storage and network hardware drivers) allows you to add additional drivers to the media. This certainly is handy as a system administrator that has different computers to manage. Instead of creating lots of different recovery media, he or she now can create only a couple and add specific drivers to the media for the different hardware configurations that he or she manages. The folder that you select here must contain all files of the driver package (files in CAT, INF and SYS formats)

The next step will depend on whether you have chosen to save it as an ISO or to write it on some removable media. In the case of an ISO, you will need to define the path (including the possibility to type in a username and password when needed to reach a specific path).

After that review your chosen options and let the recovery media be built.
let the recovery media be built

Conclusion

Getting started with Veeam Endpoint Backup is very simple to do. Accepting the defaults, which will be perfect for many users. Don’t forget to create the recovery media so you can boot your computer when necessary.

Integration with EMC Storage Snapshots coming in Veeam Availability Suite v9

$
0
0

The question that has been on everyone’s mind is: “Which array will Veeam integrate with next?” Well, we are happy to announce that Veeam Availability Suite v9 will integrate with EMC storage.

This is a big deal, as this announcement really includes two different array families and scores of configuration possibilities. Both the EMC VNX and EMC VNXe families of arrays are supported. This integration is also powerful as it includes both the Veeam Explorer for Storage Snapshots recovery technique and Backup from Storage snapshots.

Leveraging storage snapshots is the natural choice to deliver Availability for the Modern Data Center as we can take backups from storage snapshots up to 20x faster than the competition. Couple that with the restore capabilities of Veeam Explorer for Storage Snapshots (which is included in Veeam Backup Free Edition by the way!) and your data center is ready for anything.

The news today is important but it is also just as important to outline the process of how we got here. Every now and then, we’ll do polls in the Veeam Forums. If you ever see a poll in the forum asking “what do you use for primary storage?” or more recently “what version of vSphere do you plan to use by the end of this year?” are good indicators of what’s next. The forums and in particular these polls go directly to the product management team and they review the direct feedback from our customer base. This insight is critical to our forward decisions. There are more factors in the decision however. In fact, we frequently have to answer questions about who is the next array to be supported with Veeam Availability Suite. I like to say that there are three guiding principles to the process:

  1. There must be a good snapshot engine on the array. Quite simply, we don’t want to build great availability features around an inferior snapshot engine.
  2. There must be large market share. We want to provide solutions for the market and have it be used, it doesn’t make sense to build awesome technology that few would use.
  3. We need close cooperation from the storage vendor. It’s a business endeavor and Veeam commits resources to developing the storage plug-ins for integration with storage; and we’ll need their engagement to promote this great technology.

With all of that being said, let’s review how this awesome technology works with EMC storage. Let’s look first at Veeam Explorer for Storage Snapshots. I love this feature for a number of reasons, including the fact that it is included with Veeam Backup Free Edition. This integration will allow Veeam Backup & Replication to read the storage snapshots of the VNX and VNXe arrays. This can be the snapshots set up via a schedule on the storage array or within the Veeam Backup & Replication interface. Once you have a storage snapshot, you can browse those snapshots and launch these powerful restore options:

blog-5-xx-2015-vess-jpg

Leveraging the storage snapshots for restores are indeed handy and help deliver the best recovery time objectives. It’s still recommended to have a proper backup on different storage however. That’s where Backup from Storage Snapshots comes into play.

Backup from Storage Snapshots truly allows you to take backups at any time of day, even on the busiest VMs. The first step with Backup from Storage Snapshots is to prepare the VM for the backup with application-aware image processing and take a VMware snapshot on the VM. An underlying storage volume snapshot is then taken and the VMware snapshot is immediately released. This is where it gets interesting, as (unlike the competition) the Veeam backup proxy will read the data directly from the storage snapshot. There is no need to mount the storage volume snapshot to an ESXi host and register it as a datastore first before the backup. The best part is that with our patent-pending approach, we are still able to leverage VMware changed block tracking (CBT) information; which keeps incremental backups incredibly fast. Finally, once the backup is done the storage snapshot is removed. The figure below shows the steps involved with Backup from Storage Snapshots:

blog-5-xx-2015-bfss

Integration with EMC storage will be a big hit to our joint customers, partners and prospects. Veeam Availability Suite v9 is coming soon in Q3 this year (that’s right from Gostev!). I’d expect that like previous major releases we’ll have betas so you can test drive this incredible new functionality yourself. The Veeam Forums weekly digest will be the place to see that when the time is right, but until then you can sign up to be the first to know when v9 is available.

Here are some links for more information on this exciting upcoming new feature and more about Veeam Availability Suite v9:

Veeam Availability Suite v9 page

Upcoming webinar on Veeam integrating with EMC Storage

More information on Backup from Storage Snapshots [currently written to v8 supported arrays]

More information on Veeam Explorer for Storage Snapshots [currently written to v8 supported arrays]

Backup modes in depth

$
0
0

In this series we already talked about the architecture of the Veeam Endpoint Backup FREE solution and how you can get started with the solution. We explained the service running, the components that are needed and after installation how easy it is to get started with the default settings. As I said in that post for many end-users, the default options will be perfect, but for others they want to make changes to what they protect (scope), the target destination and the schedule. Target destination and Schedules are for the next post, and today we are going to concentrate ourselves at the different backup modes and how they work.

Laptop and PC backup with Veeam Endpoint Backup modes

There are three backup modes you can choose from if you look in the wizard, but actually, when selecting the last option, there is a fourth possibility called Hybrid Backup.

Entire computer

Entire computer backup is exactly what it says. A backup of your entire computer, including hidden system and recovery partitions.

We recommend using this mode as it will allow you to do a full Bare Metal Recovery, volume level restore of your choice and file or folder level restores all from the single backup. Since we are using block-level incremental backups after the first, initial full backup, it is also very efficient.

Speaking of efficiency, this mode (and the volume level backup mode) also excludes certain files that are not necessary to be in the backup such as temporary files folder, Recycle Bin, Microsoft Windows pagefile, hibernate file and VSS snapshot files from the System Volume Information folder. This will make your total backup smaller.

Volume level backup

Volume level backup is the same as entire computer backup, but with the difference that you choose the specific volumes yourself. If you choose to protect your system volume (e.g.: C:\ or the volume on which Microsoft Windows is installed) then it will automatically include the hidden partitions also and the system state data backup. Of course, you can modify the list of the volumes to backup and exclude unwanted system volumes of your laptop or PC, but be advised that it may affect your further Bare Metal Recovery process and may prevent you from restoring or booting the operating system.

Volume Level Backup of laptops and PCs

As with the entire computer backup mode, you still can perform Bare Metal Recovery and volume level recovery but only for the volume that was previously selected for backup File level recovery for this type of backup is also supported.

File level backup

You can also choose the file-level backup mode. In this mode Veeam Endpoint Backup FREE will capture only the selected folders from your laptop or PC. You can exclude explicit files and extensions (or even explicitly include them).

Of course, running this backup mode means Bare Metal Recovery or volume level recoveries are no longer supported.

Laptop and PC file level backup

As you can see, there are a few options for you. We will dive deeper into this screen when we talk about exclusions, but it’s important to understand that you can create a hybrid backup under the file level backup step. It means you can select a specific volume (for example OS volume) and then add additional folders with personal data from another volume.

Conclusion

There are different modes that you can select when configuring your laptop or PC backup depending on your needs. We always recommend choosing the entire computer backup mode as it will give you the most restore options. But if you only want to protect certain volumes or maybe only specific user data we have you covered also.

How to start with VMware VM replication using Veeam Availability Suite

$
0
0

How can you explain the difference between a backup and a replica? I know that even with lots of available information, some confusion still comes up. Let's remove the misconceptions and discuss the VMware vSphere VM replication process with Veeam.

What is replication?

Replicating a VMware virtual machine means creating a “twin” of the production virtual machine on a remote site in a ready-to-use state. Native VMDK file is stored uncompressed together with the VMX configuration file already registered in the target vSphere environment, so you can immediately power on the required VM on demand. Whenever you have problems, and whatever those problems you might have with your production application, you can always start its replica in just a few seconds from another location. In comparison with backup, replication shows faster recoverability and very quick recovery time objectives (RPOs) because instead of restoring data from the backup and registering the VM, you simply need to power-on a spare clone of a failed VM. Additionally, replicated VMs are flexible in handling since they can be used on the same site to accommodate a SAN failure or even off-site to accommodate a site-wide outage.

2-in-1: backup and replication

Veeam Backup & Replication (a part of Veeam Availability Suite) performs both backup and replication for VMware and Hyper-V, so you get a 2-in-1 solution. It performs image-based replication with compression, deduplication and changed block tracking (CBT) technologies, which reduce traffic and speed up data transfer. With Veeam Backup & Replication, you can replicate faster while reducing bandwidth consumption with Built-in WAN Acceleration, replicate from backup files, use Failover Plans with 1-click site failover and facilitate your data center migrations employing Veeam's Planned Failover feature.

Replication with Veeam may also serve as a “life hack” for a seamless VM migration and upgrade across clusters. Veeam supports VMware vSphere 4.x and higher, including the latest 6.0 release (get Update 2 for Veeam Backup & Replication v8 if you missed it somehow). Using replication you can, for instance, upgrade vSphere 5.1 to vSphere 6.0 and safely migrate your virtual machines from the ESXi 5.1 to the ESXi 6.0 host. The hidden benefit of doing a replication failover to the vSphere 6.0 environment is that you still have the older virtual machines in place in case the upgrade doesn't go as you expect.

How does Veeam's replication for VMware VMs work?

In many ways, the mechanism of Veeam's replication is similar to forward incremental backup. During the first job run, Veeam Backup & Replication creates a full virtual machine copy and then catches only the VM changes during subsequent job runs. Each replica has a number of restore points (like backup increments) which work as restore points for failover. You can configure up to 28 replica failover points with a Veeam replication job. Replication traffic floats block-by-block through a data pipe organized between the source and target hosts by means of Veeam's transport services.

How to validate replicas?

I'm sure you know what the SureBackup feature is. SureReplica technology does the same for replicas. Veeam Backup & Replication allows you to check every created VMware replica for recoverability without any manual work from you and right after your VM replica restore points are ready. When performing a SureReplica job, Veeam Backup & Replication validates replicated data for consistency, checks its configuration accuracy and tests replica for complete reliability by running it to the required restore point in an isolated virtual lab.

In fact, SureReplica works very similar to SureBackup. Via the same GUI in Veeam Backup & Replication, you create a Virtual Lab, an Application Group and configure a familiar SureBackup job, but you add a VMware VM replica instead of a backup.Application group defines virtual machines running production applications which other virtual machines are dependent on.

Licensing tips and tricks

Finally, I would like to discuss Veeam Backup & Replication licensing and dismiss one of the most common misconceptions. Do you need a Veeam license for your DR site and ESXi hosts to perform remote VMware replication? The answer is NO. You don't need to license your DR hosts. Veeam has a straightforward per-socket-licensing model and you only need to install licenses on your source-side vSphere hosts. The only exception where you will need the Veeam Backup & Replication licenses for both the production and DR sites here is when your target host is running VMs that you are also backing up or replicating.

 

Now you see how easy you can start replicating your critical VMs with Veeam. In my next post, I'm going to dive a bit deeper and focus on ways of optimizing replication traffic. Stay tuned to Veeam! And if you are interested in any particular use case or some tips and tricks, please leave your feedback and ideas here, and I'll cover the topic in my next posts.

Helpful resources on the topic:

Simplified backup & recovery for MSPs with Veeam Endpoint Backup for LabTech

$
0
0

* Disclaimer: many of the screenshots are not final yet and are subject to change before GA

Not long ago we launched Veeam® Endpoint Backup™ FREE to the market. The response so far has been massive and has exceeded our most optimistic expectations. Downloads are going strong (over 35.000 now) and the amount of feedback we are receiving is and remains incredible. We also still keep receiving feature requests and while I can’t promise you anything, we do consider all the feedback, feature requests, stories and more we are receiving on our forums very carefully. Keep them coming and thank you for all of them!

As a result of that feedback and requests, one of the most requested features is centralized management. Today, I am very pleased to introduce to you Veeam Endpoint Backup for LabTech, which will be released in a couple of months.

Veeam Endpoint Backup for LabTech (comprised of both Veeam Endpoint Backup and the Veeam Endpoint Backup Plug-in for LabTech) is a solution specifically designed for service providers using the very well-known LabTech remote monitoring and management (RMM) platform.

Through the LabTech Control Center console, service providers will have the ability to back up, recover and manage customers’ endpoint devices (and even some of those last remaining physical servers) from a single pane of glass.

Veeam Endpoint Backup for Labtech - Control panel

The solution

For the customer, the functionality remains the same as it is today with Veeam Endpoint Backup FREE, but this new solution adds remote management and monitoring capabilities for service providers as well. Customers will still have all the power, features and recovery possibilities that exist today, but the difference comes in the way the solution is managed. Veeam Endpoint Backup for LabTech brings remote deployment, remote configuration of backup jobs, monitoring and centralized management into the service provider’s hands. Let’s take a closer look now.

System dashboard

A purpose-built system dashboard specifically for the Veeam Endpoint Backup for LabTech gives you detailed information about licensing and managed clients—per client and location.

Labtech Endpoint system dashboard

Remote deployment

LabTech makes deployment of Veeam Endpoint Backup a breeze. Service providers will be able to silently deploy Veeam Endpoint Backup to each client's endpoint that has a LabTech agent installed.

Remote deployment of Veeam Endpoint for Labtech

Of course, if the client already has Veeam Endpoint Backup installed, you can use our default search query to discover those machines, and add them as a managed node in the LabTech console.

Configuration and monitoring

After a computer has Veeam Endpoint Backup installed, you will be able to configure the backup remotely through the LabTech Computer Management screen. There’s no need to log in remotely —everything can be done through a custom-tailored and easy-to-use wizard straight from the Veeam Endpoint Backup jobs tab in the Computer Management screen. This can be done for an individual computer, or for multiple/all computers in a location.

Configuring Veeam Endpoint Backup for Labtech

From that same tab, you are also able to start and stop a backup job and download the logs for troubleshooting purposes when necessary.

The Veeam Endpoint Backup jobs tab also gives all the information about the backup jobs running on that computer. The number of restore points, backup size, average duration and more are visible in a single glance from this tab. By clicking on the number of restore points link, you will dive deeper into the information and receive information such as date, duration, size per restore point, destination and the status of the job.

Per location, you will also receive an additional tab that gives you an overview of the latest backup jobs and trends including RPO statistics, or the list of endpoints experiencing backup issues most commonly.

Veeam Endpoint Backup for Labtech Overview

Dataviews will give you more information on the endpoint alerts and the monitors that watch the Veeam Endpoint Backup service.

Veeam Endpoint dataviews

Reporting

Veeam Endpoint Backup for LabTech will also provide advanced reporting. These reports can be filtered on different criteria such as location, computer type, computer, group and client.

The service provider will be able to review reports on the backup job status of a single or multiple clients to easily see which endpoints are protected. Licensing reports are available also.

Veeam Endpoint Backup reports

Unique bare-metal recovery

One of the most difficult and costly tasks for a service provider around endpoints is bare-metal recovery. As of today, the only way to achieve this is to come to the client’s site, and run through the entire process on the actual endpoint. Veeam Endpoint Backup for LabTech offers the ability to provide remote bare-metal recovery, which eliminates the need for an on-site visit. This results in less time loss for the service provider and faster recovery for the customer. This unique capability only comes with Veeam Endpoint Backup for LabTech.

The only thing the customer’s staff needs to do is insert the Veeam bootable recovery media (such as a USB stick), and boot up the endpoint from it. Once the connection has been established, the service provider will be able to run the entire process remotely, with no further actions needed from the client. This powerful and unique capability will dramatically reduce your costs of doing business as a service provider, allowing to offer more competitive service pricing to your clients.

Conclusion

Veeam Endpoint Backup for LabTech provides centralized management for Veeam Endpoint Backup through the LabTech Control Center console, enabling service providers to deploy, monitor and manage customers’ endpoints remotely. With rich reporting capabilities and the remote bare-metal recovery option, service providers will be able to bring more value and faster recovery times to the table for their clients.

Combined with Veeam Backup & Replication™ and the Veeam Backup & Replication Plug-in for LabTech, service providers will now have the ability to use the most known and established solution to protect their customers’ virtual servers, endpoints, and even those last few remaining physical servers, offering the complete protection and availability.

For more information, watch the whiteboard session the 4th of June about this solution: http://www.veeam.com/veeamlive/managing-customers-backup-environment-veeam-labtech.html

Veeam Endpoint Backup FREE: Backup targets more explained

$
0
0

In this post we will go more in depth about the different scheduling and backup targets that you can use with Veeam Endpoint Backup FREE. In the previous post we talked about the different backup modes and now we continue in our backup wizard.

Backup Targets

Whenever we take a backup, we need to store it somewhere. Most people will have a specific preference for storing their backups and Veeam Endpoint Backup FREE supports a variety of options to meet your preferences or demands.

Veeam Endpoint Backup FREE - Backup Targets guide

Local drive

This option gives you the possibility to choose between local disks or removable devices such as USB drives or FireWire drives.

We do not advice storing the backup file on the internal hard drive - whenever that drive breaks, you are not only using your data itself, but also your backups and you basically have nothing left. Storing your backups on your internal hard drive also doesn’t allow you to do an entire computer backup or protect the entire volume that holds the backup files. But in the case you have multiple disks in your computer and, for example, you want to backup data from one disk to another – you are good to go with volume or file level backups

When you use USB removable devices as a backup target, you also have the option to rotate such devices. It means you can use different devices to make sure you always have a backup available somewhere. Please note that this will create a different backup chain on each device. The backup chain will be discussed in a later post. But for now, you need to know that it means you will have one full back up on each device, and all the others will be incremental ones.

Local drive backup targets of Veeam Endpoint Backup FREE

Shared Folder

Saving your backups to a shared folder is another option you have. This could be a shared folder on your company’s fileserver, a home NAS device or any other solution you use for sharing the data around internal network. If the folder requires access credentials (username and password) for the specified destination, check the box “This share requires access credentials” and type in the needed information.

Shared volume backup target of Veeam Endpoint Backup FREE

Please note: the Populate button can be used only after the security credentials were typed in (if needed)

Veeam Backup & Replication repository

If you have a Veeam Backup & Replication server in your infrastructure and you want to save your endpoint backups to the Veeam Backup and Replication repository, then this is your option of choice. It will enable a lot of additional functionality for the IT administrators to keep control of the backups of the endpoints. We will go deep into this functionality in another post. To configure this target, you need to specify the Veeam Backup & Replication server and potentially specify your personal credentials. The next step will be to choose the repository where the administrator gave you access to. Bear in mind, repository permissions are granted at the Veeam Backup and Replication console, but Default Backup Repository is enabled from start for evaluation purposes.

Using Veeam Backup & Replication repository with Veeam Endpoint Backup FREE

Note that you need at least Veeam Backup & Replication v8 with Update 2 to take advantage of this functionality.

Retention

One of the things you might have noticed on each screen is that there the possibility to decide on your retention. Restore points are not kept forever -they are removed according to the retention policy.

The retention policy in Veeam Endpoint Backup FREE might be a little bit different then what you are used to. When choosing your retention policy in X days, we don’t take calendar days in consideration, but the amount of days when there was at least 1 successful backup.

Let’s say your retention policy is 5 days… It means you can have 3 backups (let’s say Monday, Tuesday, and Wednesday) but because you didn’t work or any other reason your computer is off for Tuesday and Friday. Saturday you have a new backup and Sunday also. At that moment, you have 5 days of backups (although it are 7 calendar days.) When the next backup runs (let’s say on Monday again) the first recovery point will become obsolete.

Conclusion

Veeam Endpoint Backup FREE delivers different possible targets to store backup file in any location of your choice. It could be a local disks, removable devices, shared folder or Veeam Backup and Replication repository. The last option will also give you additional functionality that you can use for your endpoints.

How to optimize replication traffic with Veeam

$
0
0

Recently, I blogged about how easy it is to start VMware VM replication with Veeam so you can achieve the best possible recovery time and recovery point objectives (RTPOs). Today, I want to explain how you can overcome the challenge of a heavy replication load on your network. With the assumption that your available bandwidth is limited, I'd also like to share some ways that Veeam Backup & Replication v8 can reduce replication traffic over the WAN.

Replicate onsite or offsite?

Your business goals will dictate the vSphere replication scenario that you'll need. Onsite replication is a high-availability scenario with replicas stored on the same site. An offsite scenario protects your critical data from any problems at the production site by keeping data copies on the remote site. Technically, the site depends on the location of your source and target hosts. For onsite replication, both your source and target ESXi hosts should be in the same site and connected over the LAN. For offsite replication, one or more target ESXi hosts are deployed off-premises where they are connected to the production source host via the WAN.

How much bandwidth for replication do you need?

The remote replication cycle for a VMware VM will take longer than the backup copy process for the very same VM. This additional overhead comes partly from using VMware data protection APIs (Application Program Interfaces) for creating vSphere replicated VMs. Replication over the WAN (or slow LAN) may take hours, even when transferring increments only (imagine a huge Exchange server with several gigabytes of daily changes).

You might be asking how much bandwidth is enough for your replication of vSphere VMs. The bandwidth amount depends on multiple factors, including the number of VMs, amount of data, the latency and the available window you need to fit. Below is the basic rule for estimating required connection speed:

Required WAN/LAN, MBs = ([Amount of total daily changes, MB/replication window, hours]/3600) x 8

Please note that this value will actually be too high because it doesn't consider that Veeam Backup & Replication makes the process faster through the use of a number of traffic-optimization options. This will amount to an overall time savings gained by increment-only processing.

Utilizing backup as a source

Replicas do not and cannot substitute for backups. Replicas are just another way to protect your critical data and get the best possible SLAs if there is a major failure. To maximize protection for tier-1 applications, you should employ both options. Once you already have a VM backup with a chain of increments, why not use it as a source for a remote replica and remove the replication load from production? This is one of the replication enhancements in the latest Veeam Backup & Replication v8.

When creating a remote replica from backup, we like to say: It Just Works! As always with Veeam, this process is automatic. There are no special jobs for the task, except for a regular replication job. The only trick here is that you must specify a backup repository with the required VM backups as a source of data, instead of specifying your live production VM. Veeam Backup & Replication will retrieve all of the data from the backup repository using the latest restore point from the backup chain to build a new replica-restore point, and then offload the replication traffic from your production workloads. This saves a lot of read I/O (including the snapshot process from vStorage APIs for Data Protection (VADP)) on the running virtual machine as well, especially as it usually takes longer to move data for replicated VMs off-site.

Backup as a source

Reducing replication traffic with replica seeding

Replica seeding can help you reduce the initial replication-data flow. Its underlying mechanism is much similar to a remote replica from backup because it also uses VM backup as a replica seed. Replica seeding, however, uses the backup file only during the first run of a replication job. To further build VM-replica-restore points, the replication job addresses the production environment and reads VM data from the source storage.

You need to prepare the seeding backup of the VMware VM by replicating and copying it to your target host. Because the backup copy supports WAN acceleration with global deduplication, data-block verification and traffic compression, the performance speed will be fast! When executing replica seeding, Veeam Backup & Replication will synchronize the restored data states from backup and production VMs and replicate only the changed data.
Replica seeding

Optimizing replication traffic with replica mapping

Another way to optimize bandwidth usage is replica mapping, which is when you map a production VM to its existing alternate at the DR (disaster recovery) site. This can come in handy if you need to reconfigure or recreate replication jobs when, for instance, you have relocated an existing replica to a new host or storage. If you are using a shared WAN/LAN connection, I recommend you apply network-throttling rules to prevent replication jobs from consuming the entire bandwidth available in your VMware environment.Replcia mapping

Solving possible configuration issues

Replicating VMware VMs between subnets with different network settings can lead to some configuration problems. Veeam Backup & Replication, by default, maintains the network configuration of both the original VM and its replica. DR and production networks may not necessarily match, but that's not a problem. Just set your custom rules for network mapping. Another great Veeam Backup & Replication reconfiguration feature is the ability to assign an IP-processing scheme for Windows-based, replicated VMs.

Replica Re-IP

I welcome your comments on this blogpost. You're also invited to share the traffic optimization results you achieve using Veeam Backup & Replication for VMware replication.

Follow this Veeam blog for more updates. My next post will focus on more hot topics, including performing replica failover and failback with Veeam!

Additional helpful resources:


NEW Veeam Cloud Connect Replication coming in v9

$
0
0

Last year, Veeam released Veeam Cloud Connect, a new technology that allows the easy creation and consumption of offsite backup repositories. It was the first solution specifically designed around Service Providers, both from a technical and business point of view. Its extreme ease of use and capabilities made it an instant success, and as of today several hundreds of service providers are offering offsite backup services based on Cloud Connect.

As a first generation technology, everyone was expecting additional capabilities in the following versions, and the most common request has always been “are you going to add replication capabilities?”.

As you can guess from the title of this post, that’s exactly what is coming in the next version!

Veeam Availability Suite v9 will bring Veeam Cloud Connect Replication, a fast, secure cloud-based disaster recovery (DR) solution. DR is a great solution to increase the availability of modern datacenter, and does so by leveraging replication technologies and creating an off-site replica of virtual machines. When end users want to design and create a DR site, they are facing a problem: the capital expenses of building and maintaining the secondary site. In a second location, owned or rented, they need to deploy new hardware and software according to the size of their production environments, configure it and even manage it, virtually doubling their IT infrastructure efforts. Also, because production workloads are running for the most part within the primary site, the secondary one is rarely used, thus its cost it’s even higher when compared to its value.

This is the situation where a cloud-based solution fits perfectly. By renting resources from a service provider on a pay-as-you-go model, end users have the same final result (CPU, ram, storage and networking resources available for failover operations) without any capital costs and the burden of designing and deploying the DR site.

Furthermore, VM replication through Veeam Cloud Connect is easy-to-use and simple to set-up, thanks to a simple single port connectivity via a secure, reliable SSL/TLS connection to a service provider. So, there’s no need to set up and maintain VPN connections, or open multiple ports in your customer firewalls. Yes, you heard this right: we encapsulate ALL traffic – replication management traffic, actual VM data transfers and even inter-VM communication during partial failovers – into the single port.

The end user, upon subscribing to the service and connecting to a service provider, will see a virtual cloud host, a multi-tenant view of the assigned DR site resources with CPU, RAM, storage and networking resource allocation. Basically, a cloud host serves as the replication target for the replication jobs set up by the end user.

blog-1

Failover will have multiple options. Full site failover will be obviously available, but we worked to add additional innovation: partial site failover. With that, end users will be able to failover to the DR site just a part of their workloads, while other VMs will still be running in the production site. This advanced capability will be available thanks to built-in network extension appliances, that will simplify networking complexity and preserve communication between running VMs regardless of physical location. So unlike other solutions, Veeam Cloud Connect Replication will not only manage data replication, but also the network connections between the two sites.

The Service Provider View

Disaster recovery-as-a-service (DRaaS) is no doubt one of the most requested services by end users. With Veeam Cloud Connect Replication, service providers will have a complete solution to quickly create and deliver DRaaS services for VMware vSphere and Microsoft Hyper-V environments.

blog-2

The software, thanks to its native multi-tenancy capabilities, will allow a complete isolation of end users hosted on the same hardware, as well as built-in network connectivity management for all failover types – all without the need to license, learn and maintain any additional 3rd party software.

A Complete Service

A great technology is not enough to offer a great service. To create an easy to use and quickly consumable service, especially for something powerful (and complex in the background) like DR, it takes more than just the robust replication and networking technologies. There are a few more essentials pieces, all of which are provided by Veeam Cloud Connect.

First, ease of use: once end users register a service provider, they will see the new virtual host added to their B&R. Replicating VMs to the service provider’s infrastructure is as easy as setting up a familiar replication job pointing to this cloud host as the target. And since there is no difference in setting up a replication job, the existing Veeam users do not have to learn anything new!

Second, the removal of the biggest pain point of any DR service: networking. The Network Extension appliances preserve communications with and between running replica VMs during full and partial failovers regardless of their location – and even without having to make any changes to replica TCP/IP settings before, during or after failover. You may wonder how is this even possible? Indeed, any sufficiently advanced technology is indistinguishable from magic, as Arthur C. Clarke once said.

Third, bandwidth-friendliness. Seeding, compression, replication from backup, Built-in WAN Acceleration are all provided as a part of Cloud Connect Replication to allow customers with slow or unreliable WAN connections, or large amounts of data, to protect their workloads with RPOs that was never before possible with their available bandwidth.

Finally, self-service. This is critical to any cloud service, and Veeam Cloud Connect is not an exception. This is why we will offer a web portal, running at the service provider and accessible to the end user from any device and from any location. Using this portal, the end user will be able to login and start any failover plan on their own, without requiring any intervention from the service provider.

This exciting new technology will be available in Veeam Availability Suite v9, coming in Q3 this year. I can’t wait to be able to talk more about it and show it; meanwhile you can sign up to be the first to know when v9 is available.

If you want to learn more, register now for our upcoming webinars:

Webinar for end users
Webinar for service providers

Scheduling backups with Veeam Endpoint Backup FREE

$
0
0

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.

Luckily Veeam Endpoint Backup FREE foresees in very flexible schedule options. Let’s have a look at them in depth.

Backup Schedule with Veeam Endpoint Backup FREE

Periodically

The first option you can choose from is a daily backup. For example, every day at 02.00 am in the morning when you are (normally) sleeping. While this is a great possibility because you can perform your backups when you are not working, your computer won’t be always available at that time. Energy-saving is important these days so you don’t want to let your computer run at night for a backup alone. Veeam Endpoint Backup FREE foresees in some great functionality that allows you to wake up your computer for a backup and hibernate or shutdown afterwards. Please NOTE that the wake-up functionality does not work when you are using the connected standby power model, which is mainly used for tablets.

On event

The second possibility (actually possibilities) you have is to trigger the backup on a specific event. This means you won’t be starting the backup on a time schedule. Again we provide you with some very powerful possibilities. You can start the backup on the following events:

  • Lock
  • Log off
  • When backup target is connected.

At lock and log off speak for itself. Whenever you lock your endpoint, or whenever you log off from your endpoint, the backup will start. The option to start the backup whenever the backup target is connected is a bit different but can be very powerful. Whenever you are protecting your endpoint to a removable drive, share or anything else, there is a possibility that the backup target isn’t always connected. This event will be triggered whenever that backup target gets connected to the endpoint.

This will work whenever you connect a USB device and remote storage but also whenever you connect to a network where your backup target is reachable.

For people that aren’t always connected to their backup target, this is extremely handy. For example, when you are disconnected from the network share that you use as a backup target (because of travel or any other reason) the system will automatically start the backup whenever it has access to that target again.

And there is another fantastic option available. Because you probably lock your computer a few times a day, or you connect your backup storage a couple of times, we have the option to block the backup as long as the previous one was performed less than X hours (or X minutes, days). This means that you can lock your computer multiple times a day, it won’t start a new backup every time unless the latest valid backup is older than X hours.

Combine the scheduling

What if you are able to combine the scheduling? Wouldn’t that be extremely flexible? Yes it is, and that is exactly what you can do with Veeam Endpoint Backup FREE. As I already stated it is sometimes very difficult to schedule the backup for an endpoint device depending on the behavior of the user. Road warriors such as myself aren’t always connected and switch time zones very often. Backing up on a daily basis at a fixed hour works when I am at my office, but on the road not so much. Also my backup target isn’t always connected (difficult to attach my USB device on a plane, when I am in an airport or for whatever other reason…). By using a combination of event triggers and a daily schedule, and by making sure that there is no new backup every 12 hours, I have a powerful schedule and I know that my data is protected on regular base, even when I don’t think about it because I am busy with many other things

Conclusion

Scheduling isn’t always the easiest task when you are dealing with devices that aren’t always connected or even running. Therefore Veeam Endpoint Backup FREE foresees in different methods based on triggers or a time schedule to meet your needs. Combining different scheduling events, you got a lot of possibilities to make sure that your endpoint data is protected as much as possible and available whenever it is necessary.

Veeam Customer Satisfaction Survey 2015 results

$
0
0

Each year, Veeam has a Customer Satisfaction Survey to gage the satisfaction levels and get the opinion of customers about Veeam products. We also identify strengths and weaknesses in the services we provide with this survey. Our most recent survey was administered from January 2015 to February 2015. I’d like to share some key results and meaningful metrics here.

Demographics of the survey

We collected 1,100+ responses from active Veeam customers from all over the world. The geographic areas of respondents include:

Survey demographics

49% from Europe, 32% from North America,  9% from Asia, 7% from emerging markets and 2% from Latin America

Respondents held a number of roles, including 63%, who were IT managers or IT administrators.

Respondents worked at companies with a wide range of revenues, including:

Diagrams_v3-02

84% at SMBs, 4% at mid-market companies and 11% at enterprise businesses

Veeam’s 2014-2015 Net Promoter Score

How likely is it that you would recommend Veeam to a friend or colleague?

This question reflected customers’ loyalty and willingness to recommend Veeam’s products to others. The index, which represents overall customer’s satisfaction, is called the Net Promoter Score (NPS) and usually ranges from -100 to 100.

For the last several years, we’ve observed a declining trend on average NPS for the IT industry, from 33.6 in 2012, to 23.1 in 2014. At the same time, this latest survey shows that Veeam’s index grew by 15 points compared to 2014:
Diagrams_v3-04

When evaluating Veeam’s NPS for 2015, 69.9% of respondents gave Veeam 9 or 10 points out of 10, which was a clear measure of Veeam’s high performance though our customers’ eyes.

Top 5 most important features and functionality

We asked our customers to list their top features in Veeam Backup & Replication™. According to the received data, there was a shift in customer priorities between 2014 and 2015. While Agentless Application-Aware Processing was selected as the most important feature at 41% in 2014, this year, Instant File-Level Recovery and Support for VMware vSphere and Microsoft Hyper-V shared first place and second place at 24% and 23%, respectively.

Below is the list of top five most important features & functionality in Veeam Backup & Replication in 2015.
Diagrams_v3-03-1

Infographics

The number of companies that switched to Veeam in 12 months has reached whopping 50,000. Five years ago, we could only dream about this number! This Veeam infographics helps to understand the meteoric rise of customer satisfaction rates.

veeam_customer_satisfaction_infographics_final

I also want share some great quotes from our survey report, which I personally found to be the most interesting:

  • “Veeam is a great product that makes it fun to be a sys admin!”
  • “As an IT professional for the last 15 years, I've had the opportunity to work with many a backup solution.  Hands down, Veeam Backup & Replication is the one solution that actually delivers what is promised. It Just Works!”
  • “Veeam is the only decently functional backup solution I can afford, lucky for me it's brilliant.”

What are the top features in Veeam’s products to you? Which do you find the most important? Leave your comments below or contact us on Twitter at @Veeam.

Embed this infographic on your site:

Have a look at the current Veeam Availability Suite promo:
Get Veeam Availability Suite for the price of Veeam Backup & Replication
Veeam Essentials for VMware and Hyper-V

Veeam Endpoint Backup administration: Integration with Veeam Backup & Replication

$
0
0

Read the full series:

Chapter 1 - Veeam Endpoint Backup Free Architecture & Requirements
Chapter 2 - Getting started with Veeam Endpoint Backup Free: Creating recovery media
Chapter 3 - Backup modes in depth
Chapter 4 - Backup targets more explained
Chapter 5 - Scheduling backups with Veeam Endpoint Backup FREE
Chapter 6 - Integration with Veeam Backup & Replication: Administration

 

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.

Prepare the backup repository

Before configuring Veeam Endpoint Backup job to use a repository as backup target you need to take care of repository access permissions. I bet you don’t want your production backup repository to run out of space because of uncontrolled end- user’s backups, so we got you covered.

You can delegate access to specific users, groups or even computer accounts. The procedure itself is very easy and well described here: http://helpcenter.veeam.com/endpoint/10/integrate_permissions.html

Important note - default backup repository will have ‘allow everyone’ access permissions from scratch for testing purposes and quick demo setup but we strongly advice to remove these permissions in production environments. Another note is that you can’t use a cloud repository as a target, but we will come back to that later.

Configure the endpoint’s job

We have already discussed the endpoint’s backup job configuration in my previous posts, so the only thing you need to do now is to select the Veeam Backup & Replication repository destination, type in the IP address or DNS name of the Veeam Backup & Replication server and enter the repository access credentials.

Note if you leave ‘specify your personal credentials’ checkbox unchecked, Veeam Endpoint Backup will use the computer account (NT AUTHORITY\SYSTEM) while authenticating to the repository

If all was set correctly you will be able to choose the repository and the retention range as previously explained.

Configure Endpoint Backup Job

Data protection tasks

After you have run a backup it is stored in a Veeam repository and Veeam Backup & Replication recognizes a new backup type – Endpoint backup.

Endpoint02

Under the backups node, you will view the different backups, the creation time and the amount of restore points.

EndPoint01

These views will give you a clear overview of all the protected endpoints, on which repository they are stored and the amount of restore points you have for each of them.

What’s next?

To start with, you are now able to use well known backup copy job. It gives you the possibility to move backup files to a secondary repository which might be located at the different site, and yes WAN accelerator will support endpoint backups. It also allows you to copy those backups to a cloud repository with your service provider

There is a small difference while using the restore functionality from copied endpoint files since user access permissions are not preserved during backup copy job. It means users won’t be able to restore their data from the secondary location, unless you tune the access permissions or simply use administrative account which always has access to all the backup files.

Archiving to tape is also supported: by creating a backup to tape job you can store your endpoint backups on tape media in a traditional way.

Administration Tasks

Combining two products means you get more functionality at the administration side. It becomes possible for an administrator to view statistics about Endpoint backups and gain more insight in what is happening on the different endpoints.

Endpoint Backup properties

You can easily disable an endpoint backup job from the Veeam Backup & Replication console if needed.

Removing or deleting endpoint jobs might be tricky: if endpoint job gets deleted from a console, the next time endpoint starts a backup – job will appear in the list again. Deletion simply removes the records about the job from the console, the backup, however, remains untouched and can be used afterwards for recovery. If you want to disable all the endpoints completely - using repository permissions might be a better idea.

Don’t forget that Veeam Backup and Replication’s global notification and network throttling settings apply to endpoint backup jobs.

Endpoint Backup notification

Conclusion

Integrating Veeam Endpoint Backup FREE with Veeam Backup & Replication is more than just the possibility of using your repositories as a backup target. With the integration, you receive a ton of additional possibilities such as backup copy jobs, backup to tape and even backup copy job to a cloud repository. Additional administration tasks such as global email notifications, network throttling and the ability to remove / delete endpoint backups are also options you now have.

In my next blog, I will run over the additional recovery options that you receive when integration Veeam Endpoint Backup FREE with Veeam Backup & Replication.

 

Replicating VMware VMs with Veeam: Everything you need to know about replica failover

$
0
0

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.

Failing over to a VM replica

Replica failover is switching from a damaged or failed production VM to its replica on a remote location. Replicated VMs are stored in a fully functional, ready-to-use-state, so failing over requires just a few seconds to power on the VM. You don't need any additional configurations or apply extra settings, because replicas have exactly the same configuration as their source VMs. To initiate a failover, right-click the required VM replica and choose “Failover Now” to start the failover wizard.

Failover wizard

You can customize a retention period for replication and keep up to 28 restore points for every VMware VM replica. When failing over to a replica, Veeam Backup & Replication chooses the latest restore point by default. However, you can specify any earlier replica state you want to roll back. This might be helpful in case of a software malfunction that corrupted the latest replica restore point, which means you may need to fail over to the previous good restore point.

Deciding on the next step

After you commit failover, the VM replica takes the whole workload and replaces your corrupted production server. Its performance depends on the configuration of your DR site. If there's a lower performing storage or insufficient bandwidth, users may experience latency in their work with an application running on the VM replica. Because of this, failover in Veeam Backup & Replication is an intermediate stage, which you need to finalize. You can leave your workload on the DR site forever, if there are adequate resources, and substitute the initial VM by performing a permanent failover. In this case, Veeam will remove all corresponding restore points (VM snapshots by nature) and exclude the original VM from the replication job, so that no changes continue to affect your new production VM born from the replica.

Permanent failover

If your DR site doesn't have enough resources and permanent failover is not an option, you can get back from running a replica to the original VM. When the issues on your main site are resolved, perform a failback operation. Veeam Backup & Replication automatically synchronizes both replica and original VMs for changes and allows you either to fail back to the original VM location or chose a new destination. The amount of data transferred during failback is intelligent in the way that it only transfers what has changed since the failover event. This can be a big time-saver!

Failback wizard

Working with interdependent applications

The majority of critical virtualized applications are interoperating with other services in your environment. For example, Microsoft Exchange, Active Directory and SQL can be interdependent with a domain controller, DNS and DHCP servers. The availability of interdependent applications is contingent upon maintaining these correlations. In case of a major failure, you need to restore the entire group of these servers and boot each sequentially in order to ensure their proper performance.

Veeam Backup & Replication v8 lets you create predetermined failover plans for a group of replicated VMs, which you need to boot simultaneously or in a specific order. In case of an emergency, you just need to initiate a saved failover plan in one click. You even can do it remotely from your tablet through the Veeam's web UI, which is available with the Veeam Backup Enterprise Manager component installed.

Failover plans support running pre-failover and post-failover scripts. In the most common scenarios, scripts can help you stop or suspend an application, after its failover and before booting another application from the same failover plan. For example, when you are booting a Domain Controller (DC), the script can stop the next application in a queue, so you can first get a heartbeat from the running DC. You can use BAT, CMD and EXE files as pre-failover and post-failover scripts for your failover plans.

Technically, failing over to application replicas grouped into failover plans runs the same way as a regular failover process: you roll back to the latest valid restore point and, on failover completion, you will need to finalize the process either with permanent failover, or with a failback procedure.

Failover plan

Failover plan

Using a VM replica for data center migration and planned maintenance

You never know when your hardware, host or VM will go down, but you are always aware of planned downtimes, like data center maintenance. Veeam Backup & Replication supports planned failover scenarios that help you run your migration or maintenance operations smoothly and with minimum impact on users' work. Planned failover moves the workload from the production VMs to the DR site via replicas before switching off production VMs without any data loss.

How does it work? You replicate the required production VMs to a new location as you normally do and run planned failover wizard when you're ready to start migration or maintenance. Unlike the regular failover during unexpected downtime, a planned failover synchronizes all changes from your source servers that occurred since the last replication jobs run to the replicas. Once you finish running the wizard, Veeam Backup & Replication will fail over to replicas and simultaneously turn off your source VMs.

Planned failover

Using a VM replica for testing purposes

Patches, upgrades and software fixes for critical applications potentially run the risk of system crashes, which is why you should always test every change before applying it in your production environment. Veeam's replication can help you with this, without any additional configurations or creating testing labs. Fail over to a replica and perform the required tests or apply patches on a running VM clone. Once you are done, you can safely undo failover and switch back to the production VM in its pre-failover state. All changes that occurred on the VM while it was in a failover state will be discarded and your production VM will be working in a normal mode again.

Undo failover

 

 

 

Additional helpful resources:

Viewing all 1388 articles
Browse latest View live