SQL Transaction log backup fails.

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Programming

SQL Transaction log backup fails.

Author

Topic

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 09:15:36

Hi,

I'm a clueless SQL noob trying to set a maintenance plan to backup my databases.

This is SQL 2005 running on Windows SBS 2003 R2.

I've created two maintenance plans one to do a full backup of all DBs and one to do transaction log backups every 4 hours of the databases.

The full backups run but the transaction log backup fails with

DTExec: The package execution returned DTSER_SUCCESS (0). in the logs.

I can run the backup manually from the SQL Studio but not automatically.

Any clues on what can cause this not to work?

Thanks,
nline

b.veenings
Yak Posting Veteran

96 Posts

Posted - 2007-07-11 : 09:37:37

what is the recovery model for your transactionlog?
simple or full?

Need an SQLDB consultant?
check www.veeningsengineering.nl

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 09:42:20

Full

b.veenings
Yak Posting Veteran

96 Posts

Posted - 2007-07-11 : 09:46:00

what is standing in the log file about creating the tlog backup.

you can see this by default in C:\program files\microsoft sql server\mssql.1\log, name of your job + date + time.txt.

Need an SQLDB consultant?
check www.veeningsengineering.nl

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:05:58

[code]
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3054
Report was generated on "SBS2003".
Maintenance Plan: Trans Log Backup
Duration: 00:00:00
Status: Succeeded.
Details:
[/code]

I can't see how a zero duration can be marked as succeeded.

b.veenings
Yak Posting Veteran

96 Posts

Posted - 2007-07-11 : 10:08:38

looks like it was succesful , is there an physical file at the loc of the backup?

Need an SQLDB consultant?
check www.veeningsengineering.nl

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:13:03

NO.

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:14:30

I also have event id 12291 in my application log stating that the transaction log backup failed.

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:16:00

Event Type: Error
Event Source: SQLISPackage
Event Category: None
Event ID: 12291
Date: 7/11/2007
Time: 8:00:14 AM
User: NT AUTHORITY\SYSTEM
Computer: SBS2003
Description:
Package "Trans Log Backup" failed.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:16:39

Event Type: Warning
Event Source: SQLSERVERAGENT
Event Category: Job Engine
Event ID: 208
Date: 7/11/2007
Time: 8:00:16 AM
User: N/A
Computer: SBS2003
Description:
SQL Server Scheduled Job 'Trans Log Backup.Subplan_1' (0x57E1DE68DA864F4BB5007B931AB9D60F) - Status: Failed - Invoked on: 2007-07-11 08:00:00 - Message: The job failed. The Job was invoked by Schedule 13 (Trans Log Backup). The last step to run was step 1 (Subplan_1).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

b.veenings
Yak Posting Veteran

96 Posts

Posted - 2007-07-11 : 10:20:42

This error probably means that sql server can not obtain information about the owner of the job, try changing it to the 'sa' account. then it probably works.

good luck.

Need an SQLDB consultant?
check www.veeningsengineering.nl

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 10:28:15

Ok how do I do that? And isn't using SA considered a bad security risk? Everything, I think, is setup using Windows Authentication.

b.veenings
Yak Posting Veteran

96 Posts

Posted - 2007-07-11 : 10:35:05

doesn't matter, is more important when u use service accounts, go to sql server agent and then rightclick on the transactional job and change the owner.

Need an SQLDB consultant?
check www.veeningsengineering.nl

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-11 : 12:03:24

Ok I changed them all to SA. I'll let you know if that works.

Thanks.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-11 : 12:28:26

You can find details in sql server log.

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-13 : 11:32:33

I changed the jobs to run on SA. Nothing has changed. The full backup runs the transaction log backups fail.

I am using the same backup file as a device for both jobs. Mistake?

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-13 : 17:57:29

Did you check sql server log? It tells you details of why failed.

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-13 : 20:10:25

There is nothing in the logs about this backup. It shows the full backup but not the transaction log backup


