Hi all, I'm in the process of migrating our RADIUS servers from 1.17 to 2.14. I've scoured all over for any information relating to the migration of the MySQL database. Am I just missing something here, or are the two versions completely non-compatible? If this is the case, I'll have to write a translator to migrate the data from the old DB into the new one. Steve
Hi,
Hi all,
I'm in the process of migrating our RADIUS servers from 1.17 to 2.14. I've scoured all over for any information relating to the migration of the MySQL database.
Am I just missing something here, or are the two versions completely non-compatible?
look at the schema for 1.1.x then look at the schema for 2.1.x - both SQL files are available with the source. i cant recall that there were many changes...extra columns in tables such as NAS alan
Also, instead of usergroup table in dialup.conf file you'll find radusergroup as table name. You can solve this "issue". Just delete "rad" and leave "usergroup"... Also, you have priority fields and you can comment them in dialup.conf if you don't need them. Marinko A.L.M.Buxey@lboro.ac.uk wrote:
Hi,
Hi all,
I'm in the process of migrating our RADIUS servers from 1.17 to 2.14. I've scoured all over for any information relating to the migration of the MySQL database.
Am I just missing something here, or are the two versions completely non-compatible?
look at the schema for 1.1.x then look at the schema for 2.1.x - both SQL files are available with the source. i cant recall that there were many changes...extra columns in tables such as NAS
alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Marinko Tarlac wrote:
Also, instead of usergroup table in dialup.conf file you'll find radusergroup as table name. You can solve this "issue". Just delete "rad" and leave "usergroup"... Also, you have priority fields and you can comment them in dialup.conf if you don't need them.
Thanks Alan and Marinko, After reviewing the entire situation, it doesn't appear that it's going to be as big an issue as I first thought. The only table that I use that is different in structure is the radacct table. At first, I thought I would have to migrate all of that data into the new database. However, because I aggregate daily and monthly totals into a different table, I *should* be able to switch over to the new RADIUS servers around midnight, and then thereafter, migrate my daily/monthly aggregate total tables over. I've got many custom applications that dip into the RADIUS database across the network, but I think there is only one that accesses the radacct table directly, so that's easily fixed. Thanks for the help, Steve
participants (3)
-
A.L.M.Buxey@lboro.ac.uk -
Marinko Tarlac -
Steve Bertrand