Home Download News FAQ / Knowledge Base Screenshots Documentation Support
philosophical imaginary

Differences

This shows you the differences between two versions of the page.

faq:systemadmin:how_do_i_move_citadel_to_another_host [2008/12/14 21:26]
ajc
faq:systemadmin:how_do_i_move_citadel_to_another_host [2009/08/02 16:05] (current)
ajc
Line 1: Line 1:
-====How do I move my Citadel Server to another machine?==== +====How do I move my Citadel installation to another machine?====
-As time goes by, new Hardware becomes available/gets cheaper, and you might want to utilize them to swap your citadel installation to one. What do I need to know?+
  
-Citadel stores its data in binary machine dependant format. So you can only directly copy over the binary files, if **Byte Order** and **Byte alignment** are the sameSo, moving from Sparc to Intel, or from 32 Bit Intel to 64 Bit AMD isn't possible with direct copy. For these cases we have [[documentation:system_administration_manual#database.maintenance|ARTV EXPORT]].+It is likely that your Citadel installation will outlive the hardware on which it runs We have made several options available for migrating Citadel to new hardware.
  
-In general, Citadel stores some data directly on the filesystemthat you need to copy; see the [[documentation:file_layout|File Layout]]; you need the files in the sections 'Configuration Files and Directories' and 'Data Files'.+Citadel stores its data in a binary, architecture-specific format.  As a result, you can only make a direct copy of the binary files in the **byte order** and **byte alignment** are identical on the old and new hardware.  So, for example, if you are moving from SPARC to Intel, or from 32-bit Intel to 64-bit AMD, this is not possible with a direct copy.  For these cases we have made a migration tool available.
  
-If you're going the ARTV way, you don't need the data/ dir, and citadel.control plus citadel.config. You could however, consider to pipe the two machines together using netcat:+The source (old) system must be running Citadel 7.60 or newer.  If you are running an older version, you must upgrade it first We are committed to eliminating this requirement going forward -- in other words, starting with version 7.60 we will make the over-the-wire export data format upwardly compatible.
  
-===New Box=== +You will also require OpenSSH v4 or newer, and a reasonably modern version of rsync, on both systems. 
-  nc -l -p 12345 |sendcommand "ARTV import+ 
-===Old Box=== +Go ahead and install the latest version of Citadel on the target (new) system.  The target system must be running a version of Citadel that is either equivalent to, or newer than, the version on the source system. 
-  sendcommand "ARTV export" |nc NewBoxIp 12345+ 
 +Then log in to the console of the target system as root or root equivalent, and run the "ctdlmigrateutility.  You will be prompted for the host name or IP address of the source system, as well as the username and password of a host system account that has access to all Citadel files (once again it's easiest to just go with root or a root equivalent for this). 
 + 
 +Then just sit back and watch it run.  First, the Citadel databases will be exported to an XML format, downloaded across the wire, and imported into the target system.  Afterwards, non architecture dependent files such as user photos and profiles, room info files, etc. will be copied over using rsync. 
 + 
 +After the migration utility completes its work, simply shut down the source system, restart Citadel services on the target system, and you're up and running.  You may wish to double check the configuration on the target system in case things like host IP address have changed.
  
-You should consider to first install an empty new citadel on the new box, and then put the data over. For ARTV Import you need to have a fresh installed but running Citadel server. 
Copyright © 1987-2019 Uncensored Communications Group. All rights reserved.     Login (site admin)