Full backup invisible to the next differential backup

Hi
Given that differential backups are labelled with a base Log Sequence Number
(LSN) as to know which full backup they're related to, and that they store
all changes made after that LSN. I want to know if it's possible to have a
full backup that is not taken into account when a differential backup is
created.
For instance:
1. On Monday a full backup is created
2. On Tuesday another full backup is automatically created by a 3rd-party
application
3. On Wednesday a differential backup is created.
We want this diff backup to ignore the Tuesday full backup and store all
changes since the Monday one.
4. On Thursday the DB crashes and we're able to restore in order:
- Full backup from step 1
- Diff backup from step 3
- All log backups after the diff backup on step 3
The key here is to be able to have something like a disconnected backup that
can be performed by this 3rd-party application, that doesn't interfere on
the regular backup chain.
Any thoughts are welcome.
Thanks!Dallara,
"Dallara" <someone@.microsoft.com> wrote in message
news:ObpEKvh5DHA.1636@.TK2MSFTNGP12.phx.gbl...
> For instance:
> 1. On Monday a full backup is created
> 2. On Tuesday another full backup is automatically created by a 3rd-party
> application
> 3. On Wednesday a differential backup is created.
> We want this diff backup to ignore the Tuesday full backup and store
all
> changes since the Monday one.
This is not possible.
What's the point of the third party backup if it is disregarded?
James Hokes|||The application has an automated process that
1 - gets exclusive access to the DB
2 - back it up
3 - does whatever needs to be done
if 3 fails the DB is restored, otherwise the backup can be discarded
4 - release exclusive access to DB
The idea is not to interfere with the client maintenance plans and backup
policy (if they have one).
It's basically the same idea of the COPY BACKUP for the NT backup.
"James Hokes" <noemail@.noway.com> wrote in message
This is not possible.
What's the point of the third party backup if it is disregarded?
James Hokes
> Dallara,
>
> "Dallara" <someone@.microsoft.com> wrote in message
> > For instance:
> > 1. On Monday a full backup is created
> > 2. On Tuesday another full backup is automatically created by a
3rd-party
> > application
> > 3. On Wednesday a differential backup is created.
> > We want this diff backup to ignore the Tuesday full backup and store
> all
> > changes since the Monday one.
>|||Why not take the database offline, copy the database files, put the database
back online. See ALTER DATABASE in BOL.
HTH
--
Barry McAuslin
Look inside your SQL Server files with SQL File Explorer.
Go to http://www.sqlfe.com for more information.
"Dallara" <someone@.microsoft.com> wrote in message
news:Om5pYkj5DHA.2348@.TK2MSFTNGP10.phx.gbl...
> The application has an automated process that
> 1 - gets exclusive access to the DB
> 2 - back it up
> 3 - does whatever needs to be done
> if 3 fails the DB is restored, otherwise the backup can be discarded
> 4 - release exclusive access to DB
> The idea is not to interfere with the client maintenance plans and backup
> policy (if they have one).
> It's basically the same idea of the COPY BACKUP for the NT backup.
>
>
> "James Hokes" <noemail@.noway.com> wrote in message
> This is not possible.
> What's the point of the third party backup if it is disregarded?
> James Hokes
>
> > Dallara,
> >
> >
> > "Dallara" <someone@.microsoft.com> wrote in message
> > > For instance:
> > > 1. On Monday a full backup is created
> > > 2. On Tuesday another full backup is automatically created by a
> 3rd-party
> > > application
> > > 3. On Wednesday a differential backup is created.
> > > We want this diff backup to ignore the Tuesday full backup and
store
> > all
> > > changes since the Monday one.
> >
>