Basic Assignments
 
Options & Settings
 
Main Time Information
Color Code: Yellow
Assigned To: Brandon Moore
Created By: Brandon Moore
Created Date/Time: 9/24/2018 2:06 am
 
Action Status: Blank (new)
Show On The Web: Yes - (public)
Priority: 0
 
Time Id: 4078
Template/Type: Brandon Time
Title/Caption: After hours data migration
Start Date/Time: 9/23/2018 10:00 pm
End Date/Time: 9/24/2018 2:00 am
Main Status: Active

Sorry, no photos available for this element of time.


Notes:

Wayne and I got on an after hours migration task that was scheduled. We were running Wayne's cross-server database sync tool. This was the first time that we have run this program live. It has all been test data prior to this run. The program ran without errors and we checked record counts and all seemed to be good to go. We flipped some switched to point the corporation from the data 3 server to the data 8 server and then logged in. All of the data looked great, except for one primary table. Because everything wasn't perfect, we re-pointed the corporation back to where it was originally, and disabled it on the new server. We will check that one bug and then reschedule the migration. We want to be certain that everything transferred correctly. Wayne will be reaching out to the client to let them know that we need to reschedule. No harm done.

By way of a history note... This corporation was supposed to migrated almost a month ago with some other corporations. It was left off of the list of a multi corp migration process. When we do this, a normal migration - in the old way, we have one shot at taking any number of corps from one occupied server to another, unused or new server. Because this corporation got left off, we basically started all of the other corporations using the new server and thus created potential id conflicts (auto id numbers per corp). Within the first 15 minutes after we opened up the new server, they informed us that we didn't migrate one of the corporations (it was completely left off the list to migrate). In that small of a window, already 6 tables were unable to merge without id conflicts, thus blocking us from migrating the data between servers.

In the past month, Wayne has been working on a database sync tool that crosses between servers and non-destructively mirrors and duplicates the data without hitting the id conflicts. It has been a major undertaking with multiple test runs, one-on-one info sessions, lots of emails back and forth, and writing a complete program to fully automate the process. The tool is amazing and will end up saving us thousands and thousands of clicks and hours and hours of developer time. Today was the first live run. I'd say we hit about 95%. With a little bit more tweaking, it should be fully ready. Kudos to Wayne and his cross-server database sync tool. I'm excited to see what it can do when it is fully done.