Kris: You are on the right track. A differential backup in SQL can only be applied against the last full that was taken before the differential. It sounds like you're trying to apply a differential that was created after the non-TDP backup to the full that was created through TDP. This cannot work.
I'm not a TDP/ADSM expert, so I'll let others chime in on that, but in SQL terms what you have to do is restore the non-TDP full backup, and then apply your differential to it. Any chance you're taking log backups also? The non-TDP full backup would *not* prevent you from applying the TDP full and then rolling forward using log records... Cheers, Chris ___________________________________ Chris Leonard University of Iowa ITS DBA 300 USB / 319-384-0801 MCSE, MCDBA, OCP, CIW ___________________________________ The Database Guy http://www.databaseguy.com Brainbench MVP for Oracle Admin http://www.brainbench.com ___________________________________ | ------------------------------ | | Date: Thu, 9 Oct 2003 13:17:16 +1000 | From: "Bock, Kris" <[EMAIL PROTECTED]> | Subject: TDPSQL Restore Problem | | Komrades, | I am attempting a TDPSQL restore for a | customer and running into= problems. TDPSQL Ver 5.1.5/TSM | Server 5.2.1.1. We run full backups on= the weekend and | diffs during the week. Unfortunately, the customers ran a= | MSSQL full backup (not using TDP) in between the TDP full and | diffs. As= Murphy would have it, they have now broken the | DB and require a restore. = When restoring, the full restore | completes but the TDP fails on the diff. = I know little | about MSSQL, but enough to suspect that the MSSQL full= | backup is causing the grief. Is this correct and, if so, can | anything be= done? |
