The server migration we did this morning (Tuesday, August 4) is complete as far as we can tell. The last phase of it is changing the various DNS records for our various sites so that they point to the new server. That has been done, but it takes time for the changes to DNS to propagate throughout the Internet.
Until that time, you’ll see a yellow marquee banner across the top of pages at www.laridian.com and you won’t be able to sync your user data. If you see the yellow banner, the site will be slow because it’s talking across the wire to the database server instead of having it located “right next door” on its own subnet in the same building. Once the DNS change finds its way to your machine, you’ll be back up to full speed at the new site.
I’ll write up a little post-mortem article for the techies among you just for fun.
If you have problems with our site that don’t fix themselves by Wednesday, August 5, drop us an email at firstname.lastname@example.org.
Reason for the Outage
Laridian operates services on a variety of servers located at more than one hosting company. From time to time we move these services to new locations either to enhance their capability or to save money or both. We are generally able to do this in a way that minimizes or eliminates downtime. In this case, we are moving our database server, which stores almost everything of importance at Laridian including your customer account, transaction history, user-created data (notes, highlights, and bookmarks), and all our books.
It wasn’t possible in this case to make this transition without actually stopping all updates to the database, copying the data to the new server, and restarting it at its new location. During this brief time, we couldn’t do any operations that cause the database to change, or we risked losing those changes (i.e. they would get written to the “old” location after the database has been moved to the “new” location).
Once this whole process is complete, we expect enhanced performance of the website, sync service, downloads, and other related services. Security of all of these services will be increased. And despite the more powerful hardware on which this will all be running, our costs will be lower. This will allow us to continue to produce Bibles and reference materials at prices at or below what you’ll find elsewhere.
2:45PM Remaining DNS changes complete.
1:35PM Laridian Cloud sync services are back up. The IP address for synchronization has changed, so you may continue to get the “maintenance” message (or not be able to connect at all) until DNS changes propagate to your server. This could take up to 48 hours but in our experience most of you will see the change within a couple hours of it happening (which was actually a couple hours ago).
12:00PM Domain registrar is up and down. We have been able to make some DNS changes, but not all.
11:15AM Our domain registrar chose this time to go down. Of course. This isn’t a big deal, it just means that the sites will be slower. Once we can make DNS changes, the websites and the database server will be on the same subnet. Until then, the websites have to talk across the wire to the database, which means they’ll be slower. The worst part of this is that user data synchronization (Laridian Cloud) can’t be brought back up without changing DNS. We don’t anticipate this will take long.
10:45AM Commerce, product registration, account updates, and Apple App Store in-app purchase downloads are back online. The only thing currently offline is the Laridian Cloud (user data synchronization).
PocketBible 1.x.x for iOS users: If you got a message while trying to sync that said “You’re running a very old version of PocketBible“, it’s because you’re still using version 1.x and we’re currently on version 3. To upgrade, first sync (not just backup, but sync) your user data with the server after this maintenance is over. Then search the App Store for PocketBible. The program is free. Download and run it. Register using the same customer ID and password as you have been using, then turn on automatic synchronization under Manage My Data in the menu. The program will pick up your notes, highlights, and bookmarks and you’ll just have to download your Bibles and reference books.
8:30AM Migration officially started.
8:00AM Commerce, account update, PocketBible 2.x/3.x sync service, and other related services disabled.
7:30AM PocketBible for Windows and PocketBible 1.x sync services disabled.