SharePoint

Site Recycle Bin (Service Pack 1 and CodePlex) FAQs

Do I need to uninstall the Site Recycle Bin from CodePlex if I plan to use the Site Recycle Bin in Service Pack 1?

It depends on what you’re looking for.  The Site Recycle Bin available through CodePlex will capture deleted Site Collections and Sites to disk, Site Recycle Bin in Service Pack 1 copies the Site Collections and Sites to an auxiliary SQL table until they are permanently deleted at which point are managed by Gradual Site Deletion.  Once a Site Collection or site enters this Garbage Collection phase it will be managed by the Site Recycle Bin on CodePlex and copied to disk.  In theory you could have both.  The CodePlex Site Recycle Bin to provide archival and the Site Recycle Bin in Service Pack 1 to provide quick recovery and enable Site Collection administrators to perform self-service restores.

What happens to deleted Site Collections?  Do they ever get deleted?

These objects are purged.

There already is Web application property that controls the retention period for the Site Collection level Recycle Bin.  The same property is used for the deleted Site Collections themselves; when the Site Collection was deleted prior to a specified period (30 days), the timer job permanently removes it from the Content Database.  A Site Collection in the process of being permanently removed can no longer be restored.

Standard
Administration, SharePoint

Service Pack 1 Move-SPSite w/ ‘shallow copy’

Service Pack 1 introduces a new method of moving Site Collections between Content Databases where RBS is used known as ‘shallow copy’.

Overview

What is ‘shallow copy’?

‘Shallow copy’ refers to moving structured content without moving the underlying unstructured content.  With SharePoint 2010 Products ‘shallow copy’ moves the structured Site Collection data across Content Databases without moving the unstructured data which is comprised of user created content such as PowerPoint Presentations, Word Documents, etc.

What is a ‘shallow copy’ migration?

‘Shallow copy’ migration refers to a migration technique in which structured Site Collection data is moved across Content Databases while the unstructured BLOB data remains untouched in its originally configured BLOB store.

What is a deep copy migration?

Deep copy refers to a migration technique is which unstructured BLOB data is passed through the Object Model when its associated Site Collection is moved across Content Databases, I.e. download and upload of BLOB data.

Benefits

‘Shallow copy’ capabilities provide a number of benefits, for example, shallow copy migration enables seamless movement of Site Collections across Content Databases while improving performance through enabling the unstructured data to remain in the originally configured BLOB store.  In scenarios where the same RBS provider is configured in both the source and destination Content Database the structured Site Collection data is moved without copying the underlying BLOB data – transferring only the ownership information between Content Databases.

In many SharePoint 2010 Products deployments unstructured BLOB data comprises 80% or more of the total content, ‘shallow copy’ helps administrators avoid deep copy migration significantly reducing the time required to move Site Collections between Content Databases.

Prerequisites

The following prerequisites are required to implement ‘shallow copy’ migrations.

SQL Server 2008 R2 Public Cumulative Update
SharePoint Server 2010 Service Pack 1

Administrators can leverage ‘shallow copy’ functionality in Service Pack 1 through both the Object Model and Windows PowerShell using the Move-SPSite Windows PowerShell CmdLet with the -RbsProviderMapping parameter.  The -RbsProviderMapping parameter defines the mapping between the RBS providers in the source and destination Content Databases.

Move-SPSite -Identity siteUrl -DestinationDatabase databaseName -RbsProviderMapping
    @{"sourceProvider1"="targetProvider1", "sourceProvider2"="targetProvider2"}

When using the -RbsProvideMapping parameter the ownership of the RBS pool (subset of the BLOB store documents) used by the specified Site Collection is transferred from the source to the destination Content Database without moving the underlying unstructured data associated with that Site Collection.

‘Shallow copy’ is also an efficient migration method when moving from EBS to RBS.  In an EBS to RBS scenario the EBS token is moved from the source to the destination Content Database.

For additional information on Remote BLOB Store Architecture see http://msdn.microsoft.com/en-us/library/gg316769.aspx.

For additional information on the Move-SPSite CmdLet see http://technet.microsoft.com/en-us/library/ff607915.aspx.

Standard
Administration, SharePoint

Now Serving Larger Databases…

Today we are announcing some important and exciting changes to our software boundaries and limits for SharePoint 2010 Products, in summary SharePoint 2010 Products will now support content databases up to 4TB.  However, prior to considering multi-terabyte databases you should thoroughly review the following whitepapers:

Managing multi-terabyte databases with SharePoint 2010 (http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26700)

Abstract

Managing large content databases with SharePoint 2010 requires careful planning and consideration to include capacity management, performance, and data protection.  This whitepaper provides guidance to support these considerations to include additional resources to support this guidance.

