Changes

Log into the <code>prodIP</code> box and stop all services that can modify data.

Log into the <code>prodIP</code> box and stop all services that can modify data.

  SVC='qpsmtpd sqpsmtpd crond pop3 dovecot pop3s ftp httpd-e-smith atalk smb qmail'  

 

 

 

  SVC='qpsmtpd sqpsmtpd crond pop3 dovecot pop3s ftp httpd-e-smith smb qmail'  

  for s in $SVC; do service $s stop; done

  for s in $SVC; do service $s stop; done

This action will complete very quickly as only hardlinks are used and no data is physically moved.<br>

This action will complete very quickly as only hardlinks are used and no data is physically moved.<br>

'''''Note:''' Do not be scared if your prompt looks different!<br><br>

'''''Note:''' Do not be scared if your prompt looks different!<br><br>''

Now do a reboot

Now do a reboot

=== Using the backup and restore fonctions ===

=== Using the backup and restore functions ===

The general working way is to make a backup of the old SME and to restore it on the new SME (upgraded or not).

The general working way is to make a backup of the old SME and to restore it on the new SME (upgraded or not).

The fonction "RPMCheck" can be used indirectly with the backup server (compare the list with the old and with the new hardware) to get the list of rpm's that are missing on the new hardware but it is not available for a backup on the external usb disk.  

The function "RPMCheck" can be used indirectly with the backup server (compare the list with the old and with the new hardware) to get the list of rpm's that are missing on the new hardware but it is not available for a backup on the external usb disk.  

==== Preparation ====

==== Preparation ====

Take a backup of the running old 'prod server' (see the above conf file).

Take a backup of the running old 'prod server' (see the above conf file ''/etc/affa/prodserv.conf'' ).

{{Note box| Like using the way based on "rise", your can take the first backup (takes long time) without stopping the services and the last one (is quick) after the logout of the users and the stop of the services }}

{{Note box| Like using the way based on "rise", your can take the first backup (takes long time) without stopping the services and the last one (is quick) after the logout of the users and the stop of the services }}

After the backup, set a temporary IP into the conf file of the backup job:

After the backup, set a temporary IP into the conf file of the backup job:

'''Keep in mind that:'''

'''Keep in mind that:'''

:[--preserve-newer=yes]: files on the remote server with modification time newer than on the backup are not overwritten.

:[--preserve-newer=no]: files on the remote server with modification time newer than on the backup are overwritten through the older ones of the backup.

:[--delete=yes]: all files on the remote server, which are not in the backup, are deleted.  

:[--delete=yes]: all files on the remote server, which are not in the backup, are deleted.  

After the restore, the new prodserver will reboot.

After the restore, the new prodserver will reboot.

In case of an OS upgrade, check and if necessary reconfigure the repositories of yum for the new version.

 

 

* In case of an OS upgrade, check and if necessary reconfigure the repositories of yum for the new version.

[[Category: Howto]]

[[Category: Howto]]

[[Category: Backup]]

[[Category: Backup]]

----

----