Veeam Backup for Microsoft 365 8
Veeam Explorers User Guide
Related documents
Search

Considerations and Limitations

This section lists considerations and limitations of Veeam Explorer for Microsoft SharePoint.

General

Consider the following:

  • When Veeam Explorer for Microsoft SharePoint is installed on a server on which both Veeam Backup & Replication and Veeam Backup for Microsoft 365 are installed, the notification settings will be inherited from the Veeam Backup & Replication Global Notification settings.
  • Restore using PowerShell Direct, VIX API or vSphere Automation API is not supported.
  • Restore of backed-up Microsoft SharePoint data to another Microsoft organization cannot be performed to a target Microsoft SharePoint organization whose version is earlier than the version of the restored backups.

General Restore Limitations

If your Veeam Explorer for Microsoft SharePoint comes as part of a standalone Veeam Backup for Microsoft 365 installation, you cannot restore from Veeam Backup & Replication backups by default. To enable this functionality, install Veeam Backup & Replication Enterprise edition or higher on the machine.

Status Restore Limitations

Consider the following when planning documents or list items restore:

Restore of Documents, Libraries and Lists

Consider the following:

Restore of List Items

Consider that when restoring a list item, Veeam Explorer for Microsoft SharePoint works in the following way:

  • Deletes an existing item.
  • Creates the latest version of the item anew using data from the backup.
  • Checks whether it is declared as a record.
  • If the check is a success, the process finishes.
  • If not, the created version is deleted and item versions are restored sequentially.

This logic leads to the following peculiarities of list item restore:

  • If a list or list items column is used as a lookup column in the dependent list, consider that restoring an item from the source list causes the relevant items deletion in the dependent list.
  • If a lookup column in the dependent list has the enforced relationship behavior set to Cascade Delete, then restoring an item from the source list may cause item deletion in the dependent list due to Microsoft implementation. For more information, see this Microsoft article.

To prevent this issue, you should turn off enforced relationship behavior. As a work-around, you can roll-back the SharePoint database using Veeam Explorer for Microsoft SQL Server (see this section) or roll-back the whole SharePoint server VM to the desired state using any Veeam Backup & Replication recovery option.

The following limitations should also be considered:

  • If a lookup column in the dependent list has the enforced relationship behavior set to Restrict Delete, then item restore with Veeam Explorer for Microsoft SharePoint will fail.
  • If an .ASPX page references an item using ItemID, this reference may fail to restore (as the item will be created anew with a different ItemID).
  • If a list item cannot be deleted (for example, the Welcome page of the site), consider that restore process will restore all versions of the item sequentially without deletions, adding them to Version History.
  • Restored Issue list items are assigned new IssueID.
  • Restore of Time Card list is not supported.

Restore of List Items with Links (Attachments)

Consider the following when planning for the restore of list items with links (attachments):

  • If the retention policy for target list or target document library was configured to Declare record automatically, only the last version of the item will be restored to target list or target document library. Target retention policy settings will be applied to restored item (Declare record). However, links (attachments) will not be restored.
  • If Declare this item as a record action was originally applied to list item, such item will not be restored.

Restore of Surveys

Consider the following limitations when planning for the restore of surveys, survey questions and responses:

  • Survey items can be restored to a new survey, created automatically by Veeam Explorer for Microsoft SharePoint in the specified destination instead of the previously deleted survey. However, if a new survey is created by user from scratch (not replacing a deleted one) – items cannot be restored to such a survey.
  • A survey can be restored to an existing target survey only if that target survey includes at least one item (question) same as survey questions stored in the content database.
  • If a survey question was not answered completely in the source survey, after restore the response status in the target survey will be set to Completed, anyway.
  • When restoring a single response to a survey, target response item with the same number will be deleted and restored item will be placed in the target survey after the last numbered response.

For example, if the target survey has responses #1-15 and you try to restore a response that used to be #6 on source – then target response #6 will be deleted and restored response will be assigned #16.

Restore of Sites

Consider the following:

  • When restoring site collections, make sure that such collections exist in the target location; Veeam Explorer for Microsoft SharePoint does not create site collections.
  • Before restoring team sites for a tenant organization with modern app-only authentication, make sure that a user account used for authorization has access to the root SharePoint site of this tenant organization.
  • When restoring team sites, Veeam Backup for Microsoft 365 does not restore team site owners or Microsoft 365 group members.
  • If you plan to restore SharePoint site pages, consider that Veeam Explorer for Microsoft SharePoint does not support restore of items which are not stored in the SharePoint content database (in particular, pages, page references and items based on default templates). Such items cannot be restored (neither by Restore nor by Save menu option), except for data from Wiki Content (text and images) which is stored in the database. Thus, site pages containing only text and images can be restored and displayed properly.

Note

Consider the following:

  • In case you attempt to restore such items, the following error message will be logged: Item <item> is skipped: restoration of items based on SharePoint default template is not supported.
  • In case you attempt to save such items, the following error message will be logged: Unable to save document <item>. Document content is not available.

Export and Import

Consider the following:

  • In on-premises Microsoft SharePoint organizations, importing exported Picture Library may result in IDs changed for some items.
  • Importing an exported Project Tasks list does not preserve column order.
  • Importing an exported SharePoint list does not preserve Validation Settings.
  • Export is unavailable for backups created by Veeam Backup for Microsoft 365. The operation is available only for backups created by Veeam Backup & Replication.
  • Make sure to view information about unsupported Microsoft SharePoint lists before exporting them. In particular, hidden lists are not displayed in Veeam Explorer for Microsoft SharePoint after a site backup. Thus, such lists cannot be exported. For more information, see Unsupported SharePoint Lists.
  • Export of empty SharePoint folders is not supported.

Data Type Limitations

Consider the column (field) data type when planning for the restore of your SharePoint libraries or lists:

  • If source column (field) data type was set to Lookup, but the referenced list or library was deleted, such columns (fields) will not be restored even if you restore that referenced list. The reason is that if referenced list is deleted, the reference (link) to that list is no longer valid.
  • If source column (field) data type was set to Managed Metadata, such columns (fields) will not be restored.

Workflow-Related Considerations

You may need to restore the items originally belonging to a list with no content approval required, to another list. If you try to restore such items to a list that requires content approval, item version and status will be modified in the following way:

  • If a target list is configured to include major versions only, then all versions of restored item will become major (despite the original versioning); item status will be set to Pending.
  • If a target list is configured to include both major and minor versions, then all versions of restored item will become minor (despite the original versioning); item status will be set in the following way:
  • If the last version (original) was major — status will be set to Pending.
  • If the last version was minor — status will be set to Draft.

Also, consider the following when planning for the restore of list items (with or without content approval originally required):

  • If the retention policy for target list or target document library is configured to Declare record automatically, only the last version of the item will be restored to target list or target document library. Target retention policy settings will be applied to restored item (Declare record). Besides, if Require content approval for submitted items was enabled for the original list, then after restore item status will be set to Pending.
  • Alternatively (with different retention policy settings), all versions of the original item will be restored to target list or target document library. Besides, if Require content approval for submitted items was enabled for the original list, then after restore item status in the content approval workflow will be also restored, except for the states listed. For more information, see Status Restore Limitations.

Page updated 9/10/2024

Page content applies to build 8.0.5.20

View all results across Veeam
Back to document search