Category Archives: CLOUD – SERVICE PROVIDER

The service provider point of view

Veeam Backup Office 365 & Cloud Connect

In the last few days, I have been contacted by a Service Provider to design a solution to back up the Microsoft Office 365 environment.

Actually, four months ago, I wrote three articles to show how to set up the environment using a great job of Niels and Timothy, creators and deployers the Martini project.

All details are available clicking  here,

VBO-365 Portal: A nice project just behind the corner – Part 1

Why the Service Provider needs a different way to implement this service?
I think that the two main reasons were:

1) SP has already a Cloud Connect architecture and it wants to use it in all possible scenarios.
2) SP needs always official support from Vendor before implementing any project and the Martini is not. To be clearer, the RestFul Api technology inside VBO is totally supported, the Martini portal isn’t because it is not a Veeam product.

Before continuing the read, there is one requirement to respect: VBR Cloud Connect and VBO-365 have to be installed on the same server (a Windows Server).

Let’s start!

Picture 1 shows the high-level architecture.

Enhanced Self Service Restore in Backup for Office 365 v2.0 - VIRTUALIZATION IS LIFE!Picture 1

The service provider architecture is shown on the right part of picture 1 and it is composed of VBO-365 and the Cloud Connect architectures, while the left part shows the tenant architecture where VBR Server has been installed.

Which are the actions that can be performed by the Tenant?

Backup: the tenant can’t access the VBO-365 console. It means the Tenat can’t set up or launch any sort of backup. In other words, the backup tasks are a managed services.

Restore: The tasks can be driven by the administrator of the Microsoft Office 365 organization through the use of Veeam Explores. The Cloud Connect technology creates the tunnel to connect the two entities.

Note 1: When VBR is installed by default all Veeam Explorers are installed.

I mean that not just the traditional Veeam Explorers (for Active Directory, SQL, Oracle, Exchange, Share-points) are installed but also the Explorer for One Drive and Teams. that are specific for Microsoft 365 technology.

Note 2: Does this scenario require  VBR license?

Yes, but you can use the free community edition.

The point to highlight during the setup is the authentication task that allows the explorer to communicate with VBO-365:

From the VBO-365 console selecting “General Options” (Picture 2) and from the  authentication tab enabling the tenant authentication  you can catch your goal (please for security reason use your own certificate) (Picture 3)

Picture 2

Picture 3

Let’s switch to my demo environment:

1. The Service Provider VBO-365 console, has three Microsoft 365 organizations with a backup job each  (Picture 4). Two of those use modern authentication, the third the basic one.

Picture 4

2. The Cloud-Connect architecture has been set up in order to create a tenant called  Demo-VBO (Picture 5).

Picture 5

  • The VBR Tenant Console shows how the connection towards the service provider has been set up (Picture 6).

Picture 6

The following video shows the tasks performed by the tenant to restore his data (Exchange/Sharepoint/One-Drive/Teams items) located at the Service Provider site.

Video 1

That’s all for now, take care and see you soon

VBO-365 Portal: A nice project just behind the corner – Part 3

This third part will cover the restoration options.

If you need to know how to set the portal up or the option it can provide, please read the previous articles (Part-1 – Part-2)

Let’s start with Exchange Environment:

Clicking on the Exchange voice located on the top part of the web page (in picture 1 it is highlighted with a green arrow )

Picture 1

After selecting the organization you want to restore data from (in my case is myTEST-Environment as shown in picture 2), just choose the restore point you need (Picture 3).

Picture 2

Picture 3

Picture 4 shows the mail-boxes previously saved that you can restore.

Picture 4

What’s happening on VBO-365?  As shown in picture 5 the portal has triggered a  classical restore task.

Picture 5

Which are the restore option available in the portal for the Exchange environment? As shown in picture 6, you can download the mail as a pst file (it requires outlook client installed) or restore to the original or different location as shown in picture 7.

Picture 6

Picture 7

To finish the restore tasks just click on stop restore (Picture 8 and 9).

Picture 8

Picture 9

And what about restore of One-Drive and Sharepoint items?

The procedure is very similar and the restore options are shown in pictures 10 and 11.

Picture 10

https://lnx.gable.it/wp-content/uploads/2020/11/42-martini.jpgPicture 11

VBO-365 v.5 has introduced support for Microsoft-365 Teams. It is not still available in this portal and I hope it will come soon. Stay tuned 🙂

That’s all for the VBO portal for now. Take care

VBO-365 Portal: A nice project just behind the corner – Part 2

This second article will complete the deployment scenario that began with Part 1. If you didn’t read it yet just click here.

The first important step is to enable VBO-365 to work with RestFul-API. Pictures 1 to 4 show the steps to perform the task

Picture 1

Picture 2

Picture 3

Picture 4

Now from a web browser insert the IP Address of the VBO-Portal.

https://lnx.gable.it/wp-content/uploads/2020/11/7-martini.jpgPicture 5

The login credentials are: username Admin, password the one you choose during the setup ( ‘new_password‘).

After completing the login phase, add a name to the tenant and its e-mail address (don’t worry, nothing will be sent to that e-mail address for now). Click the save button and make a note of the automatically generated. password (Picture 7)

Picture 6

Picture 7

Now it’s time to add your VBO installation to the portal

On the left menu, click on “create instance” and after selecting the just created tenant (My-Lab-Environment), at the voice Instance Type select choose “Existing instance” as shown in Picture 3.

Picture 8

In the last blanks insert the data of your VBO installation.

Picture 9

Now log out and re-login with the credentials just created (new tenant) as shown in picture 10

Picture 10

The Dashboard is still empty (Picture 11), don’t worry it’s because the portal is not still connected to VBO.

Picture 11

On the left menu, select list instances and from there just select connect (Picture 12)

Picture 12

After the connection has been successfully completed (Picture 13), the dashboard is filled up (Picture 14) and you are ready to work with it.

Picture 13

Picture 14

Some interesting items to watch at from now:

At the jobs menu, you can see the scheduling, disabling, or start the job (Picture 15)

Picture 15

Picture 16 shows the license status and 17 the activity restore logs.

Picture 16

Picture 17

In my next article, I’ll write about restoration options.

Stay tuned and see you soon.

8th December update:  If you seeing the connection is looping please download from this link the securerestore.php file and replace the old one.

Restart the configuration steps from picture 5.

8th January update: Good news, it works with VBO-365 v.5 too!

The only modify to perform is to change an entry inside the file named veeam.vbo.class.php located in /var/www/html/core.

At line 35
From: ‘base_uri’ => ‘https://’.$host.’:’.$port.’/v3/’

to ‘base_uri’ => ‘https://’.$host.’:’.$port.’/v5/