2,411
edits
Changes
Jump to navigation
Jump to search
mLine 11:
Line 11: − + − + − + Line 27:
Line 27: − − − − + − +
Minor text changes
This method is a good way to create a server clone that has identical configuration but no data, without going through all the setup again.
This method is a good way to create a server clone that has identical configuration but no data, without going through all the setup again.
==='''Procedure'''===
===Procedure===
It is preferable to make a /temp folder as files in /tmp are routinely automatically deleted by the server, and using /temp will avoid unwanted inadvertant deletion.
It is preferable to make a /temp folder as files in /tmp are routinely automatically deleted by the server, and using /temp will avoid unwanted inadvertent deletion.
If you don't have much data or email in .../users then don't bother to move that.
If you don't have much data or email in /home/e-smith/files/users then don't bother to move that.
On the server to be backed up (server1) do
On the server to be backed up (server1) do
mv /temp/users /home/e-smith/files/
mv /temp/users /home/e-smith/files/
mv /temp/ibays /home/e-smith/files/
mv /temp/ibays /home/e-smith/files/
Build another server to restore to (server2), and perform a fresh install of sme server on it. Note that any preferred hardware can be used, it does not need to be physically identical to the original server the backup was performed on.
Build another server to restore to (server2), and perform a fresh install of sme server on it. Note that any preferred hardware can be used, it does not need to be physically identical to the original server the backup was performed on.
Perform Restore from desktop on server2 using the standard server manager panel.
Perform Restore from desktop on server2 using the standard server manager panel.
On the restored server (server2), login as admin and select Configure this server.
On the restored server (server2), login as admin and select Configure this server.
Change the local IP and other settings as required, detect different NIC's, and also change to server only mode if it's going to be a second server on your network (where the backed up server was a server/gateway) and disable the dhcp server. As a minimum, make sure you change the local IP on the restored server as it will be identically configured after the restore.
Change the local IP and other settings as required, detect different NIC's, and also change to server only mode if it's going to be a second server on your network (where the backed up server was a server/gateway) and disable the DHCP server. As a minimum, make sure you change the local IP on the restored server as it will be identically configured after the restore.
Then log in to server manager on the restored server and change workgroup name and domain controller settings and any other settings required etc.
Then log in to server manager on the restored server and change workgroup name and domain controller settings and any other settings required etc.
You should now have a second server (server2) which is identically configured to server1 (except for changes that were made) but without User & Ibay data. Note that the user & ibays will exist in server manager and in the file structure, but they will be empty.
You should now have a second server (server2) which is identically configured to server1 (except for changes that were made) but without user and ibay data. Note that the user and ibays will exist in server manager and in the file structure, but they will be empty.
==='''Copying data to the restored server'''===
==='''Copying data to the restored server'''===