Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot Backup in LD43 EDD007 Error

Status
Not open for further replies.

MeridianN00b

IS-IT--Management
Jul 26, 2022
6
CA
So I have looked through these forums a bit and am wondering how screwed I currently am with this system. We have been delaying an upgrade and I have been learning the system for the past year since the previous tech retired. From what I have seen possibly a corrupt daughterboard but I'm wondering if anyone has any ideas here?

Here is my output from a LD 43 EDD and a DAT. I can provide more info if anyone is able to help me get a successful backup done. I had a power outage this morning and the UPS is failing on it so I had to manually do all the changes from the past 2 years again.


>LD 43
EDD000

.edd

DB SEQ NUM = 4646
CONFIG
EDD007


.EDD0000


.DAT
DATABASE ISSUE DATE(d/m/y)/TIME SIZE(recs) SEQNO
Main database not accessible.
Secondary database not accessible.
IntBackup 300 23/08/2019 at 00:0030 134 4644
PCMCIA database not accessible
Current external backup is on PCMCIA drive B

.
EDD0000
 
This is a classic problem when you have more than one power cut in a short period.

What's happened is that you had the first power cut and after the Option 11c had started up that it does a data dump after a couple of minutes if all is well.

However, you then have another power cut whilst it's doing the data dump. Once the power is restored, both the main and secondary backup files on the daughterboard get corrupted.

Fortunately, the external backup on the SSC card is OK and this is what you are using, although your daily backups have failed since 2019.

Anyway, go into LD 43.
Key DAT and you have already found that your two files aren't listed.
Key RES and hopefully your backup file will copy into the main storage area.
Key DAT again to check it's there.

Now reboot the system so that it looks to the "Main" to load u
p the file.
If all is OK, then after a few minutes your system will do it's data dump.
Once it's finished to log in and go to LD 43 to key in DAT to see if all 3 storage areas are listed.

The Main and Int Backup ones will be the same time and date and the secondary will always be the previous Main backup.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Here is the output from .RES

.RES
Starting database restore DATABASE RESTORE FAILED!

EDD006
00000000 00000000 00000000
.
EDD000


.DAT
DATABASE ISSUE DATE(d/m/y)/TIME SIZE(recs) SEQNO
Main database not accessible.
Secondary database not accessible.
IntBackup 300 23/08/2019 at 00:0030 134 4644
PCMCIA database not accessible
Current external backup is on PCMCIA drive B


Is it possible I need to use an account with higher authority? I know I needed a different account to accomplish an XBK backup. I have been hesitant to try restoring an XBK file though because of the EDD issues I have been having, so I manually fix everything after a power outage. I'm looking at replacing the UPS though so I'd like to try to get this sorted first.

Thanks for your help so far, I wish it would have been that simple.
 
There is still another way to correct the problem.
The first thing is to obtain a backup.
Please follow the guide to get a backup done externally.

Please let me know that you have got one done.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Another thing is to see if you can get into "pdt". Look on line for the password, assuming that it's left at default.

If "pdt" is accessible OK, then you can copy over the backup into the main.

Once in there, the commands are..

pdt> cd c:/u/db
pdt> ll (Lists out the files in the "db" folder)
(Check to see if you have any database.rec or config.rec files)
(If they exist, they might have no size or any data stored)
pdt> cd z:
pdt> ll (Lists out the files in the "Z Drive" on the SSC card)
(You should see the *.rec files)
pdt> cd c:/u/db
pdt> cp /z/database.rec .
pdt> cp /z/config.rec .
pdt> cp /z/zone.db .

pdt> ll (Lists out the files again in the "db" folder)
(Check to see if you now have the database.rec or config.rec files etc)

If all is good and you had already done a backup using the previous guide, then do the next command to reboot the system.
pdt> reboot -1
PDT in Progress. Please Wait....Done!

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Are you referring to an XBK backup from LD143? I will look into external backups today. If you have a good link handy that would be much appreciated. I will also follow the pdt steps, I'm pretty sure I have the password for that.

I have been taking regular backups with an XBK file from LD143, but I have been hesitant to try a restore because of this blurb in the pbx cookbook.

If for any reason the download aborts before completing, (wrong protocol selected, or connection broken) you will have corrupted the backup in your switch and this must be repaired. Do this in LD 43 with the EDD command. This command should be performed periodically anyway to ensure there is always a current backup in Flash ROM (used to Boot up after a power fail).

With my EDD backups not working properly, I dont want to screw it up worse by trying to restore with XRT.


Appreciate your help so far.
 
PDT: login on /sio/2
Password:
PDT in Progress. Please Wait....

ERROR: Cannot create path "c:/u/rpt/".
** ERROR - Unable to create Access File.


Is it likely that the hard drive or daughterboard is toast?
 
pdt> cd z:
pdt> ll

Directory of 'z:':

