principal db in "principal, synchronizing" state, the mirror in "restoring"

We have mirroring setup for 5 dbs, 4 of which are synchronized and 1 which is in "synchronizing" state on the principal and "restoring" state on the mirror. Mirroring for all dbs has been working fine for the past several months and we have a witness that has allowed automatic failover in the past without problems.

This database has several bulk inserts performed throughout the day and am sure there is some latency due to the size of these transactions.

Not sure as to why this is happening all of a sudden, but the db in question has been in this state for the past 12 hrs. I checked the mirroring status on the principal and it states that it is "synchronizing: data is being transferred from principal to mirror", but the mirror server states that db is in "restoring" state. Can anyone suggest as to how I can get the database on the mirroring server to get back to "mirror, synchronizing/restoring..." state? Or suggest on how I can troubleshoot this?

Thanks in advance.

Have you tried pulling up the Database Mirroring Monitor, to see what it shows? Do you have Unsent Log or Unrestored Log? Does the I/O subsystem on the mirror have comparable I/O capacity to the Principal?

Primary Filegroup is Full

I have encounting this problem:

DESCRIPTION: Error: 1105, Severity: 17, State: 2
Could not allocate space for object 'iislog' in database 'IISLOG' because the 'PRIMARY' filegroup is full.

I have check to see if the file is autogrow and it is. Is there a way to solve this problem?

ThanksCan the file grow? Is there enough room on the disk drive?

-PatP|||Yes the file can automatically grow at 10%. The space allocated is 13789MB and the actual file is 15707MB. I raise the automatically grow to 25% and that stop the SQL Messenger from sending me the email. I know it's a quick fix and that there is a major problem that is coming down the pike. Here are the configurations for the disk drive that the file is located on.

Capicity: 67.8 GB
Used: 64.9GB
Free: 2.83 GB

What would I need to do to solve this problem.

The name of the database is IISLOG which will only keep on growing. Because it logs all of the transactions from the intranet.

Please Help!!

Thanks

Lystra|||You need to offload data to another drive...you should be out of space....just....about......now....

It's probably 1 log table......which probably has a date...

You should schedule a nightly process to do this... I think I would bcp out the data...

There's another problem though...the transaction log will have to handle the deletes...|||How would I go about doing this.

Is it possible for me to copy and paste the database file to another drive in order to free up space? Or would I need to write code to do this?

As for the transaction logs they are truncating the logs.

Currently we are using the code below to remove the data, however the code is not removing all of the data and archiving it. It's causing major problem mostly on the weekend.

CREATE PROCEDURE sp_cleanupLOG AS
declare @.Today varchar(10)
select @.Today = convert(varchar(10),getdate(),101)
--select @.Today = '2002-03-30'
/*
delete rows from current iislog table
*/
delete from IISLOG..iislog
where ( LogTime >= DateAdd(day, -1, @.Today) AND LogTime < @.Today )

GO

Also if I use BCP to get the data out, can I schedule it as a job?

Thanks

Lystra|||Dont know whether it is suitable for you!

can you Dump the transaction log (Dump tran <databaseName>) everyday and take a back up of your database to another disk.

regards
Rohit