SX-2000 Light DBMS Save

[harrisskip]

We use Mitel Ops Manager to backup the phone system.  The HTML log contains the error below.  Where to I start to troubleshoot?

 DBMS SAVE starting
 Initializing for DBMS SAVE
 Logging onto the maintenance terminal
 Starting DBMS SAVE
 DBMS SAVE info: 10% complete
 DBMS SAVE info: 20% complete
 DBMS SAVE info: 30% complete
 DBMS SAVE info: 40% complete
 DBMS SAVE info: 50% complete
 DBMS SAVE info: 60% complete
 DBMS SAVE info: 70% complete
 DBMS SAVE info: 80% complete
 DBMS SAVE info: 90% complete
 SX2000 Save Completed
 Uploading SX2000 database files
 Error found. Retrying...
 DBMS SAVE failed. 

[ralph]

Do a dbms check full to see if it sees errors in your DB.

Also do a data save to hard disk and both a dbms save and data save to the optical drive.

Ralph

[harrisskip]

DBMS CHECK FULL - No errors.
DBMS SAVE - completed.
DATA SAVE prompts about removing the old data from the catalog.  Is DATA SAVE completely safe?

[lundah]

DATA SAVE writes a logfile ("*.dr_logfile1", I believe) every time it is run, when you run another, it will ask if you want to overwrite the log file from the last DATA SAVE, which you do.

However, I think your problem may be with the SX2000 not being able to upload the backup file to the OpsManager server. Check your Windows Event Log on the OpsManager server for errors when the Network Element Backup task is run, that might give you some more detail on what's going on.

[ralph]

This was an old post.   After reading it again it's obvious that my initial response was incorrect.
The error was writing to the opsman.

Ralph

[harrisskip]

This is from a log file I found.  I found similar entries in Windows Event logs, but they really don't tell me anything more than this.

                                                                                                                       
5518 OPSMaintainer 2015/09/08 10:51:31:753 @FILE:<NTLOG> LINE:<0> LOG: Backup completed successfully. ~&^                                                                                                                                                                                                 
5519 OPSSoftware 2015/09/08 10:52:18:409 @FILE:<NTLOG> LINE:<0> LOG: adbrhdlr.c-4956-Initializing ~&^                                                                                                                                                                                                     
5520 OPSMaintainer 2015/09/08 10:52:18:753 @FILE:<NTLOG> LINE:<0> LOG: <dbmssave> noranda started ~&^                                                                                                                                                                                                     
5521 OPSSoftware 2015/09/08 10:52:18:753 @FILE:<NTLOG> LINE:<0> LOG: adbrhdlr.c-1811-<dbmssave> noranda started ~&^                                                                                                                                                                                       
5522 OPSMaintainer 2015/09/08 10:58:47:190 @FILE:<NTLOG> LINE:<0> LOG: <Noranda> ADBR-abort:(Noranda) DBMS SAVE failed.  <ADBRabort>

 aborted ~&^                                                                                                                                                       
5523 OPSSoftware 2015/09/08 10:58:47:190 @FILE:<NTLOG> LINE:<0> LOG: adbrhdlr.c-1313-<Noranda> ADBR-abort:(Noranda) DBMS SAVE failed.  <ADBRabort>

 aborted ~&^                                                                                                                                         
5524 OPSSoftware 2015/09/08 10:58:52:221 @FILE:<NTLOG> LINE:<0> LOG: adbrhdlr.c-5295-<dbmssave> noranda aborted ~&^                                                                                                                                                                                       
5525 OPSMaintainer 2015/09/08 10:58:52:221 @FILE:<NTLOG> LINE:<0> LOG: <dbmssave> noranda aborted ~&^   

[lundah]

That's a new one to me. Can you do a data save to an RSD disk? Is this a redundant system, and if so, does this only happen when one plane is active?

[harrisskip]

It is a redundant system and it happens on both planes.  How do I choose to backup to RSD?  Also, how do I confirm what credentials are being used for FTP to OPSManager?

[lundah]

To do the data save to the RSD, just mount the RSD disk first ("VOL MOUNT RSD"), then you can create a folder on the RSD disk ("FILE CREATE *.<RSD NAME>.<FOLDER NAME> CAT"), then do a "DATA SAVE *.<RSD NAME>.<FOLDER NAME>

"IP SHOW" will show you the info on the IP/Ethernet adapter on the MC3E card, but only works for the system-level login.

[harrisskip]

Is there a way to see the ftp password for mnms?  How do I reset it?

[lundah]

I don't know of a way to display the current setting, but you can change it using "IP PASSWORD". You have to then do an "IP COMMIT" to save any changes to the "IP" settings, and re-load the MC3E for the changes to take effect.

[harrisskip]

I updated server and password on both planes.  How do I re-load the MC3E?  Can this be done at anytime without interrupting calls?  Thanks for all of your help thus far.  It's nice being able to get some answers.

[lundah]

Assuming the programmed activity switch is active (which on a healthy redundant system, it should be), the newly inactive plane will reset after the activity switch happens. By default this is programmed to happen every day at 2:15am, so assuming the activity switch completes normally, each plane resets every other day. If you need to reload a control plane manually, just log in and do a "load <PLID>" for the MC3E you wish to re-load. If you need to bounce the active plane, do a "activity switch force", but this will knock down any conference calls in progress and any ACD calls ringing in queue. Other calls should not be affected assuming the message links between the planes is healthy.

[harrisskip]

Lundah, thanks for your help.  I never would have figured this out without your help.  My issue was most likely due to having the wrong FTP Server IP address specified.  I also reset the password so that I would know what it was.