Logshipping Problem With Naming Transaction Log Backups

Oct 11, 2006

Hey, 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

DB Engine :: Will Transaction Log Backups Not Free Up Log During Full Backups

Nov 15, 2015

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 Related

Transaction Backups

Nov 15, 2001

I 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

View 1 Replies View Related

Transaction Log Backups

May 9, 2001

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?

View 1 Replies View Related

Transaction Log Backups

Mar 31, 2004

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.

View 14 Replies View Related

Transaction Log Backups

Mar 13, 2008

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 Related

Reading In Transaction Log Backups With T-SQL

May 30, 2002

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.

View 1 Replies View Related

Failed Transaction Log Backups

Feb 6, 2000

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

View 3 Replies View Related

Remote Transaction Log Backups

Jan 20, 1999

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

View 4 Replies View Related

Failure Of Transaction Log Backups

Jan 14, 2002

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

View 2 Replies View Related

Why Won't My Transaction Log Backups Purge

Oct 5, 2004

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

View 7 Replies View Related

Question On Transaction Log Backups

May 23, 2006

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 Related

Backups And Transaction Logs

Jan 10, 2008

Have 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

View 4 Replies View Related

Differential And Transaction Log Backups

Feb 12, 2008

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!!

View 3 Replies View Related

Transaction Log Backups (Mass Storage)

May 30, 2002

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 Related

Transaction Log Backups Failing (Miserably)

Aug 1, 2000

We 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

View 3 Replies View Related

Utility To Read Transaction Log Backups

Nov 20, 2000

Does anyone know of a utility to read SQL 7 Transaction Log Backups and present them in a meaningful format?

View 2 Replies View Related

TFS Transaction Log Backups Failing After SQL/SP2 Applied

May 29, 2007

The 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

.

View 13 Replies View Related

Unable To Take Differential Or Transaction Log Backups

Dec 7, 2007

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

View 2 Replies View Related

Load SQL 7 Database And Transaction Log Backups To SQL 2000

Jul 20, 2005

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 Related

Maintenance Plans Not Deleting Old Transaction Log Backups

Jan 31, 2007

I'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 Related

Recovery :: Log Shipping Transaction Log Backups Not Being Deleted On Primary

Oct 12, 2015

I'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 Related

SQL Server 2008 :: Backup Device Creating Backups With A New Transaction Log For Each Day

Jun 19, 2015

Having 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

Pros And Cons Of Using Transaction Replication Doing Initialization From Database Backups

Jun 27, 2007

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?

View 1 Replies View Related

LogShipping

Aug 15, 2001

Hi,
I am trying to do logShipping from one server to another.
I created the logins and restored the DB(user) with the option -
"Leave DB ReadOnly and able to restore logs"
I was surprised to see that the DB got restored but there were no users in that DB.
Since this is a read-only DB I cannot run commands like Sp_change_users_login etc.....and neither can I create a user.
Any thoghts what might have gone wrong?
TIA.

View 2 Replies View Related

LogShipping

Jul 30, 2003

Hi,

I have a question.

We have created a Logshipping (customized).

