Hi Ivan,

> On first connect to copied database the state of this "active" transaction
> is changed to "rollback", thus it becomes your stuck OIT.

this would explain the issue. So it is as designed functionality of nbackup, that probably can't be avoided, only workaround (run the sweep after restore). But given that this behaviour is part of nbackup from the very beginning, the stuck OIT really seems not to be a serious problem.

Thanks,
Michal