Since we are moving our ODK Aggregate server to a new physical location (a
new ISP and as a result a new IP address). What would be the easiest and
quickest method to minimize the downtime and change of the IP configuration
in Aggregate Server.
I have seen a solution on this forum, which suggests to run Aggregate setup
again, is that completely safe if we have 30+ surveys and their databases?
Also,if i need to run the setup again, then do I have to carefully use
exact version of the current Aggregate setup?.
If there is a guide or list of steps to safely perform this process that
would be really nice.
Note: This is where buying and using a DNS name is useful. It isolates you
from the specific IP address that your server is running on, allowing you
to move to a different hosting service without needing to change any
configuration (except, perhaps, database configuration) and that move does
not impact any of your devices, as they just point to the DNS name.
The fact that the DNS name is then aimed at a different IP address is
completely hidden from everyone. The only thing you then need to worry
about is moving the software from one physical box to another.
···
=================
General steps will be the same as for upgrades -- described here:
The biggest headache is dealing with your database (I am assuming it also
needs to move). After using ODK Briefcase to pull the contents of your
forms and submissions down to a desktop, it is best to shut down your web
server in order to move your database (the ODK Briefcase content is a
back-up/fallback should the migration not go smoothly). Obviously, during
this process, no devices will be able to download or submit forms.
Once you have migrated your database, I would then run the ODK Aggregate
installer to specify the information needed for the new server location. If
you use the same "instance name" answer as you provided previously, then
the passwords for the usernames will not be reset. Otherwise, they will be
reset and you will need to manually change them back to their previous
values.
You should then be able to place the newly-built WAR file onto the new
server, start it up, log in, and verify that all the data migrated over
correctly. You should then confirm that the passwords for the usernames
were not reset (testing that one username and password continues to work is
sufficient). Then enable downloads and uploads of the forms.
The bigger hassle will be changing the configuration on all of your devices
to point to the new server.
Since we are moving our ODK Aggregate server to a new physical location (a
new ISP and as a result a new IP address). What would be the easiest and
quickest method to minimize the downtime and change of the IP configuration
in Aggregate Server.
I have seen a solution on this forum, which suggests to run Aggregate
setup again, is that completely safe if we have 30+ surveys and their
databases? Also,if i need to run the setup again, then do I have to
carefully use exact version of the current Aggregate setup?.
If there is a guide or list of steps to safely perform this process that
would be really nice.
Yeah as Mitch_S explained you don't need to focus your time and energy on the IP Addresses. DNS is the one thing you have to focus on. Cheers and Good Luck for your project.