Category Archives: SharePoint

Quick Fix – Backup for Office 365 Self Service Recovery Fails with Incompatible Version

A couple of weeks ago we released version 2.0 of Veeam Backup for Office 365 which added support for SharePoint and OneDrive. Earlier this year I wrote about the awesome self service capabilities that are included for Veeam Cloud and Service Providers in the VBO platform, and also the huge opportunity that exists in the provider space to offer backup service for Exchange. Add to that SharePoint and OneDrive and that opportunity only gets bigger.

I’m putting together a couple of posts around the self service of SharePoint and OneDrive in the 2.0 release, but in the meantime this is a very quick fix post for those that might be getting the below error when trying to connect to service provider endpoints running VBO services for Exchange Online.

Incompatible Veeam Backup for Office 365 server version, received 9.6.3.567, expected 9.6.0.1308

To resolve this issue, then tenant needs to download the VBO 2.0 download package and install the new version of the Veeam Explorer for Microsoft Exchange that’s included in the release.

This will update the existing Explorer version from that distributed with Veeam Backup & Replication 9.5. The awesome thing about getting the upgrade as part of the VBO 2.0 package is that for the 1.5 release where self service was first introduced, tenants had to wait for Update 3 for Backup & Replication to consume the service.

Once this has been updated you can once again connect to the Cloud Connect infrastructure of the Service Provider that allows the self service recoverability function to take place.

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:

SharePoint 2010 Web UI Timeout Creating Web Application: Quick Fix

Had a really interesting issue with a large SharePoint Farm instance we host… over the last couple of days when we tried to create a new Web Application the task was failing on the SharePoint Farm members. While being initially thrown off by a couple permission related event log entries for SharePoint Admin database access there was no clear indication of the problem or why it starting happening after weeks of no issues.

The symptoms being experienced was that from the Central Admin Web Site ->; Application Management ->; Manage Web Application page, creating a New Web Application would eventually return what looked like a HTTP timeout error. Looking at Central Admin page on both servers, it showed the Web Application as being present and created and the WSS file system was in place on both servers…however the IIS Application Pool and Website where only created on the server that ran the initial New Web Application. What’s better is that there where not event logs or SharePoint logs that logged the issue or cause.

sp_timeout_error

In an attempt to try and see a little more verbose logging during the New Web Application process I ran up the new-SPWebApplication PowerShell command below:

New-SPWebApplication -Name “www.site.com.au443” -Port 443 -HostHeader “www.site.com.au” -URL “https://www.site.com.au” -ApplicationPool “www.site.com.au443” -ApplicationPoolAccount (Get-SPManagedAccount “DOMAIN\spAppPoolAcc”) -DatabaseServer MSSQL-01 -DatabaseName WSS_Content_Site -SecureSocketsLayer:$yes -Verbose

While the output wasn’t as verbose as I had expected, to my surprise the Web Application was created and functional on both servers in farm. After a little time together with Microsoft Support (focusing on permissions as the root cause for most of the time) we modified the Shutdown Time Limit setting under the Advanced Settings of the SharePoint Central Admin Application pool:

sp_timeout

The Original value is set to 90 seconds by default. We raised this to 300 and tested the New Web Application function from the Web UI which this time was able to complete successfully. While it does make logical sense that a HTTP timeout was happening, the SharePoint farm wasn’t overly busy or under high resource load at the time, but still wasn’t able to complete the request in 90 seconds.

One to modify for all future/existing deployments.