|
|
Joined: Jan 2005
Posts: 38
Member
|
Member
Joined: Jan 2005
Posts: 38 |
I have our DB up and running OK now. I reinitialized the system to get a default DB and then used the import function in the Admin tool to import trunk, extension, speed, dial, voice mail, etc in from the old db. I did the imports in stages but all went smoothly.
Lesson learned; uh, don't trust the update utility?
|
|
|
Visit Atcom to get started with your new business VoIP phone system ASAP
Turn up is quick, painless, and can often be done same day.
Let us show you how to do VoIP right, resulting in crystal clear call quality and easy-to-use features that make everyone happy!
Proudly serving Canada from coast to coast.
|
|
|
Joined: Sep 2004
Posts: 4,220 Likes: 2
Member
|
Member
Joined: Sep 2004
Posts: 4,220 Likes: 2 |
This is the one thing about the way these systems program. The i-series was known for DB corruption at a drop of a pin. I have seen it as well in the Aspire series but not EVEN close to the i-series. The rule is backup often and don't overwrite the last few saves so you always have a good backup to go back to.
|
|
|
|
Joined: Jan 2005
Posts: 38
Member
|
Member
Joined: Jan 2005
Posts: 38 |
Good advice. How do you handle the situtation when the DB is corrupted during the upgrade process? I don't belive the Admin tool will import the older 3.10 DB we had archived.
|
|
|
|
Joined: Oct 2002
Posts: 597
Member
|
Member
Joined: Oct 2002
Posts: 597 |
On the ds1000 or 2000 I would not recommend importing an older version db than what your current system is. Everytime I upgrade the s/w level I default my system. These are small systems and do not take long to program. Usually I can do dtmf programming quicker than I get my laptop out and use the pc admin!
|
|
|
Forums84
Topics94,518
Posts639,976
Members49,850
|
Most Online5,661 May 23rd, 2018
|
|
0 members (),
295
guests, and
34
robots. |
Key:
Admin,
Global Mod,
Mod
|
|
|
|
|