commvault.com commvault.com
Solved

Getting Error decrypting password when restoring a SharePoint online backup

  • 14 June 2023
  • 3 replies
  • 117 views
H
Rank
Badge +2

Hi,

 

We are trying to restore a backup job from SharePoint Online, and we have successfully managed to run the backup job. However, we encounter the following error when attempting to restore.

 

[Error decrypting password]

 

We have tried restoring back to SharePoint Online, to the proxy server, and to a SharePoint on-premises SE server. Unfortunately, we receive the same error message regardless of where we try to restore to.

Does anyone have any tips or suggestions?

 

Thanks!

icon

Best answer by HOFH 23 June 2023, 12:54

View original

3 replies

O
Rank
Userlevel 6
Badge +15

Please review this document paying specific attention to #6:

https://documentation.commvault.com/search/essential/130548_restoring_sharepoint_online_site_to_its_original_location_in_place.html

  1. If not already created during client creation, create and enter the Azure storage account details. For more information, see Create a storage account in the Microsoft documentation.

    Note: During a restore operation, the Azure storage account is used as a staging location. Verify that the Azure storage account has Resource Manager as its deployment manager and General Purpose V1 or General Purpose V2 as its account kind. For replication, select the low-cost option Locally-redundant storage (LRS). In the Advanced tab, verify that Allow access from is set to the default option All networks.

Please update me with your findings.

H
Rank
Badge +2

Hi @Orazan,

 

Thanks for replying.

 

Initially, we suspected some issues with the setup of the storage account, but I thought it only mattered when restoring back to SharePoint Online. Does it have any significance when restoring to the proxy server or SharePoint on-premises?

 

We have checked the Storage account and it’s set up as described in the documentation.

H
Rank
Badge +2

This issue has been resolved.

The problem was related to the Index server

Reply


Terms & ConditionsCookie settings