> Wish I would have read this yesterday. I'm in the middle of an
> upgrade right now and all my window's policies are slowly being
> converted right now. I figure it should finish in 10 hours. I'm
> very lucky to have the ability to keep this env down this long.
> Little upset that this known issue wasn't published on the 7.1 late
> breaking news website.
Did you call support? You don't have to wait it out.
When I first called it in, I received the "run-time workaround" (my
phrase) which is to do a ps, kill the bpdbm process shown, repeat
until done. My understanding is that bpdbm is the process waiting
five minutes to time out for each client; killing it over and over
will get through that part as fast as you can repeat (or script) the
ps/kill.
When the "upgrade the hardware definitions of the client" part is
done, either from it going through all your clients five minutes at a
time, or by you killing them to speed the loop, the upgrade will
finish as normal. At that point, run the bpplconvert manually, which
will work normally and be done in a second or two.
Whether you let it go 10 hours, timing out on each client, or use the
ps/kill method, the upgrade is the same: successful except for those
client hardware definition updates. Running the bpplconvert then
corrects that in milliseconds.
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|