SQL or File backup shows exceptions - Error: SPDBName is a component of a SharePoint server farm. It must be backed up using the Backup Exec Agent for Microsoft SharePoint Portal Server.

Article:TECH196215

Created: 2012-09-06

Updated: 2013-04-09

Article URL http://www.symantec.com/docs/TECH196215

NOTE: If you are experiencing this particular known issue, we recommend that you to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.

Article Type
Technical Solution

Product(s)

Show all

Languages

Show all

Problem

This technote is applicable to exceptions showing up during SQL agent or file backups of Sharepoint SQL servers after applying Hotfix 180964 to Backup Exec. With Sharepoint agent backups being successfully performed, a SQL agent or File backup of the SQL server hosting the Sharepoint databases will show the following exceptions for all Sharepoint databases:

Error

SQL Agent backup error (with DB name):

79-57344-33925 - Error: SharepointSQLDB is a component of a SharePoint server farm. It must be backed up using the Backup Exec Agent for Microsoft SharePoint Portal Server. Select it for backup from the Microsoft Server SharePoint Server Farms node.

File backup error (with filename instead of DB name):

V-79-57344-33925 - Error: SharePointSQLDB.mdf is a component of a SharePoint server farm. It must be backed up using the Backup Exec Agent for Microsoft SharePoint Portal Server. Select it for backup from the Microsoft Server SharePoint Server Farms node.

Cause

Normally, when Sharepoint SQL databases are backed up via the Backup Exec Sharepoint agent, an exclusion is automatically added for the SQL agent and file backups so that no exceptions are received during those backups. The databases are simply silently skipped because they are being protected by the Sharepoint agent. In this case, the exclusions are not working properly and the SQL agent or file backup does not detect that the Sharepoint databases are being protected so the exceptions are received.

Solution

Workarounds:

1) Confirm in the Sharepoint agent backups of the Sharepoint farm that all databases are properly protected with successful backups. The exceptions for those same databases can then be safely ignored in the SQL agent or file backup.

2) For SQL agent backup exceptions, in the backup job for the SQL server, the Sharepoint databases can be unchecked for backup. Note that in selecting only non-Sharepoint databases for backup in this way, if a new SQL database is created it won't be automatically added to the backup and must be manually checked in selections.

3) For File backup exceptions, an exclusion for SQL database file types (*.MDF) can be added.

Symantec Corporation has acknowledged that the above-mentioned issue is present in the current version(s) of the product(s) mentioned in this article. Symantec Corporation is committed to product quality and satisfied customers.
Symantec Corporation currently plans to address this issue by way of a patch or hotfix to the current version of the software. Please be sure to refer back to this document periodically as any changes to the status of the issue will be reflected here. A link to the patch or hotfix download will be added to this document when it becomes available. Please note that Symantec Corporation reserves the right to remove any fix from the targeted release if it does not pass quality assurance tests. Symantec's plans are subject to change and any action taken by you based on the above information or your reliance upon the above information is made at your own risk.

Supplemental Materials

Source	ETrack
Value	2922981
Description	SPS: After applying HF8, SQL DB backups give exceptions on SPS DBs even after SPS agent backups have been performed.