Tag Archives: Veeam

Quick Post – Veeam Backup for Office 365 v2 Important Patch plus Self Service Warning Fix

Last week we snuck out an important cumulative patch for Veeam Backup for Office 365 v2 bring the build number up to 2.0.0.567. The patch is actually fairly significant and I would recommend anyone running VBO to update as soon as possible. It covers Licensing, SharePoint and OneDrive, Group and Shared Mailbox fixes and enhancements as well as general server fixes.

To download and install the update, head to the VeeamKB here. There are some important notes about the upgrade process depending on your deployment configuration.

  • Execute VBO2.0-KB2765.msp as administrator on the Veeam Backup for Microsoft Office 365 server.
  • If there are any remote proxies in your environment please update those as described here 
  • If you use a remote VBO365 console and/or remote VBO365 PowerShell module installation, please contact technical support to assist you in upgrading those components.
Self Service Warning Fix:

Not related to the update, but something that I had happen to me on testing the upgraded VBO instance was that when I went to perform a Self Service through the Veeam Explorer for Exchange or Sharepoint I had the following pop up.

Once hitting ok, I didn’t have the ability to choose a Service Provider connection for the Self Service restore operation. This was the same for both Exchange the Sharepoint Explorer. Working with our support to ensure it wasn’t a regression in the latest patch we found an entry in the Explorer log files that pointed to the issue.

[28.09.2018 13:08:15] <37> Info [CloudCacheSync] Synchronizing provider 119.252.77.83

[28.09.2018 13:08:16] <37> Error Exception while connecting to endpoints [119.252.77.83]
[28.09.2018 13:08:16] <37> Error No connection could be made because the target machine actively refused it 119.252.77.83:6180 (System.Net.Sockets.SocketException)

[28.09.2018 13:08:17] <37> Error All cloud gateways are unavailable (Veeam.Backup.Core.CCloudGateSvc+CAllGatesUnavailableException)

[28.09.2018 13:08:17] <37> Error Credentials with id ‘a22f868a-a51a-473f-9f6d-cff9ff250fa3’ were not found (System.Exception)

Basically the issue was caused by the fact that I had an uncontactable Service Provider endpoint configured in the Backup & Replication Server. Once I removed the offending entry in the Service Provider section, I was able to reload the Explorers and have the ability to perform self service recoveries again. It’s probably something that won’t come up under normal tenant circumstances as I connect to multiple Service Providers from my NestedESXi Homelab instance…but something to take note of if the warning appears for you.

References:

https://www.veeam.com/kb2765

Quick Fix: Specified vCloud Director is not supported when trying to add vCD 9.1 to Veeam ONE

Back in May when VMware released vCloud Director 9.1 they also depreciated support for a number of older API versions:

End of Support for Older vCloud API Versions

  • vCloud Director 9.1 no longer supports vCloud API versions 1.5 and 5.1. These API versions were deprecated in a previous release.
  • vCloud Director 9.1 is the last release of vCloud Director to support any vCloud API versions earlier than 20.0. Those API versions are deprecated in this release and will not be supported in future releases.

Due to this, and being mid release cycle, Veeam ONE had issues connecting to vCD instances that where running version 9.1.

The error you would get if you tried to connect was:

Over the past few months i’ve had questions around this and if it was going to be fixed by way of a patch. While we are waiting for the next release of Veeam ONE that is due with Veeam Backup & Replication 9.5 Update 4 there is a way to get vCD 9.1 instances connected into the current build of Veeam ONE.

There is a HotFix available through Veeam Support to resolve the Known Issue. It involves stopping the Veeam ONE services, replacing a couple of DLL’s and then re-starting the services. Once implemented Veeam ONE is able to connect to vCD 9.1.

So if you have this problem, raise a support case, grab the HotFix and the issue will be sorted.

References:

https://docs.vmware.com/en/vCloud-Director/9.1/rn/rel_notes_vcloud_director_91.html#deprecated

Automated Configuration of Backup & Replication with PowerShel

As part of the Veeam Automation and Orchestration for vSphere project myself and Michael Cade worked on for VMworld 2018, we combined a number of seperate projects to showcase an end to end PowerShell script that called a number of individual modules. Split into three parts, we had a Chef/Terraform module that deployed a server with Veeam Backup & Replication installed. A Terraform module that deployed and configured an AWS VPC to host a Linux Repository with a Veeam PN Sitegateway. And finally a Powershell module that configured the Veeam server with a number of configuration items ready for first use.

