Monday 25 October 2010

Backup Exec 2010 SBS/Sharepoint Database Errors

Been noticing a few problems recently with Backup Exec 2010 complaining about the default SBS 2008 databases.

Specifically the logs say that the transaction logs for these databases are not being backed up and the recovery mode should be set to simple.  However, it is not straight forward to do this, particularly as the SQL Management Studio is not part of SBS

These are the errors as shown in the Backup Exec logs:

Backup- XXXXXXXX\MICROSOFT##SSEEV-79-40960-37914 - Database WSS_Content is configured to maintain transaction logs. Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

Backup- WebApplication\Content-DB 1 (XXXXXXXX\MICROSOFT##SSEE\SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab)V-79-40960-37914 - Database SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab is configured to maintain transaction logs. Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

Backup- SBS SharePoint\Content-DB 1 (XXXXXXXX\MICROSOFT##SSEE\ShareWebDb)V-79-40960-37914 - Database ShareWebDb is configured to maintain transaction logs. Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

Backup- ConfigurationV3-DB (XXXXXXXX\MICROSOFT##SSEE\SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6)V-79-40960-37914 - Database SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6 is configured to maintain transaction logs. Transaction log backups are not being performed. This will result in the log growing to fill all available disk space. Regular log backups should be scheduled or the database should be changed to the simple recovery mode.

I've put the database names in bold above to make it easier to pick them out, the long alphanumeric strings in two of them will be different on each server so be sure to substitute the correct ones when running the commands below.

To set the recovery mode to simple for these databases, use osql from the command prompt as follows:

C:> osql -E -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query
1> ALTER DATABASE WSS_Content SET RECOVERY SIMPLE
2> go
1> ALTER DATABASE ShareWebDb SET RECOVERY SIMPLE
2> go
1> ALTER DATABASE [SharePoint_AdminContent_d4e397f2-a27a-48a0-a628-d25db6672bab] SET RECOVERY SIMPLE
2> go
1> ALTER DATABASE [SharePoint_Config_29c26fca-17b8-48c1-9704-b869932abcb6] SET RECOVERY SIMPLE
2> go

NOTE: That the last two with the long alphanumeric strings need to be surrounded by square brackets [], or you will get a syntax error complaining about the '-' symbol.  I originally thought I would be clever and just quote these database names, but then I got an error saying that 'recovery' is not a recognized option.  Square brackets fixes this.