dickyam

We are upgrading from CMS R11 to R13.

We already have the 2 servers running simultaneously.

Problem is, we need to redefine all the database from R11 to R13... and this means ALL, from the Dictionary, Call Center Administration and Users Permission.

WE were told there is no other way but to redefine the database.. but I always believe there is... I just don't know how, yet.

Is there a better way? Is it possible to just backup the old database and upload it to the new Server?

The avaya partner is strong it couldn't be done... right now we are manually exporting/taking screenshots of all information in R11 for our 3 Data Centers and will define it manually to the new server.

Maybe someone here has an idea how? There should be a better way!

Please provide the procedures.. thanks.

ahays

Every CMS upgrade that I've ever done included a data migration that included the migration of all historical data, custom reports, etc. This can be done by Avaya (expensive) but most Business Partners that I work for use a company named Viable Resources, Inc. (Welcome to Viable Resources). Most of VR's employees are all of the former Avaya CMS gurus who "took the package" and retired after 20-30+ years.

regs,

.al.

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html

PBXtech.info

 

dickyam

thanks.. actually what is needed now is to reconcile the old R11 with the R13 database...this is because the R13 was configured last December... and since then, a lot of information had been defined in R11 already that we need to redefine in R13...

krishna

hai,
Calling Number Block FNE not working

martinyoung

I am curious. If the R13 was installed in December, why was it not cut into service?

Second, if for some reason you had to continue to use the R11 machine, why were changes made in it that were not done in parallel to the new CMS?

Since the old machine is still in service, and the new one is not, I will guess that you will need to do a fresh data migration. This one won't be as easy because you will be constantly telling the migration to continue since it will be finding data already there and it will ask if it can overwrite.

I would not do this until you are ready to start using the new CMS because you will run into this problem again. Stop data collection on the old machine, migrate it, connect the new CMS and start data collection again.

__________________
Marty
Retired Avaya DSIC tech