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