Re: Log Shipping Question

Full and transaction logs are almost completely independent. Almost means that you have to have a full backup to initialize the log chain. After that, a full backup has no impact on the transaction log backups. For example, if last night's backup was bad, you can go back two days and restore logs up to today. As a side effect, full backups do not mark any part of the transaction log as inactive so transaction log backups are necessary to truncate a log when in full recovery mode.

Each log backup consists of the completed and checkpointed transactions since the last transaction log backup. Once these transactions are backed up, the log space is marked inactive and can be reused.

--
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Ron" <Ron@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4A35A3CB-E733-4AE5-9780-1DACB82C9ABE@xxxxxxxxxxxxxxxx
While reviewing our log shipping setup, I noticed we backup, ship and restore
logs from 7am-7pm. We also perform a full backup at 9pm.

My question is this: Will the transaction backup at 7am pick up
transactions since the last transaction log backup at 7pm or since the full
backup at 9PM. Are we losing 2 hours of transactions?

SqlServer2005 SP2.

Thanks.
Ron

.

Relevant Pages

  • Re: Still dont understand log backups
    ... The transaction log, whether or not it is one or many files, is a serial, ... until the end of the physical log file is reached. ... backup is executed, the active "virtual" logs are backed up, but the ... Using BULK LOGGED, does the online log file contain EVERY transaction for all time -- given that I don't truncate it manually? ...
    (microsoft.public.sqlserver.server)
  • Re: Very large LDF
    ... If a database is backed up using the 'Complete Backup' option via ... You will have to backup the transaction log seperately. ... Check the Recovery model you are using for that database. ...
    (microsoft.public.sqlserver.security)
  • Re: Transaction Log Size
    ... Backup database does not empty the transaction log files. ... How to Shrink the SQL Server 7.0 Transaction Log ...
    (microsoft.public.sqlserver.server)
  • Re: Log Shipping: question about secondary dB mode?
    ... Regular transaction log backups will allow the committed and backed up portion of the log file to be reused for new transactions. ... And last to recover the db you restore the last log file using the WITH RECOVERY option and you should be all set. ... all the backup and restore jobs are proceeding without errors. ...
    (microsoft.public.sqlserver.tools)
  • Re: Large Transaction Log Backup after Database Backup
    ... script and see for yourself that the database backup doesn't truncate the ... ALTER DATABASE steve SET RECOVERY FULL ... But my understanding was that the transaction log was> truncated after a full database backup. ...
    (microsoft.public.sqlserver.server)