Replication between Cisco ACS 3.3.3 and 4.0 or 4.1

Unanswered Question
Jul 22nd, 2007

Hi friends

my customer has ASC ver. 3.3.3 as primary at windows server and secondary is new and ACS 4.0 is installed on it but is free from data.

Qes : they asking if we can replicate the database between primary acs 3.3.3 and secondary 4.0 then after that we remove primary from the network where the secondary will be primary ,we will upgrade 3.3.3 to 4.0 then will reconnect it to the network after testing.

that is only they want to avoid down time

plz give the best advise and solution

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 4 (1 ratings)
Loading.
Richard Burts Sun, 07/22/2007 - 15:06

I do not believe that this will work. My understanding is that replication in ACS checks to be sure that both machines are running the same version of ACS and will abort if they are not running the same version.

HTH

Rick

The answer is no, you cannot automatically replicate between different versions, either major (3.x to 4.x) or point (3.3.3 to 3.3.4) releases, ACS server versions have to match.

There are also some major differences between the 3.x and 4.x data storage in that up to v3.x information is stored in the registry, whereas 4.x does not.

The best method to reach the end results you seek is to install the secondary as 3.3.3, replicate, then upgrade the primary to 4.x (I would suggest that you upgrade to 4.1.3 build 12 patch 2) as there are quite a few bugs between 4.0 and that release that have been vanquishd.. Finally after you have verified the functionality of the upgraded 3.3.3 primary box, slick it and do a clean install of 4.x and replicate it from the primary.

As a practice I never re-use an upgraded system in production... I upgrade the data on a box and replicate it to a newely installed box, that leaves fewer OS ghosts in the machine to contend with.

darpotter Sun, 07/22/2007 - 22:52

For replication to work the major and minor version numbers must match, so

3.3(3) to 3.3(4) is perfectly OK, but

3.2(x) to 3.3(x) isnt

This is because replication works simply by bulk copying the raw datafiles from one box to another. Had to write it like that to keep the downtime to an absolute minimum.

Actions

This Discussion