I was hoping to see some answer from Tivoli forth-coming on this issue. However, here is my experience (from last night). All of my NT servers/workstations (with 3.7.2 clients) had started their backups and failed on Sunday night, taking down the ADSM server (3.1.2.55) with them. Yesterday, I locked the nodes in question and installed the 3.7.2.17 client on one of them as a test case. I ran an interactive session, and asked for an estimate of what would be included in a full backup. The estimate indicated that it would be largely everything on the system. The backup last night ran and essentially did a full backup. My conclusion (possibly made with not enough experimentation, but I don't have a lot of time to spend on this): it appears that if a server started the DST backup, the files were marked for backup and a subsequent backup with the fixtest client will continue backing up all of the files on the first go-round. My actions: Since I'm going to be getting full backups anyway, I'm going to unlock them over the next three days and let it back up with the current client. I will be waiting to install a new client when a fully tested client dealing with Daylight Savings Time is available (rather than a hastily assembled fixtest). (Trying to avoid the "out of the frying pan, into the fire" sort of thing). Feel free to critique my logic, or supply evidence to the contrary. Regards, Ben Huber Data Support Analyst Kelman Technologies > I have only one large NT server (200GB over Tokenring) using 3.7.2.01, the > other clients with 3.7.2.01 are small or have a 3.1 version. > > What happens if you install the fixtest v3.7.2.17 after canceling a nearly > 30 % done backup with a 3.7.2.01 client. Are these 30 % backuped agaiin due > to their incorrect date? > > If i do nothing and let the "full" backup complete and install next month > the fixed clientversion > do i run into a full backup again? > > With regards > > Stefan Holzwarth > > > > > -----Ursprüngliche Nachricht----- > > Von: Neil Schofield [mailto:[EMAIL PROTECTED]] > > Gesendet am: Sonntag, 29. Oktober 2000 21:07 > > An: [EMAIL PROTECTED] > > Betreff: Re: ATTN ALL TSM USERS: Windows NT/2000 Daylight Savings Time > > Problem - Solved > > > > Contrary to to my last e-mail, v3.7.2.17 appears to have > > fixed my problem. > > > > The first time I installed it, I forgot to stop the Scheduler > > and Client > > Acceptor services first. Even though I rebooted the client, > > some of the EXEs and > > DLLs in the BAClient directory weren't replaced. The result > > was a hybrid of the > > two versions. Re-installing with no TSM processes running > > sorted this out. > > > > I have since started an incremental backup which is currently running. > > Everything appears to be fine, with only modified files being > > backed up. > > > > Thanks very much to everybody concerned for helping me sort this out. > > > > Neil > > > > > > > > > > The information in this e-mail is confidential and may also be legally > > privileged. The contents are intended for recipient only and > > are subject > > to the legal notice available at http://www.keldagroup.com/email.htm > > Yorkshire Water Services Limited > > Registered Office 2 The Embankment Sovereign Street Leeds LS1 4BG > > Registered in England and Wales No 2366682 > >
