В TSM это и правда неочевидно, но насколько я успел проверить, onsmsync работает только в одну сторону - он модифицирует sysutils таблицы (и boot record, она же ixbar файл). В обратную сторону, т.е. изменить сроки хранения в самом storage manager-е - только при помощи выставления expiration policy. В архивах IBM есть статья на эту тему, но доступ туда перекрыт.

В таком вот аксепте

Выставь дебаггин параметр побольше в onconfig (BAR_DEBUG = 9) и смотри в файл, прописанный в BAR_DEBUG_LOG. Скорее всего, у тебя в $INFORMIXDIR/etc/ixbar файле какие-то старые записи, которые не находятся менеджером. Этот файл можно почистить ручками.

В таком вот аксепте

Сделай поиск по +onsmsync +tsm

http://www.ibm.com/search?lv=c&o=10&en=utf&v=11&lang=en&cc=us&q=%2Bonsmsync+%2Btsm&x=9&y=12


Ага, я вспомнил свой пароль !
-----------
Problem
Why are the Informix logs saved on the Tivoli Storage Manager (TSM) server not being expired?
Cause
The Data Protection for Informix does not have the capability to control the Informix backups performed by OnBar. It is only a library interface and redirects the data being backed up to the TSM server. Informix (OnBar) is actually doing the backup processing and TSM thus relies upon OnBar functionality for what is backed up and/or deleted.

In the 7.3 version of Informix there was no utility or OnBar command to manage the Informix logs. Since all the Informix log files are uniquely named, they will remain active on the TSM server and will not be removed during any expiration processing.

Solution

Version 9.21 of Informix has a "onsmsync" utility to assist with deletion/management of the Informix logs. The Informix Backup and Restore guide has information in Chapter 5 regarding the "onsmsync" utility and how it is used. This utility does not exist for the 7.3 version of Informix, but is in the 8.3 and 9.2 latest releases.

If the onsmsync utility exists, this can be used to expire/remove the Informix logs from the TSM Server. During the backup, the informix log files should be directed to a specific management class that goes to a different "stgpool" on the TSM Server and has the backup copygroup RetExtra versions parameter set to 0. Then using the onsmsync utility, logical logs can immediately be removed from the TSM-Server because the storage pool will not keep any inactive versions on TSM. This will work even on storage pools using DISK device class.

If the version of Informix that is being used does not have the onsmsync utility, then it is suggested to backup the Informix log files to a specific management class that goes to a different "stgpool" on the TSM Server. The tape volumes in this "stgpool" can be looked at and the volume deleted with "discarddata=yes" for those volumes that have not been updated since "X" number of days and thus are "X" days old.

To specify that the Informix logs go to a specific copy group, add an include statement that directs the backups to the management class that have been setup for the logs. The backup information for the logs shows:

"Node Name: INFCLIENT"
Session established with server TSMSVR: AIX-RS/6000
Server Version 4, Release 2, Level 1.0
Server date/time: 11/20/01 08:54:17 Last access: 11/20/01 08:54:02

Size Backup Date Mgmt Class A/I File
---- ----------- ---------- --- ----
500 B 11/02/01 20:41:59 DEFAULT A /ifmx07301/ifmx07301/10/753
500 B 11/02/01 20:42:00 DEFAULT A /ifmx07301/ifmx07301/10/754

Thus an include statement would be:
include /ifmx07301/ifmx07301/10/* MgmtClassName


Related information
Informix Back/Restore guide

---------------
В таком вот аксепте

Я это так и не выяснил. Попробуй, нам расскажешь.

В таком вот аксепте