In this two-part article, NAKIVO How to configure your NAKIVO Infrastructure to Backup & Restore Office 365 will go through this new feature that NAKIVO added in version 9.2.
We already talked about HERE, I will explain how to connect to your Office 365 account and backup and restore your emails account and emails or contacts.

Since to start using NAKIVO Backup & Replication v9.3 to backup and restore Office 365, we first need to configure NAKIVO infrastructure. For the best performance, we should set the NAKIVO infrastructure properly, and for that, we need to make some changes.

This article is divided into two parts:

• First part: How to configure your NAKIVO Infrastructure to Backup & Restore Office 365.
• Second part: Backup & Restore Office 365 with NAKIVO

To provide data protection for your Microsoft Office 365, the following requirements must be met:

Exchange Online must be purchased as a part of the Microsoft Office 365 plan or a standalone service.
Microsoft Office 365 account must be accessible over the network.
Provided Microsoft Office 365 (Exchange Online) credentials must have sufficient permissions to be used by the product.

Before use NAKIVO Replication & Replication with Office 365, we need to configure NAKIVO with some settings.

Mandatory components:

• NAKIVO Transporter for Office 365
• Backup Repository for Office 365
• Connect to your Office 365 account

Transporter:

To connect to your Office 365 Backup Repository, you need to attach a Backup Transporter. The Transporter needs to be specific for this Office 365 backups.

You can use the default that is created when you install your NAKIVO Backup & Replication, or you can install a new Transporter. The new Transporter can be deployed as a VMware Appliance, AWS C3 Instance, or a Nutanix AHV Appliance.

Other OS that is supported to install a NAKIVO Transporter:

Windows

• • • Windows Server 2019 Standard (x64)
    • Windows Server 2016 Standard (x64)
    • Windows Server 2012 R2 Standard (x64)
    • Update for Windows Server 2012 R2 (KB3179574)
    • Windows Server 2012 Standard (x64)
    • Windows Server 2008 R2 Standard (x64)
    • Windows 10 Pro (x64)
    • Windows 8 Professional (x64)
    • Windows 7 Professional (x64)

Linux

