Backup Transaction logs

Hi:

I have configured maintenace plan to do a full backup of sql server at 5:00 Am followed by transaction log backup every 15 mts.The transaction log backup basically appends to existing backups so there is only one file of transaction log backup.
I want to modify that the transaction logs backup only has transaction logs after 5:00 Am full backup.Right now the transaction backup has backup of all the transaction logs since i have scheduled.

Thanks for your help.

Ganesh

BOL refers

During a full database or differential backup, Microsoft? SQL Server? backs up enough of the transaction log to produce a consistent database for when the database is restored.

As you are appending the transaction log backups the device would have only transactions that are occurred after 5am as per the schedule.

I don't understand what is your problem in having the transaction log backup, if you can also perform the log backups to file as serial order based on date-time.

|||

May be i did not put the question correct.

When i restore the database i first restore the 5AM full back up .

Then before applying the transaction logs if i see the content of the transaction backup i see all the files before 5 AM too.

I just want the backups to have transaction logs only after 5 am not the entire transactions logs before 5AM.

Is there a setting in maintenace plan that i am missing.

|||

So, there are a couple of things here:

First there is no harm in a transaction log backup file having data fro before your full backup. You simply specify which datasets to restore out of the file and you should be good.

Secondly, if what you really want is a new file with a unique name which is changed after every day's 5 AM full backup, you'll probably need to do that scripting yourself. You may be able to use the Maintenance plan as a base and customize the scripts, or just write your own script for your backups. The Maintenance Plan generator is intended to create a simple, basic backup job, not to cover every possibility.

|||True as the backup of database also takes care of transaction logs and there is no problem of duplication in your case.|||

>True as the backup of database also takes care of transaction logs and there is no problem of duplication in your case.

Note that the portion of the transaction log which is included in a full backup is NOT a substitute for a log backup, nor does it interact with the log chain in any way.

Its purpose is to enable us to restore a database to a consistent point in time, when we may have been copying blocks over a 4 hour period, for example. Thus, we save the contents of the log which cover the duration of the back up, so that at the end of a restore, we roll the database forward to the point in time of the end of the backup. This gives a consistent point in time for the restore.

Again, this does not interact with the chain of log backups in any way.