SIZE DATE TIME NAME
---------- ----------- -------- ------------
32 Mar-01-1970 01:59:14 . <DIR>
1024 Apr-27-2096 12:52:26 direct.rec
25447 Apr-27-2096 12:52:36 disk.sys
661 Apr-27-2096 12:53:36 diskoscc.sym
8479 Apr-27-2096 12:52:42 ovlrescc.sym
8479 Apr-27-2096 12:52:40 sl1rescc.sym
136192 Aug-23-2019 00:01:08 database.rec
1024 Aug-23-2019 00:01:08 config.rec
256 Apr-27-2096 13:10:36 inet.db
16 Aug-23-2019 00:01:08 zone.db
25 Apr-27-2096 13:10:40 eset1.db
25 Apr-27-2096 13:10:42 eset2.db
396 Apr-27-2096 13:04:32 iprem.db
48 Apr-27-2096 13:04:32 surv.db
28702 Aug-22-2019 00:03:32 reten.pch
3756 Apr-27-2096 12:56:02 p10658_1.ssc
6632 Apr-27-2096 12:56:12 p17823_1.ssc
7744 Apr-27-2096 12:56:04 p16540_1.ssc
9592 Apr-27-2096 12:56:04 p17448_5.ssc
1728 Apr-27-2096 12:56:04 p17512_1.ssc
2272 Apr-27-2096 12:56:04 p17559_2.ssc
5624 Apr-27-2096 12:56:06 p17571_1.ssc
2344 Apr-27-2096 12:56:10 p17643_1.ssc
5792 Apr-27-2096 12:56:10 p17790_1.ssc
804 Apr-27-2096 12:56:10 p17813_1.ssc
288 Apr-27-2096 12:56:12 p17889_1.SSC
6112 Apr-27-2096 12:56:10 p17820_1.ssc
5224 Apr-27-2096 12:56:12 p17825_1.ssc
620 Apr-27-2096 12:56:12 p17845_1.ssc
724 Apr-27-2096 12:56:12 p17853_1.ssc
1072 Apr-27-2096 12:56:12 p17890_1.ssc
2792 Apr-27-2096 12:56:14 p17891_1.ssc
912 Apr-27-2096 12:56:14 p17893_1.ssc
14956 Apr-27-2096 12:56:14 p17897_1.ssc
1028 Apr-27-2096 12:56:14 p17899_1.ssc
8992 Apr-27-2096 12:56:16 p17922_1.ssc
5840 Apr-27-2096 12:56:16 p17946_2.ssc
5512 Apr-27-2096 12:56:16 p17960_1.ssc
3592 Apr-27-2096 12:56:18 p18025_2.ssc
2088 Apr-27-2096 12:56:18 p18040_1.ssc
2424 Apr-27-2096 12:56:18 p18043_1.ssc
2608 Apr-27-2096 12:56:18 p18066_1.ssc
3696 Apr-27-2096 12:56:22 p18163_1.ssc
5012 Apr-27-2096 12:56:16 p17901_1.ssc
5164 Apr-27-2096 12:56:24 p18305_1.ssc
1896 Apr-27-2096 12:56:28 p18519_1.ssc
1820 Apr-27-2096 12:56:18 p18024_1.ssc
1064 Apr-27-2096 12:56:18 p18028_1.ssc
3276 Apr-27-2096 12:56:20 p18081_1.ssc
6748 Apr-27-2096 12:56:20 p18090_1.ssc
3568 Apr-27-2096 12:56:20 p18123_2.ssc
1084 Apr-27-2096 12:56:22 p18229_1.ssc
1280 Apr-27-2096 12:56:22 p18242_1.ssc
1112 Apr-27-2096 12:56:22 p18250_1.ssc
3656 Apr-27-2096 12:56:22 p18296_1.ssc
604 Apr-27-2096 12:56:24 p18318_1.ssc
2876 Apr-27-2096 12:56:24 p18380_1.ssc
1236 Apr-27-2096 12:56:24 p18387_1.ssc
516 Apr-27-2096 12:56:24 p18433_1.ssc
4792 Apr-27-2096 12:56:26 p18444_1.ssc
26336 Apr-27-2096 12:56:26 p18446_1.ssc
5432 Apr-27-2096 12:56:28 p18677_2.ssc
13228 Apr-27-2096 12:56:28 p18739_1.ssc



It looks like the files are still there on the Z:

when I try to change back to C:

pdt> cd c:
Changing directory error for 'z:/c:


 
Your daughterboard is corrupted. Whatever you do, don't replace the SSC card as this contains your only backup dated from 2019.

You will need to follow the attached guide and require an old PCMCIA card no greated than 128 Megs.

The release 03.00 software should be on my ftp server.

Firebird Scrambler

Nortel & Avaya Meridian 1 / Succession & BCM / Norstar Programmer

Website = linkedin
 
Thanks. I just noticed the little paperclip attachments under your post and the previous one. I will save them for future use as I'm sure that backup guide will come in useful.

Sounds a bit above my expertise so I'll likely call someone in who knows what they are doing a bit better than myself at this point. I was just hoping it would be an easy fix. We do have an entire backup system packed away in boxes that should be the same as our existing system.

Thanks for all your help, forums like these are awesome with knowledgeable people willing to help novice users like me! Especially in such a niche subject.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top