NetVault Plug-in for Microsoft 365 13.0 - Release Notes

Corrected an issue where only the default tmp location could be used to store temporary files, which caused the Restore view of endpoints to be empty when the temporary directory location for NetVault was set to a custom path.

DNPO365-1045

Corrected an issue where in cases of very high load, backup jobs and process would hang.

DNPO365-1046

Corrected an issue where backups of large numbers of Microsoft SharePoint files was slow.

DNPO365-1047

Corrected an issue where the plug-in was not deleting temporary old Full Backup index files after taking an Incremental Backup.

DNPO365-1050

Corrected an issue where backing up with an expired download URL resulted in a partial backup.

DNPO365-1051

If you perform a granular restore of Outlook or OneDrive, selecting the primary node — OneDrive or Outlook — and clearing any individual user nodes behaves correctly. However, if you select a user node and clear any subnodes, the plug-in restores all items for the selected user. That is, the plug-in ignores the cleared subnodes that are marked with a red X.

DNPO365-253, DNPO365-277

As designed, if a User/Group/SP is deleted and restored with one ID, and you attempt to restore it again, the plug-in must restore it with a new ID as the first ID exists.

Workaround: Delete the previously restored object, and then perform the new restore.

DNPO365-523

Restoring a user’s OneDrive data fails with the error “User’s mysite not found.”

Workaround: Complete the following steps:

DNPO365-699

When restoring Azure AD content and the default password “nvbu123*#$” is used in the Set password for user(s) on the Restore Option screen, the restore job completes with the error “The specified password does not comply with password complexity requirements.

Workaround: If the Azure AD user restore fails with aforementioned error, even though the password meets the complexity requirements, provide the same password in the config file under the “:Azure AD User Password” stanza and perform the restore again.

DNPO365-738

When restoring a modern SharePoint Online team site — which has an associated Office 365 Group that was automatically generated upon site creation — to a a nonexistent site, a new site is created but the associated Office 365 Group is not created or associated with the restored site.

DNPO365-751

Web parts of classic SharePoint Online sites do not restore, because they use a specific template.

DNPO365-752

When relocating the backup of a SharePoint Online site to a nonexistent site, a new site is created, but any custom permission levels that were created are not restored because the scope of the permission level is limited to the original site and its subsites.

DNPO365-754

If a SharePoint Online site contains a OneNote notebook, the notebook is not backed up and restored. The remainder of the site contents are restored.

DNPO365-793

Due to a limitation of the Microsoft Graph API, events of type Appointment are restored as type Event in the calendar.

DNPO365-909

If you restore a backup of Teams that includes a Team that was deleted for any reason, the restore does not include all App tabs for the deleted Team. Because a backup job for Teams does not include separate backups for App tabs, some App tabs, including OneNote, Planner, Forms, and Streams, are excluded from the restored Team.

DNPO365-989

Due to a limitation of the Microsoft Graph API, restoring a Teams backup does not include the Channel settings. It does restore the Team, its Channel, and Team settings.

DNPO365-994

Due to a limitation of the Microsoft Graph API, the contents of a private Channel, including Files and Chat messages, cannot be restored to the same Channel.

Workaround: After performing a restore, a new public Channel is created by using the name of the private Channel and adding a -Public suffix. All the files, including the Chat history file, are created in the Files section of the public Channel, as are the tabs from the private Channel.

DNPO365-999