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 )
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 4 shows the mail-boxes previously saved that you can restore.
What’s happening on VBO-365? As shown in picture 5 the portal has triggered a classical restore task.
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.
To finish the restore tasks just click on stop restore (Picture 8 and 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.
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 🙂
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
Now from a web browser insert the IP Address of the VBO-Portal.
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)
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.
In the last blanks insert the data of your VBO installation.
Now log out and re-login with the credentials just created (new tenant) as shown in picture 10
The Dashboard is still empty (Picture 11), don’t worry it’s because the portal is not still connected to VBO.
On the left menu, select list instances and from there just select connect (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.
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 16 shows the license status and 17 the activity restore logs.
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/’
It requires and automatically installs the following packages:
apache2, mysql-server mysql-client, PHP, php-xml, composer, zip unzip php-mysql and Terraform.
At the end of this setup the screen output shows the following output.
CREATE DATABASE martini;
CREATE USER ‘martinidbo’@’localhost’ IDENTIFIED WITH mysql_native_password BY ‘mypasswordthatissupersecret’;
GRANT ALL ON martini.* TO ‘martinidbo’@’localhost’;
# Ubuntu older
GRANT USAGE ON *.* TO ‘martinidbo’@’localhost’ WITH MAX_QUERIES_PER_HOUR 0;
# Ubuntu 20.04
GRANT USAGE ON *.* TO ‘martinidbo’@’localhost’;
Now connect to mySQL DB using the following command:
mysql -u root -p
If the error shown in picture 1 appears it is necessary to follow the procedure described below:
– sudo mysql – select user,host,plugin from mysql.user; output -> root | localhost | auth_socket
the output is shown in picture 2 and it checks the plugin used for any MySQL users.
If it is auth_socket to user root just change it with the following command
– update mysql.user set plugin=’mysql_native_password’ where user=’root’; – select user,host,plugin from mysql.user; output root | localhost | mysql_native_password
the output shown in picture 3 confirms it is correctly changed.
– flush privileges;
Now retype the previous command (mysql -u root -p) and please continue with the procedure if it still doesn’t work as shown in picture 4 :
– ALTER USER ‘root’@’localhost’ IDENTIFIED BY ‘new_password‘;
– flush privileges; – quit
at this point reboot the server.
The command mysql -u root -p shows the following output:
Copyright (c) 2000, 2020, Oracle and/or its affiliates. All rights reserved. Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.
Let’s go back to martini checking if the database and the new user have been created with the command:
mysql> show databases;
If it doesn’t appear use the following steps: – use mysql – show tables; – CREATE USER ‘martinidbo’@’localhost’ IDENTIFIED BY ‘mypassword-‘; – GRANT ALL PRIVILEGES ON * . * TO ‘martinidbo’@’localhost’; – FLUSH PRIVILEGES; – CREATE DATABASE martini;
Now re-launch the martini setup command
– sudo martini-cli setup
selecting no when the prompt asks if it is the first run and follow the easy wizard as shown in picture 5.