FS_NO_MORE backing up certain SQL databases

[KerryRJ]

I am am trying to backup SQL 2008 SP1 CU 6 databases on a Windows 2008 R2 64bit box but am failing with an FS_NO_MORE error. I have enabled BE logging in the registry and find the following in the log file:- [24312] 07/15/10 20:49:47 Returning Database WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8 - Log backup supported [24312] 07/15/10 20:49:47 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\' 'WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8.' 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8.' [24312] 07/15/10 20:49:47 SQL2: BackupSnapMetaData [24312] 07/15/10 20:49:47 SQL2: BackupSnapMetaData [24312] 07/15/10 20:49:47 brUtil::SetMetaDataStream - Metadata Stream Header (602) [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a File C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8. [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8. C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_7489a238-e00e-41e9-bb25-67318ccd7fe8. [24312] 07/15/10 20:49:47 Unswitched return from FS_ReadObj() = 0x2000fe07 [24312] 07/15/10 20:49:47 Returning Database WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c - Log backup supported [24312] 07/15/10 20:49:47 brUtil::SetupDLE Succesfully set up to read the object 'C:' '\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\' 'WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c.md' 'C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c.md' [24312] 07/15/10 20:49:47 SQL2: BackupSnapMetaData [24312] 07/15/10 20:49:47 SQL2: BackupSnapMetaData [24312] 07/15/10 20:49:47 brUtil::SetMetaDataStream - Metadata Stream Header (602) [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a Directory C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\ [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Information: Active Object is a File C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c.md [24312] 07/15/10 20:49:47 brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c.md C:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\DATA\WebAnalyticsServiceApplication_StagingDB_abcbe9a8-1750-422d-a600-c05c62039d2c.md [24312] 07/15/10 20:49:47 Unswitched return from FS_ReadObj() = 0x2000fe07 I have run a SQL log backup for the 5 databases that are failing. The event log shows nothing out of the ordinary. The only thing that I can see in the log file is that the database names get truncated by between 1 and 4 characters. The databases are Sharepoint 2010 databases. Other Sharepoint 2010 databases in the same location get backed up fine. All other databases in the same location also get backed up fine. Running: BE 2010 Version 13.0 Rev. 2896 (64bit) Trial 15/60 days left Can anyone point me in a direction that will help solve this issue?

[Ken_Putnam]

See http://seer.entsupport.symantec.com/docs/316764.htm

[KerryRJ]

Hi Ken,

Thank you for the reply.
I used the article you provided for many hours before posting.

I have used TSQL to backup the log files for each of the failing databases numerous times with no resolution to the problem.
Perhaps I am wrong to assume that backing up the logs would flush and commit the transactions. If I am then what is required to flush and commit the log files in SQL 2008?

Regards

[pkh]

Since the databases are Sharepoint databases, perhaps you should be backing them up using the Sharepoint agent, rather than the SQL agent.  You are using the trial version so have have access to the Sharepoint agent.

[KerryRJ]

Hi Phk

In all 5 cases the log file shows the database name truncated i.e. the extension is missing or a single character of the extension is missing i.e. the extension in the sample posted is .md but should be .mdf. I am able to backup these databases and log files using SQL without any issues but Backup Exec is choking.

I was wondering if it was a maximum path length issue but checking one example the full path is only 149 characters long.

I am not sure I understand why the SQL agent should not be able to back up the database considering that there are numerous other sharepoint databases, with the same style/length database names, that it is backing up successfully.

Regards

[Mark_A__Bryant]

Jumping in here,

I think you are on to something with the 149 character length observation. That is precisely what my debug logs show too:

[4652] 09/23/10 22:19:18 brUtil::OpenActiveObject Information: Active Object is a File C:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_6e5b76df-2338-40d3-a2d0-31ed

[4652] 09/23/10 22:19:18 brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object SharedServices1_DB_6e5b76df-2338-40d3-a2d0-31ed c:\Program Files (x86)\Common Files\Microsoft Shared\Web Server Extensions\12\Data\MSSQL.1\MSSQL\DATA\SharedServices1_DB_6e5b76df-2338-40d3-a2d0-31ed

[4652] 09/23/10 22:19:18 Unswitched return from FS_ReadObj() = 0x2000fe07

Symantec, the balls in your court now.

[Ben_L_]

Sorry about the delayed response, but I ran a test backup of databases over 149 characters with both BE2010 and BE2010 R2 and they were both successful.  I mad ethe database paths 155 characters.

Are the debugs posted from media server or the SQL server?

Can you post the job log and debug logs from the media server and sql server?

[Mahesh_Roja]

Hope it may help it to resolve the issue

http://www.symantec.com/business/support/index?page=content&id=TECH66205

[pkh]

@Maheshroja - Which part of the document is related to the problem??

[szurlo]

Having the exact same issue.  If the full path to the DB is over 149 characters the path is truncated in the log and the DB backup fails.  I thought that might just be a log display issue but it appears that 100% of the time the dbs that fails is over 149 and the dbs that succeed are less than 149.

Example:

C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Application_Registry_Service_DB_330a9c621df24fb3baf276cd80cfbf15.mdf

The full path is 150 characters.

This DB fails with the following log error:

"brUtil::OpenActiveObject Error: 0x2000FE07 Could not find the object Application_Registry_Service_DB_330a9c621df24fb3baf276cd80cfbf15.md C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Application_Registry_Service_DB_330a9c621df24fb3baf276cd80cfbf15.md"

Note the single final character ("f" )truncated from the file extention.

Following are the other "Could not find" files as shown in the log. Notice they are all missing characters and are all exaclty 149 long as displayed in the log:

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\PerformancePoint Service Application_7a86bbf2c0a94e139d11760f235742"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Search_Service_Application_CrawlStoreDB_e605be28f1fd47d6b7cc4b4a827"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Search_Service_Application_DB_1797b9abb7404bf48849706fe075ce65_log."

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Search_Service_Application_PropertyStoreDB_a7334715e29d400c8244be51"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\SharePoint_AdminContent_a47b1799-1b4a-49c8-84ae-8330a6a921cc_log.LD"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\User Profile Service Application_ProfileDB_54cfae9257a24c9d92ccd2cd"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\User Profile Service Application_SocialDB_d1876d314f65486e9962c9501"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\User Profile Service Application_SyncDB_893ae50b46984bc6af53a3d34cb"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\WebAnalyticsServiceApplication_ReportingDB_016215ae-7634-4672-acf4-"

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\WebAnalyticsServiceApplication_StagingDB_e658976e-8fa2-4615-9c6d-33"

And here are the files that backed up succesfully:

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Bdc_Service_DB_0ad5a48e40ba43a9b1d6bdde7b361d5e.mdf"  (133 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Managed Metadata Service_f65494b4bd85433cbb18c61967647119.mdf" (143 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\Managed Metadata Service_f65494b4bd85433cbb18c61967647119_log.LDF" (147 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\master.mdf" (92 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\mastlog.ldf" (93 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\model.mdf" (91 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\modellog.ldf" (94 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\MSDBData.mdf" (94 chars)

"C:\Program Files\Microsoft Office Servers\14.0\Data\MSSQL10.SHAREPOINT\MSSQL\DATA\MSDBLog.ldf" (93 chars)