Backup job succeeds but not actually backing up

I have a server with Windows 2000 SP4+hotfixes, SQL Server
2000 SE SP3A+hotfix. The server has 4 user databases (the
largest being around 500 megs). 3 of the databases backup
fine but 1 database will not take a full backup or a
transaction log backup from the maintenance plan. The job
runs and succeeds but the file is not where it should be
(nor anywhere else).
The development server with the same configuration does
not have this same problem, and it takes about 7 seconds
to backup the database in question.
I have monitored the directory that the file should be
created in while the job is running, and the file does
create and stays there for the 5 to 7 seconds that the job
is running and then it dissappears.
I have also used File Monitor from sysinternals and
monitored the system while a backup is being run and
sqlservr.exe and sqlmaint.exe are the only things that
touch the .BAK file. Sqlservr.exe reads and writes to
the .BAK file numerous times and the last thing that
happens is sqlservr.exe opens the .BAK file, then Deletes
the .BAK file, and then closes the .BAK file. No other
applications besides sqlservr.exe and sqlmaint.exe touch
the .BAK file. The index numbers in File Monitor do not
skip any numbers.
Here are the lines from sysinternals File Monitor where
the backup is deleted:
1646 6:32:56 PM sqlservr.exe:3688 OPEN
E:\Microsoft SQL
Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
SUCCESS Options: Open Access: All
1647 6:32:56 PM sqlservr.exe:3688 DELETE
E:\Microsoft SQL
Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
SUCCESS
1648 6:32:56 PM sqlservr.exe:3688 CLOSE
E:\Microsoft SQL
Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
SUCCESS
The error message in the errorlog is:
BACKUP failed to complete the command BACKUP LOG [t_prod]
TO DISK = N'E:\Microsoft SQL
Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK'
WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
Disk space is not an issue as there is over 60 gigs free
and all the databases together barely total a 1 gig.
Backups from a script that run through a job (without the
maint plan wizard) succeed about 75% of the time but about
25% of the time the job fails with the same errors as the
maint plan fails with. I'm still trying to get File
Monitor running at the time a backup from a script fails,
but haven't been luckly enough to catch it at the right
time yet.
Any information or suggestions to resolve this problem are
greatly appreaciated as I've been trying to figure this
out for too long. If there is any other information that
would be useful to post, please let me know.
Thanks,
Trent.any clues from the NT's system or application error log
files?
this may be dumb thing to ask, but make sure that backup
retention option is properly set in db maint plan.
>--Original Message--
>I have a server with Windows 2000 SP4+hotfixes, SQL
Server
>2000 SE SP3A+hotfix. The server has 4 user databases
(the
>largest being around 500 megs). 3 of the databases
backup
>fine but 1 database will not take a full backup or a
>transaction log backup from the maintenance plan. The
job
>runs and succeeds but the file is not where it should be
>(nor anywhere else).
>The development server with the same configuration does
>not have this same problem, and it takes about 7 seconds
>to backup the database in question.
>I have monitored the directory that the file should be
>created in while the job is running, and the file does
>create and stays there for the 5 to 7 seconds that the
job
>is running and then it dissappears.
>I have also used File Monitor from sysinternals and
>monitored the system while a backup is being run and
>sqlservr.exe and sqlmaint.exe are the only things that
>touch the .BAK file. Sqlservr.exe reads and writes to
>the .BAK file numerous times and the last thing that
>happens is sqlservr.exe opens the .BAK file, then Deletes
>the .BAK file, and then closes the .BAK file. No other
>applications besides sqlservr.exe and sqlmaint.exe touch
>the .BAK file. The index numbers in File Monitor do not
>skip any numbers.
>Here are the lines from sysinternals File Monitor where
>the backup is deleted:
>1646 6:32:56 PM sqlservr.exe:3688 OPEN
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS Options: Open Access: All
>1647 6:32:56 PM sqlservr.exe:3688 DELETE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>
>The error message in the errorlog is:
>BACKUP failed to complete the command BACKUP LOG [t_prod]
>TO DISK = N'E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK'
>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>Disk space is not an issue as there is over 60 gigs free
>and all the databases together barely total a 1 gig.
>Backups from a script that run through a job (without the
>maint plan wizard) succeed about 75% of the time but
about
>25% of the time the job fails with the same errors as the
>maint plan fails with. I'm still trying to get File
>Monitor running at the time a backup from a script fails,
>but haven't been luckly enough to catch it at the right
>time yet.
>Any information or suggestions to resolve this problem
are
>greatly appreaciated as I've been trying to figure this
>out for too long. If there is any other information that
>would be useful to post, please let me know.
>Thanks,
>Trent.
>.
>|||There is no errors in the SQL errorlog, NT system or
application error logs unless I turn on the option to
verify the integrity of the backup upon completion. Then
the error message is:
Operating system error = 2 (the system cannot find the
file specified)
OR
Operating system error = 32 (The process cannot access the
file because it is being used by another process).
It's intermittent which of the above 2 errors will come
up. The os error = 32 was the reason I ran File Monitor,
but it didn't lead me to the cause as nothing but SQL
Server appeared to be using the file.
Trent.
>--Original Message--
>any clues from the NT's system or application error log
>files?
>this may be dumb thing to ask, but make sure that backup
>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>Server
>>2000 SE SP3A+hotfix. The server has 4 user databases
>(the
>>largest being around 500 megs). 3 of the databases
>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan. The
>job
>>runs and succeeds but the file is not where it should be
>>(nor anywhere else).
>>The development server with the same configuration does
>>not have this same problem, and it takes about 7 seconds
>>to backup the database in question.
>>I have monitored the directory that the file should be
>>created in while the job is running, and the file does
>>create and stays there for the 5 to 7 seconds that the
>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things that
>>touch the .BAK file. Sqlservr.exe reads and writes to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
Deletes
>>the .BAK file, and then closes the .BAK file. No other
>>applications besides sqlservr.exe and sqlmaint.exe touch
>>the .BAK file. The index numbers in File Monitor do not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688 OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688 DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job (without
the
>>maint plan wizard) succeed about 75% of the time but
>about
>>25% of the time the job fails with the same errors as
the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
fails,
>>but haven't been luckly enough to catch it at the right
>>time yet.
>>Any information or suggestions to resolve this problem
>are
>>greatly appreaciated as I've been trying to figure this
>>out for too long. If there is any other information
that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>.
>|||Sorry, forgot to comment on the retention. It has always
been set at 5 days but I have tried turning the retention
off and it makes no difference.
Trent.
>--Original Message--
>any clues from the NT's system or application error log
>files?
>this may be dumb thing to ask, but make sure that backup
>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>Server
>>2000 SE SP3A+hotfix. The server has 4 user databases
>(the
>>largest being around 500 megs). 3 of the databases
>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan. The
>job
>>runs and succeeds but the file is not where it should be
>>(nor anywhere else).
>>The development server with the same configuration does
>>not have this same problem, and it takes about 7 seconds
>>to backup the database in question.
>>I have monitored the directory that the file should be
>>created in while the job is running, and the file does
>>create and stays there for the 5 to 7 seconds that the
>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things that
>>touch the .BAK file. Sqlservr.exe reads and writes to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
Deletes
>>the .BAK file, and then closes the .BAK file. No other
>>applications besides sqlservr.exe and sqlmaint.exe touch
>>the .BAK file. The index numbers in File Monitor do not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688 OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688 DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job (without
the
>>maint plan wizard) succeed about 75% of the time but
>about
>>25% of the time the job fails with the same errors as
the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
fails,
>>but haven't been luckly enough to catch it at the right
>>time yet.
>>Any information or suggestions to resolve this problem
>are
>>greatly appreaciated as I've been trying to figure this
>>out for too long. If there is any other information
that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>.
>|||Trent and Others!
I am experiencing the same behavior on my SQL Server 7.0
running on NT (lastest service packs and patched on
both.) I too have witnessed the BAK file created and then
deleted. I do not have the maintance plan configured to
deleting old .BAK files. I do receive this error message
when I create a backup from the "backup" option (not the
database maintenance plan.) This is the message I get:
10 percent backed up. [SQLSTATE 01000] (Message 3211) 20
percent backed up. [SQLSTATE 01000] (Message 3211)
ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message
258) General network error. Check your network
documentation. [SQLSTATE 08S01] (Error 11) 30 percent
backed up. [SQLSTATE 01000] (Message 3211). The step
failed.
NOTE: I am backing up to the server harddrive(NO NETWORK
INVOLVED!!!)with 20 gigs free. This database is only
199mb in size. I suspect the "general network error" is
bogus.
Please help!
>--Original Message--
>I have a server with Windows 2000 SP4+hotfixes, SQL
Server
>2000 SE SP3A+hotfix. The server has 4 user databases
(the
>largest being around 500 megs). 3 of the databases
backup
>fine but 1 database will not take a full backup or a
>transaction log backup from the maintenance plan. The
job
>runs and succeeds but the file is not where it should be
>(nor anywhere else).
>The development server with the same configuration does
>not have this same problem, and it takes about 7 seconds
>to backup the database in question.
>I have monitored the directory that the file should be
>created in while the job is running, and the file does
>create and stays there for the 5 to 7 seconds that the
job
>is running and then it dissappears.
>I have also used File Monitor from sysinternals and
>monitored the system while a backup is being run and
>sqlservr.exe and sqlmaint.exe are the only things that
>touch the .BAK file. Sqlservr.exe reads and writes to
>the .BAK file numerous times and the last thing that
>happens is sqlservr.exe opens the .BAK file, then Deletes
>the .BAK file, and then closes the .BAK file. No other
>applications besides sqlservr.exe and sqlmaint.exe touch
>the .BAK file. The index numbers in File Monitor do not
>skip any numbers.
>Here are the lines from sysinternals File Monitor where
>the backup is deleted:
>1646 6:32:56 PM sqlservr.exe:3688 OPEN
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS Options: Open Access: All
>1647 6:32:56 PM sqlservr.exe:3688 DELETE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>
>The error message in the errorlog is:
>BACKUP failed to complete the command BACKUP LOG [t_prod]
>TO DISK = N'E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK'
>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>Disk space is not an issue as there is over 60 gigs free
>and all the databases together barely total a 1 gig.
>Backups from a script that run through a job (without the
>maint plan wizard) succeed about 75% of the time but
about
>25% of the time the job fails with the same errors as the
>maint plan fails with. I'm still trying to get File
>Monitor running at the time a backup from a script fails,
>but haven't been luckly enough to catch it at the right
>time yet.
>Any information or suggestions to resolve this problem
are
>greatly appreaciated as I've been trying to figure this
>out for too long. If there is any other information that
>would be useful to post, please let me know.
>Thanks,
>Trent.
>.
>|||I don't know if this will make any difference or not, but
do you specify the filename as the destination for the
backup, or do you create a backup device first?
Also, have you run a DBCC consistency chekc on the
database you're attempting to backup? Maybe the actual
failure is on the read from the DB side of the backup
process?
Just some early in the morning thoughts that may or may
not help.
Matthew Bando
BandoM@.CSCTechnologies (remove).com
>--Original Message--
>Sorry, forgot to comment on the retention. It has
always
>been set at 5 days but I have tried turning the
retention
>off and it makes no difference.
>Trent.
>>--Original Message--
>>any clues from the NT's system or application error log
>>files?
>>this may be dumb thing to ask, but make sure that
backup
>>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>>Server
>>2000 SE SP3A+hotfix. The server has 4 user databases
>>(the
>>largest being around 500 megs). 3 of the databases
>>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan. The
>>job
>>runs and succeeds but the file is not where it should
be
>>(nor anywhere else).
>>The development server with the same configuration
does
>>not have this same problem, and it takes about 7
seconds
>>to backup the database in question.
>>I have monitored the directory that the file should be
>>created in while the job is running, and the file does
>>create and stays there for the 5 to 7 seconds that the
>>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things that
>>touch the .BAK file. Sqlservr.exe reads and writes to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
>Deletes
>>the .BAK file, and then closes the .BAK file. No
other
>>applications besides sqlservr.exe and sqlmaint.exe
touch
>>the .BAK file. The index numbers in File Monitor do
not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor
where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688 OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
AK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688 DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
AK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
AK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
>[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
AK
>'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs
free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job (without
>the
>>maint plan wizard) succeed about 75% of the time but
>>about
>>25% of the time the job fails with the same errors as
>the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
>fails,
>>but haven't been luckly enough to catch it at the
right
>>time yet.
>>Any information or suggestions to resolve this problem
>>are
>>greatly appreaciated as I've been trying to figure
this
>>out for too long. If there is any other information
>that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>>.
>.
>|||I have noticed this same message occasionaly (about 25% of
the time) when backing up from QA or when scheduling a
backup command in a job. I found a hit on technet but it
kinda just let me to believe it was a named pipes bug and
not the actual root of the problem.
Here is the article I was talking about:
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%
3B827452
Trent.
>--Original Message--
>Trent and Others!
>I am experiencing the same behavior on my SQL Server 7.0
>running on NT (lastest service packs and patched on
>both.) I too have witnessed the BAK file created and
then
>deleted. I do not have the maintance plan configured to
>deleting old .BAK files. I do receive this error message
>when I create a backup from the "backup" option (not the
>database maintenance plan.) This is the message I get:
>10 percent backed up. [SQLSTATE 01000] (Message 3211) 20
>percent backed up. [SQLSTATE 01000] (Message 3211)
>ConnectionRead (WrapperRead()). [SQLSTATE 01000] (Message
>258) General network error. Check your network
>documentation. [SQLSTATE 08S01] (Error 11) 30 percent
>backed up. [SQLSTATE 01000] (Message 3211). The step
>failed.
>NOTE: I am backing up to the server harddrive(NO NETWORK
>INVOLVED!!!)with 20 gigs free. This database is only
>199mb in size. I suspect the "general network error" is
>bogus.
>Please help!
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>Server
>>2000 SE SP3A+hotfix. The server has 4 user databases
>(the
>>largest being around 500 megs). 3 of the databases
>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan. The
>job
>>runs and succeeds but the file is not where it should be
>>(nor anywhere else).
>>The development server with the same configuration does
>>not have this same problem, and it takes about 7 seconds
>>to backup the database in question.
>>I have monitored the directory that the file should be
>>created in while the job is running, and the file does
>>create and stays there for the 5 to 7 seconds that the
>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things that
>>touch the .BAK file. Sqlservr.exe reads and writes to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
Deletes
>>the .BAK file, and then closes the .BAK file. No other
>>applications besides sqlservr.exe and sqlmaint.exe touch
>>the .BAK file. The index numbers in File Monitor do not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688 OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688 DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job (without
the
>>maint plan wizard) succeed about 75% of the time but
>about
>>25% of the time the job fails with the same errors as
the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
fails,
>>but haven't been luckly enough to catch it at the right
>>time yet.
>>Any information or suggestions to resolve this problem
>are
>>greatly appreaciated as I've been trying to figure this
>>out for too long. If there is any other information
that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>.
>|||Hi Matthew,
Thanks for the reply. I always backup to a filename,
mainly because that's just the way I normally do it. I
have experimented with backing up to a device and it does
seem to work (although I never extensively tested it) but
it's starting to look like my only option.
I run DBCC checks weekly and they never find any errors (I
double checked the last 6 weeks of dbcc checks to make
sure they didn't find any errors)
Trent.
>--Original Message--
>I don't know if this will make any difference or not, but
>do you specify the filename as the destination for the
>backup, or do you create a backup device first?
>Also, have you run a DBCC consistency chekc on the
>database you're attempting to backup? Maybe the actual
>failure is on the read from the DB side of the backup
>process?
>Just some early in the morning thoughts that may or may
>not help.
>Matthew Bando
>BandoM@.CSCTechnologies (remove).com
>
>>--Original Message--
>>Sorry, forgot to comment on the retention. It has
>always
>>been set at 5 days but I have tried turning the
>retention
>>off and it makes no difference.
>>Trent.
>>--Original Message--
>>any clues from the NT's system or application error log
>>files?
>>this may be dumb thing to ask, but make sure that
>backup
>>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>>Server
>>2000 SE SP3A+hotfix. The server has 4 user databases
>>(the
>>largest being around 500 megs). 3 of the databases
>>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan. The
>>job
>>runs and succeeds but the file is not where it should
>be
>>(nor anywhere else).
>>The development server with the same configuration
>does
>>not have this same problem, and it takes about 7
>seconds
>>to backup the database in question.
>>I have monitored the directory that the file should be
>>created in while the job is running, and the file does
>>create and stays there for the 5 to 7 seconds that the
>>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things that
>>touch the .BAK file. Sqlservr.exe reads and writes to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
>>Deletes
>>the .BAK file, and then closes the .BAK file. No
>other
>>applications besides sqlservr.exe and sqlmaint.exe
>touch
>>the .BAK file. The index numbers in File Monitor do
>not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor
>where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688
OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
>AK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688
DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
>AK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688
CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
>AK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
>>[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.B
>AK
>>'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs
>free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job (without
>>the
>>maint plan wizard) succeed about 75% of the time but
>>about
>>25% of the time the job fails with the same errors as
>>the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
>>fails,
>>but haven't been luckly enough to catch it at the
>right
>>time yet.
>>Any information or suggestions to resolve this problem
>>are
>>greatly appreaciated as I've been trying to figure
>this
>>out for too long. If there is any other information
>>that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>>.
>>.
>.
>|||All I can say is that it's very odd. Sometimes things
that should be equivalent (like backing up to a file
directly or backing up to a device that is a file) aren't
equivalent.
It will be interestign to see if you switch to always
using a device, if you eventually see the same error.
Matthew Bando
BandoM@.CSCTechnologies (remove) .com
>--Original Message--
>Hi Matthew,
>Thanks for the reply. I always backup to a filename,
>mainly because that's just the way I normally do it. I
>have experimented with backing up to a device and it
does
>seem to work (although I never extensively tested it)
but
>it's starting to look like my only option.
>I run DBCC checks weekly and they never find any errors
(I
>double checked the last 6 weeks of dbcc checks to make
>sure they didn't find any errors)
>Trent.
>>--Original Message--
>>I don't know if this will make any difference or not,
but
>>do you specify the filename as the destination for the
>>backup, or do you create a backup device first?
>>Also, have you run a DBCC consistency chekc on the
>>database you're attempting to backup? Maybe the actual
>>failure is on the read from the DB side of the backup
>>process?
>>Just some early in the morning thoughts that may or may
>>not help.
>>Matthew Bando
>>BandoM@.CSCTechnologies (remove).com
>>
>>--Original Message--
>>Sorry, forgot to comment on the retention. It has
>>always
>>been set at 5 days but I have tried turning the
>>retention
>>off and it makes no difference.
>>Trent.
>>--Original Message--
>>any clues from the NT's system or application error
log
>>files?
>>this may be dumb thing to ask, but make sure that
>>backup
>>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>>Server
>>2000 SE SP3A+hotfix. The server has 4 user
databases
>>(the
>>largest being around 500 megs). 3 of the databases
>>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan.
The
>>job
>>runs and succeeds but the file is not where it
should
>>be
>>(nor anywhere else).
>>The development server with the same configuration
>>does
>>not have this same problem, and it takes about 7
>>seconds
>>to backup the database in question.
>>I have monitored the directory that the file should
be
>>created in while the job is running, and the file
does
>>create and stays there for the 5 to 7 seconds that
the
>>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things
that
>>touch the .BAK file. Sqlservr.exe reads and writes
to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
>>Deletes
>>the .BAK file, and then closes the .BAK file. No
>>other
>>applications besides sqlservr.exe and sqlmaint.exe
>>touch
>>the .BAK file. The index numbers in File Monitor do
>>not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor
>>where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688
> OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688
> DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688
> CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
>>[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>>'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs
>>free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job
(without
>>the
>>maint plan wizard) succeed about 75% of the time but
>>about
>>25% of the time the job fails with the same errors
as
>>the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
>>fails,
>>but haven't been luckly enough to catch it at the
>>right
>>time yet.
>>Any information or suggestions to resolve this
problem
>>are
>>greatly appreaciated as I've been trying to figure
>>this
>>out for too long. If there is any other information
>>that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>>.
>>.
>>.
>.
>|||Do you have some sort of virus scanner/open file manager active on that
server? I vaguely recall that such tools used to give us trouble with
certain versions of the scanner, the OS and SQL Server.
"Trent" <anonymous@.discussions.microsoft.com> wrote in message
news:0f9601c3b395$e9042d90$a001280a@.phx.gbl...
> I have a server with Windows 2000 SP4+hotfixes, SQL Server
> 2000 SE SP3A+hotfix. The server has 4 user databases (the
> largest being around 500 megs). 3 of the databases backup
> fine but 1 database will not take a full backup or a
> transaction log backup from the maintenance plan. The job
> runs and succeeds but the file is not where it should be
> (nor anywhere else).
> The development server with the same configuration does
> not have this same problem, and it takes about 7 seconds
> to backup the database in question.
> I have monitored the directory that the file should be
> created in while the job is running, and the file does
> create and stays there for the 5 to 7 seconds that the job
> is running and then it dissappears.
> I have also used File Monitor from sysinternals and
> monitored the system while a backup is being run and
> sqlservr.exe and sqlmaint.exe are the only things that
> touch the .BAK file. Sqlservr.exe reads and writes to
> the .BAK file numerous times and the last thing that
> happens is sqlservr.exe opens the .BAK file, then Deletes
> the .BAK file, and then closes the .BAK file. No other
> applications besides sqlservr.exe and sqlmaint.exe touch
> the .BAK file. The index numbers in File Monitor do not
> skip any numbers.
> Here are the lines from sysinternals File Monitor where
> the backup is deleted:
> 1646 6:32:56 PM sqlservr.exe:3688 OPEN
> E:\Microsoft SQL
> Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS Options: Open Access: All
> 1647 6:32:56 PM sqlservr.exe:3688 DELETE
> E:\Microsoft SQL
> Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
> 1648 6:32:56 PM sqlservr.exe:3688 CLOSE
> E:\Microsoft SQL
> Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>
> The error message in the errorlog is:
> BACKUP failed to complete the command BACKUP LOG [t_prod]
> TO DISK = N'E:\Microsoft SQL
> Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK'
> WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
> Disk space is not an issue as there is over 60 gigs free
> and all the databases together barely total a 1 gig.
> Backups from a script that run through a job (without the
> maint plan wizard) succeed about 75% of the time but about
> 25% of the time the job fails with the same errors as the
> maint plan fails with. I'm still trying to get File
> Monitor running at the time a backup from a script fails,
> but haven't been luckly enough to catch it at the right
> time yet.
> Any information or suggestions to resolve this problem are
> greatly appreaciated as I've been trying to figure this
> out for too long. If there is any other information that
> would be useful to post, please let me know.
> Thanks,
> Trent.|||I received a responds to my posting and the tech made the
point that really made sense to me. I knew transactions
rolled back. But he mentioned that a failed backup job
rolls back.
I decided to create a backup job manually. It worked!!!
Then I scheduled it through the job interfaced and it ran
as scheduled.
To clarify this to you:
Backup Job FAILS when I do the following steps:
Create a backup device, i.e. otg_backupdevice
Right click on the new backup device (otg_backupdevice)
and select "Backup a Database"
The SQL Server backup wizard window appears, select the
database (otg) to backup, add the backup device
(otg_backupdevice) and schedule the backup to occur once
a day at 12:00 A.M.
Then ran the job from the jobs window
The job fails.
Backup Job Succeeds when I do the following steps:
Create a backup device, i.e. otg_backupdevice
Go to the job window
Right-click and select new job
Name the job - OTG backup to device
Click on the "Steps" tab and click on "New Step"
Select OTG as the database
In the command window I enter "backup database otg to
otg_backupdevice"
Click on the "Schedule" tab and schedule it to backup at
10:00 am
The job suceeds
I suspect there is a problem with the backup wizard'
Kathy
>--Original Message--
>Hi Matthew,
>Thanks for the reply. I always backup to a filename,
>mainly because that's just the way I normally do it. I
>have experimented with backing up to a device and it
does
>seem to work (although I never extensively tested it)
but
>it's starting to look like my only option.
>I run DBCC checks weekly and they never find any errors
(I
>double checked the last 6 weeks of dbcc checks to make
>sure they didn't find any errors)
>Trent.
>>--Original Message--
>>I don't know if this will make any difference or not,
but
>>do you specify the filename as the destination for the
>>backup, or do you create a backup device first?
>>Also, have you run a DBCC consistency chekc on the
>>database you're attempting to backup? Maybe the actual
>>failure is on the read from the DB side of the backup
>>process?
>>Just some early in the morning thoughts that may or may
>>not help.
>>Matthew Bando
>>BandoM@.CSCTechnologies (remove).com
>>
>>--Original Message--
>>Sorry, forgot to comment on the retention. It has
>>always
>>been set at 5 days but I have tried turning the
>>retention
>>off and it makes no difference.
>>Trent.
>>--Original Message--
>>any clues from the NT's system or application error
log
>>files?
>>this may be dumb thing to ask, but make sure that
>>backup
>>retention option is properly set in db maint plan.
>>--Original Message--
>>I have a server with Windows 2000 SP4+hotfixes, SQL
>>Server
>>2000 SE SP3A+hotfix. The server has 4 user
databases
>>(the
>>largest being around 500 megs). 3 of the databases
>>backup
>>fine but 1 database will not take a full backup or a
>>transaction log backup from the maintenance plan.
The
>>job
>>runs and succeeds but the file is not where it
should
>>be
>>(nor anywhere else).
>>The development server with the same configuration
>>does
>>not have this same problem, and it takes about 7
>>seconds
>>to backup the database in question.
>>I have monitored the directory that the file should
be
>>created in while the job is running, and the file
does
>>create and stays there for the 5 to 7 seconds that
the
>>job
>>is running and then it dissappears.
>>I have also used File Monitor from sysinternals and
>>monitored the system while a backup is being run and
>>sqlservr.exe and sqlmaint.exe are the only things
that
>>touch the .BAK file. Sqlservr.exe reads and writes
to
>>the .BAK file numerous times and the last thing that
>>happens is sqlservr.exe opens the .BAK file, then
>>Deletes
>>the .BAK file, and then closes the .BAK file. No
>>other
>>applications besides sqlservr.exe and sqlmaint.exe
>>touch
>>the .BAK file. The index numbers in File Monitor do
>>not
>>skip any numbers.
>>Here are the lines from sysinternals File Monitor
>>where
>>the backup is deleted:
>>1646 6:32:56 PM sqlservr.exe:3688
> OPEN
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS Options: Open Access: All
>>1647 6:32:56 PM sqlservr.exe:3688
> DELETE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS
>>1648 6:32:56 PM sqlservr.exe:3688
> CLOSE
>> E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>> SUCCESS
>>
>>The error message in the errorlog is:
>>BACKUP failed to complete the command BACKUP LOG
>>[t_prod]
>>TO DISK = N'E:\Microsoft SQL
>>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
.B
>>AK
>>'
>>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>>Disk space is not an issue as there is over 60 gigs
>>free
>>and all the databases together barely total a 1 gig.
>>Backups from a script that run through a job
(without
>>the
>>maint plan wizard) succeed about 75% of the time but
>>about
>>25% of the time the job fails with the same errors
as
>>the
>>maint plan fails with. I'm still trying to get File
>>Monitor running at the time a backup from a script
>>fails,
>>but haven't been luckly enough to catch it at the
>>right
>>time yet.
>>Any information or suggestions to resolve this
problem
>>are
>>greatly appreaciated as I've been trying to figure
>>this
>>out for too long. If there is any other information
>>that
>>would be useful to post, please let me know.
>>Thanks,
>>Trent.
>>.
>>.
>>.
>>.
>.
>|||Just wanted to say a quick thank you to all that replied
with suggestions. I finally stumbled accross the problem
when looking for something else. Someone had entered an
invalid named pipes alias in the client network utility on
the server. Deleting this alias solved all my problems
and my backups (full and trans log) have not failed since
removing this alias.
Trent.
>--Original Message--
>I have a server with Windows 2000 SP4+hotfixes, SQL
Server
>2000 SE SP3A+hotfix. The server has 4 user databases
(the
>largest being around 500 megs). 3 of the databases
backup
>fine but 1 database will not take a full backup or a
>transaction log backup from the maintenance plan. The
job
>runs and succeeds but the file is not where it should be
>(nor anywhere else).
>The development server with the same configuration does
>not have this same problem, and it takes about 7 seconds
>to backup the database in question.
>I have monitored the directory that the file should be
>created in while the job is running, and the file does
>create and stays there for the 5 to 7 seconds that the
job
>is running and then it dissappears.
>I have also used File Monitor from sysinternals and
>monitored the system while a backup is being run and
>sqlservr.exe and sqlmaint.exe are the only things that
>touch the .BAK file. Sqlservr.exe reads and writes to
>the .BAK file numerous times and the last thing that
>happens is sqlservr.exe opens the .BAK file, then Deletes
>the .BAK file, and then closes the .BAK file. No other
>applications besides sqlservr.exe and sqlmaint.exe touch
>the .BAK file. The index numbers in File Monitor do not
>skip any numbers.
>Here are the lines from sysinternals File Monitor where
>the backup is deleted:
>1646 6:32:56 PM sqlservr.exe:3688 OPEN
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS Options: Open Access: All
>1647 6:32:56 PM sqlservr.exe:3688 DELETE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>1648 6:32:56 PM sqlservr.exe:3688 CLOSE
> E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK
> SUCCESS
>
>The error message in the errorlog is:
>BACKUP failed to complete the command BACKUP LOG [t_prod]
>TO DISK = N'E:\Microsoft SQL
>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832.BAK'
>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
>Disk space is not an issue as there is over 60 gigs free
>and all the databases together barely total a 1 gig.
>Backups from a script that run through a job (without the
>maint plan wizard) succeed about 75% of the time but
about
>25% of the time the job fails with the same errors as the
>maint plan fails with. I'm still trying to get File
>Monitor running at the time a backup from a script fails,
>but haven't been luckly enough to catch it at the right
>time yet.
>Any information or suggestions to resolve this problem
are
>greatly appreaciated as I've been trying to figure this
>out for too long. If there is any other information that
>would be useful to post, please let me know.
>Thanks,
>Trent.
>.
>|||For the job, if you right-click it, select "history" and (important) check "show step details", do
you see any error messages that help? I assume that the result from the job execution as failed, of
course.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Kathy" <anonymous@.discussions.microsoft.com> wrote in message
news:011f01c3b5f2$c460b0d0$a501280a@.phx.gbl...
> I received a responds to my posting and the tech made the
> point that really made sense to me. I knew transactions
> rolled back. But he mentioned that a failed backup job
> rolls back.
> I decided to create a backup job manually. It worked!!!
> Then I scheduled it through the job interfaced and it ran
> as scheduled.
> To clarify this to you:
> Backup Job FAILS when I do the following steps:
> Create a backup device, i.e. otg_backupdevice
> Right click on the new backup device (otg_backupdevice)
> and select "Backup a Database"
> The SQL Server backup wizard window appears, select the
> database (otg) to backup, add the backup device
> (otg_backupdevice) and schedule the backup to occur once
> a day at 12:00 A.M.
> Then ran the job from the jobs window
> The job fails.
> Backup Job Succeeds when I do the following steps:
> Create a backup device, i.e. otg_backupdevice
> Go to the job window
> Right-click and select new job
> Name the job - OTG backup to device
> Click on the "Steps" tab and click on "New Step"
> Select OTG as the database
> In the command window I enter "backup database otg to
> otg_backupdevice"
> Click on the "Schedule" tab and schedule it to backup at
> 10:00 am
> The job suceeds
> I suspect there is a problem with the backup wizard'
>
> Kathy
> >--Original Message--
> >Hi Matthew,
> >
> >Thanks for the reply. I always backup to a filename,
> >mainly because that's just the way I normally do it. I
> >have experimented with backing up to a device and it
> does
> >seem to work (although I never extensively tested it)
> but
> >it's starting to look like my only option.
> >
> >I run DBCC checks weekly and they never find any errors
> (I
> >double checked the last 6 weeks of dbcc checks to make
> >sure they didn't find any errors)
> >
> >Trent.
> >>--Original Message--
> >>I don't know if this will make any difference or not,
> but
> >>do you specify the filename as the destination for the
> >>backup, or do you create a backup device first?
> >>
> >>Also, have you run a DBCC consistency chekc on the
> >>database you're attempting to backup? Maybe the actual
> >>failure is on the read from the DB side of the backup
> >>process?
> >>
> >>Just some early in the morning thoughts that may or may
> >>not help.
> >>
> >>Matthew Bando
> >>BandoM@.CSCTechnologies (remove).com
> >>
> >>
> >>--Original Message--
> >>Sorry, forgot to comment on the retention. It has
> >>always
> >>been set at 5 days but I have tried turning the
> >>retention
> >>off and it makes no difference.
> >>
> >>Trent.
> >>--Original Message--
> >>any clues from the NT's system or application error
> log
> >>files?
> >>
> >>this may be dumb thing to ask, but make sure that
> >>backup
> >>retention option is properly set in db maint plan.
> >>
> >>--Original Message--
> >>I have a server with Windows 2000 SP4+hotfixes, SQL
> >>Server
> >>2000 SE SP3A+hotfix. The server has 4 user
> databases
> >>(the
> >>largest being around 500 megs). 3 of the databases
> >>backup
> >>fine but 1 database will not take a full backup or a
> >>transaction log backup from the maintenance plan.
> The
> >>job
> >>runs and succeeds but the file is not where it
> should
> >>be
> >>(nor anywhere else).
> >>
> >>The development server with the same configuration
> >>does
> >>not have this same problem, and it takes about 7
> >>seconds
> >>to backup the database in question.
> >>
> >>I have monitored the directory that the file should
> be
> >>created in while the job is running, and the file
> does
> >>create and stays there for the 5 to 7 seconds that
> the
> >>job
> >>is running and then it dissappears.
> >>
> >>I have also used File Monitor from sysinternals and
> >>monitored the system while a backup is being run and
> >>sqlservr.exe and sqlmaint.exe are the only things
> that
> >>touch the .BAK file. Sqlservr.exe reads and writes
> to
> >>the .BAK file numerous times and the last thing that
> >>happens is sqlservr.exe opens the .BAK file, then
> >>Deletes
> >>the .BAK file, and then closes the .BAK file. No
> >>other
> >>applications besides sqlservr.exe and sqlmaint.exe
> >>touch
> >>the .BAK file. The index numbers in File Monitor do
> >>not
> >>skip any numbers.
> >>
> >>Here are the lines from sysinternals File Monitor
> >>where
> >>the backup is deleted:
> >>1646 6:32:56 PM sqlservr.exe:3688
> > OPEN
> >> E:\Microsoft SQL
> >>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
> .B
> >>AK
> >> SUCCESS Options: Open Access: All
> >>1647 6:32:56 PM sqlservr.exe:3688
> > DELETE
> >> E:\Microsoft SQL
> >>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
> .B
> >>AK
> >> SUCCESS
> >>1648 6:32:56 PM sqlservr.exe:3688
> > CLOSE
> >> E:\Microsoft SQL
> >>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
> .B
> >>AK
> >> SUCCESS
> >>
> >>
> >>The error message in the errorlog is:
> >>BACKUP failed to complete the command BACKUP LOG
> >>[t_prod]
> >>TO DISK = N'E:\Microsoft SQL
> >>Server\MSSQL$TXL\BACKUP\t_prod\t_prod_db_200311241832
> .B
> >>AK
> >>'
> >>
> >>WITH INIT , NOUNLOAD , NOSKIP , STATS = 10 , NOFORMAT
> >>
> >>Disk space is not an issue as there is over 60 gigs
> >>free
> >>and all the databases together barely total a 1 gig.
> >>
> >>Backups from a script that run through a job
> (without
> >>the
> >>maint plan wizard) succeed about 75% of the time but
> >>about
> >>25% of the time the job fails with the same errors
> as
> >>the
> >>maint plan fails with. I'm still trying to get File
> >>Monitor running at the time a backup from a script
> >>fails,
> >>but haven't been luckly enough to catch it at the
> >>right
> >>time yet.
> >>
> >>Any information or suggestions to resolve this
> problem
> >>are
> >>greatly appreaciated as I've been trying to figure
> >>this
> >>out for too long. If there is any other information
> >>that
> >>would be useful to post, please let me know.
> >>
> >>Thanks,
> >>Trent.
> >>.
> >>
> >>.
> >>
> >>.
> >>
> >>.
> >>
> >.
> >