[dba-SQLServer] From a reader

All Sql Server Backups are Serialized, that means you need to restore in
that specific order with a Full Backup always being the 1st backup you can
restore.  Thus if you reader restore the Sunday Full backup, and has a 2nd
Full Backups on Monday, he needs to restore the 2nd Full backup with
Monday's Logs in order to be up to date.  If the user wishes to minimize the
time of the restores (in case it's too big), then he would do well to
schedule differential backups for the duration of the month while the diff
backup file size is less than the full backup.  This is subjective and it
depends highly on the application.  So he would be able to do 1) full
restore from Sunday, followed by tlog restores
2) once the diff backup kicks off he would restore diff backups followed by
tlog backups

another option, as it sounds like what your user is doing is setting up a
log shipping routine, for a standby server.

-Francisco
http://sqlthis.blogspot.com | Tsql and More...


On Thu, Apr 2, 2009 at 9:48 AM, Nancy Lytle <nancy.lytle at gmail.com> wrote:

>
> What I think he is missing is that any data that was added/changed to DB1
> from the last log backup before the Monday night full backup of DB1 to the
> beginning of the 1st log backup of DB1 after the full backup Monday night
> will be missing, and the somehow SQL Server knows this and that is why it
> won't allow that 'after full backup log' to be restored.
>
>
>
> Does that help any?
>
> Nancy Lytle
> N_Lytle at terpalum.umd.edu
>
>
>
>
>
>
>
>
>
>
>
>  EMAILING FOR THE GREATER GOOD
> Join me
>
>
>
> > From: ssharkins at gmail.com
> > To: dba-SQLServer at databaseadvisors.com
> > Date: Thu, 2 Apr 2009 12:17:56 -0400
> > Subject: [dba-SQLServer] From a reader
> >
> > Without drawing a diagram, he loses me in para 2. Any help?
> >
> > Susan H.
> >
> >
> > Could you be kind enough to clarify a BIG question I have about
> Transaction
> > Log application? If I have a database in full recovery model (DB1) and I
> do
> > a full backup I can then restore this backup on a different server
> > (DB1_copy) and apply the transaction log backups from DB1 to DB1_copy. I
> > should have no problem and my tests confirm this.
> >
> >
> >
> > But let's say I take a full backup of DB1 on Sunday. T-log backups of DB1
> > continue on an hourly basis. Monday morning, I restore DB1 on a different
> > server as DB1_copy with NORECOVERY and start applying all T-log backups
> WITH
> > NORECOVERY to DB1_copy that have been taken from DB1. Monday night, I
> take a
> > full backup of DB1 but don't restore it to DB1_copy, instead I apply (or
> try
> > to apply) the subsequent T-log backups of DB1 since Monday's full backup
> to
> > DB1_copy. Based on my tests this doesn't work. Below is the SQL Server
> > message. Does every full backup reset something internally ?
> >
> >
> >
> > Thanks
> >
> >
> >
> > David Agnew
> >
> > 305.905.6312
> >
> >
> >
> > SQL Server message.
> >
> > Server: Msg 4326, Level 16, State 1, Line 1
> >
> > The log in this backup set terminates at LSN 21000000025000001, which is
> too
> > early to apply to the database. A more recent log backup that includes
> LSN
> > 21000000040500001 can be restored.
> >
> > Server: Msg 3013, Level 16, State 1, Line 1
> >
> > RESTORE LOG is terminating abnormally.
> >
> >
> >
> > _______________________________________________
> > dba-SQLServer mailing list
> > dba-SQLServer at databaseadvisors.com
> > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> > http://www.databaseadvisors.com
> >
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>