A Public School District Builds an Insurer-Accepted Immutable Backup Chain for Infinite Campus With Files.com

A US public school district serves more than ten thousand students across dozens of schools, taught and supported by thousands of teachers and staff.

Everything the district does rests on one dataset. In a public district, enrollment is not just a headcount. State funding is set per pupil and makes up the majority of the general fund, and the student information system, Infinite Campus, is where that enrollment lives, along with the record of every student the district serves.

Infinite Campus was backed up every day. The district wanted those backups to land somewhere separate from the primary environment, with an independent copy to fall back on and an immutable copy behind it.

The district selected Files.com to be that middle tier. It became an unattended bridge from Infinite Campus to immutable Wasabi storage, creating a three-copy chain without a dedicated backup product or team. Three years on, the district has a standing backup posture its cyber insurer has accepted.

An Independent Home for Every Backup

The requirement was simple to state: the district's most sensitive dataset needed a recovery path that did not depend on the primary environment surviving. Corruption, a bad change, and ransomware are the cases a backup chain exists for, and the district wanted a copy that none of them could reach.

The chain also had to be demonstrable. Its cyber insurer reviews the district's recovery posture, and what an insurer looks for is a chain that ends somewhere immutable: storage that nothing inside the district's environment, and nobody who compromises it, can alter or delete. The district wanted a chain it could show the insurer end to end.

Tens of Gigabytes a Day, With No Backup Engineering Team

Building that chain was normally a project. An off-site, immutable backup chain usually meant dedicated backup software to license and operate, or engineering time to build and maintain a pipeline. A district IT department had neither sitting idle. It had a school system to keep running.

And the volume did not pause. A full SIS backup landed every day and kept landing year after year. Any chain with a person in the middle would decay the first month that person was busy. Whatever the district built had to run unattended, indefinitely, and be provable when the insurer asked.

The requirements were clear: move each large nightly backup off the primary environment, replicate it to immutable storage, restrict who could reach it, and keep the entire chain unattended.

Files.com Between Infinite Campus and the Immutable Copy

What the district built was a three-copy chain with Files.com as its automated middle: the primary Infinite Campus environment, an independent copy on Files.com, and an immutable third copy on Wasabi.

The district's systems team set up automated SFTP jobs to deliver each day's Infinite Campus backup straight to Files.com. From there, Files.com Remote Server Sync replicated every backup onward to Wasabi, the district's immutable archive tier and the copy built for the worst case, because nothing in the district's primary environment could rewrite or delete it.

Access was as narrow as the job, with group-based folder permissions holding the backup tree to the people who needed it. And because the chain was built from the platform's own capabilities, an SFTP endpoint on one side and Remote Server Sync on the other, there was no backup product to license and no pipeline for the team to maintain. The backups moved because Files.com moved them.

Three Copies, One Immutable, and the Insurer's Sign-Off

Three years on, the chain has done what it was built to do. With the Files.com pipeline in production, the district has a standing, provable backup posture for its student records.

• Every day's Infinite Campus backup lands on Files.com automatically: tens of gigabytes a day, sustained for three years, with nobody moving a file by hand.
• Every backup flows onward to Wasabi, giving the district a third, immutable copy that a compromise of the primary environment cannot reach.
• The archive has real depth: years of SIS backup history ready to fall back on.
• The district demonstrated the full chain to its cyber insurer and had it accepted.

That acceptance is the compounding result. The copies accumulate every night whether anyone is watching or not, and proving the posture is now a demonstration rather than a project.

Recovery That Does Not Depend on the Primary System Surviving

Today, a bad day in the primary SIS environment is not a bad day for the student records themselves. The records of every student in the district exist in three places, and the third sits on storage that no failed change, no compromised credential, and no mistake inside the district can touch.

Getting there took no dedicated backup product and no new team. The result is an arrangement a district IT department can actually sustain, and three years of unattended nightly backups say it has.