Backup and restore log useful for DB corruption

[pmhaynes]

I had a extension that i could not get rid of. Mitel recommeded a backup and restore to resolve
From what i could tell there was no visability of what was happening during this backup and restore
Did it find the issue and resolve it?
Was there more than one number with an issue?

I was told about this command and log file
It's probably in the manual somewhere but i didnt know about it
so i thought i would share it with the community

All sorted now

https://phonesystemhelp.info/mivb-database-corruption-logs/

[sunspark]

you didn't have to do all that, (and especially the backup restore is the last last last solution)

If you have a problem with an extension:

1st suggestion (depending on the version of your Mivb)

Command: gdm check users / gdm repair

2nd solution: activate the hidden menu: sdsdebug on / sdsdebug off
then solve the problem of your extension

3rd solution: there is a hidden command that allows you to override database error, which allows you to solve the backup problem for example.

[pmhaynes]

Thanks for the reply
I agree the backup restore was a last resort
I didn’t do it lightly and without trying sds debug
In this case it was recommended by mitel tech support
 

[august]

In maintenance command, after the restore:

type *.dr.logfile_1

press ok

If something did not restore properley, you will see it.

[sarond]

Hi pmhaynes,

I feel that most people are missing the point of your posts. You are already giving the solution to help others, I understand that and appreciate it as your blog is quite helpful.

Maybe some aren't following your link. Could I suggest also putting a TL;DR in the original post here so that others can see at a glance what you have achieved?

[sunspark]

hi sarond,

I also appreciate the solution of pmhaynes. I just proposed another approach if it encounters the same problem, to avoid the backup / restore.