Spot the obvious omission….

A revised software announcement from IBM today:

IBM Tivoli Storage Manager for Microsoft SharePoint V5.4 delivers data protection for your Microsoft SharePoint environments


Customers are increasingly depending on Microsoft SharePoint Portal and Windows SharePoint Services to store, manage and access documents across their enterprise. With this growth of business critical data and content within the SharePoint evironment, customers want to manage and protect this data. IBM Tivoli Storage Manager for Microsoft SharePoint, the newest member of the Tivoli Storage Manager family, allows you to quickly and confidently restore your Microsoft SharePoint business data and content due to a business interruption of almost any kind.

Highlights of V5.4:

Backup and recovery of Microsoft SharePoint Portal 2003 and Microsoft Office SharePoint Server 2007 environments

Granular item-level backup and restore capability

Ability to restore portals, top level sites, subsites, and individual document libraries, attachments, lists, folders, areas, and sub areas

Schedule full, incremental, or differential backup at the site-level, subsite-level, and item-level, and preserves all meta-data versions

Yep, you’ve guessed it…

No “TSM for Lotus Quickr” or “TSM for Lotus Connections”…  Now to be fair, I guess that it would be possible to use “TSM for Mail” to backup the Domino version of Quickr, or “TSM for Application Servers” to backup the WAS-based Connections or Quickr/J2EE, but that really isn’t the point…  If IBM feels the need to publicly offer support for MS products before its own then what does that say to the customers that are currently evaluating Sharepoint vs. Quickr?   Grrrr….

Actually, I can remember standing at Lotusphere 2004 asking the Workplace guys when Tivoli Monitoring or TSM would properly support WSE and WCS and got a shrug of the shoulders – it wasn’t something that the Lotus guys could influence, nor did they really see a need for it – looking after the infrastructure once it was deployed was someone else’s problem.  However, it is a BIG issue for those on customer site’s managing the products, and for those in partners like mine that have to advise our customers and to design the architecture.  The phrases “absence of” and “joined up thinking” spring to mind…