SharePoint 2010 Configuration Database has a huge LOG File size problem.

You detected that SharePoint 2010 configuration database has a big LOG file size and you have  a low disk space problem.

This is happening because SharePoint Configuration Database are set to full recovery mode by default. Full recovery mode does not auto shrink / truncate the log files on a full backup. In this mode System Admins are responsible to maintaining getting Transactional Log Backups and Shrinking Log files. If Simple recovery mode is selected when you get a full backup the log files will be shrinked. But Microsoft does not recommend changing to simple recovery mode in a production environment.

You can check the Recovery mode by using SQL Server Management Studio (SSMS) by selecting “SharePoint Config” database (Right Click)-> Properties -> Options.

Full recovery mode allows the SQL admins to backup the transcation logs incrementally, simple recovery mode does not allow this and only allows full or differential backups, no transaction log backups. And Full Recorvery mode has provide you to recovery at specific time manner.

For more information about SQL Server Recovery Models

SharePoint Configuration Database is the heart of a SharePoint farm and according to size of farm lots of transactions happens.Especially every Timer Job run can cause high transactions on SharePoint Configuration Database. And There are nothing to prevent or reduce this logs rate by making any changes on SharePoint Side.

So for production enviroments SQL Admin should make a recovery and maintenance plans for preventing unnecessary growth of log files. It should be done by getting frequently Transactional Log backups and shrinking transaction log files.

The frequency has changed  system by system. It could be done 30 min to 1 day frequency, according to your transaction log growth.To prevent this kind of problem, make automize or manuelly get your Transactional backups and shrink the log files for a defined period.

For Backup Transaction Log Please check fallowing artcile:

For Shrink Transaction Log file:

Sharepoint 2010 Restore problem with SqlException The restart-checkpoint

Object <Content Database> failed in event OnRestore. For more information, see the spbackup.log or sprestore.log file located in the backup directory. SqlException: The restart-checkpoint file ‘Drive:\MSSQL10_50.MSSQLSERVER\MSSQL\Backup\xxxx.CKP’ could not be opened. Operating system error ‘3(The system cannot find the path specified.)’. Correct the problem, or reissue the command without RESTART. RESTORE DATABASE is terminating abnormally.

When SQL Server has been installing , it creates a default SQL Server Database backup folder like ‘Drive:\MSSQL10_50.MSSQLSERVER\MSSQL\Backup’

This error occurs that the BACKUP or RESTORE process needs to create a checkpoint file that will indicate at what point any failure occurs. This allows the WITH RESTART option to be used . The WITH RESTART option specifies that SQL Server should restart a restore operation that has been interrupted and continue restore operation where the interruption has occured . The information about how much data the BACKUP or RESTORE command had processed before the interruption occurred is stored in a checkpoint file in the BACKUP directory like ‘Drive:\<SQL INSTANCE>\MSSQL\Backup

The checkpoint file is a temporary file, deleted when the restore process is completed, and is normally placed in the default backup folder.

Some of the reasons the checkpoint file cannot be created :

– The “backup” directory does not exist under the directory where SQL Server is installed.
– The drive where the “backup” directory resides is full.
– The “backup” directory is not accessible to the SQL Server account.

For fixing the issue you may check fallowings.

– Verify that the BACKUP directory exists under the directory where SQL Server is installed. If it does not exist, create it.
– Verify that there is available space on the drive where the BACKUP directory resides.
– Verify that the SQL Server startup account has permission to read from and write to the BACKUP directory.

This error has a limited impact and does not prevent a restore operation from succeeding. This error message occurs when a restore is interrupted, and the checkpoint file that is used to restart a restore is not written, or the checkpoint file is not written correctly. If you receive this error, it means that, if for some reason the restore operation is interrupted in the middle of the process, you have to restart it from the beginning of the backup file rather than the checkpoint file.

Check fallowing KB articles for more information :






Backup Error on Moss2007: Object Shared Search Index failed in event OnPrepareBackup, The current operation timed-out after 3600 seconds

If you getting error in spbackup.log file when getting backup like:
Error: Object Shared Search Index failed in event OnPrepareBackup. For more information, see the error log located in the backup directory.
WebException: The current operation timed-out after 3600 seconds
Debug: at Microsoft.Office.Server.Search.Administration.SearchSharedApplication.Microsoft.SharePoint.Administration.Backup.IBackupRestore.OnPrepareBackup(Object sender, SPBackupInformation args) at Microsoft.SharePoint.Administration.Backup.SPBackup.RunPrepareBackup(SPBackupRestoreObject node)

When performing a backup of a search application, sometimes the operation for pausing the search application fails. In this case, the backup of the search index cannot continue. In that case, the SSP backup is virtually useless. Pre-SP2, the process of backing up the search database will continue. Post-SP2, the failure to pause the search application during a backup process will also result in failure of backing up the search databases, and the search databases will be marked with the same error as the search index component.
For More info:

Upgrade to Moss 2007 SP2

Sharepoint 2010 Backup Folder Configuration

If you are getting an error when backup operation  like  :

Cannot open backup device ‘E:\yedekk\spbr000000000BE.bak’. Operating system error 3(The system cannot find the path specified.).
BACKUP DATABASE is terminating abnormally.

Ensure that the following are given the Full Control file share and NTFS permissions for the backup shared folder:

  • The account used by the SQL Server service account.
  • The Windows SharePoint Services Timer V4 (SPTimerV4) account.
  • The logged on account, if you are using Windows PowerShell to perform the backup or restore.
  • If the backup folder is a network share, ensure that all accounts that are listed above have access to both the share and the folder itself.
  • If you are performing a backup or restore operation between two SharePoint farms, services on both farms must have the permissions described above.

Step by Step Configuration

1) Creating a backup folder where we want to store sharepoint backup files on specified computer in your domain. After that you have to share this path and create a network path .

2) If you create the shared folder on a computer other than the one running SQL Server, ensure 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.Give Full Control for  SQL Server Service Account .You can find SQL Server Service Account that first connect your SQL Server -> Start -> All Programs -> Microsoft SQL Server 2008 -> Configuration Tools -> SQL server configuration Manager.

3)  Give Full Control to Sharepoint Timer Service Account. for do that connect your Microsoft Sharepoint Server 2010 installed machine and run-> services.msc

4) Give Full Control to The SharePoint Central Administration application pool identity account

5) Lets configure our sharepoint from Central Administration. Connect your CA and -> Backup and Restore ->
Configure Backup Settings and type your network path to “Backup File Location” section .

6) Click Ok than perform a backup .

Some Resources:
Prepare to back up and recover