SharePoint 2010 Disaster Recovery Part 1

What is Disaster Recovery?

In IT, Disaster recovery means to protect your data from the unexpected disaster.

Natural disaster like Earthquake, flood ECT.
Manmade disaster (something not do intentionally). It may be some miss configuration of files. Unintentionally delete the some of the important files.

SharePoint 2010 End User Recovery

Recycle Bin (Two Stage)
Document Versioning

Recycle Bin (Two Stage)

First-stage recycle bin –

When users delete Files/List items it goes to First stage recycle bin. Also called "End user Recycle bin". Content in this recycle bin is counted on Site quota, so when you delete a file, it goes to recycle bin, but you won’t get any additional free space, still it occupies site quota. This recycle bin is accessible to the end users, and its Security trimmed (Even a site collection admin can't see end user's recycle bins, He/She needs to use "Site collection Recycle bin" to see end user's recycle bin.

Second-stage recycle bin –

When the content deleted from First-stage recycle bin or its life time on First-stage recycle bin is over then it moved to Second stage recycle bin. Here Items not counted on Site quota, But total space occupied by second stage recycle bin is based on Central administration setting "Second stage Recycle bin Percentage in Live site's Quota". This Recycle bin acts at site collection level, and can be accessed only to site collection Admin.

Document Versioning:

When you store critical documents in the SharePoint libraries, sometimes it becomes necessary to track all the changes and to maintain version history for them. There might be a time when you would need to restore files back to an older version if any inadvertent change happens. You can also track changes for auditing purposes. Versioning provide you a facility to restore the last version with existing version. If you delete the version from the SharePoint List it will move to the Recycle bin you can restore the specific version from there.

Comments

SharePoint RPC Protocols Examples Using OWSSVR.DLL

What is SharePoint RPC Protocols? Part 1 This reference includes information about the methods and usage of SharePoint Foundation Remote Procedure Call (RPC) protocol. This protocol can be used in Win32-based applications or in ASPX applications to make HTTP POST requests to the server. Methods in this protocol that do not modify the contents of the database can also be used in URL protocol to make HTTP GET requests. Definition taken from http://msdn.microsoft.com/en-us/library/ms448359.aspx You will find the OWSSVR.DLL in SharePoint 2010 Server Physical Path: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\ISAPI and MOSS C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\ISAPI OWSSVR.DLL List of commands DialogView Display ExportList GetProjSchema GetUsageBlob HitCounter RenderView To read more about the OWSSVR.DLL command Please read the URL Protocol from Microsoft Blog having a URL http://msdn.microsoft.com/en...

SharePoint 2013 Search Database Part 1

SharePoint 2013 Search architecture drastically change, as earlier in FS4SP 2010 we have 2 search applications “FASTContentSSA” and “FASTQuerySSA” and 7 total database in use. Following are the List of DB (FS4SP) FASTContentSSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTQuerySSA Search Service Application DB Search Service Application Crawl Store DB Search Service Application Property Store DB FASTSearchAdminDatabase : Fast Search Admin Database In SharePoint 2013 search has only 1 Search Service application and 4 database in use. No property store database need any more, now the properties are directly stored inside the index component and all the index directly indexed to the physical system where FS4SP data comes from database as well as from the File system now data directly stored and indexed/ retried from the Physical disk because of this performance increase and search experien...

STS CryptographicException Error : Key set does not exist

Common mistakes Both SharePoint Site and SSO Site NOT running on the same application pool. Application pool identity user doesn’t have permission to access the certification. Solution to this problem Set the same identity pool to : 2. Be sure to grant rights to the certificate for the App Pool running the web service Start -> Run -> MMC File -> Add/Remove Snapin Add the Certificates Snap In Select Computer Account, then hit next Select Local Computer (the default), then click Finish On the left panel from Console Root, navigate to Certificates (Local Computer) -> Personal -> Certificates You're certificate will most likely be here. Right click on your certificate -> All Tasks -> Manage Private Keys Set you're private key settings here. Add app pool account Reset iis

SharePoint For Developers

Search This Blog