A Trade Show Contractor Versions Its Design Library With Files.com Sync and Amazon S3

A North American trade show contractor builds trade shows. As the general contractor for an event, the company is responsible for the means and methods behind the whole production: floor plans, exhibit structures and graphics, rigging, permitting, and on-site execution, delivered for show organizers, exhibitors, and corporate event producers across North America.

Behind every show floor sits a design operation. Graphic designers, structural and concept designers, and floor plan designers work in Illustrator, InDesign, and AutoCAD, and the files they produce are the documents a show gets built from. A single floor plan can represent months of one designer's work. The company's business runs on design files, and a design file is only as durable as the last application that saved it.

Corruption Arrives From Places No Policy Reaches

Corruption of creative files cannot be prevented at the source. It arrives through application bugs, network hiccups, and save behavior no policy reaches, and it lands on whichever file a designer happens to be in. The stakes scale with the file. A basic plan can be recreated quickly. A complex event file carries months of one designer's work, and rebuilding it is a project in itself.

The company wanted a history behind every working file, so that a bad save costs a restore rather than a redraw. The only durable answer to corruption that cannot be stopped is recoverability: keep a version of every file, and be able to go back to any point in it.

Versioning Terabytes Without Changing How Designers Work

At the company's scale, that was the hard part. The active design tree ran to terabytes and was growing continuously, far too much to copy onto workstations or back up by hand. And a version history of a tree that size threatens to become its own runaway storage problem, so any recovery layer needed retention rules built in from the start.

That set the requirements: version every design file automatically, restore any file to a point in time, change nothing about how designers work, keep the archive in storage the company owns, and cap the history so it never grows without limit. The company's design tree already ran on Files.com, the mounted drive its design teams work from every day. IT built the recovery layer with Files.com Sync and a versioned Amazon S3 bucket of the company's own.

A Timed Sync Into a Versioned Bucket the Company Owns

Files.com Sync turned the working design tree into a continuously versioned archive that maintains itself.

Using Files.com's remote server sync, the design tree pushes into an S3 bucket in the company's own AWS account on a timed schedule, leaving the working files in place. No designer triggers anything or changes how they save. The drive they work on is the same drive it was before.

The bucket does the remembering. With S3 versioning on, each push that changes a file adds to that file's history instead of overwriting it, so a damaged InDesign or AutoCAD file can be pulled back exactly as it existed before the bad save. Restores can be filtered to a point in time.

The history is bounded on purpose. A lifecycle rule on the bucket permanently removes non-current versions after a set period while always retaining the newest few as a safety margin, so the archive protects terabytes of active work without becoming an unbounded second copy of it.

IT proved the pattern before trusting it: the sync ran first against the smaller floor plans folder, and once the versions and restores checked out, the same sync was re-run from the parent directory to take in the full design tree. Pilot to production coverage took about a month.

Restores Instead of Rebuilds

With the sync in production, the company recovers a damaged design file from its version history instead of rebuilding it.

• A corrupted or badly saved file is recoverable from a prior version, with no redraw.
• The protection applies itself to new work. Every file designers add to the tree is versioned within minutes of landing, with no backup job to run per machine or per project.
• The archive belongs to the company: its bucket, its AWS account, its retention rules, holding a rolling history of terabytes of active design work.

Loss That Can't Be Prevented, Made Recoverable

Nothing about the corruption itself changed. Design applications fail the way they always did, and the company never expected to stop them. What changed is what a failure costs. When a designer opens a damaged floor plan, the conversation with IT is about which version of the file to bring back. Files.com Sync, pushing the working tree into a versioned bucket the company owns, put a ceiling on the loss: a bad save costs the work done since the last push, not the months since the drawing began.