I believe the only way to accomplish this would be to set up a separate
small TSM server just for this testing, and have the server travel in
time along with the client. Once the time traveler gets to the point
farthest in the future that it's going to go to, leave the test TSM
server there. You can always do a Point-in-Time restore of an earlier
state.

I would definitely not try this with your main production TSM server!

I remember this kind of issue from Y2K testing, and the rule then was
that you should never attempt to take data from the future and place it
in the past.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
               Academic Computing & Communications Center



On Mon, 22 Feb 2010, Steve Harris wrote:

>Hello Again,
>
>
>I have a client with a requirement to perform testing at different times
>into the future.  They wish to set the clocks, backup, do some testing,
>backup,  set the clock again, and so on.
>
>They wish to be able to roll forward and *backward* to any time that they
>have tested at.
>
>Now I realize that the TSM scheduler will have conniptions if the server
>time is too far out.  Assuming that we kick off a backup by some other
>means, will TSM handle being able to roll back and forth in this manner?
>Will the client be able to see a backup on march 1 that was taken at a
>client time setting of October 1 2010?
>
>Any pointers/gotchas  gladly received.
>
>Regards
>
>Steve
>
>Steven Harris
>TSM Admin
>Paraparaumu, New Zealand.
>