Backup failure: after MCD 4.0 SP1 upgrade

[Jakt99]

Have just upgrade from V9 to MCD 4.0 SP1 on MXe

Upgrade performed seemlessly using sw installer (upgrade / off line).

All handsets, trunks, voicemail working a treat. The problem is when I perform a backup of customer DB it pops up with Backup fail message pretty much straight away.

Have tried several times and doesn't matter if I select or not backing up call history and/or voicemail messages. Below is what poped up in software logs imediately after one failure, though not sure if related:

- - - -

Log Number: 646
Severity: Error
Date: 2010/Apr/14
Time: 11:53:19
Source: BRManager
Description: Progress Monitor - createBackupTask() Unable to determine if there is enough room for a backup
File Name and Line Number: BR_Manager.cpp;1425

Log Number: 645
Severity: Error
Date: 2010/Apr/14
Time: 11:53:19
Source: BRManager
Description: BR_Manager->Failed to get space used for '/vmail/c/voxdrv'
File Name and Line Number: BR_Manager.cpp;959

Log Number: 644
Severity: Error
Date: 2010/Apr/14
Time: 11:53:19
Source: ML_Defs
Description: directorySpaceUsed()->Failed to open directory (/vmail/c/voxdrv).
File Name and Line Number: ML_Defs.cpp;4643

Log Number: 634
Severity: Error
Date: 2010/Apr/14
Time: 11:51:16
Source: BRManager
Description: Progress Monitor - createBackupTask() Unable to determine if there is enough room for a backup
File Name and Line Number: BR_Manager.cpp;1425

Log Number: 633
Severity: Error
Date: 2010/Apr/14
Time: 11:51:16
Source: BRManager
Description: BR_Manager->Failed to get space used for '/vmail/c/voxdrv'
File Name and Line Number: BR_Manager.cpp;959

Log Number: 632
Severity: Error
Date: 2010/Apr/14
Time: 11:51:16
Source: ML_Defs
Description: directorySpaceUsed()->Failed to open directory (/vmail/c/voxdrv).
File Name and Line Number: ML_Defs.cpp;4643

- - - -

Bouncing ther Mxe didn't make any difference.

Anyone else experience this or have some ideas??

 

[IrwinMFletcher]

Go to the rtc shell and type the following command:

opendir("/sysro")

then try

opendir("/vmail/c/voxdrv")

both should return a non-zero value.

Here's an example:

-> opendir("/sysro")
value = 494591024 = 0x1d7adc30
-> opendir("/asda")
value = 0 = 0x0
-> opendir("/vmail/c/voxdrv")
value = 494590688 = 0x1d7adae0
->

As you can see, if the directory doesn't exist, then it will return 0, which is most likely happening in this case. Simpler yet, ftp into the box and make sure that the /vmail/c/voxdrv directory exists. If it doesn't that's good news for you as I would guess that the installer has problems and didn't create the full vmail partition. If the directory IS there, then that's bad as there is most likely a HDD corruption issue that won't let the SW access it.

 

[thewolfman]

I have seen this plenty of times.

Is this not the problem, where you just need to add the IP Address of your 3300 into your trusted sites in IE.....

 

[IrwinMFletcher]

Wolf, I don't think so as these logs are complaining about directories local to the 3300. The ones you are talking about are related to the saving and restoring of the actual backup on the pc. Or so I believe....

 

[Jakt99]

Apologies for late response

Thanks gents for info.

For IrwinMfletcher

I suspect that the problem is directory / HHD related. Have ftp'd into 3300. Can access the vmail directory and view all files and sub directories, eg see the /vmail/c directory but can't access it. Next Logged into RTC and performed opendir commend as discussed, with following results:

Shell restarted
-> opendir("/vmail/c/voxdrv")
opendir("/vmail/c/voxdrv")
value = 0 = 0x0 (not good)

-> opendir("/sysro")
opendir("/sysro")
value = 520282536 = 0x1f02e1a8

So perhaps a corruption on HDD.

Have performed a DBMS check full as well, no erros encountered. 3300 has not alarms either.

Have escalated to Mitel support and waiting on suggestions.

Worst case will have swap back to V9 and re-install
MCD 4.0

 

[IrwinMFletcher]

If you get that result from the shell, then it's a HDD problem as that is essentially an OS call. You might be able to reinstall, but I wouldn't feel comfortable with it.