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 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 see 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/