Hi,
Somewhat. I haven't tested it throughly yet.
But, I do, based on the 'Migrate Server Howto':
http://mirror.contribs.org/smeserver/contribs//ptehvand/howtos/rsyncmigrate.htmlDo the rsync using the following commands in a cron-script:
*rsync -vP -z --delete -a -e "ssh -c blowfish" <oldserver>:<old directory> <new directory>
A trailing "/" after the old directory is very important in some cases.
The directories needed for a bare metal migration are:
* /home/e-smith/
* /home/netlogon/
* /etc/e-smith/templates-custom/
* /etc/e-smith/templates-user-custom/
* /etc/group
* /etc/gshadow
* /etc/passwd
* /etc/shadow
* /etc/smbpasswd
* /etc/ssh/
* /opt/
* /var/lib/mysql/
* /root/
* *the ones with trailing "/" mean you need to have it in the rsync command at the <old directory> point /etc/sudoers (if you use sudo)
NOTE: Copy the root to another dir than the original target machine /root.
In case of failiure of the main PDC - do the following.
* Copy the BU-root to the root dir of the backup-machine and watch out for the following:
* Once you copy over the /root directory you may experience issues with your .ssh/known_hosts file not being compatable any more
* Your network cards - and drivers - may not be the same in both servers - you may need to modify this at the admin console
Making the newly restored server Live
* At a root prompt type:
/sbin/e-smith/signal-event post-upgrade
then
/sbin/e-smith/signal-event reboot
When the server comes back up it should be identical to the PDC.
The disadvantage of this method is that it does not take place automatically.
If anybody have additions to this - please give feedback..
Cheers
/G