OXE backup fails

[jetcster]

8770 2.6.07.06, migrated from 4760
Automatic OXE backup isn't working, 8770_ARC\OXEBackup is empty.
It worked at 4760 OK.
I've tried a manual backup from maintenance application, the same result: no backup, scheduler log shows no errors

[7/4/2016 1:06:16 PM] Scheduler: The jobset 'JS13' is starting.
[7/4/2016 1:06:16 PM] Scheduler: The job 'JS13\J14' is started.
[7/4/2016 1:06:16 PM] Scheduler: Job 'JS13\J14' completed successfully at 7/4/2016 1:06:16 PM (duration 00/00/00 00:00:00).
[7/4/2016 1:06:16 PM] Scheduler: The jobset 'JS13' is stopped.

[rolfo333]

In your scheduler, there is another execution report as well (not only the top level one of the task).
Could you please post the messages in there as well(status or execution report of second level item of the backup task)?

Br
roldo

[jetcster]

No problem, here it is:

[7/4/2016 1:12:15 PM] Scheduler: The job is started.
[7/4/2016 1:12:16 PM] Scheduler: Job completed successfully at 7/4/2016 1:12:15 PM (duration 00/00/00 00:00:01).

It was under "Reports", inside the task. No other reports there.

[jetcster]

Sorry, that's wrong one, belonging to another try.

Here is the correct one:

[7/4/2016 1:06:16 PM] Scheduler: The job is started.
[7/4/2016 1:06:16 PM] Scheduler: Job completed successfully at 7/4/2016 1:06:16 PM (duration 00/00/00 00:00:00).

[rolfo333]

I am not sure where to start to look.
The task has a duration of 0 which wonders me.

Can you look ff the 8770 made a backup of OXE in /usr4/BACKUP/IMMED ?

For your release, there are really a lot of patches. What is your patch status?

[jetcster]

Yes, 0 duration is curious.

No, there is no backup there with appropriate date/time.

Patch list:

Code: Select all

; Automatically generated

[8770.2.6.07.06]
Patch_260706A_JAR=crqms00175145 - impossible to access  to voicemail  hotel mode  with 8082 / 8088
Patch_260706B_EXE=crqms00181624: Randomly OXE link unavailable on 8770 UUM
Patch_260706C_EXE=crqms00184472, crqms00186281
Patch_260706D_EXE=crqms00183340 - 8770 R2.6.7.1/Configuration/Automatically node is deleted from configuration application regularly/1-182415945
Patch_260706E_WAR_V1=crqms00186515 - 8770 2.6.07.04/Topology/Modified image in topology is not take in account after save/1-181224708
Patch_260706F_WAR_V1=crqms00187033  - 8770 Service : NMC Service manager crashes after server upgrade
Patch_260706I_APACHE=crqms00166355
patch_260706j_jar_exe=crqms00185687, crqms00178818
patch_260706k_jar=crqms00188050, crqms00188532
patch_260706l_exe=crqms00185396 : 8770 R2.6.07.05/OXO synchro fails 1 time over 2/1-183484431
patch_260706m_jar=crqms00188538 - 8770 slow done when there are ldap activities like synchronization.
patch_260706n_php_v1=crqms00188227 : In Directory application , the end customer would like to see the attribute "physicaldeliveryofficename"
patch_260706o_aar=crqms00188812:Mass provisionning : value "Kein" in the field "Keyprofile"
patch_260706p_war_jar=crqms00176262,  crqms00189077, crqms00189079, crqms00189082, crqms00189084, crqms00189103, crqms00189112, crqms00189117,crqms00189119, crqms00189141, crqms00189340, crqms00189120, crqms00189124, crqms00189140, crqms00189379, crqms00189472, crqms00189479, crqms00189480, crqms00189482, crqms00189481, crqms00189144, crqms00189483, crqms00189646, crqms00189123
patch_260706q_jar=crqms00190085 , crqms00190062 , crqms00190242 , crqms00190241
patch_260706r_exe=crqms00189936: The OT sync fails with error ''Error: TUI voicemail is not configured in the associated node'.
patch_260706s_conf=crqms00189612  Apache Server Restart
Patch_260706T_WAR=crqms00189239, crqms00189247
Patch_260706U_JAR_V1=crqms00191043, crqms00189623, crqms00190736
Patch_260706V_EXE=crqms00189207 8770 R2.6.07.05.a/ Audit / Audit Timeout for CPU6 step2 / 1-185894381.
Patch_260706W_JAR_WAR=crqms00189606, crqms00189077
Patch_260706X_WAR=crqms00192258::OV 8770 2.6.07.06/Topology/Alarm bubbles is
Patch_260706Y_WAR=crqms00192323::OV 8770 2.6.07.06/Topology/links between nodes is limited as 6
Patch_260706Z_WAR_AAR=crqms00192461, crqms00192285
Patch_260706ZA_EXE_AAR=crqms00192290, crqms00192557

Thanks for your help.

[rolfo333]

Hello,

for this release patches ZB to ZG are available as well but they do not say anything about OXE backup.

In order to do a backup of OXE, mtcl, swinst, and adfexc passwords need to be managed in the configuration application.
The network in 8770 needs to be set up correctly (network number 8770 = free number, subnetworknumber 8770 = OXE network number (0 if it is 0), subnetwork node number 8770 = OXE network number * 100 + OXE node number).

Do you experience any other problems - like configuring OXE or connecting to OXE out of 8770?

Br
rolfo

[rolfo333]

I just found an article in TKC:

http://alcatel-lucent-enterprise.force. ... 0&nrows=20

Scenario :

I have installed an OmniVista 8770 server connected to an OmniPCX Enterprise.
Everthing works fine, except taking backups of the OXE.
When I run the task I see that it runs, I get a message that it has completed, but no backups are made.
The default storage folder is empty : c:\8770_ARC\OXEBackup

I have set the passwords for the mtcl and swinst account and checked the savedatabase checkbox.

Environment :

OV8770 Release = 2.0.09.01.a
OXE Release = R10.1.1 - j2.603.29.b

Solution :

- Delete and create again, network, subnetwork and Oxe node in configuration application.
- Restart the service nmc manager.
- Do a complete synchronization then enter the password of adfexc, swinst and mtcl

Maybe this works.

[jetcster]

OK, thanks, will try.

It's a pity there are no logs to see a problem cause and reports are all green.

[tgn]

Environment :

OV8770 Release = 2.0.09.01.a
OXE Release = R10.1.1 - j2.603.29.b

Solution :

- Delete and create again, network, subnetwork and Oxe node in configuration application.
- Restart the service nmc manager.
- Do a complete synchronization then enter the password of adfexc, swinst and mtcl

Maybe this works.

Yes this will solve the issue. But the root failure is still present in actual 8770 releases.
This issue occurs everytime when you create the network, subnetwork and oxe with the 8770 installation wizzard.
So better create the instances by yourself after installation...

bad bad wizzard...

regards...



--- back to basics... focus your eyes on the essential things... ---