Re: [ADSM-L] TDP-SQL behavior for diff backup of new databases

Hi Del,

Here is the log from the diff restore.  By creating a database in the middle of 
the week (and we only run a full on the weekends), there is no full backup to 
go along with the diff.  What I expected to happen the first time TDP tried a 
diff backup on a newly created database was either:
a) TDP recognizes there is no full, and the diff becomes a full backup for the 
first run (preferred action)
b) TDP fails the backup (at least I know there is a problem)
It looks like neither happened.  So it appears that I could have a potential 
gap in coverage of up to a week for new databases?

09/01/2009 13:45:33 Restore of SQLBackupTest failed.
09/01/2009 13:45:33 An exception occurred while executing a Transact-SQL 
statement or batch.
09/01/2009 13:45:33 The database "SQLBackupTest" does not exist. RESTORE can 
only create a database when restoring either a full backup or a file backup of 
the primary file.

Thanks,
-steve

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Del Hoobler
Sent: Wednesday, September 02, 2009 11:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] TDP-SQL behavior for diff backup of new databases

Hi Steve,

You don't show the error messages, so it is difficult to guess what is
happening.
I assume you are restoring the DIFFERENTIAL as well as the previous FULL
when you perform the restore?
If so, is it possible something else is running a FULL backup, for
example, a snapshot tool?

Thanks,

Del

----------------------------------------------------


"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 09/02/2009
10:33:48 AM:

> [image removed]
>
> TDP-SQL behavior for diff backup of new databases
>
> Schaub, Steve
>
> to:
>
> ADSM-L
>
> 09/02/2009 10:34 AM
>
> Sent by:
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> Please respond to "ADSM: Dist Stor Manager"
>
> Window 2003 Server, SQL Server 2005, TSM 5.5.1.0 TDP 5.5.1.0
>
> We are taking weekly full and daily diff backups of SQL databases using
TDP.
> What appears to happen if a database is created mid-week is that the
> DIFF backup appears to work, no errors are flagged.  However, an
> attempt to restore this database fails, complaining that it doesn't
> have a full backup.
>
> Can someone confirm the behavior I think we are seeing in TDP, and
> if there is a recommended workaround so that we don't get caught by it?
>
> Thanks,
>
> Steve Schaub
> Systems Engineer, Windows
> BlueCross BlueShield of Tennessee
>
>
> -----------------------------------------------------
> Please see the following link for the BlueCross BlueShield of
> Tennessee E-mail disclaimer:  http://www.bcbst.com/email_disclaimer.shtm

-----------------------------------------------------
Please see the following link for the BlueCross BlueShield of Tennessee E-mail 
disclaimer:  http://www.bcbst.com/email_disclaimer.shtm