Backup settings and configuration of Avaya CM

[Benami]

Hi,

I'm pretty new to Avaya CM. I have no formal Avaya training, but I've managed to study enough to operate our Avaya CM (running version 6.3). One thing I still struggling with is backing up the configuration and settings.
Initially I thought that Data Backup/Restore in the SMI will do the trick, however, when it does not seem to do what I am looking for. I've created a backup, changed the configuration for some of the stations and made a restore. The stations configuration was not restored.
I tried using ASA, but again, with limited success. The ASA has the ability to export some of the settings, however, not all the configuration is exportable, nor is it easy to do (you need to manually repeat it for every 'table').

Is there anything I'm missing?

 

[kyle555]

what specific settings are you trying to backup/restore? remember to do a save translation either in asa or in the backup webpage before the backup.

All that contains relative to telephony config is the XLN file/call processing database. The state of your phone being call forwarded, or to which number, is not. While there are backup/restore parameters for H323 endpoints through the Utility Server and automatically with Session Manager for user level things like set volume, call log, contacts, per-button-ring-control etc, those are things where the state is not maintained in CM per se, so you wouldn't expect a PBX backup to retain that.

But, say the simple config of changing a phone's coverage path from 1 to 2 and having a call-fwd key or not not being maintained in a backup you restore, i'd say you're not saving the live config from volatile to non-volatile memory before backing up the non-volatile memory.

 

[Benami]

Thanks for your prompt reply.
How do save the live config from volatile to non-volatile memory? Apparently I've never done it and the system was not rebooted...

 

[kyle555]

save translation. when you backup via web page, there's a box to do that before the backup happens.

or via cli/asa

or, normally, if you "display system maintenance" you'll see it's set to automatically do so usually at 10pm everyday as well.