Changes

{{Level|Developer}}

{{Level|Developer}}

===Restore smeX in vmware using a desktop backup and winscp===

==Restore smeX in vmware using a desktop backup and winscp==

This method is usefull for a restore or upgrading a version (I used it to upgrade from 7.51 to 8.0 in vmware esxi 4.1).  

This method is usefull for a restore or upgrading a version (I used it to upgrade from 7.51 to 8.0 in vmware esxi 4.1).  

In this mini-howto I will show howto restore a backup made to the desktop into a new SME server. In stead of using an USB-stick we will transport the backup using SSH (scp or secure copy).

In this mini-howto I will show howto restore a backup made to the desktop into a new SME server. In stead of using an USB-stick we will transport the backup using SSH (scp or secure copy). Since many sme-servers run in vmware, and using usb or iso-files can be complicated or impossible on ESX servers using SSH is a good alternative to transport the backup to the server.

Since many sme-servers run in vmware, and using usb or iso-files can be complicated or impossible on ESX servers using SSH is a good alternative to transport the backup to the server.

===Step 1. Make backup from original server to desktop in the server-manager===

 

==Forum discussion==

This how-to can be discussed on the forums [http://forums.contribs.org/index.php/topic,49417.0.html here]

 

 

==Make backup from original server to desktop in the server-manager==

  go the http://ip/server-manager and backup to desktop

  go the http://ip/server-manager and backup to desktop

===Step 2. install new SME server (sme8.x) from iso in vmware===

 

==Install new SME server (sme8.x) from iso in vmware==

Give it a temporary IP-adddress. When restoring it will get the ip-adresses from the server that was backed-up===

Give it a temporary IP-adddress. When restoring it will get the ip-adresses from the server that was backed-up===

- do not use vmx network cards, but use e1000 nic's instead, see http://bugs.contribs.org/show_bug.cgi?id=7197

- do not use vmx network cards, but use e1000 nic's instead, see http://bugs.contribs.org/show_bug.cgi?id=7197

- log in via web-management console http://ip/server-manager and change remote acces so you can log in via ssh as root from internal network

- log in via web-management console http://ip/server-manager and change remote acces so you can log in via ssh as root from internal network

===Step 3. install vmware tools in the newly installed sme-server===

 

==Install vmware tools in the newly installed sme-server==

See http://wiki.contribs.org/VMware_Tools#SME_Server_8.0_Guest_on_ESXi_4.0_Update_1

See http://wiki.contribs.org/VMware_Tools#SME_Server_8.0_Guest_on_ESXi_4.0_Update_1

in my case: SME Server 8.0 Guest on ESXi 4.0 Update 1

in my case: SME Server 8.0 Guest on ESXi 4.0 Update 1

((((((((((((((((((((

((((((((((((((((((((

===Step 4. update the new SME server to latest packages before restoring from backup===

 

==Update the new SME server to latest packages before restoring from backup==

Before update set yum straight

Before update set yum straight

check if this is still needed here: http://forums.contribs.org/index.php/topic,49362.0.html

check if this is still needed here: http://forums.contribs.org/index.php/topic,49362.0.html

===Step 5. restore with the backup file===

==Restore with the backup file==

- first make a snapshot in vmware, so you have a snapshot with updated packages (in case something goes wrong)

- first make a snapshot in vmware, so you have a snapshot with updated packages (in case something goes wrong)

- copy sme.tzg to / directory new sme server (for instance form windows desktop with [winscp]http://winscp.net/eng/index.php (= cp via ssh) )

- copy sme.tzg to / directory new sme server (for instance form windows desktop with [winscp]http://winscp.net/eng/index.php (= cp via ssh) )