That was the part I was forgetting. So the "data saveset" that the 
index refers to should be browsable, up till it's browse date, provided 
that the index saveset has not expired? 

----------------------------------------------------------------------------------------

Correct. As a CFI backup refers to a db instance, it does not make sense to 
create a CFI entry for itself. This is one logical explanation.

The other one would be that you simply would create a new index instance 
whenever you would backup the CFI - consequently you
would always run one CFI backup behind (as you cannot back it up while writing 
to it). That is the other explanation.

Finally, what would you see - one entry for each *.rec file that is included. 
And as there is exactly one for each CFI instance, there
would be a 1:1 relation ship (CFI entries : MI entries). This would make no 
real sense.

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld AT avus-cr DOT de via Backup Central.
|Forward SPAM to abuse AT backupcentral DOT com.
+----------------------------------------------------------------------

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER