Getting Started SharePoint “2013” Web view18.07.2014 · Permissions for the SPTimerV4 timer service and SQL Server account in SharePoint 2013. The Windows SharePoint Services

Prepared by

Sriram BalaSharePoint Practice

Microsoft SharePoint 2013 -

Configuring High Availability BackupVerified Against Build #15.0.4128.1014

Configuing High Availability Backup 2

Table of ContentsConfiguring High Availability Backup....................................................................................4

Requirements to back up and restore SharePoint 2013....................................................4

Restrictions when you backup and restore SharePoint 2013.............................................5

How to create a shared folder...........................................................................................5

Configure backup and restore permissions...........................................................................6

Before you begin...............................................................................................................6

Permissions for the SPTimerV4 timer service and SQL Server account in SharePoint 2013.......................................................................................................................................... 6

Group memberships required to run backup and restore operations in Central Administration................................................................................................................... 6

Setting permissions to run SharePoint backup and restore operations by using Windows PowerShell......................................................................................................................... 7

To add a user to or remove a user from the SharePoint_Shell_Access role by using Windows PowerShell.......................................................................................................7

Backup solutions................................................................................................................... 8

Downloadable resources about backup................................................................................9

TechNet articles about backup for SharePoint 2013.............................................................9

Use Central Administration to back up a SharePoint farm..................................................10

To back up a farm by using Central Administration.........................................................10

Use SQL Server tools to back up a SharePoint farm...........................................................11

To back up the databases associated with a farm by using SQL Server tools.................11

Back up web applications...................................................................................................13

Use Windows PowerShell to back up a web application......................................................13

To back up a web application by using Windows PowerShell..........................................13

Use Central Administration to back up a web application...................................................14


To back up a web application by using Central Administration.......................................14

Use SQL Server tools to back up a web application............................................................16

To back up a web application by using SQL Server tools.................................................16

Back up service applications...............................................................................................17

Use Central Administration to back up a service application in SharePoint.....................17

Back up content databases................................................................................................19

Use Central Administration to back up a content database in SharePoint 2013.................19

To back up a content database by using Central Administration.....................................19

Use SQL Server tools to back up a content database in SharePoint 2013..........................21

To back up a content database by using SQL Server tools..............................................21

Back up site collections......................................................................................................22

Use Central Administration to back up a site collection in SharePoint 2013....................22

To back up a site collection by using Central Administration..........................................22

Back up apps...................................................................................................................... 23

Back up content databases................................................................................................23

Back up the configuration database...................................................................................24

Back up the Secure Store Service application database.....................................................24

Back up the App Management service application database..............................................24

Back up a site collection.....................................................................................................25

To back up a site collection by using Windows PowerShell.............................................25

Workflow Backup................................................................................................................27

Backup solution packages in SharePoint 2013...................................................................29

To back up trusted solutions by using Central Administration.........................................29

To back up trusted solutions by using Windows PowerShell............................................31


Configuring High Availability BackupIt is important to make sure that you have backed up and can recover the data that you need if a failure occurs. Consider the information, procedures, and precautions in this article before you backup and restore the environment. This article discusses restrictions and requirements for backup and recovery and how to create a shared folder on the network that can receive backed-up data.

Requirements to back up and restore SharePoint 2013

Before you back up data, create a shared folder that stores the data. For best performance, create this folder on the database server. If you want to archive the backups to another server, you can copy the whole backup folder to that server after backup is complete. Be sure to copy and move the whole backup folder and not the individual backup folders under this folder.

The SQL Server VSS Writer service, which is available with SQL Server 2008 R2and SQL Server 2012 database software, must be started for the SharePoint 2013 VSS Writer service to work correctly. By default, the SharePoint 2013 VSS Writer service is not automatically started.

Make sure that the SharePoint Foundation 2013 Administration service is started on all farm servers before you perform a backup. By default, this service is not started on stand-alone installations.

Make sure that the user accounts that you want to perform a backup have access to the shared backup folder.

If you use Central Administration to back up, the database server's SQL service account, the Timer service account, and the Central Administration application pool identity account must have Full Control permissions to the backup locations.

The database server and farm server that you want to back up must be able to connect to one another.

If you use SQL Server with Transparent Data Encryption (TDE), and you use either SharePoint tools or SQL Server tools to back up your environment, the TDE encryption key is not backed up or restored. You must manually back up the key. When you restore the environment, you must manually restore the key before you restore the data..


Restrictions when you backup and restore SharePoint 2013You can’t back up or restore everything in a SharePoint environment. You cannot use a backup made from one version to restore to another version.

You can use a backup made from one version to upgrade to another version. The update level of the farm to which you restore cannot be lower than the update level of a

backup.The destination farm must have the same or newer update level.

If you perform a backup while a task that creates or deletes databases is running, pending changes might not be included in the backup.Do not modify the spbackup.xml file. SharePoint 2013 uses this file. A change can make the backups unusable.

How to create a shared folderUse this procedure to create a shared folder on the network that can receive and hold backed up data. You can also use this shared folder when you restore data. If you already have a shared folder that serves this purpose, you do not have to perform this procedure. By performing the following procedure, you ensure that you can access the shared folder from the computer that runs SQL Server database software and from the computer that hosts the SharePoint Central Administration website.

To create a shared folder

1. Verify that the user account that is performing this procedure is a member of the Administrators group on the computer on which you want to create the shared folder.

2. If you create the shared folder on a computer other than the one running SQL Server, make sure that the service account for SQL Server (MSSQLSERVER) is using a domain user account and that it has Full Control permissions on the shared folder.

3. On the server on which you want to store the backup data, create a folder.4. On the Sharing tab of the Properties dialog box, click Advanced Sharing, and then click

Permissions, add the following accounts and assign them Full Control of the shared folder:o SQL Server service account (MSSQLSERVER)o The SharePoint Central Administration application pool identity accounto The SharePoint 2013 Timer service account (if you are using SharePoint Server 2013

to perform backups).


Configure backup and restore permissionsYou can configure backup and restore permissions for SharePoint 2013 by using the SharePoint Central Administration website or Windows PowerShell. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have made with your organization.

Before you begin

Before you back up or restore SharePoint 2013, you must make sure that the timer service account, SQL Server service account, and users who run the backup or restore operations have the correct permissions or are members of the correct Windows security groups or SharePoint groups. You must configure these permissions and group memberships when you first deploy SharePoint 2013. You have to update permissions and group memberships when you add new farm components to the environment and if you want to add users who will perform backup and restore operations.

Permissions for the SPTimerV4 timer service and SQL Server account in SharePoint 2013The Windows SharePoint Services Timer V4 (SPTimerV4) and the SQL Server service account in SharePoint 2013 perform backup and restore operations on behalf of users. These service accounts require Full Control permissions on any backup folders.

Group memberships required to run backup and restore operations in Central AdministrationYou must make sure all user accounts that use Central Administration to back up or restore your farm and farm components have the group memberships that are described in the following table.Farm component Member of Administrators group

on the local computerMember of Farm Administrators SharePoint group

Farm Yes NoService Application

Yes No

Content Database

Yes No

Site Collection No YesSite, list, document library

No Yes


Setting permissions to run SharePoint backup and restore operations by using Windows PowerShell

You must make sure that all user accounts that use Windows PowerShell to back up or restore your farm and farm components are added to the SharePoint_Shell_Access role for a specified database and have the permissions described in the table later in this section.

You can run the Add-SPShellAdmin cmdlet to add a user account to this role. You must run the command for each user account. Moreover, you must run the command for all databases to which you want to grant access.

To add a user to or remove a user from the SharePoint_Shell_Access role by using Windows PowerShell

1. Verify that you have the following memberships:o SecurityAdmin fixed server role on the SQL Server instance.o db_owner fixed database role on all databases that are to be updated.o Administrators group on the server on which you are running the Windows

PowerShell cmdlets.An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 Products cmdlets.

2. On the Start menu, click All Programs.3. Click Microsoft SharePoint 2013 Products.4. Click SharePoint 2013 Management Shell.5. At the Windows PowerShell command prompt, type the following command:

Add-SPShellAdmin -Username <User account> -Database <Database ID>Where:

o <Database ID> is the GUID assigned to the database.To add a user account to all the databases in the farm, type the following command:ForEach ($db in Get-SPDatabase) {Add-SPShellAdmin -Username <User account> -Database $db}Where:

o <User account> is the user whose account you want to remove.To remove a user account from all the databases in the farm, type the following command:ForEach ($db in Get-SPDatabase) {Remove-SPShellAdmin -Username <User account> -Database $db}Where:


o <User account> is the user whose account you want to remove.To view the user accounts currently added to the databases in the farm, type the following command:ForEach ($db in Get-SPDatabase) {Get-SPShellAdmin -Database $db}

You might also have to grant additional permissions to the users who run the backup or restore operation by using Windows PowerShell. The following table shows the permissions that are required.Farm component

Member of Administrators group on the local computer

Member of Farm Administrators SharePoint group

Full control on backup folder

Farm Yes No YesService Application

Yes No Yes

Content Database

Yes No Yes

Site Collection No Yes YesSite, list, document library

Yes No Yes

Backup solutionsThe following articles on TechNet and related resources provide information about backup solutions for SharePoint 2013. These articles are written to meet the requirements of information technology (IT) professionals who are responsible for the planning, design, deployment, and operations of backup and recovery solutions. These solutions might be in enterprise, corporate, or branch office environments. The IT professionals who are responsible for backup and recovery solutions are expected to have an understanding of the technical details that are contained in this section.A backup is a copy of data that is used to restore and recover that data after a system failure. While backups allow you to restore data after a failure they are also useful to keep for routine purposes. These purposes include copying a database from one server to another, setting up database mirroring, and archiving to comply with regulatory requirements.If you make appropriate backups, you can recover from many system failures, such as the following:

Media failure User errors (such as deleting a file by mistake)


Hardware failures (such as a damaged hard disk or permanent loss of a server) Natural disasters

Downloadable resources about backupDownload the following content for information about backup.

Content DescriptionBack up and restore: SharePoint Server 2013

A visual display of the backup and restore tools, scenarios and tasks available for SharePoint Server 2013.

Backup planning workbook Workbook to help you plan strategies for backup and restore for a SharePoint 2013 environment.

TechNet articles about backup for SharePoint 2013The following articles about backup are available to view online. Writers update articles on a continuing basis as new information becomes available and as users provide feedback.

Content DescriptionBack up farms in SharePoint 2013

Describes the procedures that you can use to back up the complete farm.

Back up farm configurations in SharePoint 2013

Describes the procedures that you can use to back up farm configuration settings.

Back up web applications in SharePoint 2013

Describes the procedures that you can use to back up a web application that is associated with the farm that include configuration and content databases.

Back up service applications in SharePoint 2013

Describes the procedures that you can use to back up a service application that is associated with the farm that include configuration and content databases.

Back up User Profile service applications in SharePoint Server 2013

Describes the procedures that you can use to back up a User Profile Service application that is associated with the farm that include configuration and content databases.

Back up Search service applications in SharePoint 2013

Describes the procedures that you can use to back up the Search service application that is associated with the farm that include configuration and indexes.

Back up the Secure Store Service in SharePoint 2013

Describes the procedures that you can use to back up the Secure Store service application that is associated with the farm that include configuration and content databases.

Back up content databases in SharePoint 2013

Describes the procedures that you can use to back up a content database that is associated with the farm.

http://technet.microsoft.com/en-us/library/ee428327(v=office.15).aspx









http://technet.microsoft.com/en-us/library/gg576965(v=office.15).aspx













http://go.microsoft.com/fwlink/p/?LinkId=256660




Back up databases to snapshots in SharePoint Server 2013

Describes the procedures that you can use to back up a content database that is associated with the farm by saving the database to a snapshot.

Back up customizations in SharePoint 2013

Describes the procedures that you can use to back up customizations that are associated with the farm.

Back up site collections in SharePoint 2013

Describes the procedures that you can use to back up site collections that are associated with the farm.

Back up apps for SharePoint in SharePoint 2013

Learn how to back up apps for SharePoint in SharePoint 2013.

Export sites, lists, or document libraries in SharePoint 2013

Describes the procedures that you can use to export a list, site, or document library that is associated with the farm. You can then import the items into another farm or move them to another place in this farm.

Use Central Administration to back up a SharePoint farmYou can use Central Administration to back up the farm.

To back up a farm by using Central Administration

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.

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

3. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the farm from the list of components, and then click Next.

4. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type section, select either Full or Differential.

5. In the Back Up Only Configuration Settings section, click Back up content and configuration settings.

6. In the Backup File Location section, type the UNC path of the backup folder, and then click Start Backup.

7. You can view the general status of all backup jobs at the top of the Backup and Restore Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh.




