Home All Groups Group Topic Archive Search About

Transaction Log Backup complete yet shows as failed?

Author
17 May 2005 8:16 PM
Jeffrey Sheldon via SQLMonster.com
As of 6pm last night, our two hour transaction log backups on our financial
SQL system indicate failed from Enterprise Manager.

The SQL log file shows all of our databases log files successfully backed
up and the files do reside on the outside server.

In the Database Maintenance Plan history this error appears:

The file \\Server\D$\MSSQL\TRANSLOGS\DBname\DBname_tlog_200505171600.TRN
already exists. This backup command is ignored

For some reason the transaction log 2 hour backup plan skips the verify
backup step of the translog backup.

For the four databases that show error, the Verify Backup step is not
present.

More mind boggling is this occurs for different databases every two hours.
The same database at 2pm that errors is not the same database at the 4pm
backup.

Tried to google the message but came up with nothing...

Jeff

--
Message posted via http://www.sqlmonster.com

Author
17 May 2005 8:30 PM
Tibor Karaszi
Looks to me like you have doubled the jobs. Are you sure you only (try to) do one log backup at each
occurrence for each database?

Show quoteHide quote
"Jeffrey Sheldon via SQLMonster.com" <forum@nospam.SQLMonster.com> wrote in message
news:d7460790f6b94ea897f87430e0e2aada@SQLMonster.com...
> As of 6pm last night, our two hour transaction log backups on our financial
> SQL system indicate failed from Enterprise Manager.
>
> The SQL log file shows all of our databases log files successfully backed
> up and the files do reside on the outside server.
>
> In the Database Maintenance Plan history this error appears:
>
> The file \\Server\D$\MSSQL\TRANSLOGS\DBname\DBname_tlog_200505171600.TRN
> already exists. This backup command is ignored
>
> For some reason the transaction log 2 hour backup plan skips the verify
> backup step of the translog backup.
>
> For the four databases that show error, the Verify Backup step is not
> present.
>
> More mind boggling is this occurs for different databases every two hours.
> The same database at 2pm that errors is not the same database at the 4pm
> backup.
>
> Tried to google the message but came up with nothing...
>
> Jeff
>
> --
> Message posted via http://www.sqlmonster.com
Are all your drivers up to date? click for free checkup

Author
17 May 2005 8:55 PM
Jeffrey Sheldon via SQLMonster.com
You would think that but I checked the jobs and no duplication...now
looking at it further this is what is happening.

Transaction log backup kicks off at 4pm.
It is scheduled to backup all user databases.

in the job report you see

DB1 Backup
DB1 Verify Backup
DB2 Backup
DB3 Backup
DB3 Verify Backup

DB2 gets the file backed up to the off site server but it doesn't get the
verify backup step of the job.  The SQL Log does NOT show DB2 (whereas
previously I said it did)

I may just do a good ole reboot of the server (which hasn't been done in a
while or just stop and restart SQL server)

Any other ideas are appreciated.

jeff

--
Message posted via http://www.sqlmonster.com
Author
18 May 2005 7:41 AM
Tibor Karaszi
I'm out of ideas, I'm afraid. Well, one thing is that something strange happens because you backup
to UNC (I presume as you mentioned "off site"). Is trying to backup locally an option, if only for
troubleshooting purposes? Also, is DB2 bigger that the other databases?

Show quoteHide quote
"Jeffrey Sheldon via SQLMonster.com" <fo***@SQLMonster.com> wrote in message
news:b25380f1178f45768d898afee21f5268@SQLMonster.com...
> You would think that but I checked the jobs and no duplication...now
> looking at it further this is what is happening.
>
> Transaction log backup kicks off at 4pm.
> It is scheduled to backup all user databases.
>
> in the job report you see
>
> DB1 Backup
> DB1 Verify Backup
> DB2 Backup
> DB3 Backup
> DB3 Verify Backup
>
> DB2 gets the file backed up to the off site server but it doesn't get the
> verify backup step of the job.  The SQL Log does NOT show DB2 (whereas
> previously I said it did)
>
> I may just do a good ole reboot of the server (which hasn't been done in a
> while or just stop and restart SQL server)
>
> Any other ideas are appreciated.
>
> jeff
>
> --
> Message posted via http://www.sqlmonster.com

Bookmark and Share