Onbar physical followed by onbar logical...then...ontape ?

I have always been taught not to mix onbar and ontape, and have taken that at face value And not experimented. Netbackup server failures has me pondering if it would be possible To do a onbar -r -p, onbar -r -l n #, followed by ontape logical recovery (log tapes put on disk when backup server died). I called support, and like me they had been trained not to mix, and had not tried either. Anyone tried it? Thanks, -- Sam "The generation of random numbers us too important to be left to chance." Robert R. Coveyou Oak Ridge National Laboratory sending to informix-list

Gentsch, Sam wrote: > I have always been taught not to mix onbar and ontape, and have taken > that at face value > And not experimented. > > Netbackup server failures has me pondering if it would be possible > To do a onbar -r -p, onbar -r -l n #, followed by ontape logical > recovery > (log tapes put on disk when backup server died). > > I called support, and like me they had been trained not to mix, and had > not tried either. > > Anyone tried it? > > Thanks, > > > > -- > Sam > "The generation of random numbers us too important to be left to > chance." > Robert R. Coveyou > Oak Ridge National Laboratory > sending to informix-list Well, the onbar -r -l -n will try and restore ... and then attempt to bring the engine to quiescent; so following this with ontape -l will "probably" not work. However, onbar -r -p onbar -r -l -n "non-existent log number - or 'log number in future' or'duff object id in ixbar.<servernum> file'" MAY leave the engine in fast recovery and then ontape -l might work :D Obiouvsly, set up a test instance and check it out.

since you were taught not to mix onbar and ontape the, since you archive using onbar you will have been backing up your logical logs using onbar as well, I assume this is a purely hypothetical question