Farren, Q1: I won't expect problems with the 3.7 client on Solaris 8. Q2: You're right: nearly all files get expired, all new files get into the backup. TSM has no problem with this scenario, just have ready enough database space in TSM. Just one limitation: All filespaces (mountpoint) with identical names (e.g. /var) will get updated as described, all new mountpoints will create new filespaces in TSM, but all no longer existing filespaces will not get deleted automatically after a retention period. You'll have to delete them manually after you no longer need them.
Best regards, Michael -- Michael Bartl, Dipl. Inform. (FH) mailto:[EMAIL PROTECTED] Backup Services, IT Germany/Austria Tel: +49-89-92699-806 Cable & Wireless Deutschland GmbH. Fax: +49-89-92699-302 Landsberger Str. 155, D-80687 Muenchen http://www.cw.com/de Farren Minns wrote: > > Hello TSMers > > OK, I have two questions for you today. > > Question 1 > > The first one is quite straight foward. I am presently running TSM Server > 3.7.3.8 on a Solaris 7 box and have just installed a new Solaris 8 box. > This is the first Solaris 8 machine we have and up to now I have been > putting TSM Client 3.7.2.0 on all of our machines. So what I want to know, > is will that version of the client run ok on a Solaris 8 machine. > > Question 2 > > My next question is this. Let's say I have a machine called FRED that is no > longer needed. Up to this point I have been getting TSM to incrementally > back it up every day. I then re-build this machine and still call it FRED > so that TSM will still be able to see it as before, but of course it will > have different data on it. > > So next time I run an incremental backup of this machine, I understand that > it will expire loads of files, but will it be able to cope with this, or > should I delete the present filespaces before doing a new full backup. > > Thanks in advance for any help you can give me > > Kind Regards > > Farren Minns - Trainee TSM and Solaris System Admin - John Wiley & Sons
