Backup SV9500 via Telephony Server Maintenance Menu....

[solidpro]

Hi All

I presumed that from the SV9500 web-based maintenance menu it would be straightforward to do a office data download, and then upload later to restore it. This would mean if the VM host was still functioning on the same IP with the same licenses, at the same software level, simply downloading and uploading the office data would be a clean way to go back quickly/easily.

I tried it a few ways but it never seems to do anything. I tested by rename an extension on ANDD, then doing a MEM_HDD on the name, doing an office data backup (download) and then deleting the name and doing another MEM_HDD and restoring the office data file and nothing comes back. I did another MEM_HDD and a reboot and the name still doesn't come back.

Does anyone know the correct proceedure for a simple office data backup and restore?

I'm running on a simple VM, not a physical unit with 2 CF card slots.

cheers

 

[phadobas]

I see what;s wrong:

You set a name with ANDD.
You MEM_HDD backup your data.
You go to the maintenance menu and download your backed up office data.
Then you go to the PBX and alter ANDD.
Then you go to the maintenance menu and upload (restore) your earlier backed up data.
Then you check ANND and it's not restored from your backup. This is where you FAIL! Once you upload from the maintenance menu your earlier backed up data, you need to reboot the system for the restored data to go into memory. When you upload your backup from the maintenance menu, it doesn't go to the memory of the phone system. It goes to the CF Card (or CFast card) only. You need to reboot to make that data go into memory and into use.

In your post you say that you did another MEM_HDD and reboot but nothing comes back. Again, your earlier backed up data was only on the CF card. Not in memory. So when you did MEM_HDD, the data from memory got written to CF card, and that overwrote the backup you "restored" from the maintenance menu. So the reboot only restored what you just backed up from memory, not from earlier backup you restored to the CF Card.

So what you need to do is this (to test):

- Set some ANDD data
- MEM_HDD to back up.
- In the maintenance menu, save the office data
- Now alter ANDD to something else.
- In the maintenance menu, restore the office data.
- From the maintenance menu, reboot the pbx.
- Once rebooted, log back in and ANDD should show the original, backed up data, not the altered data.

 

[solidpro]

Hey - thanks, i've been experiementing with how you said and I can see you way does work. I think that's confusing is that I expected the restore data recovery on the SV9500 to function similarly to the SV8300/IPS2000 and it's relationship with temp memory as opposed to work memory and it's a little different. Also it's different to the Aspire/SV8100 too.

With the SV8300/IPS2000, you have 2 stores of data. Lets call them running, which is live/temp and could be full of changes which have been made to the startup/ROM/work memory which is stored in ROM and will be what's used in a short term power cycle. So on an SV8300, if you powered up the PBX, made some changes, DIDN'T save to ROM (work) and rebooted, all your changes would be lost. I guess you could say the IPS/SV8300 operate with a tempstore and a work store and change or a restore always only applies to the temp store. The IPS2000 and I think the SV8300 used solid state ROM to store OS/Office data rather than 1 or 2 CF cards.

However on the SV9500, if you powered up the PBX, make a change, DIDN'T do the MEM_HDD command (which I is moving/copying the data from TEMP to WORK) and rebooted, all your changes would still be lost! Which is why we do a MEM_HDD manually, or wait for it to automatically happen at about 2am. However unless the SV8300 where the officedata restore is treated the same way - sent to RAM/live/hot/running memory, the SV9500 recovers the officedata to WORK/ROM/startup.

Do I have this the right way around?

I guess all this will only make sense if you're also familiar with the workings of the older IPS/SV8300.

A bit off topic, but the SV8100 is even weirder, where some command changes are instant/live/permanent, and some require you to disconnect to do a backup to rom / startup / have the changes you've made actually take effect, but you only know which commands work which was through experience!

 

[DoubleDriveLine]

When talking about NEC systems they were all developed by independent groups. There was no cross platform collaboration outside of CCIS for a long time. When you try to apply cross platform logic between them, you will just get a headache.

Here are the families. At this point I think I have touched all of them except a few of the 2400 variants, SL2100 and the DSX.

Electra Professional -> Electra Elite 48/192 -> Electra Elite IPK -> IPK2 (Hardware from IPK)

Aspire -> IPK2 (Software from Aspire) -> SV8100 -> SV9100

1400 -> 2000 IVS -> 2000 IVS2 -> 2000 IPS -> SV8300 -> SV9300

2400 (and all its variants) -> SV8500 -> SV9500

SL1100 -> SL2100

I am leaving out the Nitsuko variants. I worked on the Tie Onyx before it became Nitsuko and then later Nitsuko NEC but that was a very long time ago.

DSX? was that a Nitsuko variant?

There was an earlier NEC system that i replaced once but I never worked on it. I think it was a 48 port key system.

And this last one I just remembered the legendary Infoset 408. I installed 3 of those and was certified on it. It was not very long before it became a failed project and all of the parts dried up on the market place.