Backup-Recovery on Fortran 2026

Profitool

Mon, 01 Jan 0001 00:00:00 +0000

We are experts on Profitool, a long-running Fortran ERP. We have migrated a production Profitool deployment from 32-bit to 64-bit, added modern language features, and built the testing and deployment pipeline around it. If you run Profitool — or a similar Fortran-based ERP — we can take it forward instead of forcing you to start over.

Where we add value

32-bit to 64-bit migration without losing decades of business logic — see Expertise → 32 → 64-bit migration.
Modern extensions: SQL database access, regular expressions, hash maps, and REST APIs added directly into the existing Fortran codebase.
Containers and reproducible builds so the same binary you test is the binary you ship.
A real test framework — TAP-style unit tests with prove runners, instead of “compile and pray”. See Examples → Unit Tests.
Day-to-day operations: backup, restore, data recovery, and version-control discipline around a codebase that may have started before any of those existed.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

Backup and recovery

Mon, 01 Jan 0001 00:00:00 +0000

A Fortran ERP that loses a day’s data is not a software problem — it’s a business problem. We design backup and recovery for systems where the database, the data files, the binaries, and the build artefacts all matter, and all have to come back together.

Where we add value

Backup strategies that actually get tested, not just scheduled.
Restore drills — proving recovery works before you need it.
Point-in-time recovery across SQL databases plus the on-disk Fortran data files that live alongside them.
Disaster recovery plans that account for the build system and the source tree, not just the data.
Migration of old backups onto modern storage — tightly related to Legacy data.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au

Legacy data

Mon, 01 Jan 0001 00:00:00 +0000

A lot of Fortran systems sit on top of decades of data: binary records in undocumented formats, files copied from machines that no longer exist, tapes nobody has read in years. We are comfortable in that territory — and we know how to bring that data back into a system you can use today.

Where we add value

Reading old binary formats — record-based, fixed-width, vendor-proprietary, or whatever the previous decade left you with.
Reverse-engineering schemas from the Fortran code that wrote the files, when documentation is long gone.
Pulling data off old media and old machines onto modern storage with integrity checks.
Migrating recovered data into modern stores (SQL, files, APIs) without losing fidelity — see Examples → SQL.
Long-term archiving plans so this is the last time anyone has to do it.

Talk to us

simon@unisolve.com.au or scottp@dd.com.au