The goal of the project was to release a PowerShell script that fully deployed and configured a Veeam platform on vSphere with backup repositories, vCenter server and default policy based jobs automatically configured and ready for use. This could then be adapted for customer installs, used on SDDC platforms such as VMware Cloud on AWS, or for POCs or lab use.

While we are close to releasing the final code on GitHub for the project, I thought I would branch out the last section of the code and release it separately. As I was creating this script, it became apparent to me that it would be useful for others to use as is or as an example from which to simplify manual and repetitive tasks that go along with configuring Backup & Replication after installation.

Script Overview:

The PowerShell script (found here on GitHub) performs a number of configuration actions against any Veeam Backup & Replication Server as per the included functions.

All of the variables are configured in a config.json file meaning nothing is required to be modified in the main PowerShell script. There are a number of parameters that can be called to trigger or exclude certain functions.

There are some pre-requisites that need to be in place before the script can be executed…most importantly the PowerShell needs to be executed on a system where the Backup & Replication Console is installed to allow access to the Veeam PowerShell Snap-in. From there you just need a new Veeam Backup & Replication server and a vCenter server plus their login credentials. If you want to add a Cloud Connect Provider offering Cloud Connect Backup or/and Replication you enter in all the details in the config.json file as well. Finally, if you want to add a Linux Repository you will need the details of that plus have it configured for key based authentication.

You can combine any of the parameters listed above. An example is shown above where -ClearVBRConfig has been used to reverse the -RunVBRConfigure parameter that was executed first to do an end to end configure. For Cloud Connect Replication, if you want to configure and deploy an NEA there is a specific parameter for that. If you didn’t want to configure Cloud Connect or the Linux Repository the parameters can be used individually, or together. If those two parameters are used, the Default Backup Repository will be used for the jobs that are created.

Automating Policy Based Backup Jobs:

Part of the automation that we where keen to include was the automatic creation of default backup jobs based on vSphere Tags. The idea was to have everything in place to ensure that once the script had been run, VMs could be backed up dependant on them being added to vSphere Tags. Once done the backup jobs would protect those VMs based on the policies set in the config.json.

The corresponding jobs are all using the vSphere Tags. From here the jobs don’t need to be modified when VMs are added…VMs assigned those Tags will be included in the job.

Conclusion:

Once the script has been run you are left with a fully configured Backup & Replication server that’s connected to vCenter and if desired (by default) has local and Cloud Connect repositories added with a set of default policy based jobs ready to go using vSphere Tags.

There are a number of improvements that I want to implement and I am looking out for Contributors on GitHub to help develop this further. At its base it is functional…but not perfect. However it highlights the power of the automation that is possible with Veeam’s PowerShell Snap-In and PowerCLI. One of the use-cases for this was for repeatable deployments of Veeam Backup & Replication into POCs or labs and for those looking to standup those environments, this is a perfect companion.

Look out for the full Veeam SDDC Deploy Toolkit being released to GitHub shortly.

References:

https://github.com/anthonyspiteri/powershell/tree/master/BR-Configure-Veeam

Quick Fix – Backing up vCenter Content Library Content with Veeam

A question came up in the Veeam Forums this week about how you would backup the contents of a Content Library. As a refresher, content libraries are container objects for VM templates, vApp templates, and other types of files. Administrators can use the templates in the library to deploy virtual machines and vApps via vCenter. Using Content libraries results in consistency, compliance, efficiency, and automation when deploying workloads at scale.

Content Libraries are created and managed from a single vCenter, but can be shared to other vCenter Server instances. VM templates and vApps templates are stored as OVF file formats in the content library. You can also upload other file types, such as ISO images, text files, and so on, in a content library. It’s possible to create content libraries that are 3rd party hosted, such as the example here by William Lam looking at how to create and manage an AWS S3 based content library.

For those looking to store them locally on an ESXi datastore there is a way to backup the contents of the content library with a Veeam Backup & Replication File Copy job. This is a basic solution to the question posed in the Veeam Forums however it does work. With the File Copy, you can choose any file or folder contained in any connected infrastructure in Backup & Replication. For a Content Library stored on an ESXi datastore you just need to browse to the location as shown below.

The one caveat is that the destination can’t be a Veeam Repository. There is no versioning or incremental copy so every time the job is executed a full backup of the files is performed.   

