Sharepoint Sites getting locked

%3CLINGO-SUB%20id%3D%22lingo-sub-911600%22%20slang%3D%22en-US%22%3ESharepoint%20Sites%20getting%20locked%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911600%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Team%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20%26nbsp%3B%20We%20are%20facing%20SharePoint%20site%20getting%20locked(adding%20content%20prevented)%20in%20Central%20admin%20in%20every%20weekend%20for%20fast%20few%20months.%20Every%20week%20we%20manually%20getting%20unlocked%20this%20site%20to%20make%20site%20is%20work.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20analysed%20the%20issue%20our%20side.%20But%20still%20we%20are%20not%20able%20to%20figure%20out%20the%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20find%20our%20below%20analysis.%3C%2FP%3E%3CP%3E1.%26nbsp%3B%20Every%20week%20end%20we%20do%20back%20up%20of%20the%20sharepoint%20site%20using%20commvalut%20tool.%26nbsp%3B%20For%20large%20file%20site%20we%20are%20facing%20this%20issue.%26nbsp%3B%20Not%20sure%20what%20is%20happening%20in%20the%20background%20operation.%26nbsp%3B%20We%20suspect%20during%20that%20time%2C%20the%20site%20is%20getting%20locked.%3C%2FP%3E%3CP%3E2.%20Then%20we%20found%20that%2C%20SQL%20server%20CPU%20usage%20is%20almost%20full.%26nbsp%3B%20We%20do%20upgrade%20sql%20server%20cpu%20for%20minimize%20the%20performance.%20But%20still%20no%20luck.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENote%3A%20We%20recently%20upgreaded%20SQL%20server%202008%20to%20SQLServer%202012%20for%20database.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%20and%20suggestions%20much%20appreciated.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3ESivaraman.P%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-911600%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharepoint%20site%20locked%20in%20CA%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-911691%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20Sites%20getting%20locked%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-911691%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F425452%22%20target%3D%22_blank%22%3E%40Sivaramancts%3C%2FA%3E%26nbsp%3BWhen%20you%20do%20backup%20process%20the%20databases%20will%20be%20locked%20for%20sometime%20and%20then%20released%2C%20it%20seems%20release%20part%20is%20not%20working%20as%20expected%2C%20since%20you%20use%20Commvault%20it%20can%20be%20the%20culprit%20in%20this%20case%2C%20have%20you%20checked%20with%20your%20Commvault%20support%3F%3C%2FP%3E%3CP%3EWhen%20a%20backup%20process%20fails%20it%20can%20leave%20the%20sites%20locked%20as%20you%20are%20already%20mentioning%20that%20it%20happens%20for%20big%20sites%20it%20should%20be%20the%20case.%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20you%20have%20Site%20Quotas%20for%20sites%3F%20It%20can%20also%20have%20impact%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-914738%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20Sites%20getting%20locked%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-914738%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F410289%22%20target%3D%22_blank%22%3E%40SinhaKislay%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20verified%20with%20the%20Commvault%20team.%26nbsp%3B%20They%20are%20working%20on%20this.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThey%20are%20working%20on%20this%20issue.%26nbsp%3B%20They%20are%20analyzing%20could%20be%20two%20solutions.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1.%20Low%20disk%20space.%3C%2FP%3E%3CP%3E2.%26nbsp%3B%20When%20back%20starts%20from%20Commvault%2C%20already%20SQL%20backup%20was%20running%20in%20the%20background.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-914852%22%20slang%3D%22en-US%22%3ERe%3A%20Sharepoint%20Sites%20getting%20locked%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-914852%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F425452%22%20target%3D%22_blank%22%3E%40Sivaramancts%3C%2FA%3E%26nbsp%3Byes%20these%20could%20be%20scenarios%2C%20good%20luck%2C%20i%20hope%20my%20post%20was%20helpful%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
New Contributor

Hi Team,

          We are facing SharePoint site getting locked(adding content prevented) in Central admin in every weekend for fast few months. Every week we manually getting unlocked this site to make site is work. 

 

We analysed the issue our side. But still we are not able to figure out the issue. 

Please find our below analysis.

1.  Every week end we do back up of the sharepoint site using commvalut tool.  For large file site we are facing this issue.  Not sure what is happening in the background operation.  We suspect during that time, the site is getting locked.

2. Then we found that, SQL server CPU usage is almost full.  We do upgrade sql server cpu for minimize the performance. But still no luck. 

 

 

Note: We recently upgreaded SQL server 2008 to SQLServer 2012 for database. 

 

Any ideas and suggestions much appreciated. 

 

Regards,

Sivaraman.P

 

 

 

 

 

 

3 Replies
Highlighted

@Sivaramancts When you do backup process the databases will be locked for sometime and then released, it seems release part is not working as expected, since you use Commvault it can be the culprit in this case, have you checked with your Commvault support?

When a backup process fails it can leave the sites locked as you are already mentioning that it happens for big sites it should be the case. 

Do you have Site Quotas for sites? It can also have impact?

Highlighted

@SinhaKislay 

I have verified with the Commvault team.  They are working on this. 

 

They are working on this issue.  They are analyzing could be two solutions.

 

1. Low disk space.

2.  When back starts from Commvault, already SQL backup was running in the background.

Highlighted

@Sivaramancts yes these could be scenarios, good luck, i hope my post was helpful