backup db occurs error

Now I meet a question when backup SQLserver7.0,It prompt me the following attachment and I check the SQLserver log :"Using 'xpsql70.dll' version '1998.11.13' to execute extended stored procedure 'xp_msver'.
Error: 9002, Severity: 17, State: 2,The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.."

Pls help me. Thanks with best regards.Error: 9002, Severity: 17, State: 2,The log file for database 'tempdb' is full. Back up the transaction log for the database to free up some log space.."

I am receiving this error when attempting a restore of a 7.0 database. The log is set to autoextend. Immediately following these messages I am getting a "write failure on backup device".

Anyone experiencing these problems? Could it be that tempdb's log file has been corrupted? Any help with this would be greatly appreciated.

backup db occurs error

Today I backup the SQLServer7.0,it prompt me error:
"Microsoft SQL-DMO(ODBC SQLState:42000)
Backup,CHECKALLOC,bulk copy,SELECT INTO,and file manipulation(such as CREATE FILE) operations on a database must be serialized.
Reissue the statement after the current backup,CHECKALLOC,or file manipulation operation is completed.
Backup or RESTORE OPERATION terminating abnormally."

Pls help me. Thanks with best regards.The error simply means that at the time the backup dump operation was attempted it could not be executed (because of other activity in progress).

Often, this is a result of attempting to run backups when maintenance is in progress.

If that is the issue try to run or schedule backup dumps at times when DB maintenance is complete (not in progress).sql

Backup Behaviour During Full/Diff/Log Backups Running Concurrently

If log backups are started while a full backup is already running, what if
any effect occurs to the full backup? In SQL Server 2000 I think that all
log backups are paused if a full is already running. I can't find any MS
articles that explains explicitly what the interaction/behaviour or result is
if full/diff/log backup jobs for the same database should overlap. Thanx.
-CqlboyThe backup that started first will block other backups. for example if you
start the log backup and then database full backup(log backup still running)
the full database will be blocked on log backup to finish and vice
versa...also same behavior true for differential backup.
"Cqlboy" wrote:
> If log backups are started while a full backup is already running, what if
> any effect occurs to the full backup? In SQL Server 2000 I think that all
> log backups are paused if a full is already running. I can't find any MS
> articles that explains explicitly what the interaction/behaviour or result is
> if full/diff/log backup jobs for the same database should overlap. Thanx.
> -Cqlboy|||Thanx. I've heard that if you execute a DIFF while FULL is running it will
error out. This has been fixed in 2005. I'm more interested in finding out
what if a FULL can maintain transactional consistency if a LOG backup was
performed during execution of the FULL. Log backups truncate the inactive
portion of the log. A FULL uses the transaction log as part of it's strategy
to compile the FULL backup.
"harvinder" wrote:
> The backup that started first will block other backups. for example if you
> start the log backup and then database full backup(log backup still running)
> the full database will be blocked on log backup to finish and vice
> versa...also same behavior true for differential backup.
> "Cqlboy" wrote:
> > If log backups are started while a full backup is already running, what if
> > any effect occurs to the full backup? In SQL Server 2000 I think that all
> > log backups are paused if a full is already running. I can't find any MS
> > articles that explains explicitly what the interaction/behaviour or result is
> > if full/diff/log backup jobs for the same database should overlap. Thanx.
> > -Cqlboy

Backup Behaviour During Full/Diff/Log Backups Running Concurrently

If log backups are started while a full backup is already running, what if
any effect occurs to the full backup? In SQL Server 2000 I think that all
log backups are paused if a full is already running. I can't find any MS
articles that explains explicitly what the interaction/behaviour or result i
s
if full/diff/log backup jobs for the same database should overlap. Thanx.
-CqlboyThe backup that started first will block other backups. for example if you
start the log backup and then database full backup(log backup still running)
the full database will be blocked on log backup to finish and vice
versa...also same behavior true for differential backup.
"Cqlboy" wrote:

> If log backups are started while a full backup is already running, what if
> any effect occurs to the full backup? In SQL Server 2000 I think that all
> log backups are paused if a full is already running. I can't find any MS
> articles that explains explicitly what the interaction/behaviour or result
is
> if full/diff/log backup jobs for the same database should overlap. Thanx.
> -Cqlboy

Backup Behaviour During Full/Diff/Log Backups Running Concurrently

If log backups are started while a full backup is already running, what if
any effect occurs to the full backup? In SQL Server 2000 I think that all
log backups are paused if a full is already running. I can't find any MS
articles that explains explicitly what the interaction/behaviour or result is
if full/diff/log backup jobs for the same database should overlap. Thanx.
-Cqlboy
The backup that started first will block other backups. for example if you
start the log backup and then database full backup(log backup still running)
the full database will be blocked on log backup to finish and vice
versa...also same behavior true for differential backup.
"Cqlboy" wrote:

> If log backups are started while a full backup is already running, what if
> any effect occurs to the full backup? In SQL Server 2000 I think that all
> log backups are paused if a full is already running. I can't find any MS
> articles that explains explicitly what the interaction/behaviour or result is
> if full/diff/log backup jobs for the same database should overlap. Thanx.
> -Cqlboy