2007-07-12 19:18:20.88 Server      Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86) 
	Mar 23 2007 16:28:52 
	Copyright (c) 1988-2005 Microsoft Corporation
	Workgroup Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

2007-07-12 19:18:20.89 Server      (c) 2005 Microsoft Corporation.
2007-07-12 19:18:20.89 Server      All rights reserved.
2007-07-12 19:18:20.89 Server      Server process ID is 6556.
2007-07-12 19:18:20.89 Server      Authentication mode is WINDOWS-ONLY.
2007-07-12 19:18:20.89 Server      Logging SQL Server messages in file 'F:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-07-12 19:18:20.91 Server      This instance of SQL Server last reported using a process ID of 2236 at 7/12/2007 6:56:05 PM (local) 7/12/2007 11:56:05 PM (UTC). This is an informational message only; no user action is required.
2007-07-12 19:18:20.91 Server      Registry startup parameters:
2007-07-12 19:18:20.91 Server      	 -d F:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-07-12 19:18:20.91 Server      	 -e F:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-07-12 19:18:20.91 Server      	 -l F:\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-07-12 19:18:20.97 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2007-07-12 19:18:20.97 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2007-07-12 19:18:21.64 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2007-07-12 19:18:22.21 Server      Attempting to initialize Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-07-12 19:18:22.21 Server      The time stamp counter of CPU on scheduler id 1 is not synchronized with other CPUs.
2007-07-12 19:18:24.30 Server      Attempting to recover in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC). This is an informational message only. No user action is required.
2007-07-12 19:18:24.36 Server      Database mirroring has been enabled on this instance of SQL Server.
2007-07-12 19:18:24.52 spid5s      Starting up database 'master'.
2007-07-12 19:18:24.85 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2007-07-12 19:18:25.05 spid5s      CHECKDB for database 'master' finished without errors on 2007-06-29 22:00:13.553 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:25.18 spid5s      SQL Trace ID 1 was started by login "sa".
2007-07-12 19:18:25.19 spid5s      Starting up database 'mssqlsystemresource'.
2007-07-12 19:18:25.21 spid5s      The resource database build version is 9.00.3042. This is an informational message only. No user action is required.
2007-07-12 19:18:25.43 spid8s      Starting up database 'model'.
2007-07-12 19:18:25.43 spid5s      Server name is 'SBS2003'. This is an informational message only. No user action is required.
2007-07-12 19:18:25.58 spid8s      CHECKDB for database 'model' finished without errors on 2007-06-29 22:00:23.710 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:25.66 spid8s      Clearing tempdb database.
2007-07-12 19:18:25.97 Server      The certificate was successfully loaded for encryption.
2007-07-12 19:18:25.99 Server      Server is listening on [ 'any' <ipv4> 1433].
2007-07-12 19:18:25.99 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2007-07-12 19:18:25.99 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\sql\query ].
2007-07-12 19:18:25.99 Server      Server is listening on [ 127.0.0.1 <ipv4> 1434].
2007-07-12 19:18:25.99 Server      Dedicated admin connection support was established for listening locally on port 1434.
2007-07-12 19:18:26.04 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
2007-07-12 19:18:26.16 spid8s      Starting up database 'tempdb'.
2007-07-12 19:18:26.24 spid8s      CHECKDB for database 'tempdb' finished without errors on 2007-06-29 22:00:23.710 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:26.32 spid11s     The Service Broker protocol transport is disabled or not configured.
2007-07-12 19:18:26.32 spid11s     The Database Mirroring protocol transport is disabled or not configured.
2007-07-12 19:18:26.46 spid11s     Service Broker manager has started.
2007-07-12 19:18:26.83 spid15s     Starting up database 'msdb'.
2007-07-12 19:18:26.83 spid16s     Starting up database 'AdventureWorksDW'.
2007-07-12 19:18:26.83 spid17s     Starting up database 'AdventureWorks'.
2007-07-12 19:18:27.07 spid17s     CHECKDB for database 'AdventureWorks' finished without errors on 2007-06-29 22:00:28.757 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:27.11 spid16s     CHECKDB for database 'AdventureWorksDW' finished without errors on 2007-06-29 22:00:26.367 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:27.13 spid15s     CHECKDB for database 'msdb' finished without errors on 2007-06-29 22:00:24.367 (local time). This is an informational message only; no user action is required.
2007-07-12 19:18:27.25 spid5s      Recovery of any in-doubt distributed transactions involving Microsoft Distributed Transaction Coordinator (MS DTC) has completed. This is an informational message only. No user action is required.
2007-07-12 19:18:27.25 spid5s      Recovery is complete. This is an informational message only. No user action is required.
2007-07-12 19:18:52.77 spid52      Using 'xpstar90.dll' version '2005.90.3042' to execute extended stored procedure 'xp_instance_regread'. This is an informational message only; no user action is required.
2007-07-12 19:19:24.96 spid52      Starting up database 'ProLaw'.
2007-07-12 19:19:25.38 spid52      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 19:21:25.02 spid51      Starting up database 'ProLaw'.
2007-07-12 19:21:25.36 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 19:21:27.40 spid52      Starting up database 'ProLaw'.
2007-07-12 19:21:27.80 spid52      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 19:22:22.29 Server      CPU time stamp frequency has changed from 266281 to 2133429 ticks per millisecond. The new frequency will be used.
2007-07-12 23:00:32.88 spid53      I/O is frozen on database model. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:32.91 spid54      I/O is frozen on database msdb. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:32.93 spid55      I/O is frozen on database AdventureWorksDW. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:32.93 spid57      I/O is frozen on database AdventureWorks. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:32.93 spid56      I/O is frozen on database ProLaw. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:32.93 spid52      I/O is frozen on database master. No user action is required. However, if I/O is not resumed promptly, you could cancel the backup.
2007-07-12 23:00:34.46 spid55      I/O was resumed on database AdventureWorksDW. No user action is required.
2007-07-12 23:00:34.46 spid52      I/O was resumed on database master. No user action is required.
2007-07-12 23:00:34.49 spid57      I/O was resumed on database AdventureWorks. No user action is required.
2007-07-12 23:00:34.49 spid56      I/O was resumed on database ProLaw. No user action is required.
2007-07-12 23:00:34.49 spid54      I/O was resumed on database msdb. No user action is required.
2007-07-12 23:00:34.49 spid53      I/O was resumed on database model. No user action is required.
2007-07-12 23:00:34.83 Backup      Database backed up. Database: master, creation date(time): 2007/07/12(19:18:24), pages dumped: 1, first LSN: 230:16:55, last LSN: 230:144:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}1'}). This is an informational message only. No user action is required.
2007-07-12 23:00:34.83 Backup      Database backed up. Database: ProLaw, creation date(time): 2007/06/18(14:22:16), pages dumped: 1, first LSN: 6730:752:1, last LSN: 6730:754:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}6'}). This is an informational message only. No user action is required.
2007-07-12 23:00:34.90 Backup      Database backed up. Database: AdventureWorksDW, creation date(time): 2007/06/18(14:15:30), pages dumped: 1, first LSN: 32:368:37, last LSN: 32:392:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}4'}). This is an informational message only. No user action is required.
2007-07-12 23:00:34.96 Backup      Database backed up. Database: AdventureWorks, creation date(time): 2007/06/18(14:15:30), pages dumped: 1, first LSN: 41:736:37, last LSN: 41:760:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}5'}). This is an informational message only. No user action is required.
2007-07-12 23:00:35.05 Backup      Database backed up. Database: msdb, creation date(time): 2005/10/14(01:54:05), pages dumped: 1, first LSN: 191:496:37, last LSN: 192:24:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}3'}). This is an informational message only. No user action is required.
2007-07-12 23:00:35.07 Backup      Database backed up. Database: model, creation date(time): 2003/04/08(09:13:36), pages dumped: 1, first LSN: 24:128:37, last LSN: 24:152:1, number of dump devices: 1, device information: (FILE=1, TYPE=VIRTUAL_DEVICE: {'{2B68F014-A4DE-4D6F-8F8E-45EFBFB3F67F}2'}). This is an informational message only. No user action is required.
2007-07-12 23:14:00.40 spid16s     SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:14:00.42 spid16s     SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:14:00.42 spid16s     SQL Server has encountered 3 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:14:00.42 spid51      Starting up database 'ProLaw'.
2007-07-12 23:14:00.98 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 23:25:00.16 spid15s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:25:00.17 spid15s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:25:00.17 spid15s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:25:00.25 spid51      Starting up database 'ProLaw'.
2007-07-12 23:25:01.16 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 23:36:00.25 spid13s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:36:00.27 spid13s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:36:00.27 spid13s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:36:00.29 spid51      Starting up database 'ProLaw'.
2007-07-12 23:36:01.24 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 23:47:00.29 spid17s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:47:00.29 spid17s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:47:00.29 spid17s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:47:00.29 spid51      Starting up database 'ProLaw'.
2007-07-12 23:47:01.18 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-12 23:58:00.34 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:58:00.34 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:58:00.34 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-12 23:58:00.43 spid51      Starting up database 'ProLaw'.
2007-07-12 23:58:01.39 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-13 00:00:32.40 spid17s     This instance of SQL Server has been using a process ID of 6556 since 7/12/2007 7:18:27 PM (local) 7/13/2007 12:18:27 AM (UTC). This is an informational message only; no user action is required.
2007-07-13 00:09:00.61 spid14s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:09:00.63 spid14s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:09:00.63 spid14s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:09:00.63 spid51      Starting up database 'ProLaw'.
2007-07-13 00:09:01.20 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-13 00:20:00.33 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:20:00.33 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:20:00.33 spid16s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:20:00.33 spid51      Starting up database 'ProLaw'.
2007-07-13 00:20:00.93 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-13 00:31:00.26 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:31:00.26 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:31:00.26 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 00:31:00.27 spid51      Starting up database 'ProLaw'.
2007-07-13 00:31:00.81 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.
2007-07-13 08:13:00.77 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Object Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 08:13:00.78 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'SQL Plans' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 08:13:00.78 spid19s     SQL Server has encountered 1 occurrence(s) of cachestore flush for the 'Bound Trees' cachestore (part of plan cache) due to some database maintenance or reconfigure operations.
2007-07-13 08:13:00.78 spid51      Starting up database 'ProLaw'.
2007-07-13 08:13:01.55 spid51      CHECKDB for database 'ProLaw' finished without errors on 2007-06-29 22:00:49.600 (local time). This is an informational message only; no user action is required.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-14 : 00:56:04

That means log backup job never run, check plan's log file to see why. Do you run all steps in single schedule? Did you include all dbs in single plan? How many dbs are in full recovery model?

nlinecomputers
Starting Member

17 Posts

Posted - 2007-07-14 : 09:53:47

Rmiao,

Please read up thread. We've covered some of this. The DB is in full recovery. The plan runs enough to generate errors in the server's application event log. The job's log is posted up thread. Note that it claims the backup runs successfully. It also says it takes 0 seconds to run. I've got different logs claiming it runs, some that don't, and some that show nothing. And no backup file.

I have two backup plans. One runs at 9pm to do a full backup of all DBs on the server. I have a second backup plan that runs just transaction logs of the prolaw DB, every 4 hours. The first one runs. The transaction log doesn't.

The backups are done to a single file as a device. If I run the transaction log plan manually it works. It doesn't run as scheduled.

rmiao
Master Smack Fu Yak Hacker

7266 Posts

Posted - 2007-07-14 : 12:36:50

Does second plan generate log file? Any message in that log file? By the way, full backup job runs at 11pm based on sql server log.

Just try to get more details to help you, so sound down.

Next Page

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources