Mastercopy Failed

[frank]

It looks like you are going to waste a lot of time on this.
At some point, I would:

- Lock MAO on main CPU
- Backup the database from your MAIN CPU
- Install new software from scratch on stand by CPU
- Configure network on stand by CPU + restore DB + restore license
- STOP MAIN CPU
- START STANDBY CPU
- Make sure all boards are up, all features are working, no error message
- Install new software from old MAIN CPU
- Configure network
- Do a master copy from B to A
- Do a bascul to switch back to cpuA

[Lee0125]

Yes, it took a lot of time. Because the client is more cautious, actions like switching CPUs require announcements and scheduling at the right time.
I'll keep your recommended approach in mind. When there's a suitable opportunity, I'll give it a try.
Thanks again

[alex]

IO2N has nothing to do with replication.
Looks very strange.
Many times did bascul, and double bascul, no one ever noticed. You actually check this talking to somebody over PSTN on PABX and doing bascul on CLI - never had a problem with that, just a click on the phone.
So I mean you got smth wrong initially. Switching CPUs never been a problem, works like a charm.

[Lee0125]

The most troubling aspect of this issue is that sometimes it works, and sometimes it doesn't .
So, I'm trying to change hardware (except for CPU8) to see if I can get lucky, even though I know
that it's not very hardware-related .