• • • Ubuntu 18.04 Server (x64)
    • Ubuntu 16.04 Server (x64)
    • SUSE Linux Enterprise Server 12 SP3 (x64)
    • SUSE Linux Enterprise Server 11 SP4 (x64)
    • Red Hat Enterprise Linux 7.6 (x64)
    • Red Hat Enterprise Linux 7.5 (x64)
    • Red Hat Enterprise Linux 7.4 (x64)
    • Red Hat Enterprise Linux 6.9 (x64

For this article, I will install a new VMware Transporter Appliance.

Backup Repository for Office 365:

To store Office 365, we need a specific Backup Repository for these backups. The new Backup Repository needs to be connected to a Transporter. It can be the default or a new one that we can create.

Also, the new Backup Repository needs to be set in the Transporter. If you have an NFS share or virtual disks, you need to add this to the Transporter.

For this article, I will add a second virtual disk to the Transporter so that we can use it as a Backup Repository.

Office 365 account:

So that NAKIVO Backup & Replication Office 365 can backup all your objects in your Office 365, you need to connect NAKIVO to your Office 365. For that, we need to connect to portal.azure.com using Office 365 account and register the NAKIVO app and create API Permissions.

Configure NAKIVO Transporter.

As stated above, I will add the new Office 365 Backup Repository to the newly created Transporter. It can be done in two ways.

1. Add Virtual Disk to Transporter VM.
2. Mount an NFS Share in Transporter.

Add Virtual Disk to Transporter VM.

Is the simplest option to add the new Repository option to a transporter.

Edit your NAKIVO Transporter VM and Add the new Virtual Disk to the VM.

The size of the disk depends on the amount, email\users accounts, and data of your Exchange Online Office 365 account. For this case, we will add a 1Tb disk.

After you add the Virtual Disk Reboot the VM and configure the new Disk in the Transporter.

After the reboot, connect to your Transporter VM console. In the VM console, you will check the Transporter main menu, select Manage NAKIVO services.

Next, select the Onboard repository storage. Here you should see the new Virtual Disk created above. Select the disk and Enter.

Confirm that you want to use this new Disk for Backup Storage.

Confirm with Enter and Transporter will create the new partition by default the Storage in /opt/nakivo/repository/.

After the last step, you can go back to the NAKIVO Backup & Replication GUI to create your Office 365 Repository

Mount an NFS Share in Transporter.

If instead, we want to mount an NFS Share in the Transporter, we need to change Transporter Network Settings and root password so that we can mount the NSF Share Storage Repository.

In this case, since I needed to add a second Network Interface to connect to the NFS network, we need to configure the Network Settings for first (not mandatory we could use DHCP), and second Interface (showed in the VM setting above image).

First, we need to change the root password so that we can ssh to the transporter and mount the NFS Share.

Change Root password:

In Transporter VM Console in the main menu, select Security settings.

Select Change root password and enter your new root password.

Change Network Settings:

In the main menu, select Network Settings.

In the next image, we see the two Network Interfaces from the Transporter VM.

The first interface is in DHCP and is the management interface and the second interface (the one we added into the VM) is the new Network Interface for Storage network.

We will configure the Storage Network Interface so that Transporter can access to the Storage System and Mount the new NSF Share for Backup Repository.

In the Interface, enable the interface and add all the IP settings that are needed.

Note: Since this is an Interface for Storage, no gateway is added, but even was not for Storage, you cannot have two Gateways (you could, but you need extra configurations in the Linux network).  Also, since this is a Storage Network, I have changed the MTU to 9000 for Jumbo frames.

After you finish with your setting, press F10 and save all the configurations (sometimes the save doesn’t save all the settings, you need to return to the interface to add it again and save again).

Note: If you want the management interface as static, also change the first interface. I have also changed for the management interface to static, but this example is just for Storage Network.

Now that we have our NAKIVO Transporter root password and network changed, we can now login with ssh to Transporter to mount the NSF Share.

After creating the NSF Share in my Synology, I just need to mount it.

Mount the NSF Share and create a file just to make sure rw permissions are ok.

After you mount the NFS Share, you can now go to NAKIVO Backup & Replication GUI and add the new Office 365 Backup Repository using the NFS Share.

Create Backup Repository for Office 365.

In the Configuration tab and Repositories, you can add the new Office 365 Backup Repository.

Click Add Backup Repository.

Next, we need to configure the Backup Repository.

1 – Name of the Backup Repository. You can add any name is not a data field.

2 – In this section is where we assign the Transporter that we will use for Office 365 Backups, in this case, the one we created above.

Note: Remember that the Transporter for Office 365 is associated with the Office 365 Repository.

3 – Type of Repository, in this case, we are creating for Office 365.

4 – Add the path for the type of Storage Repository we created above. 

Since we have created two types, if is NFS Share or the Virtual Disk in the Transporter Appliance, we just need to add the path for each case. Add the path and click Add.

If you get this next error, then you need to check the permissions of your NFS Share that you created above.

Permission in the Folder should be: owner rwx, group rwx

In this case, the folder didn’t have the appropriate permissions, so we need to run chmod 77 in the mount folder.

After fixing this issue, the Office 365 Backup Repository was successfully created.

The last part of configuring NAKIVO Backup & Replication Office 365 is to connect NAKIVO to your Office 365 account.

Connect to Office 365 account.

To connect to your Office 365 account, NAKIVO needs four records from your Azure account to be configured in the NAKIVO Inventory.

• • Display Name
  • Tenant ID
  • Azure Client ID
  • Azure Client Secret

Besides the above information from your Azure account, we also need to permit your NAKIVO Backup & Replication tool to be authorized to access the Office 365 account. And this is done in your Azure account.

First, connect to portal.azure.com with your Office 365 account.

Then int the main menu, select Azure Active Directory.

Inside the Azure Active Directory register a new App. Select App Registrations.

After you are inside of App Registrations, you need to click New Registration.

Give a name for your new App and select the option “Accounts in any organizational directory (Any Azure AD directory – Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)” and click register.

After your App registration is done, you get information that you will later on to register in NAKIVO Office 365 Inventory.  Click View API Permissions.

In this section, we will add the permissions that NAKIVO Backup and Restore have on your Office 365 account.

1 – Select API Permissions

2 – Select Microsoft Graph

3 – Select Applications Permissions

4 – In the select permissions, enter “user.read”. Then it shows all user read permissions so that we can select the one we need.

5 – In the dropbox select Mail.ReadWrite and User.ReadWrite.All 

6 – Click Update Permissions.

After you add the permissions to the API Microsoft Graph, you need to grant admin consent for YourAzureAccountName. 

Note: Consent is the process of a user granting authorization to an application to access protected resources on their behalf. An admin or user can be asked for consent to allow access to their organization/individual data.

After you grant consent, all permissions should move from Not Granted for YourAzureAccountName to Granted for YourAzureAccountName.

After the last step, we need to create a Secret key, and we are done configuring our Azure Office 365 account for NAKIVO Backup & Replication.

1 – In the menu, select Certificates & Secrets.

2 – Click New client secret.

3 – Select a Name\Description for the Secret key (the expiring date is up to you). If it expires or you lose the key, you need to create a new one.

4 – Click add o create the Secret Key.

5 – Copy and save the key. You will need it in the NAKIVO Inventory account.

After the last step, the configuration of your Azure Office 365 account is finished, return to your NAKIVO Backup & Replication GUI.

Create NAKIVO Inventory for Office 365

In NAKIVO Backup & Replication GUI select Inventory click ADD New and select Microsoft Office 365 Account.

Next, in the account, fill the data with the records copied from the Azure App information that we created above.

In the next image, you can check which field belongs to which field in the Inventory account fields (check the numbers in the image). Also, copy and paste the key that you have saved before.

Then the Inventory Office 365 account is created.

After the last step, we are done with Azure Office 365 account, and NAKIVO Inventory Office 365 account are configured, and you are ready to start Backup and Restore your Office 365 account.

Final Comments:

In this article, How to configure your NAKIVO Infrastructure to Backup & Restore Office 365, we configured all NAKIVO Backup & Replication with new Transporter, new Backup Repository and register in Azure Office 365 account NAKIVO Backup & Replication.

Next article and second part is: Backup & Restore Office 365 with NAKIVO

RESOURCES

• NAKIVO Office 365: https://www.nakivo.com/office-365-backup/
• Trial Download: /resources/download/trial-download/
• Datasheet: nakivo-backup-replication-datasheet.pdf
• Success Stories: /customers/success-stories/

I hope this information was useful.

Note: Share this article if you think it is worth sharing.

©2020 ProVirtualzone. All Rights Reserved

Note: This post was sponsored by Nakivo Inc