サポートと今すぐチャット
サポートとのチャット

NetVault Plug-in for Microsoft 365 13.2 - User Guide

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.

Adding patterns to use for exclusion and inclusion

From the backup selection tree, you can create and store patterns of mailboxes, mailbox folders, users, sites, and teams that you want to include and exclude for all selected user mailboxes that you back up and for each tenant. When you specify patterns to exclude or include, or both, the plug-in stores them with a Backup Selection Set. When you submit a backup job, you can select the set with the stored patterns. The plug-in then populates the backup list with mailboxes whose folder names meet the specified inclusion and exclusion patterns. There is no limit to the number of patterns that you can specify. Be aware that the plug-in gives priority to exclusions.

 
To add patterns to use for exclusion and inclusion
1
In the Navigation Pane, click Create Backup Job, and click next to the Selections list.
2
In the selection tree, open the applicable client node.
3
Click Plug‑in for Microsoft 365, and select View Inclusion/Exclusion from the context menu.
The plug-in adds two subnodes, Include Patterns and Exclude Patterns, to the Microsoft 365 node.
4
To specify an exclusion pattern, which takes priority over inclusion patterns, complete the following steps:
a
Click Exclude Patterns, and then select one of the following options:
•
Add Folder Pattern
 
* 
NOTE: The Add Folder Pattern feature supports only mailbox folders; it does not support OneDrive, SharePoint Online, or Teams.
•
Add User Pattern
 
* 
NOTE: The Add User Pattern supports exclusion and inclusion of selected users, sites, and teams.
b
In the Enter exclude pattern dialog box, type the pattern to exclude, and click OK.
Use a Portable Operating System Interface (POSIX) regular expression (regex) to create an exclusion pattern. For example, if you want to exclude the Junk E-Mail folder, type Junk*.
5
To specify an inclusion pattern, complete the following steps:
a
Click Include Patterns, and then select one of the following options:
•
Add Folder Pattern
•
Add User Pattern
b
In the Enter include pattern dialog box, type the pattern to include, and click OK.
Use a POSIX regex to create an inclusion pattern. For example, if you want to select all mailboxes that start with A to G or a to g, type ^[a-gA-G].
 
* 
NOTE: The exclusion and inclusion feature supports all regex patterns.
The plug-in lists an informational node with the new patterns below the corresponding subnodes. When you set up a backup job, you can select or clear the applicable patterns.
6
When you are finished, click Save, enter a name in the Create New Set dialog box, and click Save.
The name can contain alphanumeric and nonalphanumeric characters, but it cannot contain non-Latin characters. On Windows, there is no length restriction. However, a maximum of 40 characters is recommended on all platforms.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択