>> >> > And what happen on rollover ?
>> >>
>> >> You can't start any new transactions - which is a pretty serious
>> >> problem when you need to use one to make backup to restore.
>> >>
>> >> Adam
>> >
>> > I imagine that's a case for IBSurgeon? They'd be able to rescue that
>> > wouldn't they?
>> > Alan
>>
>> What I would try in such case - set database to read only,
>> and lower next transaction value a bit (in db header, using hex editor)
>>
>> Ivan
>>
>
> It looks dangerous with 100- 200 concurrent connections on single
> database working 24/7

I was talking about situation when you already spent up all transactions
and you need one more to be able to rescue db by backup/restore.

> / What else besides backup/restore cycle could be
> done ?

Not much. Perhaps ensure that you do not waste too much transactions
by their improper handling.

> I planned to do backup of my database weekly,but not full restore
> only control restore to validate backup integrity.I seems that I need
> to change my plans.
> Maybe nbackup could allow (with new switch) to reset this counter ? but
> is this even possible ?

No, nbackup makes physical copy, it does not reset anything.

Ivan
http://www.volny.cz/iprenosil/interbase/