Re: Backup failure due to full-text indexing



Everything is working fine now.
Rebuilding the fulltext catalog everytime, just before the "backup
database", seems to solve the problem.

"Hilary Cotter" wrote:

Thanks Mickael, keep us informed.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Mickael Parisot" <mparisot@xxxxxxxxxxxxx> wrote in message
news:6326618F-47F9-40C1-B144-E8E35EB2E4B0@xxxxxxxxxxxxxxxx
Thanks a lot. You are really nice.

I tried something else:
1) Rebuild the fulltext catalog before backup database
2) Shift the backup log after backup database (it was starting at the same
time before)
3) Run filemon to check which process is accessing the fulltext catalog

Filemon indicates that only sqlservr.exe is accessing the fulltext catalog
when rebuild and backup occured.
Right now, the last backups are succesfull. I hope this will continue and
it
may give some hints.

"Hilary Cotter" wrote:

I'm not sure. I opened a support incident on this case with Microsoft. We
were getting catalog corruption errors but these were due to something
else.
Microsoft wanted us to run a debugger for them and send them the dump but
we
were unable to do so. We also run filemon to figure out what was trying
to
open the file and it was SQL Server. Microsoft did tell us it was fixed
in
SP 1. We still get the errors.

I can reopen the case and get more info for you if you want.
--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.

This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Mickael Parisot" <mparisot@xxxxxxxxxxxxx> wrote in message
news:868D8C36-9464-4496-92A5-49160D94AE5E@xxxxxxxxxxxxxxxx
Not really. The fulltext catalog is working well and the maintenance
plan
is
working sometimes.
I think that a process is using the fulltext catalog while a rebuild
occurs
for example.
In this case, the rebuild would fail and the catalog folder would be
erased.
Thus, the backup cannot be done because the fulltext catalog filegroup
is
now "OFFLINE".
Am I correct?

"Hilary Cotter" wrote:

does this apply?

http://support.microsoft.com/kb/923355/en-us

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business
intelligence.

This posting is my own and doesn't necessarily represent
RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Mickael Parisot" <mparisot@xxxxxxxxxxxxx> wrote in message
news:427784E4-1CFA-421C-A559-D1D6191FA253@xxxxxxxxxxxxxxxx
Thank you for your replies!
There is another error message in the maintenance plan history I
didn't
see
before.
It seems that the fulltext catalog is offline sometimes which would
explain
why the backup could not be done.
But what could turn off the fulltext catalog?

Executing the query "BACKUP DATABASE [BihrOnline2_commerce] TO DISK
=
N'K:\\BOL_BACKUPS\\BihrOnline2_commerce\\BihrOnline2_commerce_backup_200609141600.bak'
WITH NOFORMAT, NOINIT, NAME =
N'BihrOnline2_commerce_backup_20060914160012',
SKIP, REWIND, NOUNLOAD, STATS = 10 " failed with the following
error:
"The
backup of the file or filegroup "sysft_Bihr_FTC" is not permitted
because
it
is not online. BACKUP can be performed by using the FILEGROUP or
FILE
clauses
to restrict the selection to include only online data. BACKUP
DATABASE
is
terminating abnormally.". Possible failure reasons: Problems with
the
query,
"ResultSet" property not set correctly, parameters not set
correctly,
or
connection not established correctly.

"Hilary Cotter" wrote:

Actually I just realized we get this error message every time we do
a
transaction log dump. This error seems to be a warning message more
than
anything else.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business
intelligence.

This posting is my own and doesn't necessarily represent
RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Mickael Parisot" <mparisot@xxxxxxxxxxxxx> wrote in message
news:8134E131-74B5-4ACA-A2E4-9C3C9CF445A7@xxxxxxxxxxxxxxxx
SP1 is already applied on SQL Server 2005.
Displayed version number is 9.0.2047.
It is running on two cluster nodes (Windows Server 2003 R2
Enterprise
x64
Edition).

"Hilary Cotter" wrote:

IIRC, this is solved in SP1.

--
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business
intelligence.

This posting is my own and doesn't necessarily represent
RelevantNoise's
positions, strategies or opinions.

Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html

Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com



"Mickael Parisot" <mparisot@xxxxxxxxxxxxx> wrote in message
news:21D9ED05-21D8-44F2-961E-1D5B4CAF4796@xxxxxxxxxxxxxxxx
Hi,
Sometimes, I got the following error while trying to perform a
database
backup.
This backup is done on a regular basis using a maintenance
plan.
There is a full-text catalog in the database and there must be
a
conflict
somewhere.
Any idea?

------------

Date 14/09/2006 08:00:11
Journal Windows NT (Application)

Source MSSQL$BOL_PROD
Catégorie Server
Événement 3221229105
Utilisateur BRSAS\frbthhqisql36.sql
Ordinateur FRBTHHQISQL36

Message
The operating system returned the error '32(The process cannot
access
the
file because it is being used by another process.)' while
attempting
'CreateFile' on
'J:\BOL_PROD_DATA\MSSQL.4\MSSQL\FTData\Bihr_FullTextCatalog\SQL.HDR'
at
'fulltext.cpp'(529).















.



Relevant Pages

  • Re: Backup failure due to full-text indexing
    ... Shift the backup log after backup database (it was starting at the same ... Run filemon to check which process is accessing the fulltext catalog ... Director of Text Mining and Database Strategy ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Backup failure due to full-text indexing
    ... It seems that the fulltext catalog is offline sometimes which would explain ... BACKUP can be performed by using the FILEGROUP or FILE clauses ... Director of Text Mining and Database Strategy ...
    (microsoft.public.sqlserver.fulltext)
  • Re: Disappearing conflicts and snapshot
    ... Create a new database, and restore the backup into this database. ... Hilary Cotter ...
    (microsoft.public.sqlserver.replication)
  • RE: How do I restore from mdf and ldf files?
    ... Tasks -> Backup Database ... Tasks -> Restore Database ... Windows 2003 Server with Latest Service Pack ... Pre-requisites for Sharepoint Backup and Restore: ...
    (microsoft.public.sharepoint.portalserver)
  • Re: RMAN restore of full backup fails completely
    ... You are not using a catalog database. ... You might have autobackup controlfile on, ... Your autobackup has been made *prior* to the backup! ... plus archivelog', when i try a restore on the other server however, the ...
    (comp.databases.oracle.server)

Loading