SQL 7 SP1 NT 4.0 SP5
I created a backup plan for transaction logs only to run every 30 minutes. It works great for all databases except the Master and my main database scdb_v2.
The routine backups up the other 3 databases with no issue.
Why is this happening ?
Thanks,
Craig Somberg
mailto:csomberg@stageone.com
The space allocated to the Log in question is 180 GB. During this time period I was running TLog backups every 5 minutes, yet the log continued to chew through to 80 GB used, even after the process was complete and a final TLog backup had been taken. It continued to stay very large until the Full backup was complete -- or something else that I'm unaware of completed. Like every other DBA I typically take a TLog backup to shrink the log, but what appeared to be the case here was the Full completed and it released the used log space. All said, will Transaction Log backups not free up the log during Full backups?
View 3 Replies View RelatedI setup a maintenance plan to create full backups every night and to backup the transaction logs every hour. In the backup log, it always fails on backing up the transaction log for Master and MSDB. I believe this is because the recovery model for these two databases is set to "SIMPLE". Is it ok to change the recovery model on these two system databases to "FULL"?
Thanks,
Ken Nicholson
I am trying to create a backup for the transaction logs on one
of the databases I support. The problem is in EM, the only
options it gives me are a Full DB Backup or a Differential DB
Backup. I have other DB's with TL backup's, why can't I on this
particular one?
I have 5 databases on my sql server and they are taking backups on everyday twice. ANd we are not taking any transactional log backups.Now i have very larger log files which are more than 6 GB each.And the databases are less in size compared to the logfiles.
Should I take transaction log backups with truncate option...
PLease suggest me the best stratagy i should follow to overcome the problem.
Thanks.
Yesterday I received a message from the Trans Log backup job that it could not complete because a full backup wasn't completed. I checked and a full backup was completed that morning 5:00 AM. This happened during the 4 PM run and again at 5 PM. There was enough space to do the backup, even though I did a shrink file on the log. I, also, ran another backup between 5-6 PM. Between both of these activities, the job completed during the 6 PM run. Is this a common occurance? Has anyone else seen this happen. I am curious. Any light that can be shed on this, would be greatlt appreciated. Tom.
View 6 Replies View RelatedHello All,
We are experiencing a backup problem on many of our database servers. We use one common server to store our backups. The backup of our databases is failing intermitantly. The strange thing is the backup file are partialy created, then we receive the following errors:
Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3201: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open backup device ' olfesdbbackupoldrmsdbmsdb_db_200010101918.BAK'. Device error or device off-line. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally.
SQL Server error log shows:
BackupDiskFile::CreateMedia: Backup device ' olfesdbbackupoldrmsdbmsdb_db_200010101918.BAK' failed to create. Operating system error = 32(The process cannot access the file because it is being used by another process.).
The file was created with 0 KB prior to coming up with these messages.
TOLDR - 10/10/00 7:55:15 PM
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3202: [Microsoft][ODBC SQL Server Driver][SQL Server]Write on ' olfesdbbackupoldrdrvlocal1drvlocal1_db_200010101951.BAK' failed, status = 5. See the SQL Server error log for more details.
[Microsoft][ODBC SQL Server Driver][SQL Server]Backup or restore operation terminating abnormally.
SQL Server error log shows:
BackupMedium::ReportIoError: write failure on backup device ' olfesdbbackupoldrdrvlocal1drvlocal1_db_200010101951.BAK'. Operating system error 5(Access is denied.).
Error 5 is 'Access Denied". It had written 24,902 KB to the file prior to coming up with this message. It was almost finished, as the normal size for this backup is in the 28,700KB range.
Any suggestions?
-Matt
I have a backup regime where i take a full backup of my production database once a day and then 3 min log backups, I backup my msdb and master once a week.
I need to write a script to scroll through a given directory and restore the log backups in date/time order(with no restore) until the last file and then restore.
I know this is availible in the backup history but if my SQl box crashes and i cant get a uptodate master and msdb the backup history will not be uptodate to restore the database to it's current state.
Can anybody help with a script? or give me any pointers of how to read in filenames in SQL (please remenber i am a SQL virgin).
Thanks
Barry.
Using SQL Server 6.5 and NT 4.0,..I'm trying to schedule a backup of a transaction log from one SQL Server
to another SQL Server both running NT 4.0. I keep getting:
dbsvolopen:Backup device t:ackup
emote.dat failed to open, operating system error =5 (Access denied)
I've checked every conceivable permissions entry on the target NT server and am now reading about the
different security modes for communicating between SQL Servers but I'm concerned that this may not be
where the problem really resides. Time is money.
Has anyone else configured a backup strategy where the database has a full backup to tape daily and the
transaction log is backed up every couple of hours, without truncatre, to disk, on another SQL Server?
Thanks in advance,
Doug
The Transaction log backups that I do for the msdb and master databases ALWAYS fail. The full database backups always succeed. Are the master and msdb databases not supposed to have their transaction logs backed up? Jobs where configured thru the Database Maintenance wizard. Will the jobs fail if nothing has changed in either database? I am also confused by the fact that database and log backups for the model database ALWAYS work when I expect their to be little if none activity in that database.
Thanks in advance,
Riley
Hi
We are running SQL Server 2000 and making full database backups using a maintenance plan. The transaction logs are being backed up via a separate plan.
However, the transaction log backups aren't purging but the database ones are. They are both run under the same id and both write to the same directory. Old text reports also get purged fine. I've got 'Delete older than 1 week' ticked for everything.
Can anyone think of anything else to check ?
Thanks
New to Sql Server, running SQL Server 2000.Our transaction log file backups occasionally fail as the size of thetransaction log gets really huge. We'd like to schedule additionaltransaction log backups. Does that require an exclusive on the databaseor can the db be used during a transaction log backup?Also, does switching to a bulk mode recovery model before a bulkoperation then switching back to full recovery mode after present anyissues?Thanks in advance.
View 16 Replies View RelatedHave a small shop and a maintenance plan that does a full backup on all user databases every night. I would have thought that a full backup (transaction log, too), would reduce the size of the transaction logs? Isn't that the point of a full backup? Mine seem to be growing larger. I do the shrink, rebuild indexes, backup the databse, backup the transaction log, clear history and folders older than 7 days. For example, the following db decreased only once during the period. But, note how the transaction log size continues to increases most of the time.
db, trn
253,196 - 394,245
253,193 - 365,695
253,191 - 360,572
254,219 - 381,699
254,223 - 406,346
254,223 - 411,018
Can someone explain this to me? Am I doing something wrong or just not understanding the process correctly?
Thanks,
Janet
Hi,
On our SQL Server 2005 SP 2 i recently updated our Backup Plan.
I now make a Full backup every night, Differential backup every hour and Transaction log backup every 15 minutes.
This all works fine all the time except sometimes when the differential and transaction log backups want to run on the same time and then 1 of the 2 fails.
The error i get is code 0xC0010018. Error loading a task.
I made 1 Maintenance Plan with a subplan for each backup type (Full, differ....), so i can schedule them the way i want.
Searched the internet for an answer but i couldn't find it. The tasks only fail when the run simultaneous. Starting them manually always works.
Anybody has an idea what i need to do to get this working properly?
Thanks!!
I want to backing up my hourly transaction log backups direct to a mass storage unit as opposed to the local server. However when trying to set this up it only gives me option of backing up to local drives, even though I have a drive mappping to the mass storage unit.. I'm there is a simple around this.Would appreciate any advice..many Thanks..
View 2 Replies View RelatedWe have a maintenance plan in SQL 7.0 that is performs a full backup each night and is supposed to perform tran log backups every two hours throughout each business day. For the most part, the first tran log backup after the full backup works fine, but the others fail.
Any ideas?
Thanks!
Ellen
Does anyone know of a utility to read SQL 7 Transaction Log Backups and present them in a meaningful format?
View 2 Replies View RelatedThe SQL server transition log backups for the ReportServer and ReportServerTempDB databases have stopped working ever since I applied SQL Server SP2 to my TFS. I know this because I know the date the SQL SP was applied and I see that my transaction logs started to fail immediately after application of the SP. This is noted because the backup logs for SQL server start to contain the failure immediately after SP2 application. The failure is because the databases are now set to the simple recovery model (or they were set to the simple model before application of SP2 and the previous SQL server allowed or properly ignored transaction log backups with the simple database recovery model). Why is this failing since the backup task indicates that databases with simple recovery are automatically excluded? Is the reportserver and reportservertempdb both supposed to be simple recovery? I thought reportserver was usually full recovery.
Here's the contents of TfsTransactionLogBackup_20070308160004.txt before the SP2 application:
Code SnippetMicrosoft(R) Server Maintenance Utility (Unicode) Version 9.0.2047
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:00
Status: Succeeded.
Details:
Here's the contents of TfsTransactionLogBackup_Subplan_20070308180007.txt immediately after application of SP2:
Code Snippet
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:05
Status: Warning: One or more tasks failed..
Details:
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:02.
Task end: 2007-03-08T18:00:02.
Failed:(0) Database 'ReportServer' will not be backed up because it does not have its recovery model set to Full or BulkLogged.
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:02.
Task end: 2007-03-08T18:00:02.
Failed:(0) Database 'ReportServerTempDB' will not be backed up because it does not have its recovery model set to Full or BulkLogged.
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:03.
Task end: 2007-03-08T18:00:03.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServer] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServer_backup_200703081800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServer_backup_20070308180002', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Command:BACKUP LOG [ReportServer] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServer_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServer_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [ReportServerTempDB] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServerTempDB_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServerTempDB_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTracking] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTracking_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTracking_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsIntegration] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsIntegration_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsIntegration_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsVersionControl] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsVersionControl_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsVersionControl_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTrackingAttachments] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTrackingAttachments_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTrackingAttachments_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsActivityLogging] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsActivityLogging_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsActivityLogging_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsBuild] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsBuild_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsBuild_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Config_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Config_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Config_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Content_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Content_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Content_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TFSWarehouse] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTFSWarehouse_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TFSWarehouse_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-03-08T18:00:03.
Task end: 2007-03-08T18:00:03.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServerTempDB] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServerTempDB_backup_200703081800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServerTempDB_backup_20070308180002', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Command:BACKUP LOG [ReportServer] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServer_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServer_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [ReportServerTempDB] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupReportServerTempDB_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''ReportServerTempDB_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTracking] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTracking_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTracking_backup_20070308180002'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsIntegration] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsIntegration_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsIntegration_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsVersionControl] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsVersionControl_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsVersionControl_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsWorkItemTrackingAttachments] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsWorkItemTrackingAttachments_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsWorkItemTrackingAttachments_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsActivityLogging] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsActivityLogging_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsActivityLogging_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TfsBuild] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTfsBuild_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TfsBuild_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Config_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Config_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Config_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [STS_Content_TFS] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupSTS_Content_TFS_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''STS_Content_TFS_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
GO
BACKUP LOG [TFSWarehouse] TO DISK = N''E:SQL ServerDatabase ServicesMSSQL.1MSSQLBackupTFSWarehouse_backup_200703081800.trn'' WITH NOFORMAT, NOINIT, NAME = N''TFSWarehouse_backup_20070308180003'', SKIP, REWIND, NOUNLOAD, STATS = 10
And here it is after the KB934458 has been applied:
Code Snippet
NEW COMPONENT OUTPUT
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3054
Report was generated on "TEAMSERVER".
Maintenance Plan: TfsTransactionLogBackup
Duration: 00:00:06
Status: Warning: One or more tasks failed..
Details:
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:03.
Task end: 2007-05-01T08:00:04.
Failed:(0) Database 'ReportServer' will not be backed up because it does not have its recovery model set to Full or BulkLogged.
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:03.
Task end: 2007-05-01T08:00:04.
Failed:(0) Database 'ReportServerTempDB' will not be backed up because it does not have its recovery model set to Full or BulkLogged.
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:04.
Task end: 2007-05-01T08:00:04.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServer] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServer_backup_200705010800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServer_backup_20070501080004', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Back Up Database (Transaction Log) (TEAMSERVER)
Backup Database on Target server connection
Databases that have a compatibility level of 70 (SQL Server version 7.0) will be skipped.
Databases: All user databases
Type: Transaction Log
Append existing
Task start: 2007-05-01T08:00:04.
Task end: 2007-05-01T08:00:04.
Failed:(-1073548784) Executing the query "BACKUP LOG [ReportServerTempDB] TO DISK = N'E:\SQL Server\Database Services\MSSQL.1\MSSQL\Backup\ReportServerTempDB_backup_200705010800.trn' WITH NOFORMAT, NOINIT, NAME = N'ReportServerTempDB_backup_20070501080004', SKIP, REWIND, NOUNLOAD, STATS = 10
" failed with the following error: "The statement BACKUP LOG is not allowed while the recovery model is SIMPLE. Use BACKUP DATABASE or change the recovery model using ALTER DATABASE.
BACKUP LOG is terminating abnormally.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly
.
Hello SQL Server 2005 SE sp1.
Unable to take differential or transaction log backups. Get the error message a full backup need to be down. Have done a full backup. Immediately upon completion of full have tried diff and transaction log. Still no luck
Other databases on server are fine. Full backup will restore.
Thanks,
Joe
What does this error message mean ? We have SQL2000, with database FULL RECOVERY. Other databases on the server are fine. Backups stopped working a week ago. Can't remeber anything changing
+++++++++++++++++++++++++++
The backup data in 'D:BackupTI backup.BAK' is incorrectly formatted. Backups cannot be appended, but existing backup sets may still be usable. [SQLSTATE 42000] (Error 3266) BACKUP DATABASE is terminating abnormally. [SQLSTATE 42000] (Error 3013). The step failed.
Hello everyone! Looking for some insight here on database backups that fail.
We have many SQL servers that we maintain by storing Job/Maintenence Plan history on a central server, which then emails out daily reports to let us know what backed up last night and what didn't
This was easy to do in SQL 2000, not so much in SQL 2005. I have put together a query that gathers the info I need for the successes:
SELECT DISTINCT '00000000-0000-0000-0000-000000000001' AS Plan_ID, mpld.line1 as "Plan Name", bud.database_name as "Database", mpld.server_name, 'Backup Database' as Activity, mpld.succeeded, bs.backup_finish_date, DATEDIFF (MS,bs.backup_start_date,bs.backup_finish_date) as Duration, bs.backup_start_date, mpld.error_number, mpld.error_messageFROM msdb.dbo.sysmaintplan_logdetail mpld
INNER JOIN msdb.dbo.backupset bs
on (select convert(char(12),mpld.start_time,109))=(select convert(char(12),bs.backup_start_date,109))-- on bs.database_name=bud.database_name
inner join
msdb.dbo.bu_dbs bud
on bs.database_name = bud.database_name
WHERE mpld.succeeded = 1 and mpld.line2 like 'Backup%' and bs.type='d'
and bs.backup_start_date > ( SELECT CONVERT(char(12), (GETDATE()-1), 109) )
ORDER BY bud.database_name DESC
But I am having trouble using a query to determine the databases the FAILED during backup. MSDB.BackupSet and MSDB.SYSMaintPlan_LogDetail really have nothing,because often times, even if a step in a Maint. Plan fails, the plan finishes reporting success.
Does anyone know of a good way to gather info about failed database backups?
Thank you!
Mario
Is it possible to load both the SQL 7 database and transaction logbackups to SQL 2000 ? I assume it will perform the upgrade during theload.Thanks,James
View 4 Replies View RelatedI'm the dba for a large company and have setup many maintenance plans for our sql servers. One of the options I have set is to delete old backups of databases and transaction logs after 2 days. For some reason, the old database backups are being deleted, but the old transaction logs backups are not. I have them being put in the same directory. Anybody have any ideas why this is happening and what if any fix is available?
View 1 Replies View RelatedHey, my logshipping is working just fine but the name of the backup file is of a concern to me. It's using the name in the format of DbName_20061011200002.trn. I know 20061011 is the date. That's fine. 2000 is supposed to be the time but it's giving the wrong time. It's supposed to be 1500 because the time right now is 3pm. And I dont know why the last 2 digits before the .trn are for. Is this something new in SQL 2005 logshipping? SQL 2000 didn't have it. Thank you.
View 4 Replies View RelatedI've got log shipping set up, and everything seems to be working fine, but the log files are not being deleted from the primary server despite configuring log shipping to retain them for 3 days. I see no errors concerning the log shipping, but did not configure a monitor. What process is responsible for deleting the older log backups, and how can I look for errors. I could simply set up a jog to delete the older files, but that will only mask the issue.
View 3 Replies View RelatedHaving a lot of problems with backup device creating backups with a new transaction log for each day. This is causing the backups to grow way to fast. Seems to be random with our clients. Created new device backups but getting same problem. A manual backup selecting overwrite all existing backup sets will fix it. But starts the cycle all over again.
View 9 Replies View Related
I am using transaction replication between a transaction and reporting database server. When I use a snapshot to initialize my subscribers, I currently get a lot of deadlocks during the snapshot creation. I am considering using a database backup instead. Can anyone tells me how to reduce the table locks that I am getting during snapshot creation or advice on using database backups?
Hi,
I am using SQL server 2000 and I created a maintenance plan. I started the jobs manually for the first time to see if everything will do as it's supposed to do before the scheduel takes place.
The DB backup are successful. When I start the Transaction Log backup job it returns failed. But when I look on the actual server ine the default directory the transaction logs are there with the current date and time.
Why do I always get a failed message. It says in the job history - The job failed. The job was invoved by user xxxxx. The last step to run was step 1(step 1).
Does anyone have an idea why I get this message. Also it says that is notified me by net send and it never does.
Hi all,
SQl server 7
I have a job to run every six hours to take the transaction log backup.
but the job has failed.
when viewed through view job history its giving the below error msg.
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
I tried starting the job but its failing with the same error msg.
pls help.
TIA
Hi All,
Greetings,
SQL Server 7,
I have scheduled transaction log backup for every 6 hours.
the scheduled job ran as per scheldue at 12pm but its giving error
The job failed. The Job was invoked by User comcreation. The last step to run was step 1 (Step 1).
sqlmaint.exe failed. [SQLSTATE 42000] (Error 22029). The step failed.
there is enough space in the drive where transaction log backup
is stored
Please help me.
Hi
Had a weird error yesterday, can anybody shed any light on it.
I got the following error in a SQL 7(sp2) database.
'The log file for database 'IT2PROD' is full. Back up the transaction log for the database to free up some log space..
Error: 9002, Severity: 17, State: 2'
The Transaction Log has unrestricted file growth and auto grow file set and the disk has over 20gb of free space.
The only explanation I can think of is that the Log tried to extend during the hourly backup. Would this cause the above error ??? The backup file is usually about 80mb but was over 300mb when this happened.
Any ideas ????
Thanks in advance
Gary
Hi Greeting,
Sql sever7
OS winNT
We have scheduled transaction log backup for user database to run every one hour. Now the transaction has failed. it gives out put
[12] Database oas: Delete Old Backup Files...
Unable to delete file E:mssql7 logsoasoas_tlog_200608111300.TRN. 0 file(s) deleted.
When we try to delete the file manully, we get alert message "can not delelte the file as it is in use."
Please suggest how to solve this.
Awating for reply
Thanks in Advance
Adil
Any thoughts as to why I get this error, every hour. How do I fix it?
Be gentle I'm a SQL novice.
Error reported in the Application Event Log.
Package "Hourly Transaction Log" failed.
OS: Windows Ser_2003_sp1
Source: SQLISPackage
Category: None
Type: Error
Event ID: 12291
File Name dtsmsg.rll
File Version: 2005.90.3042.0
Product Name: Mic SQL Server.
Product Version: 9.0.3042.
Time 3:00:01 PM
Type: Error