NetVault Plug-in for Microsoft 365 13.1

Using the Microsoft 365 admin portal to obtain configuration details Entering the configuration details in the plug-in Improving backup and restore performance by modifying parameters in the configuration file

Backing up data

Defining a backup-and-recovery strategy Adding patterns to use for exclusion and inclusion Performing backups

Selecting data for a backup Setting backup options Finalizing and submitting the backup job

Restoring data

Selecting data for a restore Finalizing and submitting the restore job Relocating a mailbox or OneDrive account during the restore process Searching for granular items

Troubleshooting

Entering the configuration details in the plug-in

After you have identified application ID, password, and domain name, you must enter the information in the configuration section for the plug-in.


	NOTE: The user configured for SharePoint Online should have Global administrator access to the site it backs up and the location to which it intends to restore the backed up contents. The user configured for the plug-in must be a member of the Teams platform to generate backup and restore jobs for Teams.

In the Navigation Pane, click Create Backup Job, and click

next to the Selections list.

In the selection tree, open the applicable client node.

Click Plug‑in for Microsoft 365, and select Configure from the context menu.

On the Configure dialog, complete the following fields using the information that you recorded during the previous process, Using the Microsoft 365 admin portal to obtain configuration details.

•

Application Domain

•

Application ID

•

Application Password


	CAUTION: Do not use the Change Settings option in the WebUI to enter or update these settings.

If you are protecting SharePoint Online or Teams, or both, select the Enter Global Administrator Credentials check box, and enter the user name and password for the administrator.

Verify that the administrator has the Global admin role assigned and is an owner or member of the Teams that you want to protect. Complete the Administrator Username field using the User Principal Name (UPN) format — for example,user1@testdomain.onmicrosoft.com.

To save the settings, click OK.

With the account properly configured, you can click the Plug‑in for Microsoft 365 node to display the available mailboxes and the OneDrive users and groups.

Improving backup and restore performance by modifying parameters in the configuration file

If you want to manage the performance of backup and restore jobs for Microsoft Outlook, SharePoint Online, Teams, and OneDrive accounts, you can modify the following parameters in the “nvoffice.cfg” file. The default location of this file is C:\Program Files\Quest\NetVault\config.

The values that you use depend on the value that you select for the Enable multi-streaming options for backup and restore jobs, as well as the bandwidth supported by your network.

The following tables list the parameters, their default settings, and a description of their impact.

Table 1. Parameters supported for network resilience
Parameter	Default	Description
Resiliency:Retry Count	3	Indicates the number of times that the plug-in runs GRAPH API after a failure occurs.
Resiliency:Retry Delay	5 (in seconds)	Indicates how long the plug-in should wait before running GRAPH API again after a failure occurs.

Table 2. Parameters supported for Outlook
Parameter	Default	Description
MsOutlook:Mails Without Attachment	1000	Indicates the number of email messages that one GRAPH API call can fetch of emails that do not have attachments. The 1000 value is the maximum allowed.
MsOutlook:Mails With Attachment	10	Indicates the number of email messages that one GRAPH API call can fetch of emails that have attachments. You can increase this value to increase the data-transfer rate, depending on the size of the attachments and network bandwidth.
MsOneDrive:Restore Chunk Size	5 (in MB)	Indicates the Chunk Size that can be used to restore — upload — mail attachments and attachments of type Event in chunks over OneDrive. The Chunk Size must be a multiple of 320 KiB (327,680 bytes). Using a Chunk Size that does not divide evenly by 320 KiB results in errors when committing some the files. You can increase this value to increase the data-transfer rate, depending on the network bandwidth. If you exceed a supported rate, the GRAPH API might generate a TIMEOUT exception.

Table 3. Parameters supported for OneDrive
Parameter	Default	Description
MsOneDrive:Backup Chunk Size	5 (in MB)	Indicates the Chunk Size that can be used to back up — download — files. The Chunk Size must be a multiple of 320 KiB (327,680 bytes). Using a Chunk Size that does not divide evenly by 320 KiB results in errors when committing some the files. You can increase this value to increase the data-transfer rate, depending on the network bandwidth. If you exceed a supported rate, the GRAPH API might generate a TIMEOUT exception.
MsOneDrive:Parallel Files Metadata per folder	1000	Indicates the number of files with metadata that one GRAPH API call can fetch. The 1000 value is the maximum allowed.
MsOneDrive:Restore Chunk Size	5 (in MB)	Indicates the Chunk Size that can be used to restore — upload — files. The Chunk Size must be a multiple of 320 KiB (327,680 bytes). Using a Chunk Size that does not divide evenly by 320 KiB results in errors when committing some the files. You can increase this value to increase the data-transfer rate, depending on the network bandwidth. If you exceed a supported rate, the GRAPH API might generate a TIMEOUT exception.
MsOneDrive:Enable Parallel Download per User	TRUE	Enables parallel downloads of OneDrive files for each OneDrive user. Otherwise, files download sequentially.
MsOneDrive:Maximum Parallel Download Sessions per User	20	Controls the number of parallel file downloads. By default, 20 download sessions occur at any time and at most, 20 files download in parallel.
MsOneDrive:File Size Limit in Parallel Download Sessions	2048 (in KB)	Filters out the files to be downloaded in parallel. Only files whose size is less than or equal to the value of this parameter download in parallel.

