Mastercopy Failed

[oldboy]

Your logs do not look like from swinst 2/3/1 menu.
Do you run mastercopy command from CLI? If yes, forget it. Always use swinst menu for CPU cloning.

Why Alex ??? it is the same thing

With swinst login - you have swinst rights and environment (my opinion).

Yep just asking, never done it that way in the 25+ years of playing OXE but i know both will work,

[alex]

Your logs do not look like from swinst 2/3/1 menu.
Do you run mastercopy command from CLI? If yes, forget it. Always use swinst menu for CPU cloning.

Why Alex ??? it is the same thing

Not actually.
"A long time ago in a galaxy far, far away...." there was a document from Alcatel about not using mastercopy from CLI, just use swinst menus. Can't find it now but this is written in R5.1 docs:

[Lee0125]

Hi~~~
Today I did some tests

1. Main CPU -->no action
stand-by CPU--> use swinst (2-3-1) to run mastercopy is ok

2. Main CPU -->no action
stand-by CPU--> use mastercopy cmd to run mastercopy is ok

3. Main CPU -->user swinst to run immediate backup(2-4-1-1)
and choose 1、11
1 Backup mao, voice guides and accounting data
11 Backup Linux (Unix) site specific data

---When the backup execution is completed--

stand-by CPU--> use mastercopy cmd to run mastercopy is not ok
And then it will become as shown in the picture below, it reboot

4. Use swinst to run mastercopy again , similar to before, it will remain
stuck for about 10 minutes.
So, I proceeded to stop it again , it show message as shown in the picture
above

5. Next, I turned off the standby CPU and replaced IO2N.
After booting up, execute the master copy once again，then the system displays

-->Error mapping remagen, stat=-7


Duplication update for accounting has now started.

Accounting duplication update is already running.<--

Of course, it failed again...

Mention the third point , I'm accustomed to performing a backup of the main CPU
before executing the master copy . Because of the messages that appear in the end
,I'm guessing whether it's related to the backup item option1 (accounting data)...

ps : cdmao & checkdb , the result is as follows

(110)au8892a> cdmao
/DHS3data/mao
(110)au8892a> checkdb
Data base checking in progress ...
/....................................../

[frank]

I would reinstall your OS from scratch :/

[Lee0125]

I have previously replaced the hard drive~~

[oldboy]

Have you done a database rebuild ?? fichges force_recover_dico make sure you do a cdmao first and then run that comand on the main and try and do a mastercopy

[Lee0125]

A few years ago, when upgrading from R5.0Ux to R12.2, I followed the instructions in the system documentation and executed this command (upgrade steps R5.0Ux->R7.1->R9.1->R11.1-R12.2) , as shown in the picture

After that, I haven't performed a database rebuild

So you mean to run "fichges force_recover_dico" on the Main CPU first and then run the mastercopy?

During the execution process, it shouldn't affect phone usage, right? I remember it shouldn't...

[oldboy]

Correct it wont affect a thing

[Lee0125]

ok~ I'll try ，thank you !

[Lee0125]

Hi~All
Today I did some tests again ( I have to perform routine checks every month )
1. replace IO2N with stand-by CPU -->Because the previous attempt to replace the IO2N didn't resolve the issue ,so it was rolled back
2. Use swinst to run mastercopy ( My plan is: If the execution fails, then I will run "fichges force_recover_dico" on the main CPU )
The process is as showed in the diagrams P1 to P3 . In the end, it's okay

According to the information from the diagram in P2, a similar issue occurred last time , but it seemed like had stop
, then I had Interrupted it .

The situation today is different .When it showed a message similar to the one in P2, the system automatically restarts.
Afterwards, it's completed . This process seems like it's completing the previously unfinished task.

I will continue to perform some tests on this issue, including this command "fichges force_recover_dico", if it fails next time."
There are any new developments, I will provide updates.

Thank you all for your suggestions.