On 11/30/2010 01:18 PM, Ricardo Freitas wrote: > I would like to know what is the best way to backup all my system > configuration and radiator files.
There are a couple of possibilities to do this. The best method depends mostly on your configuration and how you have installed Radiator. I would start by backing up the configuration directory, normally under /etc, the logging directory and other locations that are best checked from the Radiator configuration file. If you have installed Radiator from .tar.gz file and have not done make install, you can roll it back to a .tar.gz archive. If you have done make install, then Radiator files have been copied into directories such as /usr/lib/perl5/site_perl/. If you do "make -n install" as non-root user, you can check what the installer would do and where the files are copied to. You should be careful to check the locations especially if you have modified the Radiator files yourself. In this case you want to make sure that all these modifications are part of the backup. When you have collected the Radiator files get a list of installed packets and programs on your server. On Linux something like "dpkg -l" or "rpm -qa" should give you the view what packages, and especially Perl packages you have installed. If you run Windows, check the Windows installation instructions mentioned below. Please check http://www.open.com.au/radiator/documentation.html and the installation instructions. These instructions will help you to locate the important packages that Radiator needs. For example, if you need MS-CHAP or MS-CHAPv2, you must have the MD4 digest package. Otherwise you will get problems during the runtime. > Any of you guys have made this in the past? It is possible, but depends a lot how you have done the installation and what your configuration is. > I'm guessing this is a bit more tricky than just copying the files from > the server to a backup up computer. It can be as easy as that, especially if you can easily duplicate your server installation. Of course then there is the question of firewall rules, database access lists and so on, but then again, it depends on what your needs are. In other words, collecting the Radiator distribution and configuration files should be quite straight forward and creating a backup server involves much more work. > Thank you for the help My pleasure. I'll try to summarize a bit: If are running from the distribution directory, copy it to the backup. If you have done make install, copy the distribution directory you did make install from and see the perl site-perl directories. In both cases, remember the configuration directory, log directory and check the configuration file for other locations and files such as certificates. Also make sure that local modifications, if any, get backed up. I strongly recommend setting up a test server for testing the backup and backed up configuration. > Ricardo Heikki -- Heikki Vatiainen <h...@open.com.au> Radiator: the most portable, flexible and configurable RADIUS server anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
