Luminate Online Database Migration FAQ

Frequently asked questions about Luminate Online database migrations.
Will our site be accessible to Constituents and/or Admins throughout this maintenance?
Your services will be unavailable to both Administrators and Constituents.  A standard site maintenance page, similar to when we deploy a release, will be displayed to advise visitors of the maintenance until the update is complete.
 
What will be the timeline of the upgrade?
We are targeting to begin work at 10:00 p.m. CST and expect to conclude the maintenance no later than 4:00 a.m. CST.
 
What is the actual down time can we expect?
The estimated downtime for your site during the planned 6-hour maintenance window can be up to 4 hours.
 
Are we locked in to the date we are scheduled for migration?
Yes, in order to keep the timeline we have across all improvement projects and Luminate releases, we need to keep to the scheduled maintenance times.
 
How is this maintenance performed to maintain database integrity?
We are currently replicating data between the existing database server and the new database server.  During the maintenance window, we will take the site offline, allow all database updates to complete, point the site to the new database, initiate test protocol, bring site online backed by the new database.
 
Is there a roll back for this maintenance if it is not successful?
Yes, if during our testing we encounter any issue, we will be able to roll back to the current database and restore services as it currently exists today. This rollback process is estimated to require less than 30 minutes.
 
What if there is an issue 2 days… 1 week… etc… after the upgrade?
The current database will remain in our datacenter for 2 weeks while we monitor the new databases post-upgrade and will be storing backups. If at any time we observe degradation in services or data we will roll back to the previous database. 
 
Has this ever been done before for Luminate Online or is it a new procedure?
Under this process and leadership team, we have previously upgraded Luminate databases successfully and most recently upgraded the Luminate CMS database as well as several test databases. We have not encountered any issue where we needed to roll back.
 
What is the reasoning for performing this database migration?
We anticipate the reward from this maintenance will be marked improvements to performance and stability across the Luminate Platform.  We are taking every precaution to ensure data migration is successful and that the impact to you and your site is minimal.

Are we locked in to the date we are scheduled for migration?
Yes, in order to keep the timeline we have across all improvement projects and Luminate releases, we need to keep to the scheduled maintenance times. If you would like to know when your site will be upgraded, please reach out to Customer Support.

Environment

 Luminate

Was this article helpful?