Hi,

We have implemented a FTI on a very huge text data table for performance improvement. The table has 27 million records and proposed time for FTI population is around 5 days (Considering the processor speed, number of processors and disc configuration etc.)

We started the FTI population on Friday, but on Sunday it got shut down for unknown reason. Incidentally we found that the Server Back up process started execution as per the schedule (on Sunday morning) and both the processes were running at the same time. Attached below are the sequences of messages in the error log -

--------------------------------------------------------------
01/24/ 2003 2:49:41 AM: The transaction cannot be appended to the project <SQLServer SQL0001000005> queue. File: E:\FullTextCatalogs\SQL0001000005\SQL0001000005.Nt fy1.gthr. Error: 80070021 - The process cannot access the file because another process has locked a portion of the file.

01/24/2003 2:49:46 AM: The transaction cannot be appended to the project <SQLServer SQL0001000005> queue. File: E:\FullTextCatalogs\SQL0001000005\SQL0001000005.Nt fy1.gthr. Error: 80070021 - The process cannot access the file because another process has locked a portion of the file.

01/24/2003 2:50:04 AM: The critical error 9 occurred in project <SQLServer SQL0001000005>. Error: 8007054e - Unable to complete the requested operation because of either a catastrophic media failure or a data structure corruption on the disk. . The project has been shut down. The system is probably low on the resources. Free up resources and restart the service.
--------------------------------------------------------------

From the above sequence it looks like some process (backup?) has locked the catalog file, subsequently MSS has logged thousands of error messages causing snow ball effect, resulting in lack of resources and eventually shutting down the process. But we are not sure if Back up is culprit for stopping FTI population.

The question is - Can execution of Server back up process stop the FTI population? How can we avoid this without conflicting the Backup schedule? Any pointers in this direction will be appreciated.

Thanks
Chetan