(We didn't use the logshipping wizard SQL 2000)

On Primary server
The backup strategy is :

Everyday we take a Fullbackup followed by every 15 mins we take transaction log backup.

Day 1:

Full Backup at 12:00 AM
Transaction log backup from 4:00 AM to 11:45 PM

Day 2:

Full Backup at 12:00 AM
Transaction log backup from 4:00 AM to 11:45 PM

Day 3:
.
.
.

On Secondary server

Everyday will restore the full backup daily and followed by the transaction log backup restore with no recovery mode.

Day 1:

Full Backup Restore at 2:00 AM
Transaction log backup Restore from 5:00 AM to 12:45 AM

Day 2:

Full Backup Restore at 2:00 AM
Transaction log backup Restore from 5:00 AM to 12:45 AM

Day 3:
.
.
.

The problem we have is

A third server which is remote need the full backup for the first time only and everyday they need a log backup alone and not the daily fullbackup to logship the server. Will that be possible
using the logs alone for logshipping but not considering the full backup file.

Third server

Like:

One time Full Backup Restore at 4:00 AM

Day 1:

Only
Transaction log backup Restore from 9:00 AM to 4:45 AM

Day 2:

Only
Transaction log backup Restore from 9:00 AM to 4:45 AM

Day 3:
.
.
.

Don't the server throws an error saying that

Msg 4305, Sev 16: The log in this backup set begins at LSN 13000001816200001, which is too late to apply to the database. An earlier log backup that includes LSN 13000001723100001 can be restored. [SQLSTATE 42000]
Msg 3013, Sev 16: RESTORE LOG is terminating abnormally. [SQLSTATE 42000]

We don't know how to fullfil the request. I don't think Logshipping wizard skips the full backup file for logshipping if it has been schedule for full backup everyday and logbackup every 15 mins.

Please help. is there anyway we can solve this problem.

Thanks,
Anu

View 12 Replies View Related

Logshipping

Jun 21, 2008

i have configured logshipping how to change roles is
the question. By using sp_changeprimary role the database
has become suspected sp_change secondary role and sp_change monitor role is not working please guide on this issue

View 1 Replies View Related

Logshipping

Sep 7, 2005

HiI have a problem in logshipping any one help would be appreciated.during logshipping when i am adding data (log.data,transactlog)to thedestination database when i select the destination server name(server2)itdidn't showing any drives present .instead showing local drives.if i select3rd server then it shows perfect all the available drives .If any one knowsthe error please let me know u help would be appreciated.Thanks,pardhi--Message posted via SQLMonster.comhttp://www.sqlmonster.com/Uwe/Forum...eneral/200509/1

View 4 Replies View Related

Logshipping Restore

Jul 12, 2004

I have setup logshipping between 2 SQL Server 2000 servers. It looks like everything is working (The transaction log files are being created, The log files are being copied to the secondary server. The restore job on the secondary server is running every 15 minutes successfully).

I cannot tell if it is actually applying the transactions.

If it is applying the transactions, it is not updating the monitor.

Does anyone have any ideas what might be causing this problem?

Thanks,
Ken Nicholson

View 1 Replies View Related

Replication And Logshipping

Aug 18, 2004

Hi Guys,
Our servers are all standard edition of SQL Server 2000. We are trying to build Disaster recovery site with standby sql servers.

We have 2 options for this:- one is Replication(Transactional) and the other is Logshipping.

Since we don't have standard edition, Log shipping is not and option. However, we can buy just one sql enterprise edition for this pupose if logshipping requirs only one enterprise edition.

IF I CHOOSE THE LOGSHIPPING OPTION, CAN I IMPLEMENT THE STANDBY SERVER BY ONLY HAVING ONE ENTERPRISE EDITION SQL SERVER (STANDBY SERVER) where as all the pulishers are standard edition sql servers??

IF NOT IF WE CHOOSE TO GO BY TRASACTIONAL REPLICATION, HOW HARD IS TO CREATE THE STANDBY SERVER WHEN WE HAVE MOST OF THE TABLES WITHOUT PRIMARY KEYS PERTICULALY FOR THIS SERVER??

Thanks for your input and I always appreciate all you guys help in this forum.
Thanks
:confused: :confused:

View 4 Replies View Related

Logshipping Mystery.

Jul 17, 2007

Hey All,
Hope this is the right place for this post.

I set up logshipping between two databases recently. everything looks fine. the backup, copy and restore jobs are all suceeding(from the job log). the problem is no Tlogs are being restored in secondary database. The restore job skips all the tlogs and says it did not find any tlog back up file to restore!! The jobs finishes with this:

007-07-17 14:40:30.59 Could not find a log backup file that could be applied to secondary database 'SaaSNet_dataStore'.2007-07-17 14:40:30.59 The restore operation was successful. Secondary Database: 'SaaSNet_dataStore', Number of log backup files restored: 02007-07-17 14:40:30.59 Deleting old log backup files. Primary Database: 'SaaSNet_DataStore'2007-07-17 14:40:30.59 The restore operation was successful. Secondary ID: '5808a414-2ada-41d2-a8a0-2cf84f85174a'

Appreciate your help

View 3 Replies View Related

LogShipping And Database Backup

Mar 2, 2006

Hello,

have a question about logshipping and full database backup: during a full database backup the log will be backed up too and emptied. If I run a full backup on databases which is setup for logshipping - does it mean I will loose data on the standby side ?

Thanks in advance,

Bernd