Dear Paul, you beeing unhappy with the product may want to re-think either of usage of TSM at all at your site or the necessity of the MODE=ABSOLUTE backup.
I do not know anybody who generaly does regulare "absolute" backups in TSM for reasons you mentioned. For me, I had performance problem when restoring desktop and "\documents and settings\" data from PC-clients. In contrast toyour mailing it was not caused by "traversing recovery log", but by search times on LTO tapes. I solved my problem by placing backups of data concerned on a TSM DISK-based storage pool. This was quite simple & perfect solution for my scenario&problem. As far as I understood your epxlanation you merely want to use "absolute" because "you have been told that.. etc. etc." I strongly believe that an general and unevaluated "beeing told that" is neither a sound reason to express either positive or negative verdicts of anything, including but not restricted to TSM, nor a wise motivation to do something in a particular way. best regards Juraj Salak, Austria > -----Ursprüngliche Nachricht----- > Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im > Auftrag von Paul Dudley > Gesendet: Dienstag, 29. Mai 2007 01:49 > An: [email protected] > Betreff: Re: Point in time restore problem > > Well, I will give it a go, but this just confirms my belief > that TSM is the most user-unfriendly, frustrating, annoying, > unwieldy IT system I have encountered in 22 years of IT work. > > Regards > Paul > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of William Boyer > > Sent: Sunday, 27 May 2007 1:08 PM > > To: [email protected] > > Subject: Re: [ADSM-L] Point in time restore problem > > > > Instead of doing a SELECTIVE backup on a periodic basis, which won't > update > > the last backup date/time of the filespace, use the > MODE=ABSOLUTE of > > the backup copygroup. In your domain, make a copy of the > active policy > > set and change all the management class backup copygroups to > > MODE=ABSOLUTE instead of the default of MODIFIED. > > Then on your "occasional" timeframe, run an admin schedule > to activate > > this policy set, do your backups which are incremental and > then the > > next day run another admin schedule to activate your MODE=MODIFIED > > policyset. This way your schedules don't change and as > far > > as the client is concerned you just ran a unqualified INCREMENTAL > > backup and the filespaces are updated. Since the active > policyset will > > have ABSOLUTS, you'll get a copy of every file whether it's > changed or > > not. > > > > I've been doing TSM not for over 8-years and this is the first time > I've ever > > thought of a way to use multiple policyset definitions in a domain. > > > > Bill Boyer > > "Backup my harddrive? How do I put it in reverse?" - ?? > > > > > > -----Original Message----- > > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf > > Of Paul Dudley > > Sent: Saturday, May 26, 2007 8:59 PM > > To: [email protected] > > Subject: Re: Point in time restore problem > > > > From what I read the standard incremental backup is > restricted in that > it only > > backs up new or changed files since the last incremental backup. > > > > However I have been told that we need to run "absolute" incremental > backups > > on a periodic basis - these incremental backups backup all files > > whether they have changed or not, so that the "Last Incr > Date" is > > updated, so that "Point in time" restores don't have to traverse > > through a huge transaction log and spend long periods of time > > restoring files that were later deleted. > > > > I quote from the dsmc help option for incremental backups: > > > > Mode: > > Permits you to back up only files that changed since the last backup > (modified). > > Also permits you to back up the files whether they changed or not > > (absolute). > > > > What I want to know is if you can run an absolute backup from the > command > > line on the client server. > > > > The end result I want to achieve from all of this, is to run full > backups on a > > periodic basis so that when I have to perform a "Point in time" > > restore it does it quickly and does not have to > traverse a huge > > transaction log and restore files that were later deleted. > > > > Regards > > Paul > > > > > > > ANL - CELEBRATING 50 YEARS > > ANL DISCLAIMER > This e-mail and any file attached is confidential, and > intended solely to the named addressees. Any unauthorised > dissemination or use is strictly prohibited. If you received > this e-mail in error, please immediately notify the sender by > return e-mail from your system. Please do not copy, use or > make reference to it for any purpose, or disclose its > contents to any person. > 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 Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet. 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 is strictly forbidden.
