Proof your CM backups work??

[learningSkype]

hi all, has anyone ever had to use your daily or weekly CM backups? how did you prove that they worked? we have backups scheduled for every PBX as well as AAM, SMGR and other. but I don't know how to prove that they actually work. in fact, I've never had to use them. any suggestions?

 

[iggy1952]

learningSkype

I have used a CM XNL backup to restore an ESS server that crashed. The Avaya Recovery Team first restored the System Platform and then were moved the latest CM XNL backup to the ESS CM template and performed a reset system 4. The backup successfully restored everything.

iggy1952

 

[kyle555]

No reason you couldn't just spin up a VMWare CM. You'd be able to restore your backup to it to prove they work and not much else, but it would do the job.

 

[dialtonebone]

I would just spin up another system. If you are on CM6 or CM7 you can do this in VMWare in a few hours.

 

[montyzummer]

IN the reports section of the web interface on CM , you can run a report to check on failed and succsesful backups , you can also check that the .xln files in your backup location have a valid timestamp and that the file size matches that of the .xln in /etc/opt/defty directory in CM.

ACSS (UC/SBCE/SM/SME)

Not that they mean a thing anymore , get a brain dump pass the test crash the system.

 

[jimbojimbo]

In reality, the XLN file is transferred to any ESS/LSP servers and a cm reset is done to pull the XLN translations in. You basically validate your translations every day with the survivable processors.

 

[Ava88]

I do in this way if the customer would like to verify:
Restore the xlm backup to other development mechanic (i.e. vm or same hw model server) to see whether the configuration backup is here or not.

Ava88