SX2000 data save error

[BigDogE]

I need a little help figuring this one out. I have a SX2000 redundant system running 33.2.2.6
When I try to perform a data save , the following occurs

data save

Delete the old log file? (yes/no)
Yes
Log file cannot be created.
File System returned: Node already exists
DATA SAVE/RESTORE/CONVERT is terminated.


Is there a way to get rid of this error?
unfortunately I do not have a recent backup to try and restore from, but not sure of what steps to take to fix this either.

Any help would be appreciated... thanks.

 

[BigDogE]

Great idea, with the following results. I believe my data save files are just hosed.

fil rename *.DR.LOGFILE_1 *.DR.LOGOLD_2

FS error: Could not rename file *.DR.LOGFILE_1 to *.DR.LOGOLD_2
Reason: File format error.

So back to mitel approved vendor for mitel help ......if I can get it.

 

[MitelInMyBlood]

Try these two commands:

cat info *.dr

then

file info *.dr.config

Should look something like this:

FS info: Displaying file information for catalog *.DR
  *.DR.CONFIG
  *.DR.LOGFILE_1
FS info: Displayed file information for catalog *.DR
  *.DR.CONFIG
    Node Type:        CATALOG
    Redundant:        NO
    Attributes:       Record delete
    Record Size:         36
    High Record:        147
    Blocks:              13
FS info: Displayed file information for *.DR.CONFIG

Original MUG/NAMU Charter Member

 

[BigDogE]

*.DR.LOGFILE_1
FS error: Could not display file information for *.DR.LOGFILE_1
Reason: File format error.
*.DR.CONFIG
Node Type: CATALOG
Redundant: NO
Attributes: Record delete
Record Size: 36
High Record: 141
Blocks: 13
FS info: Displayed file information for *.DR.CONFIG
FS info: Displaying file information for catalog *.DR
*.DR.LOGFILE_1
*.DR.CONFIG
FS info: Displayed file information for catalog *.DR

 

[MitelInMyBlood]

One more command, this should give you the date/time of your last datasave as well as give you a dump of the results

type *.dr.logfile_1



Original MUG/NAMU Charter Member

 

[BigDogE]

I have the advantage of having a second system running in parrallel here. following is the status on both systems on the trouble area.

Working Node
FS info: Displayed file information for *.DR.LOGFILE_1
*.DR.LOGFILE_1
Node Type: FILE
Redundant: NO
Attributes: NO Record delete
Record Size: 1
High Record: 6666
Blocks: 16
FS info: Displayed file information for *.DR.LOGFILE_1

Non Working Node
FS error: Could not display file information for *.DR.LOGFILE_1
Reason: File format error.


I think that explains my trouble in a nut shell. I cannot touch the file, but I can't save with it still there. Unless I do a fresh install and reconfigure from scratch, I would possibly be able to send the disk to Mitel to kill off the file.

That is unless someone else has an easier way? mount on a linux box or something?

 

[MitelInMyBlood]

I've been told it is possible to recover a system using a DBMS SAVE and DBMS RESTORE.

WHat happens if you try the CAT INFO *.DR command
and the FILE INFO *.DR.CONFIG

Your database is the config file. The *.DR.LOGFILE_1 is only a capture text file of the report as it (the data save) is occurring.

What happens if you try
cat info *.DBMS
and
file info *.DBMS ?



Original MUG/NAMU Charter Member

 

[BigDogE]

My Guess is data save looks to delete the old text file before running, and since mine has errored out, it can't writeover it.

cat info *.DBMS

FS info: Displaying file information for catalog *.DBMS
*.DBMS.JOURNAL
*.DBMS.DB_CHECK_STATUS
*.DBMS.DB_CHECK_TIME
FS info: Displayed file information for catalog *.DBMS

file info *.DBMS

*.DBMS
Node Type: CATALOG
Redundant: NO
Attributes: Record delete
Record Size: 36
High Record: 3
Blocks: 2
FS info: Displayed file information for *.DBMS

 

[MitelInMyBlood]

Also..
Your database is stored in RAM on the PBX. What's on the hard disk is a copy of the database along with the O/S

Since you have another running system there, I would leverage that to build up a new drive, everything but a database, then dismount it. Put it on the system that's in trouble (don't push any buttons) and issue the command vol mount disk then see if you can save a database to it. (and perform a DBMS SAVE).

I'm shooting in the dark on this as I've never tried it, but it seems logical. You've got to have a formatted drive with the system O/S on it (this creates the file structure) and if you can get the system to mount it then my thoughts are that you should be able to get a datasave.

Original MUG/NAMU Charter Member

 

[MitelInMyBlood]

Do you know if there's a database on the redundant plane?

It might be a good idea to try this on the inactive side with the system partitioned so as not to imperil the running side.

Original MUG/NAMU Charter Member

 

[nytalkin]

I've lost track here. Have you tried to partition the planes and just power down one plane and reload? I see that a DBMS save was successful. When it comes back try to DATA SAVE again.

NO GOOD DEED GOES UNPUNISHED!

 

[nytalkin]

Just an aside..................judging by the responses here, I don't think you could get better help by paying a vendor.

NO GOOD DEED GOES UNPUNISHED!