SharePoint 2019 restore site collections takes long time

SGH 1,211 Reputation points

When I do the restore for a site collection whose backup file size is 1.2 GB, it takes more than 3 hours to complete when another site collection of ~ 0.9 GB takes 15 minutes to complete. How can I monitor what is causing the delay. Is there a way to define this restore command as a job in central administration and monitor it.

Right now as it does not produce any logs , I am not able to see what causes the delay.

SharePoint Server
SharePoint Server
A family of Microsoft on-premises document management and storage systems.
2,148 questions
SharePoint Server Management
SharePoint Server Management
SharePoint Server: A family of Microsoft on-premises document management and storage systems.Management: The act or process of organizing, handling, directing or controlling something.
2,761 questions
0 comments No comments
{count} votes

2 answers

Sort by: Most helpful
  1. JoyZ 18,026 Reputation points

    @SGH ,

    If you are using powershell to backup and restore the site, there is no such status check similar to that in UI:

    Sometimes, system resources and network elements also affect backup and recovery performance.

    Here is an article about Backup and restore best practices in SharePoint Server for your reference:

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

  2. sadomovalex 3,621 Reputation points

    if you use Restore-SPSite cmdlet for restore then backup then you may enable verbose logging and check ULS logs during restore process. Common reasons of slowness of site collection restore are many versions of the files in doclibs, orphaned custom features (features which were activated on site collection but then were uninstalled from the farm), features with long running event receivers). You may try to indicate these errors from ULS log.

    0 comments No comments