http://technet.microsoft.com/en-us/library/jj871017(v=office.15).aspx











Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.

Use SQL Server tools to back up a SharePoint farmIf you want to back up the complete farm, you must use either Windows PowerShell or Central Administration. You cannot back up the complete farm by using the SQL Server tools because you cannot use the tools to back up the farm’s configuration. However, you can back up all the databases that are associated with the farm. The databases that are associated with the farm are determined by the services and features that you have installed on the farm.

To back up the databases associated with a farm by using SQL Server tools

1. Verify that the user account that is performing this procedure is a member of the SQL Server db_owner fixed database role on all databases that are to be backed up.

2. Open SQL Server Management Studio and connect to the correct instance of the SQL Server Database Engine.

3. In Object Explorer, expand Databases.4. Right-click the database that you want to back up, point to Tasks, and then click Back Up.5. In the Back Up Database dialog box, in the Source area, select the kind of backup that

you want to perform from the Backup type list. For more information about which backup type to use, see Recovery Models (SQL Server).

6. In the Backup component area, click Database.7. Either use the default name that is provided or specify a name for the backup set in the

Name text box.8. Specify the expiration date for the backup set. This date determines how long, or when, the

backup set can be overwritten by any later backups that have the same name. By default, the backup set is set to never expire (0 days).

9. In the Destination area, specify where you want to store the backup.10. Click OK to back up the database.11. Repeat steps 1-10 for each farm database.



Back up web applicationsYou can back up a web application by using the SharePoint Central Administration website, Windows PowerShell, or SQL Server tools. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requirements, and service level agreements that you have with your organization.

Use Windows PowerShell to back up a web application You can use Windows PowerShell to back up a web application manually or as part of a script that can be run at scheduled intervals.

To back up a web application by using Windows PowerShell

1. Verify that you have the following memberships:o securityadmin fixed server role on the SQL Server instance.o db_owner fixed database role on all databases that are to be updated.o Administrators group on the server on which you are running the Windows

PowerShell cmdlets.An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 Products cmdlets.

2. Start the SharePoint 2013 Management Shell.o For Windows Server 2008 R2:

On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.

o For Windows Server 2012: On the Start screen, click SharePoint 2013 Management Shell.

If SharePoint 2013 Management Shell is not on the Start screen: Right-click Computer, click All apps, and then click SharePoint 2013

Management Shell.

3. At the Windows PowerShell command prompt, type the following command:Backup-SPFarm -Directory <BackupFolder> -BackupMethod {Full | Differential} -Item <WebApplicationName> [-Verbose]Where:

o <BackupFoler> is the path of the folder that you use for storing backup files.


o <WebApplicationName> is the name of the web application. To display the name of the web application, at the Windows PowerShell command prompt, type the following command: Backup-SPFarm -ShowTree

Use Central Administration to back up a web applicationYou can use Central Administration to back up a web application.

To back up a web application by using Central Administration1. Verify that the user account that is performing this procedure is a member of the Farm

Administrators group.2. Start SharePoint 2013 Central Administration.

o For Windows Server 2008 R2: Click Start, click Microsoft SharePoint 2013 Products, and then click

SharePoint 2013 Central Administration.o For Windows Server 2012:

On the Start screen, click SharePoint 2013 Central Administration.If SharePoint 2013 Central Administration is not on the Start screen:

Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.


4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the web application from the list of components, and then click Next.


6. In the Back Up Only Configuration Settings section, click Back up content and configuration settings.

7. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.

8. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.


If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 6.


Use SQL Server tools to back up a web applicationYou cannot back up the complete web application by using SQL Server tools. However, you can back up all the databases that are associated with the web application. To back up the complete web application, use either Windows PowerShell or Central Administration.

To back up a web application by using SQL Server tools1. Verify that the user account that is used to back up the databases is a member of the SQL

Server db_backupoperator fixed database role on the database server where each database is stored. Additionally, verify that the user account has Full Control permissions on the backup folder.

2. Open SQL Server Management Studio and connect to the database server.3. In Object Explorer, expand Databases.4. Right-click the database that you want to back up, point to Tasks, and then click Back Up.5. In the Back Up Database dialog box, in the Source area, select the kind of backup that

you want to perform from the Backup type list. 6. In the Backup component area, click Database.7. Either use the default name that is provided or specify a name for the backup set in the



