Switching the recovery log between roll-forward and normal mode can necessitate a full database backup. If you have space triggers defined, and a new database volume was added, then that would also cause this.
If indeed there are currently 13 incrementals (would be good to see Q DB F=D output, just to be certain), check the activity log between the last successful database backup and the failed backup, to see if any messages lend insight (like space being added to the database, or recovery log mode changed). Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/17/2007 03:12:45 AM: > Hi all, > > thanks Ramakrishna, there was no extention or reduction on the database > since the last full, in fact, we had 13 successful incrementals before the > failure. > > Andi, I´ll take a second look at the script, although it has been working > for over a year on 10-odd TSM-servers on Windows2003 an has been working on > Sun for quite a while. > > But still no clue to why TSM wants a full backup in this situation, does > anyone have a comprehensive list of criteria beyond having a full as first > backup and a maximum of 32 incrementals? > > Thanks, > > Markus > > > > > -- > Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte > Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail > irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und > vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte > Weitergabe dieser Mail oder von Teilen dieser Mail ist nicht gestattet. > > Wir haben alle verkehrsüblichen Maßnahmen unternommen, um das Risiko der > Verbreitung virenbefallener Software oder E-Mails zu minimieren, dennoch > raten wir Ihnen, Ihre eigenen Virenkontrollen auf alle Anhänge an dieser > Nachricht durchzuführen. Wir schließen außer für den Fall von Vorsatz oder > grober Fahrlässigkeit die Haftung für jeglichen Verlust oder Schäden durch > virenbefallene Software oder E-Mails aus. > > Jede von der Bank versendete E-Mail ist sorgfältig erstellt worden, dennoch > schließen wir die rechtliche Verbindlichkeit aus; sie kann nicht zu einer > irgendwie gearteten Verpflichtung zu Lasten der Bank ausgelegt werden. > ______________________________________________________________________ > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorised copying, disclosure or distribution of the material in this > e-mail or of parts hereof is strictly forbidden. > > We have taken precautions to minimize the risk of transmitting software > viruses but nevertheless advise you to carry out your own virus checks on > any attachment of this message. We accept no liability for loss or damage > caused by software viruses except in case of gross negligence or willful > behaviour. > > Any e-mail messages from the Bank are sent in good faith, but shall not be > binding or construed as constituting any kind of obligation on the part of > the Bank.
