Considerations and Limitations

In this article

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

    General

    Using an internet proxy server is only possible in Veeam Explorer for Microsoft Exchange that comes as part of the Veeam Backup for Microsoft Office 365 distribution package.

    If you start item-level recovery directly for the backup of the SharePoint VM, mapping of a SharePoint site to a content database in the Restore wizard will fail, and Veeam Backup & Replication will display the following error: "Unable to find SQL Server VM hosting the content database for the selected SharePoint site".

    Backup of the same VM by both Veeam Backup & Replication and Veeam Agent for Microsoft Windows may be required, for example, if Microsoft SQL Server running on the VM operates as part of a failover cluster.

    Status Recovery Limitations

    Consider the following when planning recovery of documents and list items:

    Restore of Documents, Libraries and Lists

    Restore of List Items

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

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

    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 corresponding 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, it is recommended to 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 the corresponding section of this guide) or roll-back the whole SharePoint server VM to the desired state using any Veeam Backup & Replication recovery option.

    Also consider the following limitations:

    • If a lookup column in the dependent list has the enforced relationship behavior set to RestrictDelete, 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 Items with Custom Content Type

    For item restore, Veeam Explorer for Microsoft SharePoint uses content types that exist in the target library or list. If you restore an item with a custom content type, and the target location does not contain this content type, the restore process will fail with the following error: "Cannot find corresponding Content-Type for: 15_.000. Original ContentTypeID: ‘XXX’".

    Restore of Surveys

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

    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

     

    Considerations and LimitationsNote

    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 item(s) originally belonging to a list with no content approval required, to another list. If you try to restore such item(s) 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):

    1. If the retention policy for target list/document library is configured to Declare record automatically, only the last version of the item will be restored to target list/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 recovery item status will be set to Pending.
    2. Alternatively (with different retention policy settings), all versions of the original item will be restored to target list/library.
      Besides, if Require content approval for submitted items was enabled for the original list, then after recovery item status in the content approval workflow will be also restored, except for the states listed (see "Status Recovery Limitations" above).