Community
Moving the a private hosted server
Ashley Griffin,
User (Posts: 61)
Oct 19, 2016 6:14:55 pm EDT
Support level: Free or trial
Hi
I loaded the server on to a test PC, how can i move this keeping all the settings?
I would like to get it in to a final location for more detailed testing.... however i have address books, users setup etc...
Need to know how to backup and restore (or just move the whole thing).
Many Thanks
I loaded the server on to a test PC, how can i move this keeping all the settings?
I would like to get it in to a final location for more detailed testing.... however i have address books, users setup etc...
Need to know how to backup and restore (or just move the whole thing).
Many Thanks
Conrad,
Support (Posts: 3076)
Oct 19, 2016 8:16:03 pm EDT
Hello Ashley,
The server stores it's data files in the installation folder C:\Program Files\Remote Utilities - Server\ .
Service configuration settings are stored in this registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities\MiniInternetId
Administrator Console settings are stored here:
HKEY_CURRENT_USER\SOFTWARE\Usoris\Remote Utilities\MiniInternetId
One question though. Is the server machine at the new location supposed to have the same DNS name (or IP address) as your current server? Remember that the Hosts you have already deployed as well as the properties of respective connection entries in your Viewer address book/books contain the address (IP or DNS) of your old server machine. If you migrate your server and change its address/DNS name the Hosts and Viewers won't be able to use the new server.
While migration does not happen very often according to our customer feedback and reports, In subsequent updates we'll still provide an easier way to migrate. Namely, we'll put all data and settings into a single folder or a file that you'll just need to copy to the new location to transfer your data. Still, the IP/DNS issue remains.
By the way, a possible migration is the reason why we recommend that you use a DNS name over IP address for the server. Pointing your DNS name at a new IP address is a simple task, whereas assigning the IP address of the old server to the new one may not be possible.
The server stores it's data files in the installation folder C:\Program Files\Remote Utilities - Server\ .
Service configuration settings are stored in this registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\Usoris\Remote Utilities\MiniInternetId
Administrator Console settings are stored here:
HKEY_CURRENT_USER\SOFTWARE\Usoris\Remote Utilities\MiniInternetId
One question though. Is the server machine at the new location supposed to have the same DNS name (or IP address) as your current server? Remember that the Hosts you have already deployed as well as the properties of respective connection entries in your Viewer address book/books contain the address (IP or DNS) of your old server machine. If you migrate your server and change its address/DNS name the Hosts and Viewers won't be able to use the new server.
While migration does not happen very often according to our customer feedback and reports, In subsequent updates we'll still provide an easier way to migrate. Namely, we'll put all data and settings into a single folder or a file that you'll just need to copy to the new location to transfer your data. Still, the IP/DNS issue remains.
By the way, a possible migration is the reason why we recommend that you use a DNS name over IP address for the server. Pointing your DNS name at a new IP address is a simple task, whereas assigning the IP address of the old server to the new one may not be possible.
Ashley Griffin,
User (Posts: 61)
Oct 20, 2016 12:11:35 am EDT
Support level: Free or trial
We managed this by backing up the folders:
C:\Program Files\Remote Utilities - Server\data
C:\Program Files\Remote Utilities - Server\Logs
C:\Program Files\Remote Utilities - Server\stat
C:\Program Files\Remote Utilities - Server\Statistics
Installed on the new server, stopped the service, copied the above in to the server correct location, restarted the service. It then had the users and address books (and i am assuming the log files).
We did have to accept the new encryption key from that server which was fine.
We always use DNS names to negate problems like this with IP addresses, thanks for pointing this out though, its easy to miss.
The existing viewer signed in, can see the address books and we can see the test host we have running.
C:\Program Files\Remote Utilities - Server\data
C:\Program Files\Remote Utilities - Server\Logs
C:\Program Files\Remote Utilities - Server\stat
C:\Program Files\Remote Utilities - Server\Statistics
Installed on the new server, stopped the service, copied the above in to the server correct location, restarted the service. It then had the users and address books (and i am assuming the log files).
We did have to accept the new encryption key from that server which was fine.
We always use DNS names to negate problems like this with IP addresses, thanks for pointing this out though, its easy to miss.
The existing viewer signed in, can see the address books and we can see the test host we have running.
Conrad,
Support (Posts: 3076)
Oct 20, 2016 6:48:51 am EDT
Hi Ashley,
Good :) Let me know if you need help with anything else. More features are coming in beta 3 so stay tuned.
Thanks.
Good :) Let me know if you need help with anything else. More features are coming in beta 3 so stay tuned.
Thanks.
* Website time zone: America/New_York (UTC -5)