05-02-2012 07:25 AM - edited 03-19-2019 04:51 AM
I am trying to upgrade from CUCM version 6.1.1a (6.1.1.2000-3) to 6.1.3.2000-1 through Software Installation / Upgrade. The database I'm working with has a cluster with the publisher and subscriber, but for now I'm only upgrading in laboratory the publisher. The upgrade seems ok , in the end he says he did the upgrade but when I try to switch-version got the following error "error: after sync switch version failed."
However doing the "> switch-version nodatasync", the call manager is reset and climb the right partition and apparently did well to upgrade, at least I can check the database and the objects are there. Anyone know if there are any implications of using the command nodatasync? Or what does the command nodatasync?
05-04-2012 07:31 AM
The 'nodatasync' option means that the user facing features (UFF) are not extracted and updated in the switched version. If you use the 'nodatasync' option, any changes to things like MWI state, CFA changes, DND setting and the other UFF settings will not be extracted from the current database and updated in the switched to version.
I took a quick look for other instances of this error, but I could not find any. Is that the exact message or something like the message you saw?
Thanks,
Dan Keller
Technical Marketing Engineering
07-21-2014 05:38 AM
I have the same problem with these same version and the the exact message is: "error: after sync switchversion failed."
Thanks
Szabolcs
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide