Weird Backup DB Problems in SQL Server 7

[jwbeaty]

Here's a weird one.

I'm running SQL Server 7 and when I run a backup something weird
happens. When I perform the backup via Enterprise Manager by right
clicking on the database I want to backup, I click on OK but no
progress blocks show up in the window showing you the status of the
backup. The completion window pops up saying that the DB has been
backed up. OK--Fine, maybe the backup is really quick. Then, through
Explorer, I look at the directory where the database backup is placed.
It reads 0 KB - but - about a minute later the the size of the backup
changes to the correct size. Seems strange, wouldn't the "completed"
window show up after the backup is out there??

Well, to make matters a little more interesting, when I define this
one database in a maintenance plan, the plan will complete but no
backup is present! The log file shows it runs OK - and - when I run
the plan through query analyser it says OK, too. But, no backup is
present.

What gives?

[Greg D. Moore \(Strider\)]

"jwbeaty" <jw*****@swbell.net> wrote in message
news:3f**************************@posting.google.c om...

Here's a weird one.

I'm running SQL Server 7 and when I run a backup something weird
happens. When I perform the backup via Enterprise Manager by right
clicking on the database I want to backup, I click on OK but no
progress blocks show up in the window showing you the status of the
backup. The completion window pops up saying that the DB has been
backed up. OK--Fine, maybe the backup is really quick. Then, through
Explorer, I look at the directory where the database backup is placed.
It reads 0 KB - but - about a minute later the the size of the backup
changes to the correct size. Seems strange, wouldn't the "completed"
window show up after the backup is out there??

Well, to make matters a little more interesting, when I define this
one database in a maintenance plan, the plan will complete but no
backup is present! The log file shows it runs OK - and - when I run
the plan through query analyser it says OK, too. But, no backup is
present.
Can you script out what you are doing and show where your backups are going
(or at least where you think they are going. :-)


What gives?

[jwbeaty]

"Greg D. Moore \(Strider\)" <mo*****@greenms.com> wrote in message news:<Kj********************@twister.nyroc.rr.com> ...

"jwbeaty" <jw*****@swbell.net> wrote in message
news:3f**************************@posting.google.c om...

Here's a weird one.

I'm running SQL Server 7 and when I run a backup something weird
happens. When I perform the backup via Enterprise Manager by right
clicking on the database I want to backup, I click on OK but no
progress blocks show up in the window showing you the status of the
backup. The completion window pops up saying that the DB has been
backed up. OK--Fine, maybe the backup is really quick. Then, through
Explorer, I look at the directory where the database backup is placed.
It reads 0 KB - but - about a minute later the the size of the backup
changes to the correct size. Seems strange, wouldn't the "completed"
window show up after the backup is out there??

Well, to make matters a little more interesting, when I define this
one database in a maintenance plan, the plan will complete but no
backup is present! The log file shows it runs OK - and - when I run
the plan through query analyser it says OK, too. But, no backup is
present.

Can you script out what you are doing and show where your backups are going
(or at least where you think they are going. :-)

What gives?

Sure. Here's the generated backup maintenance plan:

EXECUTE master.dbo.xp_sqlmaint N'-PlanID
3096F3E1-111C-47AE-A34B-265DA966360C -Rpt "D:\MSSQL7\LOG\Backup FOO_DB
Database4.txt" -WriteHistory -VrfyBackup -BkUpMedia DISK -BkUpDB
"D:\MSSQL7\BACKUP" -DelBkUps 3DAYS -BkExt "BAK"'

I ran it manually under Query Analyzer and it generates a 0 KB file in
the directory D:\MSSQL7\BACKUP then the 0 KB file vanishes--BUT, the
logfile says the job ran without error. It only does this on one
database. All other database maintenance plans run fine. If I run a
BACKUP DATABASE command from analyzer, it runs OK.

I just worked around this by creating a BACKUP sql statement in a job.
DBCC CHECKDB on the database shows nothing out of the ordinary (no
errors, etc.)

Anyway, I will be doing some more research on this. If I find out
anything I will post it here. If anyone has ever seen this scenario
before, let me know.

Thanks all.