Some old fashion ways would be to
A) export the backups for that file space, then you could import with
relative dates down the road...
B) rename the filespace BUT the inactive versions would still expire based
on "retain extra versions" so that might not buy you much...
      but you could rename the file space, allow the actual filespace to
continue to backup
      and not run expiration until you completed an export of the ~renamed~
filespace (us this if the export might run for days...)

just a couple of thoughts...

Dwight E. Cook
Systems Management Integration Professional, Advanced
Integrated Storage Management
TSM Administration
(918) 925-8045



                                                                       
                      Shannon Bach                                     
                      <SBach AT MGE DOT COM>          To:       ADSM-L AT 
VM.MARIST DOT EDU
                      Sent by: "ADSM:          cc:                     
                      Dist Stor                Subject:  Backing up files that 
may have virus
                      Manager"                                         
                      <[email protected]                                
                      .EDU>                                            
                                                                       
                                                                       
                      02/26/2004 09:24                                 
                      AM                                               
                      Please respond to                                
                      "ADSM: Dist Stor                                 
                      Manager"                                         
                                                                       
                                                                       





I have a TSM Client V5.1.6 (NW6) whom I backup incrementally on a nightly
basis with my MVS OS/390 2.10, TSM Server 5.1.7.  I received a call from
the administrator of this (client)server that he may have a virus on his
server and would I retain his backup from 3 nights ago which may be the
last good backup pre-virus.  Here are my questions I hope someone who has
gone through this before may help me with.

1.  The MC for this client is our default of  3 incremental backups, 1
active and 2 inactive.  I'm pretty sure I will have to rebind all of this
nodes files for a specific length of time in order to keep the last good
backup for awhile.  Does anyone know if there is an alternative to this?
He has not specified a time-length but I'm assuming it may take at least 3
months to find out if he does have a virus, what files it may have
affected.  (This is my guess , I don't even know for sure what type of data
he keeps on his server).

2.  What are the possibilities of him restoring the virus accidentally down
the line.  For example, he may have a file that only gets changed once a
year.  What if 6 months from now he restores this file because it is the
last active version and it is infected with the virus.  Would this put the
virus back on his system?  Is there anyway I can avoid this from happening?
Does this make sense or am I being a paranoia?

I'll take any helpful opinions or advice I can get.  Thank you in advance!



Shannon Bach
Madison Gas & Electric Co.
Operations Analyst - Data Center Services
e-mail sbach AT mge DOT com