10/05/2026
“Restore yesterday’s clean backup and stop making this personal.” My father-in-law, Kenneth, said it over the phone while I stood in the plant IT room holding a cracked-screen phone with a photo of work order 88417 on it. I’m John, 42, and I do IT support at the manufacturing plant owned by my wife Jessica’s family.
Two years earlier I lost a better network job during a restructuring. The plant became the paycheck that kept our mortgage current, which meant disagreeing with Kenneth was never just a workplace problem.
Kenneth, 67, ran operations. A worker named Luke, 27, had been injured on Line Four during second shift the night before. The maintenance database now showed a shutdown request that Kenneth said should not be there.
According to him, Robert, a 29-year-old maintenance technician, had entered the record after Luke was hurt and made the request look older than it really was. Kenneth wanted me to restore the automated backup from 1:00 a.
m. the previous morning, before the disputed entry appeared in the system. The backup itself was ordinary; our application server took snapshots overnight.
Restoring that 1:00 a. m.
copy over the live maintenance database would roll the system back to
the state it had before work order 88417 existed. Any maintenance entries created later that day would disappear from the ordinary live view unless someone rebuilt them afterward.
Kenneth called that “clean.” The problem was my phone. The previous afternoon, before Luke’s injury shift, Robert had been at my desk because his tablet would not sync.
While I reset it, he complained that a shutdown ticket for Line Four kept bouncing between maintenance and production. He had a printed work order in his hand, and I photographed it so I could compare the ticket number and creation time with the sync queue.
I forgot about the picture until Luke got hurt. Now the live database showed the same number: 88417. I was not a safety engineer.
I could not tell from a work-order screen whether Line Four should have been shut down at a particular minute, and I could not tell who made an operational decision. But I knew two things I was qualified to know: the 1:00 a.
m. backup predated the ticket, and my photograph of the ticket predated Luke’s injury. So Robert could not have invented the entire work order after the accident the way Kenneth was claiming.
I looked at the printed service schedule clipped beside my monitor. The outside maintenance contractor had already listed Line Four for inspection that week.
That did not prove a shutdown had been ordered, but it made the ticket less random than Kenneth wanted it to sound. I called Jessica before doing anything. She is 40 and works outside the plant.
“Dad says you’re holding up production over a bad maintenance entry,” she said. “I’m refusing to roll the database back before the current version is preserved.”
“Is there a difference?” “A big one to me.” Jessica was quiet for a second.
“John, you know how scared they are. Luke got hurt.
Contracts are tight. Dad thinks Robert created something after the fact and everybody is treating it like a cover-up.” “I’m not calling it a cover-up.”
“Then why not restore the backup?” I looked at the photograph again.
“Because that backup is from before the ticket existed. Restoring it would make the live system look like the ticket was never created at all.” Jessica asked whether I had shown Kenneth the photo.
I told her not yet. She said maybe I should do that before this became a family war.
I told her I would stick to the records I legitimately maintained and let the safety review decide what they meant. After we hung up, I checked the retention window on the server logs. The oldest automated copies and audit logs around the incident would begin rotating out under normal policy soon.
I had authority to place relevant system material under retention hold for an active incident review, but nobody had done it yet. Before I clicked anything, Kenneth appeared in the IT-room doorway.
He had driven back to the plant. “You called Jessica?” “She’s my wife.”
“She’s my daughter, and she does not need to be put in the middle of plant business.” “I didn’t ask her to make a plant decision.”
Kenneth stepped closer. “This company is keeping your household afloat. I gave you a job when nobody else was calling you back.
Robert made a mess in the system. Restore the 1:00 a.
m. backup, let operations reopen whatever legitimate maintenance work belongs there, and we move on.” I turned the monitor enough for him to see the restore screen, but I did not start it.
“If I restore this copy, work order 88417 disappears from the live database because it was created after that snapshot.”