Table 4. Parameters supported for SharePoint Online
Parameter	Default	Description
MsSharePoint:Backup Chunk Size	5 (in MB)	Indicates the Chunk Size that can be used to back up — download — files. The Chunk Size must be a multiple of 320 KiB (327,680 bytes). Using a Chunk Size that does not divide evenly by 320 KiB results in errors when committing some the files. You can increase this value to increase the data-transfer rate, depending on the network bandwidth. If you exceed a supported rate, the GRAPH API might generate a TIMEOUT exception.
MsSharePoint:Enable Parallel Download per Site	TRUE	Enables parallel downloads of SharePoint files for each SharePoint site. Otherwise, files download sequentially.
MsSharePoint:Maximum Parallel Download Sessions per Site	20	Controls the number of parallel file downloads. By default, 20 download sessions occur at any time and at most, 20 files download in parallel.
MsSharePoint:File Size Limit in Parallel Download Sessions	2048 (in KB)	Filters out the files to be downloaded in parallel. Only files whose size is less than or equal to the value of this parameter download in parallel.
MsSharePoint:Parallel Files Metadata per Folder	1000	Fetches the metadata for a number of files in a single Graph API call. This is the maximum value possible. This parameter is only applicable when the value of the parameter [MsSharePoint:Enable Parallel Download per Site] is set to FALSE.

Table 5. Parameters supported for Teams
Parameter	Default	Description
MsTeams:Backup Chunk Size	5 (in MB)	Indicates the Chunk Size that can be used to back up — download — files. The Chunk Size must be a multiple of 320 KiB (327,680 bytes). Using a Chunk Size that does not divide evenly by 320 KiB results in errors when committing some the files. You can increase this value to increase the data-transfer rate, depending on the network bandwidth. If you exceed a supported rate, the GRAPH API might generate a TIMEOUT exception.
MsTeams:Enable Parallel Download per Team	TRUE	Enables parallel downloads of Teams files for each Teams channel. Otherwise, files download sequentially.
MsTeams:Maximum Parallel Download Sessions per Team	20	Controls the number of parallel file downloads. By default, 20 download sessions occur at any time and at most, 20 files download in parallel.
MsTeams:File Size Limit in Parallel Download Sessions	2048 (in KB)	Filters out the files to be downloaded in parallel. Only files whose size is less than or equal to the value of this parameter download in parallel.

Backing up data

•

Defining a backup-and-recovery strategy

•

Adding patterns to use for exclusion and inclusion

•

Performing backups

Defining a backup-and-recovery strategy

The purpose of creating Microsoft 365 backups is to recover a mailbox or site contents that are damaged from media failure or data corruption. Reliable use of backup for recovery requires a strategy that maximizes data availability and minimizes data loss, while accounting for defined business requirements.

A strategy is divided into two pieces: a backup piece and a restore piece.

•

The backup piece defines the type and frequency of backups that are required to meet the goals for availability of the database and for minimizing data loss.

•

The restore piece defines who is responsible for performing restores, and how restores should be performed to recover from the particular type of damage or failure.

Your backup plan should define at what intervals the backups are performed, how backups are stored, how long backups are retained, and how the backup media are reused.

The plug-in provides the following types of backup:

•

Full Backups only: You can choose to perform only Full Backups if the backup size is small, the backup window is not an issue, or storage media is not a constraint. In such scenarios, you can schedule Full Backups every night or every N hours depending on the frequency of updates.

If a failure occurs, the plug-in is only required to restore a single saveset.

•

Full and Incremental Backups: For quicker backups and minimum use of storage media, you can include Full and Incremental Backups in your strategy. For example, you can schedule Full Backups every Sunday and Incremental Backups every day or every N hours depending on the frequency of updates.

If a failure occurs, the plug-in is required to restore data from the recent Full Backup and each Incremental Backup in the backup sequence. The restore might take longer if several Incremental savesets have to be restored. For example, if the failure occurs on Saturday, the plug-in is required to restore the Full Backup taken on Sunday and Incremental Backups taken from Monday through Friday.


	NOTE: For Teams, Full Backups include all standard items. Incremental Backups include files, folders, and chat messages.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

NetVault Plug-in for Microsoft 365 13.1 - User Guide

Entering the configuration details in the plug-in

Improving backup and restore performance by modifying parameters in the configuration file

Backing up data

Defining a backup-and-recovery strategy