Considerations and Limitations

In this article

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

    General

    When Veeam Explorer for Microsoft SharePoint is installed on a server on which both Veeam Backup & Replication and Veeam Backup for Microsoft Office 365 are installed, the notification settings will be inherited from the Veeam Backup & Replication Global Notification settings.

    Status Recovery Limitations

    Consider the following when planning documents/list items recovery:

    Restore of Documents, Libraries and Lists

    Restore of List Items

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

    This logic leads to several peculiarities of list item restore, as described below.

    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 (as described in 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 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, site's "Welcome" page), consider that restore process will recover all versions of the item sequentially without deletions, adding them to Version History.
    • Restored Issue list items are assigned new Issue ID.
    • Restore of Time Card list is not supported.

    Restore of List Items with Links (Attachments)

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

    Restore of Surveys

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

    Restore of Sites

     

    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

    Data Type Limitations

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

    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:

    1. 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.
    2. 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 as follows:

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

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.