One way to work around this is to set the destination to a location that is being backed up in a Veeam Job or an Agent Job. However if the intention is to just protect the immediate contents of the library than have a full once off backup shouldn’t be an issue.

You can also create/add to a File Copy job from the Files view as shown above.

In terms of recovery, The File Copy job is doing a basic file copy and doesn’t know about the fact the files are part of a Content Library and as you can see, the folder structure that vCenter creates uses UIDs for identification. Because of this, if there was a situation where a whole Content Library was lost, it would have to be recreated in vCenter and then the imported back in directly from the File Copy Job destination folder location.

Again, this is a quick and nasty solution and it would be a nice feature addition to have this backed up natively…naming and structure in place. For the moment, this is a great way of utilizing a cool feature of Veeam Backup & Replication to achieve the goal.

Veeam on the VMware Cloud Marketplace Protecting VMware Cloud on AWS Workloads

At VMworld 2018, myself and Michael Cade gave a session on automating and orchestrating Veeam on VMware Cloud on AWS. The premise of the session was to showcase the art of the possible with Veeam and VMware that resulted in a fully deployed and configured Veeam platform. We chose VMware Cloud on AWS for the demo to showcase the power of the Software Defined Datacenter with Veeam, however our solution can be deployed onto any vSphere platform.

Why Veeam with VMware Cloud on AWS:

I’ve have spent a lot of time over the past couple of months looking into VMware Cloud on AWS and working out just where Veeam fits in terms of a backup and recovery solution for it. I’ve also spent time talking to VMware sales people as well as solution providers looking to wrap managed services around VMC and the question of data protection is often raised as a key concern. There is a good article here that talks about the need for backup and how application HA or stretched clustering is not a suitable alternative.

Without prejudice, I truly believe that Veeam is the best solution for the backup and recovery of workloads hosted on VMware Cloud on AWS SDDCs. Not only do we offer a solution that’s 100% software defines it’s self, but we can extend protection of all workloads from on-premises, through to the SDDC and also natively in AWS covering both backup, replication as well as offering the ability to use Cloud Connect to backup out to a Veeam Cloud and Service Provider. I’ll go into this in greater detail in a future post.

Veeam on the VMware Cloud on AWS Marketplace:

At the same time as our session on the Monday there was another session that introduced the VMware Cloud Marketplace that was announced in Technical Preview. As part of that launch, Veeam was announced as an initial software partner. This allows for the automated deployment and configuration of a Veeam Backup & Replication instance directly into a deployed SDDC and also configures an AWS EC2 EBS backed instance to be used as a Veeam Repository.

The VMware Cloud Marketplace will offer the ability to browse and filter validated third-party products and solutions, view technical and operational details, facilitate Bring Your Own License (BYOL) deployments, support commercial transactions, and deliver unified invoices. We plan to open Cloud Marketplace to a limited Beta audience following VMworld and are working on additional features and capabilities for future releases. We envision the Cloud Marketplace will quickly expand, introducing new third-party vendors and products over time and becoming the de-facto source for customers to extend the capabilities of VMware Cloud on AWS and VMware Cloud Provider Partner environments.

Compared to what Michael and I showcased in our session, this is a more targeted vanilla deployment of Veeam Backup & Replication 9.5 with Update 3a into the SDDC. At the end of the process, you will be able to access the Veeam Console, have it connected to the VMC vSphere endpoint and have the EC2 Veeam repository added.

This is done via CloudFormation templates and a little bit of PowerShell embedded into the Windows Image.

Being embedded directly into the VMware Cloud Marketplace is advantageous for customers looking to get started quick with their data protection for workloads running on VMware Cloud o AWs. Look out for more collateral from myself, Veeam and VMware on protecting VMC with Veeam as well as a deeper look at our VMworld session which digs into the automation and orchestration of Veeam on VMware Cloud on AWS using Chef, Terraform, PowerShell and PowerCLI.

References:

Introducing VMware Cloud Marketplace

https://cloud.vmware.com/cloud-marketplace

https://marketplace.vmware.com/vsx/solutions/veeam-availability-suite-for-vmware-cloud-on-aws-9-5?ref=search#summary

VMworld 2018 Recap Part 2 – Community and Veeam Recap

