TSM Topics Feed
Friday, March 27, 2009
I found this link listed on ADSM.org and thought I would pass it along. Here is a link that will take you to the TSM 6.1 documentation. Supposedly the upgrade doc alone is over 200 pagers. Not sure if any of you are "dying" to try 6.1, but I am planning on testing it soon.
Friday, March 20, 2009
Did I.Q.'s just drop substantially around the world? Go sell crazy somewhere else! Why would IBM even consider buying Sun? Definitely not for their Server technology, it's gotta be for their software portfolio. Most people are not aware that IBM's makes more money from their software division than hardware. (At least they used to...still think they do). But still, I gotta think Sun would be better served by a buyout from HP or Cisco...maybe Dell, but Dell seems uninterested from what I have read.
Thursday, March 12, 2009
Geoffrey Huntley recently asked me what situation would an Active Data pool be useful? To be honest, I couldn't think of a good situation. Since I don't use an Active Data Pool I thought I would throw the question out to our fellow readers to get some feedback as to how you might be using ADPs. My biggest reason for not using them was the PIT restore issue. You can read my full gripe here. Basically if TSM wont utilize it when doing a PIT then what's the benefit? I'd say more than half, if not 75%, my restores are from older dates.
To go along with the ADP story I have moved this older post up for easy reference.
With the release of TSM 5.4 Tivoli has added the ability to create an active data storage pool to allow for faster restore times. We have been looking into using them at work when I stumbled upon this interesting factoid in the description of the active data pools limitations:
- The server will not attempt to retrieve client files from an active-data pool during a point-in-time restore. Point-in-time restores require both active and inactive file versions. Active-data pools contain only active file versions. For optimal efficiency during point-in-time restores and to avoid switching between active-data pools and primary or copy storage pools, the server retrieves both active and inactive versions from the same storage pool and volumes.