9. In the Destination area, specify where you want to store the backup.10. Click OK to back up the database.11. Repeat steps 1-10 for each database that is associated with the web application.


Back up service applicationsYou can back up a service application by using the SharePoint Central Administration website or Windows PowerShell. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization.

Use Central Administration to back up a service application in SharePoint

You can use Central Administration to back up a service application.To back up a service application by using Central Administration


2. Start SharePoint 2013 Central Administration.o For Windows Server 2008 R2:

Click Start, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Central Administration.

o For Windows Server 2012: On the Start screen, click SharePoint 2013 Central Administration.

If SharePoint 2013 Central Administration is not on the Start screen: Right-click Computer, click All apps, and then click SharePoint 2013

Central Administration.3. In Central Administration, on the home page, in the Backup and Restore section, click

Perform a backup.4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the

service application from the list of components, and then click Next. To back up all the service applications, select the Shared Service Applications node.


6. In the Backup File Location section, in the Backup location box, type the path of the backup folder, and then click Start Backup.

7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.


If you receive any errors, you can review them in the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.


Back up content databasesYou can back up a content database by using the SharePoint Central Administration website, Windows PowerShell, or SQL Server tools. The backup tool that you use depends on the kind of environment that you have deployed, your backup schedule requires, and service level agreements that you have made with your organization.

Use Central Administration to back up a content database in

SharePoint 2013You can use Central Administration to back up a content database.

To back up a content database by using Central Administration







Perform a backup.4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select the

content database that you want to back up from the list of components, and then click Next.5. On the Start Backup — Step 2 of 2: Select Backup Options page, in the Backup Type

section, select either Full or Differential.6. In the Backup File Location section, type the Universal Naming Convention (UNC) path of

the backup folder, and then click Start Backup.7. You can view the general status of all backup jobs at the top of the Backup and Restore Job

Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.


If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 5.


Use SQL Server tools to back up a content database in SharePoint

2013You can use SQL Server tools to back up a content database.

To back up a content database by using SQL Server tools

1. Verify that the user account that is performing this procedure is a member of the SQL Server db_backupoperator fixed database role on the database server where each database is stored.

2. Open SQL Server Management Studio and connect to the database server.3. In Object Explorer, expand Databases.4. Right-click the database that you want to back up, point to Tasks, and then click Back Up. 5. In the Back Up Database dialog box, in the Source area, select the kind of backup that

you want to perform from the Backup type list. 6. In the Backup component area, click Database.7. Either use the default name that is provided or specify a name for the backup set in the



9. In the Destination area, specify where you want to store the backup. 10. Click OK to back up the database.11. Repeat steps 1-9 for each content database that you want to back up.


Back up site collectionsYou can back up a site collection in SharePoint 2013 by using the SharePoint Central Administration website or Windows PowerShell

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

You can use Central Administration to back up a site collection.

To back up a site collection by using Central Administration

1. Verify that the user account performing this procedure is a member of the Farm Administrators group. Additionally, verify that the Windows SharePoint Services Timer V4 service has Full Control permissions on the backup folder.






Perform a site collection backup.4. On the Site collection backup page, select the site collection from the Site Collection

list.5. Type the local path of the backup file in the Filename box.6. Click Start Backup.7. You can view the general status of all backup jobs at the top of the Granular Backup Job

Status page in the Readiness section. You can view the status for the current backup job in the lower part of the page in the Site Collection Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.


Back up appsThe apps for SharePoint is a powerful new feature for SharePoint 2013. For more information, see Overview of apps for SharePoint 2013. For a graphical representation of apps for SharePoint, see SharePoint 2013: App Overview for IT Pro.We recommend that you regularly back up at the farm level. However, business or IT requirements might require you to back up the apps for SharePoint in addition to normal farm backups. If you regularly back up the apps for SharePoint environment, you reduce the possibility of data losses that might occur from hardware failures, power outages, or other problems. It is a simple process that helps make sure that data and configurations that compose the apps for SharePoint environment are available for recovery, if that is required. The app for SharePoint content and packages are in the SharePoint 2013 content databases in individual site collections. All app for SharePoint license and security data is stored in the App Management Service and the Secure Store Service application databases. Additional app for SharePoint data is stored in the SharePoint 2013 configuration database, in the form of Internet Information Services (IIS) web sites or web applications, and Web Part packages. You must back up the following SharePoint 2013 databases at the same time:

Content Configuration Secure Store Service application App Management service application

If you have to eventually restore the databases, you have to restore the same version of each database that you backed up. In other words, don't restore a content database that's six months older than the configuration database.For more information about the SharePoint 2013 databases, see Database types and descriptions (SharePoint 2013). For a graphical representation of the SharePoint 2013 databases, see Databases that support SharePoint 2013You can back up an apps for SharePoint environment by using the SharePoint Central Administration website, Windows PowerShell, or SQL Server tools.

Back up content databasesContent databases can store data for multiple site collections. However, if you have many site collections, we recommend that you add enough content databases to keep the size of each database below 200 GB for optimal system performance. For more information, see Back up content databases in SharePoint 2013





http://technet.microsoft.com/en-us/library/cc678868(v=office.15).aspx

http://technet.microsoft.com/en-us/library/cc678868(v=office.15).aspx


http://technet.microsoft.com/en-us/library/fp161230(v=office.15).aspx


Back up the configuration databaseThe SharePoint 2013 configuration database stores data about all SharePoint databases and Internet Information Services (IIS) web sites or web applications. This includes trusted solutions, Web Part packages, site templates, and web application settings, and farm settings that are specific to SharePoint 2013, such as default quota and blocked file types. For more information, see Back up farm configurations in SharePoint 2013.

Back up the Secure Store Service application databaseThe Secure Store Service database stores and maps credentials such as account names and passwords. To back up the Secure Store database for an apps for SharePoint environment, see Back up the Secure Store Service in SharePoint 2013.

Back up the App Management service application databaseThe App Management service application database stores the app licenses and permissions for all apps downloaded from the App Catalog site in SharePoint 2013. To back up the App Management database, follow the same procedures as most other SharePoint 2013 service applications.






Back up a site collectionYou may have multiple site collections that host apps for SharePoint in your environment. When you backup apps for SharePoint you must also back up all site collections where the apps are hosted.

To back up a site collection by using Windows PowerShell


PowerShell cmdlets.An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.

Note:If you do not have permissions, contact your Setup administrator or SQL Server administrator to request permissions.


1. On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.


If SharePoint 2013 Management Shell is not displayed on the Start screen:

Right-click Computer, click All apps, and then click SharePoint 2013 Management Shell.

.3. At the Windows PowerShell command prompt, type the following command:

Backup-SPSite -Identity <SiteCollectionGUIDorURL> -Path <BackupFile> [-Force] [-NoSiteLock] [-UseSqlSnapshot] [-Verbose]Where:

o <SiteCollectionGUIDorURL> is the ID or URL for the site collection you want to back up.

o <BackupFile> is the path of where the backup file is located.


If you want to overwrite a previously used backup file, use the Force parameter. You can use the NoSiteLock parameter to keep the read-only lock from being set on the site collection while it is being backed up. However, using this parameter can enable users to change the site collection while it is being backed up and could lead to possible data corruption during backup. To display the site collection GUID or URL at the Windows PowerShell command prompt, type the following command:Get-SPSite | format-list -property id,url

If the database server is running an Enterprise Edition of SQL Server, we recommend that you also use the UseSqlSnapshot parameter for more consistent backups. You can also export sites or lists from these snapshots.


Workflow BackupSharePoint administrators must account for both the SharePoint 2010 Workflow platform and the SharePoint 2013 Workflow platform when they consider backup and restore scenarios.The SharePoint 2010 Workflow platform is integrated with SharePoint Server. When you back up SharePoint Server, or the underlying In contrast, backing up the SharePoint 2013 Workflow platform is a separate operation from backing up SharePoint Server 2013. Like SharePoint Server, Workflow Manager stores all of its content and configuration information in a SQL Server database. An important assumption is that the SQL Server layer of both SharePoint Server and Workflow Manager are highly available services. In other words, both the SharePoint databases and Workflow Manager databases must be kept in sync. From the SharePoint administrator's perspective, Workflow Manager is a separate service that is backed up and administered in its own realm. SharePoint backups should be coordinated with Workflow Manager backup’s. However, there are not any specific actions that must be performed in SharePoint Server in order to backup the SharePoint 2013 Workflow platform..You can back up customizations that are made to SharePoint 2013 sites by using the SharePoint Central Administration website or Windows PowerShell. Which backup tool you use depends on what kind of environment you have deployed, what your backup schedule requires, and what service level agreements you have made with your organization? Before you begin this operation, review the following list of possible customizations that you can make to your sites:

Customizations packaged as solutions (.wsp files). Solutions contain developed site elements, and are typically created by developers. Developed site elements include the following:

o Web Partso Workflowso Site and list definitionso Document converterso Event receiverso Timer jobso Assemblies

Authored site elements, which are typically created by web designers, are not explicitly compiled and are located in a content database. Authored site elements include the following:

o Master pages


o Cascading style sheetso Formso Layout pages

Changes to the Web.config file Third-party solutions and their associated binary files and registry keys, such as IFilters Changes to sites created by direct editing through the browser Developed customizations that are not packaged as solutions


Backup solution packages in SharePoint 2013Solution packages can be created by using SharePoint Designer 2013 or Visual Studio 2012. We strongly recommend that all customizations be deployed as solution packages.

A solution package is a deployable, reusable file that can contain a set of Features, site definitions, and assemblies that apply to sites, and that you can enable or disable individually. Solution packages can include Web Parts, site or list definitions, custom columns, new content types, custom fields, custom actions, coded workflows, or workflow activities and conditions.

The method that you use to back up solution packages is determined by whether the customizations are deployed as trusted solutions or sandboxed solutions.

Trusted solutions are solution packages that farm administrators deploy. Trusted solutions are deployed to the entire farm and can be used on any site within the farm. Trusted solutions are stored in the configuration database. Trusted solutions are backed up when a farm is backed up by using SharePoint 2013 backup, and are included in configuration-only backups. You can also back up trusted solutions as a group or individually. Trusted solutions are visible in the backup hierarchy.

Sandboxed solutions are solution packages that site collection administrators can deploy to a single site collection. Sandboxed solutions are stored in the content database that is associated with the site collection to which the solution packages are deployed. They are included in SharePoint 2013 farm, web application, content database, and site collection backups, but are not visible in the backup hierarchy and cannot be selected or backed up individually.

We recommend that you keep a backup of the original .wsp file and the source code used to build the .wsp file for both trusted solutions and sandboxed solutions.

To back up trusted solutions by using Central Administration

1. Verify that the user account that is performing this procedure is a member of the Farm Administrators group.



o For Windows Server 2012:


On the Start screen, click SharePoint 2013 Central Administration.If SharePoint 2013 Central Administration is not on the Start screen:

Right-click Computer, click All apps, and then click SharePoint 2013 Central Administration.


4. On the Perform a Backup — Step 1 of 2: Select Component to Back Up page, select Solutions, and then click Next.You can also select an individual solution, if you only want to back up a single solution.


6. In the Backup File Location section, type the Universal Naming Convention (UNC) path of the backup folder, and then click Start Backup.

7. You can view the general status of all backup jobs at the top of the Backup and Restore Job Status page in the Readiness section. You can view the status of the current backup job in the lower part of the page in the Backup section. The status page updates every 30 seconds automatically. You can manually update the status details by clicking Refresh. Backup and recovery are Timer service jobs. Therefore, it may take several seconds for the backup to start.If you receive any errors, review the Failure Message column of the Backup and Restore Job Status page. You can also find more details in the Spbackup.log file at the UNC path that you specified in step 4.


To back up trusted solutions by using Windows PowerShell


PowerShell cmdlets.An administrator can use the Add-SPShellAdmin cmdlet to grant permissions to use SharePoint 2013 cmdlets.


On the Start menu, click All Programs, click Microsoft SharePoint 2013 Products, and then click SharePoint 2013 Management Shell.


If SharePoint 2013 Management Shell is not on the Start screen: Right-click Computer, click All apps, and then click SharePoint 2013

Management Shell.3. At the Windows PowerShell command prompt, type the following command to back up all of

the solutions in the farm. To back up a single solution, add the name of the solution to the item path "farm\solutions".Backup-SPFarm -backupmethod full -directory <UNC location> -item "farm\solutions"Where:

o <UNC location> is the UNC location of the directory that you want to back up to.

Documents

Getting Started SharePoint “2013” Web view18.07.2014 · Permissions for the SPTimerV4 timer service and SQL Server account in SharePoint 2013. The Windows SharePoint Services