Database Maintenance for SharePoint 2010 Products (http://www.microsoft.com/download/en/details.aspx?id=24282)

Abstract

This white paper provides information and guidelines for maintaining the databases that host Microsoft® SharePoint® 2010 data and configurations. It describes and provides examples of the database maintenance tasks that we recommend when using SharePoint 2010.

Before you implement any database maintenance tasks or modify your SharePoint 2010 databases, read the following support article: Support for changes to the databases that are used by Office server products and by Windows SharePoint Services (http://go.microsoft.com/fwlink/?LinkId=110812&clcid=0x409).

To learn more about this announcement see the SharePoint Team Blog at http://sharepoint.microsoft.com/blog.

To learn more about the new software boundaries and limits see SharePoint Server 2010 capacity management: Software boundaries and limits at http://technet.microsoft.com/en-us/library/cc262787.aspx.

Standard
Administration, SharePoint

SharePoint 2010 Cumulative Updates and Service Packs

Updated June 29, 2011

SharePoint Server 2010 Cumulative Updates and Service Packs

File Version Description Downloads and Documentation
14.0.5114.5003 June 2010 Cumulative Update KB983497
KB2124512
KB2182938
KB2204024
KB2281364
14.0.5123.5000 August 2010 Cumulative Update KB2352342 
KB2352355
14.0.5128.5000 October 2010 Cumulative Update KB2394320
14.0.5130.5002 December 2010 Cumulative Update KB2459257
14.0.5136.5002 February 2011 Cumulative Update KB2475878
14.0.5138.5001 April 2011 Cumulative Update KB2512800
14.0.6029.1000 Service Pack 1 KB2460045
14.0.6106.5000 June 2011 Cumulative Update KB2356599

SharePoint Foundation 2010 Cumulative Updates and Service Packs

File Version Description Downloads and Documentation
14.0.5114.5003 June 2010 Cumulative Update KB2028568
14.0.5123.5000 August 2010 Cumulative Update KB2352346
14.0.5128.5000 October 2010 Cumulative Update KB2394323
14.0.5130.5002 December 2010 Cumulative Update KB2459125
14.0.5136.5002 February 2011 Cumulative Update KB2475880
14.0.5138.5001 April 2011 Cumulative Update KB2512804
14.0.6029.1000 Service Pack 1 KB2460058
14.0.6106.5000 June 2011 Cumulative Update KB2356591

Resources

SharePoint 2010 Products Updates Resource Center

Standard
Administration, SharePoint

Service Pack 1 – Site Recycle Bin

Site Recycle Bin

Service Pack 1 introduces long awaited Site Recycle Bin functionality that enables self-service recovery of site collections and sites. In the past IT Professionals were tasked with restoring entire databases to recover deleted site collections and sites and would generally require expensive restore environments to support the task. Now in Service Pack 1 administrators can quickly and easily recover site collections and sites accidentally deleted by their owners in a process similar to that of the Recycle Bin we have for Lists, Libraries, and Documents.

The Site Recycle Bin leverages Gradual Site Delete through implementing a delay between Gradual Site Delete and permanent deletion of the deleted Site Collection.

User Interface

Users are presented with new text when deleting Sites instructing users that all site content will be sent to the site collection Recycle Bin (see Figure 1 Deleting http://sharepoint.contoso.com/sites/customers/Fabrikam).

Figure 1 Deleting http://sharepoint.contoso.com/customers/Fabrikam

DeleteSite1

Site Restore

Site Collection administrators can restore deleted Sites in the same manner through which Items, Lists, and Libraries are restored through the Recycle Bin; however, the size of the Site is not reported through the user interface which differs from content to include Items, Lists, and Libraries.  To restore a Site, the Site Collection administrator selects the checkbox next to the Site to be restored and selects Restore Selection (see Figure 2 Restoring http://sharepoint.contoso.com/sites/customers/Fabrikam).

Figure 2 Restoring http://sharepoint.contoso.com/sites/customers/Fabrikam

DeleteSite2

NOTE

In the event the Site has been recreated using the same Url, the Site must first be renamed or deleted for the restore to succeed; however, when restoring My Site personal sites, any newly created My Site personal site using the same Url as the Site to be restored is overwritten.

The Site Recycle Bin in SharePoint 2010 leverages the retention policies specified at the Web application level for the Recycle Bin in SharePoint 2010.

Object Model

SPWebApplication.GetDeletedSites(Url) returns a SPDeletedSitesCollection that contains all SPDeletedSites with the specified Url.

SPDeletedSiteCollection

SPDeletedSiteCollection represents a collection of SPDeleteSite objects or Site Collections that are associated with a particular Web application, including a top-level Web site and all its sub-sites.

SPDeletedSite

SPDeletedSite represents a collection of deleted sites in a Web application, including a top-level Web site and all its subsites.

SPDeletedSite Properties

SiteId returns the Site Id (GUID) associated with the specified SPDeletedSite.

Url returns the Url associated with the specified SPDeletedSite.

ContentDatabaseId returns the Id of the Content Database associated with the deleted Site.

Restore restores the deleted site collection.

To learn more about Service Pack 1 for SharePoint 2010 see my post on the SharePoint Team Blog at http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=973.

Standard
Administration, SharePoint

Service Pack 1 – Storage Metrics (StorMan.aspx)

In SharePoint 2010 we removed StorMan.aspx (Storage Space Allocation) (see http://support.microsoft.com/kb/982587/EN-US) which in previous versions of SharePoint enabled granular management and insight into storage. For example, the page would show you the top 100 documents or document libraries in terms of size. With that information end users could the page to clean up content from their site(s) by deleting the large content that they no longer needed. In Service Pack 1 we are bringing back an improved StorMan.aspx, enabling users to better understand where their quota is going and act upon that information to reduce the size of their sites.

Storage Metrics provide insight into how storage is being used across Site Collections and Sites enabling administrators and owners to quickly identify content that can be archived or removed in order to remain within their allocated quotas.

To begin using Storage Metrics select Site Actions, and then click Site Settings.

From Site Settings select Storage Metrics under Site Collection Administration (see Figure 1 Site Settings http://sharepoint.contoso.com/).

Figure 1 Site Settings http://sharepoint.contoso.com/

StorMan1

Storage metrics will be displayed for the selected Site Collection/Site (see Figure 2 Storage Metrics http://sharepoint.contoso.com/).

Figure 2 Storage Metrics http://sharepoint.contoso.com/

StorMan2

To learn more about Service Pack 1 for SharePoint 2010 see my post on the SharePoint Team Blog at http://sharepoint.microsoft.com/blog/Pages/BlogPost.aspx?pID=973.

Standard