VMworld 2018 has come and gone and after a couple of days recovery from the week that was, i’ve had time to reflect on what was a great week and an another great VMworld in Las Vegas. For me, the dynamic of what it is to be at a VMworld has changed. The week is not just about the event, the announcements or the sessions…but more about what myself and my team are able to achieve. While we are participants of VMworld we are also working and need to be adding value on all fronts.

This year I left Las Vegas with a sense of achievement and the belief that the week was extremely successful both personally and from a Veeam Product Strategy point of view. In this post (which is Part 2 of my VMworld 2018 recap) I am going to go over what went down with the VMware community during the event and close off with a quick Veeam roundup.

Community:

I felt like the community spirit was in full effect again at VMworld. Between all the sessions, parties and events my overall feeling was that there was a lot of community activity going on. Twitter it’s self came to life and everyones timelines where filling up with #VMworld media. The grass roots community still fuels a lot of VMware’s success and you can’t underestimate the value of influence and advocacy at this level. Certainly, Veeam and other vendors understand this and cater to supporting community events while looking after members with vendor branded swag.

One important thing I would like to highlight is the power of the local community and how something small can turn into something huge. My good friend from Australia, Tim Carman had an idea last year to create an As Built PowerShell Documentation script. He first presented it at his local VMUG…then a few months later he presented it at the Melbourne VMUG UserCon and last week, he presented it with Matt Allford in front of 500 plus people at VMworld. Not only that, but the session was voted into the daily top ten and is currently the second most downloaded via the online session download page!

Hackathon:

Another amazing thing that happened at VMworld was the team that I was lucky enough to be a member of took out the Hackathon. Aussie vMafia 2.0, lead by Mark Ukotic took out the main prize on the back of an idea to put a terminal in the (H5) Client and running commands. Again, what I was most pleased about with Mark, Tim and Matt’s success was exposure from the sessions and Hackathon win. They are great guys and well deserving of it. It goes down as one of my best VMworld highlights of all time!

Veeam Highlights and Sessions:

Finally to wrap things up, it was a great VMworld for Veeam. I spoke to a lot of customers and partners and it’s clear that our Availability Platform that’s driven through our strong ecosystem alliances is still very much resonating and seen to be leading the industry. Being hardware agnostic and software only carries massive weight and it was pleasing to have that validated by talking to customer and partners during the course of the event.

In terms of our sessions, we had two different breakouts. One covering some of the brilliant new features in Update 4 of Backup & Replication 9.5 presented by Danny Allan and Rick Vanover.

And myself and Michael Cade presented on automation and orchestration of Veeam on VMware Cloud on AWS. Michael talks about the session here, but in a nutshell we came up with a workflow that orchestrates the deployment of a Veeam Backup & Replication Server with Proxies onto a vSphere environment (VMC used in this case to highlight the power of the SDDC) and then deploys and configures a Veeam Linux Repository in AWS, hooks that into a VeeamPN extended network and then configures the Veeam Server ready to backup VMs.

Finally…it wouldn’t be VMworld without a Veeam party, and this year didn’t fail to live up to expectation. Held at the Omnia nightclub on Tuesday night it was well received and we managed to fill the club without the need to pull in a headline act. And as I tweeted out…

Wrap Up:

Overall, VMworld ticked a lot of boxes and was well received by everyone that I came across. IT’s been a good run of three VMworld’s in a row in Vegas, however it’s time to move back to where it all started for me in 2012 in San Fransisco. It’s going to be interesting going back to the Mascone Center and a city that hasn’t got the best reputation at the present moment due to social issues and the cost of accomodation is astronomical compared to Vegas. However, location is one thing…it’s what VMware and it’s ecosystem partners bring to the event. This year it worked! Hopefully next year will be just as successful.

Veeam @VMworld 2018 Edition…

VMworld 2018 is less than a week away, and I can’t wait to fly into Las Vegas for my sixth VMworld and second with Veeam. It’s been an interesting year or so since the last VMworld and the industry has shifted a little when it comes to the backup and recovery market. Data management is the new buzz and lots of vendors (us included) have jumped onto the messaging around data growing at more than exponential rates…sprawling to more platforms than ever before and finally…being more critical than ever. The criticality and power of data is real and VMware still have a lot to say about where an how that data is processed and stored!

VMworld is still a destination event and Veeam recognises VMware’s continued influence in the IT industry by going all in at VMworld 2018. The ecosystem that VMware has built over the past ten to fifteen years is emense and though challenged a few years ago, came back with a bang in 2017. I’m looking forward to seeing VMware’s continues evolution at this years event! Like VMware,

