Back Up And Recovery

Performance finest practices for SharePoint backup and restore operations Backup and restore operations consume server resources and limit server performance while the operations are running. Follow these best practices to reduce resource usage and increase the performance of servers and the backup or restore task.


The Windows Server Backup feature provides a basic backup and recovery solution for computers running the Windows Server 2008 or Windows Server 2008 R2 operating system. Windows Server Backup replaces the previous Windows Backup feature that was available with former versions of the Windows operating system.


Windows Server Backup consists of a Microsoft Management Console snap-in, command-line tools, and Windows PowerShell lets that provide you the ability to perform scheduled full and incremental backups to disk and perform quick recoveries.


You can use Windows Server Backup to back up a full server (all volumes), selected volumes, the system state, specific files, folders, and even Hyper-V virtual machines. You can recover volumes, folders, files, certain applications, and the system state. And, in case of disasters like hard disk failures, you can perform a bare-metal recovery by loading the Windows recovery environment and triggering the restore.


Windows Server Backup is intended for use by everyone who needs a basic backup solution—from small businesses to large enterprises—but is even suited for smaller organizations or individuals who are not IT professionals.

As a leading authority in offering both on-premises and cloud solutions, atQor is an Azure Expert Managed Services Provider. Therefore, we are ideally situated to optimize your Azure backup and recovery setup.


Backing up and recovering data supports many business scenarios, including the following:


  • Recovering unintentionally deleted content that is not protected by the recycle bin or versioning.
  • Moving data between installations as part of a hardware or software upgrade.
  • Recovering from an unexpected failure.


When you start a backup of the Search service application, SharePoint 2013 starts a SQL Server backup of the Search administration database, crawl databases, and property databases. The process also backs up the index panel files in parallel.


By considering how the backup and recovery processes for the Search service application affect your service-level agreement.


The backup process is as follows:


  • Master merges are paused to preserve the master index.
  • A full database backup starts.
  • The master index is backed up.
  • The pause in packed is much shorter than during a backup of SharePoint 2010 Products and Office SharePoint Server 2007 search and does not last the full duration of the backup process.
  • All shadow indexes are backed up.
  • An incremental database backup starts.
  • Edges are resumed.
  • Master merges are resumed.



Configuration-only backup use and benefits;


A configuration-only backup extracts and backs up the configuration settings from a configuration database. You can use built-in tools to back up the configuration of any configuration database, whether it is currently attached to a farm or not. You can restore a configuration backup to the same or another server farm.


When you restore a configuration, you overwrite settings in the farm if values for those settings are in the configuration backup. Settings in the farm that are not in the configuration backup are not changed.


Situations in which you might want to restore a configuration from one farm to another farm include the following:


  • Replicating a standardized farm configuration to be used throughout an environment.
  • Moving configurations from a development or test environment to a production environment.
  • Moving configurations from a stand-alone installation to a farm environment.
  • Configuring a farm to serve as part of a standby environment.


SharePoint 2013 stores the following kinds of settings in the configuration-only backup:

  • Antivirus.
  • Information rights management (IRM).
  • Outbound email settings (only restored when you perform an overwrite).
  • Customizations deployed as trusted solutions.
  • Diagnostic logging.


Supports with built-up recovery options;

  • Restore from a farm backup that was created by using built-in tools.
  • Restore from the backup of a component taken by using the farm backup system.
  • Restore from a site collection backup.
  • Connect to a content database by using the unattached content database feature, back up or export data from it, and then restore or import the data.