TSM Topics Feed

Thursday, March 16, 2006

TSMExpress Update


Yesterday I sat through a TSMExpress presentation and thought I would explain the product to those of you interested. First off TSMExpress is a Windows only product and has limited support for applications (basically Exchange and SQL). TSMExpress will only support a 20GB DB and ALL BACKUPS GO TO DISK! Yes that’s right; there is no direct backup to tape option. What TSMExpress utilizes is the backupset function that has been updated to enhance the backupset catalogue to be more like BackupExec or Arcserve. This is how TSMExpress will handle the Grandfather, Father, Son process of backup. Here is how it works, TSMExpress backs up all data to disk and keeps the data on disk for up to 14 days. What I haven’t got an answer to involves the disk pools and their use of the FILE device class. TSMExpress, from what the presentation showed, use the normal TSM disk pools but instead uses the FILE device class. According to the presentation the FILE device class can span drives (currently on TSM it cannot since you have to state a single drive/folder location for the files to be created.

TSMExpress’ tape creation and handling is also a little different in that is doesn’t use tape pools like we know them in TSM. There are no primary and copy tape pools, to put the data out to tape you generate a backupset (they call it a media copy). TSMExpress allows for multiple backupsets on a tape so tape usage won’t be as bad as you might have been thinking, and they have enhanced the restore process so backupsets can be explored on the file level through the GUI.  The other nice feature is that if the TSMExpress DB was ever corrupted or unable to be restored it can be recreated through the backupset catalogues (interesting feature). So once the data is on tape you send it offsite and the backupsets become your DR solution.

TSMExpress is expected to be upgradeable to TSM by next year but currently it cannot upgrade to its beefier older sibling. The backupsets are transferable, however, so you can move data between products in that way. The web interface is also a “Dummies” version and is very easy to work with as you can see it’s pretty basic.  What I didn’t hear was whether the web interface was integrated or part of the ISC. I will have to ask around on that one. Overall I would say TSMExpress looks to be a good product to fill a much needed role for the SMB market.

4 comments:

  1. Hi Chad,
    I asked local IBM to get the trial version but they say I have to wait till the end of March :)
    To your post:
    1) I really wonder about the time needed for a backupset creation ...
    2) If the DB can be recreated using the "tape scanning" - does it mean there is no DB backup to be made? Or it can be appended to the data on the tape as other products do?
    3) how about tape/library definitions and paths? checkin/checkout processes?
    4) just a small correction - TSM >5.3 CAN have file device class spanned over multiple directories/disks

    I am really curious about this new product ....

    Harry

    ReplyDelete
  2. Hi,

    although some features are copied from other products (push install of clients -> Veritas BE; Database on Tape Media -> Legato Networker) I am really looking forward to this TSM Express.
    I am also interested in the checkout / checkin process.
    It seems that some forthcoming features of the new TSM are integrated (Backupsets of TDP Clients).
    Unfortunately TSM Express does not support Lotus Domino.
    On march, 31st I will be on an IBM event where I will get the trial install on my notebook and I will have the chance to ask the IBM technical guys.

    Regards
    /noodles

    ReplyDelete
  3. Hi all ,

    I would like to know if your TSM server is configured with two Ip address , a backup of client is possible on this server ?

    I thought it's not possible , because of the redirection of the networks packet .

    Thanks for all of your answer .

    Yours Sincerely .

    ReplyDelete
  4. Our TSM server has over 6 IP's. Now only one of those is resolved by DNS and considered the "client" network. The rest are non-routed private backup networks.

    ReplyDelete