All personal commentary, all opinion, no fights please....
It's worth it to understand a little bit of
MDE's structure - it is not exactly one big Database (DB) that can go down, and take everything with it

.
Instead - this is a system consisting of a central master - with many slaves. Each Hotel has replicated slave DBs, so when the main system dies? They have the latest data on your reservation. Each RESTAURANT has a local system... WHEN (not if) MDE crashes? They know you are coming

. DME is a whole separate system that pulls info from MDE.
FPs are another story, as are Magic "Everythings" (bands, cards, neck braces....) - these perform direct communications: no local park backups.
Again, all personal opinion - all of this is why I strongly suggest copying EVERY reservation number to one or more Cell Phone's, as a readable PDF. If you don't know how? It's done using a "Print to PDF" application - any MDE page that can be printed can be stored on a smart phone.... allowing you to SHOW that data to anyone. What they choose to do with it is their decision.
A great trick is to PRINT "My Reservations" to a PDF just before you leave, and store this on your Cell Phone - it will allow you to rattle off ALL Res Numbers, SHOW the Res numbers, and ask the all important question - "Where is YOUR Data?", in the event of an MDE Crash. Alternately? (we do both) - carry a PRINTOUT of all Res info - including ticket info.
Worth noting.... DB folks debate the wisdom of Client/Server DB copies. There are advantages, and disadvantages. The greatest value of "copy and retain" systems occurs when a massive CENTRAL DB is just too unreliable, overloaded, or is accessed by an overloaded network, to bet a business process on. One of the greatest DISadvantages of replicated systems - performing last minute updates. That data MAY or MAY NOT ripple through the DB "Copies" in a timely fashion.
Again, all opinion, not fact, based on about 27 years of work in this area.... it's not easy to create one big "system", and totally eliminate points of Network failure, Central system failure, local system failure.
Amazon has, perhaps, done the BEST job surrounding this this issue.
Meanwhile? In the absence of anyone being able to connect.... "here is my paper - contradict it"

. Again, all opinion, not truth, no fights please.....