onsdag 9 september 2009

TSM V6.1.1.0 incorrectly writes volume history entries for database backups using a date with the year 2047.

After database backups, the database backup volume's date/time
information could be invalid showing 2047/11/30 00:00:00.
This behavior can occur if the TSM snapshot monitoring thread
and database backup thread are running at the same time. The
incorrect date will only affect the expiration and deletion of
the volume.
TSM Versions Affected:
TSM 6.1.1 servers on all platforms

Fixes are available
IBM Tivoli Storage Manager (TSM) server V6.1.1.x interim fix downloads

IBM Tivoli Storage Manager V6.1 Fix Pack 2 (6.1.2) Server Downloads