Changes

From SME Server
Jump to navigationJump to search
Line 74: Line 74:  
*Note the backup & restore may take many hours to complete depending on data size etc.
 
*Note the backup & restore may take many hours to complete depending on data size etc.
 
* After restore, the Configuration of the new server should be identical to the old server.
 
* After restore, the Configuration of the new server should be identical to the old server.
* Note with two servers connected during ssh copying operations, basic networking configuration of the new unrestored SME9 server will need to be temporarily different to the old server to avoid clashes
+
* Note with two servers connected during ssh copying operations, basic networking configuration of the new unrestored SME9 server will need to be temporarily different to the old server to avoid clashes.
 +
 
 +
 
 +
======<big>Migrate using the Lazy Admin Tools</big>======
 +
 
 +
 
 +
*[[Lazy_Admin_Tools#Server_Migration|Lazy Admin Tools]] provide a set of shell scripts that will archive all the important system files and restore them into a newly installed system, this is well documented in the Wiki. The various aspects of the system are saved in different files so that parts can be restored without having to restore all. An example might be to restore the users, but not the domains. It does not backup the data, but the wiki documentation provides sample commands to copy the data from one system to another using scp and/or rsync. All contribs must be re-installed, and any associated data (usually in /home/e-smith/db configuration files) maybe be copied across as required.
    
======<big>Reinstall Contribs after restore</big>======
 
======<big>Reinstall Contribs after restore</big>======

Navigation menu