TSM is very complex. It has a lot of options and features. Training
sessions are a great way to show users how to use the product, but
not as a means to discuss the non-intuitive parts of the product and
how to get around them. There are too many of them. Why not address
the non-intuitive
: PIT-Restore does not show dirs
Hi all,
I try do do an point-in-time-restore to the 19-Jul-2006 on a w2k-Server
(TSM Client 5.3.4.0). I can go down in the gui just to the mountpoint
but I dont see that base-directory. Do I make a pit-recovery 20-Jul-2006
it shows the base-directory as inactive
It's not just a matter of the retention values, but also the number of
versions. Assuming you run backup on a daily basis, if an object changes
every day, then you will only be able to restore that object up to 10 days
ago. Thus for the case of an object changing every day, the 184 day
retention
Does anyone else out there think that this is a bad design? We have
lots of users who fall into this trap, and I'm tiring of having to
explain it to them. First, they use PIT-restore when they don't need
to, because it's one of the first things they see in the restore
GUI. Then, they don't see
End user training is also very important and disclosures and other
documentation should be given to the user so situations do not happen.
To you have training meetings or anything like that? Documentation
about how it works and what you business process are for TSM should all
be known by the end
Hi all,
I try do do an point-in-time-restore to the 19-Jul-2006 on a w2k-Server
(TSM Client 5.3.4.0). I can go down in the gui just to the mountpoint
but I dont see that base-directory. Do I make a pit-recovery 20-Jul-2006
it shows the base-directory as inactive. With a pit-restore from
