Retired sysadmin legacy software rescue exposes archive risk

A retired sysadmin legacy software job turned into a tax-audit rescue after a US corporation asked a former UK support engineer to recover documents from a system he had not used in about 20 years, according to The Register’s On Call column. The case is a reminder that decommissioning old products does not eliminate the operating risk if customers still depend on archived data and the people who understand it have left.

The Register identified the engineer by the pseudonym “Roger” and said he had spent decades supporting applications at a UK-based business. In 2015, that company ended support for older products and told customers to preserve documents and invoices separately, either on paper or in durable digital formats, because the systems were expected to be retired.

Roger retired in 2021. A year later, he learned that a large US company had bought his former employer and dismissed the European support team, according to his account to On Call. That left the acquirer exposed when a German customer later needed records from the old software during a tax audit.

Why did the retired sysadmin have to restore the legacy software?

The German customer had kept its backup disks, but the backups held raw application data rather than ready-to-read documents. According to Roger’s account, the missing piece was the old process that turned ASCII files into documents, which depended on a print server running bespoke software.

The US owner asked Roger to reconstruct the files for a day rate roughly equal to one month of his pension, The Register reported. The company did not have the institutional knowledge in-house after the support cuts, and the customer’s paper archive had been lost.

Roger said he remembered enough of the installation process and obscure print-server settings to find the code, run the software and convert the archived ASCII data into PDF files. The company’s problem was not storage discipline: the customer had retained the backup media. The failure was recoverability, a separate issue that often shows up only when regulators, auditors or courts demand usable records.

The work did not end with the PDF conversion. Auditors later challenged the records for 2013 because many invoices appeared in the recovered documents but were absent from the accounting data, according to The Register. Roger traced the mismatch to an import error: one year’s archive had been loaded twice, which doubled the invoice count and made the customer’s records look suspicious.

Roger charged another day to find that error, the column reported. A younger project participant then suggested that several other archives had been preserved in the same format, raising the possibility of more recovery work. Roger declined to turn the assignment into a return to full-time employment.

The episode closed with an unusual detail. Roger told The Register that the income from the job would complicate his own tax position, so he donated the fees to the care home where he lives. The home’s management welcomed the donation, according to his account.

For acquirers, the lesson is direct: buying a company also means buying its support liabilities, even for products marked as ended. Cutting the team that understands a legacy system may improve near-term cost lines, but it can leave the buyer dependent on retirees when customers need legally usable data years later.

This story draws on original reporting from The Register.