Veeam is evolving as well, and we are building out own own strong ecosystem based on a software first, hardware agnostic platform that results in the greatest flexibility in the backup and recovery market. We continue to support VMware as our number 1 technology partner and this year we look to build on that with support for VMware Cloud on AWS and enhanced VMware features sets built into our core Backup & Replication product as we look to release Update 4 of 9.5 later in the year.

Veeam Sessions @VMworld:

Officially we have two breakout sessions this year, with Danny Allan and Rick Vanover presenting a What’s New in Update 4 for Veeam Backup & Replication and Michael Cade and myself presenting a session on Automation and Orchestration of VMware and Veeam on VMware Cloud on AWS. There are also a couple of vBrownBag Tech Talks where Veeam features including talks from Michael Cade and Michael White while Dave Russell will be presenting a Partner Spotlight session.

https://my.vmworld.com/widget/vmware/vmworld18us/uscatalog?search=Veeam

Veeam @VMworld Solutions Exchange:

This year, as per usual we will have significant presence on the floor, with a Main Booth Area doing demo’s prize, giveaways, having an Experts Bar and acting as sponsor of the opening night hall crawl. We also have an in booth Theatre where I will be presenting on our new vCloud Director integration with Veeam Cloud Connect.

Veeam Community Support @VMworld:

Veeam still gets the community and has been a strong supporter historically of VMworld community based events. This year again, we have come to the party are have gone all-in in terms of being front and center in supporting community events. Special mention goes to Rick Vanover who leads the charge in making sure Veeam is doing what it can to help make these events possible:

  • Opening Acts
  • VMunderground
  • vBrownBag
  • Spousetivities
  • vRockstar Party
  • Vanguard Takeover

Party with Veeam @VMworld:

Finally, it wouldn’t be VMworld without attending Veeam’s seriously legendary party. This year we are looking to top last years event at Hakkasan nightclub by taking over one of the hottest club in Vegas… Omnia Nightclub! If it’s anything like the VeeamON 2015 Party that I attended it’s going to go off!! I know how hard it is to plan evening activities at VMworld and there is no doubt that there are a lot of decent competing parties on the Tuesday night…however whatever you do, you need to make sure that you at least stop by Caesars Casino and party in green. RSVP here.

https://www.eventbrite.com/e/veeams-legendary-vmworld-party-2018-tickets-45869296300

Final Word:

Again, this year’s VMworld is going to be huge and Veeam will be right there front and center of the awesomeness. Please stop by our sessions, visit our stand and attend our community sponsored events and feel free to chase me down for a chat…I’m always keen to meet other members of this great community. Oh, and don’t forget to get to the party!

Veeam Availability Console 2.0 Update 1 Important Patch Release

Earlier this month a patch was released for Veeam Availability Console 2.0 Update 1. Contained in the list of fixes is an important note about those that manage Windows Agents through VAC that are sending backups via backup copy jobs. In short there was an issues with the reporting and billing leading to some incorrect value for the tenant quota usage.

There are also a number of other resolved issues including some monitoring and alarm fixes as well as for those using the ConnectWise Plugin. The patch is advised to be deployed to all VCSPs running VAC especially those with tenants sending backup copy jobs as mentioned above.

To apply the patch, head to the VeeamKB here and follow the instructions. You need to have at least VAC 2.0 Update 1 Build 2.0.2.1750 as shown below.

From there, make sure you have a backup of the database, close down the Web UI and execute both MSI packages as administrator on the server.

The first one updates the VAC server.

The second one updates the ConnectWise Manage Plugin. Once completed the patches are applied and VAC 2.0 Update 1 is up to date running on version number Server Version 2.0.2.1807. Note that updated Windows for Agent Builds have been pushed out and can be upgraded as per my post a few months back.

References:

https://www.veeam.com/kb2694

Video – Protecting AWS and Hybrid Workloads with Veeam and N2WS

Back in April, I was lucky enough to present at the AWS Summit in Singapore. The session was a joint one with Alex Thomson from N2WS on how Veeam and N2WS are protecting native workloads within AWS and also extending that out to protecting Hybrid workloads sitting on-premises back to AWS or within VMware Cloud on AWS. The session video is embedded below and goes for about 30 minutes.

