Microsoft Sharepoint Backup Issue Resolution
Though Microsoft Sharepoint is very capable of managing electronic files and scanned documents in low volumes, it tends to bog down performance and cause back up headaches when working with large volume Microsoft Office SharePoint Server (MOSS) environments. These limitations present new challenges to the Sharepoint backup and restore process.
Sharepoint archiving and retention management issues
Also because of SharePoint’s Blob or Information Silo architecture, it’s difficult to determine which file is an official record, first rendition, or is suitable for sharepoint archiving. Copies are made and then resubmitted under a different Blob than the original file. The new file can also be identified as the achievable file. This means that you may have two separate Blobs with the same file residing in each as an achievable first rendition record. Because of this, it becomes very hard to deploy accurate and effective Sharepoint retention management practices.
Furthermore, organizations may archive all files in Tier 1 architecture to ensure that they do not delete the original file. This causes problems in performing file backup SLA’s, and can cause businesses to jeopardize any compliance, regulation, and governance policies. It is hard to determine who has security rights to each copy of a file spanned across multiple Blobs.