Backup SharePoint 2010 Site Collection from Central Admin

This article explains how to backup and site collection in SharePoint 2010 as well as how to restore a previously backup-up site collection. Demonstrates how to: Use SharePoint 2010 Central Administration to back up a site collection, Use SharePoint 2010 Management Shell to restore a site collection.

Use Central Administration to back up a site collection in SharePoint Server

To back up a site collection using the SharePoint Central Administration tool, perform the following steps:

1. Open the SharePoint Central Administration site on a SharePoint Server (Start, All Programs, Microsoft SharePoint 2010 Products, SharePoint 2010 Central Administration).

2.       In Central Administration, on the Home page, in the Backup and Restore section, click Perform a site collection backup.

Site Collection Name: http://site/

File Name: d:\backup\Backupname.bak

3. On the Site collection backup page, select the site collection from the Site Collection list.
4. Type the local path of the backup file in the Filename box.
5. Enter the backup location and the filename ending with extension .bak in the Filename box. Select Overwrite Existing File if you want to overwrite, and then click Start Backup

After starting the backup, SharePoint 2010 displays the Granular Backup Job Status page. On this page, the granular backup progress can be monitored and displays site collection backup status and content export status.

Note

Site collection backups don’t include workflows.

6.       A backup of the site collection done using SharePoint Central Administration cannot be restored via the SharePoint Central Administration GUI. This backup can be restored only using Windows PowerShell cmdlet Restore-SPSite.

PowerPivotFarm.wsp error.Login to sharepoint server and run the below from managed power shell

Solution:

Install-SPSolution -Identity PowerPivotFarm.wsp -GACDeployment –Force

RDP Kill-Task Manager is not running under administrative privileges

It is possible that Task Manager is not running under administrative privileges. Following methods can resolve this issue:

------

Method 1:

------

1)... From a DOS prompt type "quser".

2)... This gives you a list of connected sessions with session IDs

3)... Identify the dodgy session ID and type 'logoff <SessionID>'.

                EG:C:\Windows\system32>logoff.exe 9

You can also check remote servers as well by doing:

quser /server:servername

Which gives you information about connected sessions for the specified server.

------

Method 2:

------

1.     Click Start, click All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.

2.     If you are prompted for an administrator password or for confirmation, type your password, or click Continue.

3.     At the command prompt, type taskmgr.exe, and then press ENTER.

(Task Manager starts with administrative privileges.)

 4.     Switch to the Users tab and log off a user account.

Connecting server via MSTSC shows blank screen

We had strange problem today with SQL server, as it was asking a restart since Thursday. After the reboot when I am trying to connect via MSTSC, it shows blank screen. When I am pinging my server I could able to see reply.

Solution:

Restart the User profile service will fix this kind of issue. We need to connect through another server from server manager and perform this activity

Attaching the same content database more than once to a SharePoint 2010 farm.

We can't attach the same content database (restored from backup with different DB name)

We need to run the below CMD from SharePoint application server to change the Database ID and attached to particular Web application.

Mount-SPContentDatabase -AssignNewDatabaseId "WSS_StagingContentDB_123" -WebApplication "http://site:84"

Bottom Line:

You cannot attach the same content database more than once to a farm, even on different Web applications. Each site collection in a content database has a GUID that is associated with it, which is registered in the configuration database.

Therefore, you cannot add the same site collection twice to the farm, even in separate Web applications. Although you can successfully attach the database in this situation, you will be unable to start the site collection.

If you need a duplicate copy of a site collection in the same farm, first attach the database that contains the site collection to a separate farm, and then use the Stsadm backup and restore operations to copy the site collection over to the other farm. The Stsadm backup and restore process creates a new GUID for the site collection.

Access Denied to SharePoint 2010 site collection administrator

We have an issue with SharePoint. We did content deployment from one Environment to another. After that it says Access Denied for me, even though am site collection administrator

Below is the troubleshooting steps performed.

I have Delete the web application and recreated (but not the content database)

I have Recreate the web application and reattach the content database(s)

I have IISRESET for good measure

I have checked in "Site collection Quotas and Locks option".

                -Set-SPSite -Identity "http://site:88" -LockState "Unlock"

I have changed the account for the APP Pool was running on IIS.

I have used managed account to perform the content deployment activity

I have added myself DB_owber to this particular site DB (SQL front)

Solution:

Sharepoint server Failed to read the acls for an item.Hence we need to run the following command from Sharepoint 2010 management Shell:

$webApp = Get-SPWebApplication http://Site:9999

$webApp.GrantAccessToProcessIdentity("Domain\serviceac")

ELSE

After configuring the Secure Store you need to go back to the secure store page, select your PerformancePoint target application check box then click on Refresh Key. You will need to renter your pass phrase then click OK.

Input a passphrase in both fields.  I used “The wise man would rather be sat on by a bee” for the Dev environment and Test

SharePoint Server Architecture

Overview:

This guide details the SharePoint Architecture on Lab environments. It does not include Pre-Production or Production environments.

SharePoint Three Tiers Architecture:

SharePoint fundamentally a three-tiered application Web, Application and Data tier.

The web tier will have server or servers running in Windows server Internet Information Services (IIS) which responds to end user request for information and deliver the content to the user.

The Application tier the Service Application tier where various service applications runs and that are shared between farm members. List of applications like search service application, Managed Metadata Service, User Profile Synchronization Service etc.

The third tier is the database tier which runs SQL Server and that stores all content within a SharePoint environment.

SharePoint 2010 Hardware and Software Configuration Requirements:

Component	Requirement
Framework	SQL Server Setup installs the following software components required by the product: ·         .NET Framework 4.0 SP1 ·         SQL Server Native Client ·         SQL Server Setup support files
Software	Windows Server 2008 R2 SQL Server 2008 R2 SP1 Internet Information Services (IIS) Manager version 9.0 SharePoint 2010 SP1
Network Software	Network software requirements for the 64-bit versions of SQL Server 2008 R2 are the same as the requirements for the 32-bit versions. Supported operating systems have built-in network software. Stand-alone named and default instances support the following network protocols: ·         Shared memory ·         Named Pipes ·         TCP/IP ·         VIA
Virtualization	Not applicable.
Internet Software	Microsoft Internet Explorer 6 SP1 or a later version is required for all installations of SQL Server 2008 R2. Internet Explorer 6 SP1.
Memory	16 GB (SharePoint Servers), 64 GB RAM for SQL 01, 128 GB RAM for SQL 02
Hard Disk	C:  x GB  Operating System D:  x GB  Applications (*** Only on SharePoint servers) G:  x GB  Applications (*** Only on SQL Servers) H:  x GB  SQL Data (*** Only on SQL Servers) I:    x GB SQL Data (***Only on the Cube SQL Servers) O:  x GB  SQL Logs (*** Only on SQL Servers) T:   x GB  TempDB (*** Only on SQL Servers)
Drive	A CD or DVD drive, as appropriate, is required for installation from disc.
Display	SQL Server 2008 R2 graphical tools require Super VGA or higher resolution: at least 800x600 pixel resolution.
Other Devices	Pointing device: A Microsoft mouse or compatible pointing device is required.

Note:

We can set up a farm by installing everything related to SharePoint 2010 in a single server.

But in some production farm, SQL Server runs on a separate server and can have multiple front end web servers.