Alex and I talk about Veeam’s vision for Intelligent Data Management, an introduction into N2WS, a look at VTL solutions for offsite backups and finish out with an introduction into how Veeam works natively with VMware Cloud on AWS.

Veeam has pioneered the market of Availability for the Always On Enterprise by helping enterprises meet recovery time and point objectives (RTPO) of less than 15 minutes on any cloud or hybrid platform. Veeam recently acquired N2WS, a leading provider of cloud native backup and DR solutions providing backup automation and instant recovery for AWS workloads. Come and hear how N2WS is leading the backup and recovery of EC2 instances and native AWS workloads, how Veeam VTL technology leveraging the AWS Storage Gateway offers offsite cloud repositories as well as how Veeam is offering leading availability solutions for VMware Cloud on AWS.

Speakers

– Anthony Spiteri, Global Technologist, Product Strategy, Veeam.
– Alexander Thomson, Sales Director EMEA & APAC, N2WS

Released: Backup for Office 365 2.0 …Yes! You Need to Backup your SaaS

Last week the much anticipated release of Veeam Backup for Office 365 version 2.0 (build 2.0.0.567) went GA. This new version builds on the 1.5 release that was aimed at scalability and service providers. Version 2.0 adds support for SharePoint and OneDrive. Backup for Office 365 has been a huge success for Veeam with a growing realisation that SaaS based services require an availability strategy. The continuity of data on SaaS platforms like Office 365 is not guaranteed and it’s critical that a backup strategy is put into place.

Version 1.5 was released last October and was focused on laying the foundation to ensure the scalability requirements that come with backing up Office365 services were met. We also enhanced the automation capability of the platform through a RESTful API service allowing our Cloud & Service Providers to tap into the APIs to create saleable and efficient service offerings. In version 2.0, there is also a new set of PowerShell commandlets that have been enhanced from version 1.5.

What’s New in 2.0:

Office 365 Exchange was the logical service to support first, but there was huge demand for the ability to extend that to cover SharePoint and OneDrive. With the release of version 2.0 the platform now delivers on protecting Office 365 in its entirety. Apart from the headline new features and enhancements there are also a number of additional ones that have been implemented into Backup for Microsoft Office 365 2.0.

  • Support for Microsoft SharePoint sites, libraries, items, and documents backup and restore.
  • Support for Microsoft OneDrive documents backup and restore.
  • Support for separate components installation during setup.
  • Support for custom list templates in Veeam Explorer for Microsoft SharePoint.
  • Support for comparing items with Veeam Explorer for Microsoft Exchange.
  • Support for exporting extended logs for proxy and controller components.

We have also redesigned the job wizard that enhances setup, search and maintaining visibility of objects.

Architecture and Components:

There hasn’t been much of a change to the overall architecture of VBO and like all things Veeam, you have the ability to go down an all in one design, or scale out depending on sizing requirements. Everything is handled from the main VBO server and the components are configured/provisioned from here.

Proxies are the work horses of VBO and can be scaled out again depending on the size of the environment being backed up. Again, this could be Office 365 or on-premises Exchange or SharePoint instances.

Repositories must be configured on Windows formatted volumes as we use the JetDB database format to store the data. The repositories can be mapped one to one to tenants, or have a many to one relationship.

The API service is disabled by default, but once enabled can be accessed via a URL to view the API commands in Swagger, or directly via the API endpoint.

Free Community Edition:

In terms of licensing, VBO is licensed per Office 365 user in all organizations. If you install VBO without a license, you will trigger Community Edition mode that allows you to have up to 10 user accounts in all organizations. This includes 1 TB of Microsoft SharePoint data. The Community Edition is not limited in time and doesn’t limit functionality.

Installation Notes:

You can download the the latest version of Veeam Backup for Microsoft Office 365 from this location. The download contains three installers that covers the VBO platform and two new versions of the Explorers. Explorer for Microsoft OneDrive for Business is contained within the Explorer for Microsoft SharePoint package and installed automatically.

  • 0.0.567.msi for Veeam Backup for Microsoft Office 365
  • 6.3.567.msi for Veeam Explorer for Microsoft Exchange
  • 6.3.568.msi for Veeam Explorer for Microsoft SharePoint

To finish off…It’s important to read the release notes here as there are a number of known issues relating to specific situations and configurations.

Links and Downloads:

« Older Entries