Toy Story 2 was in heavy production at Pixar in 1998 when the studio nearly lost it to a single command. In Pixar’s own Studio Stories short “The Movie Vanishes,” released as a bonus feature with the film, technical leads Oren Jacob and Galyn Susman tell the story directly. Working late on the model files, they watched directories begin to disappear from the shared Unix server. Someone had run a recursive delete at or near the root of the project, and the system was tearing through the file tree, removing assets as fast as it could.
By the time the command was stopped, a large share of the film was gone. In the Pixar account, the deletion took out character models, sets, and animation data, amounting to roughly 90 percent of the movie. The natural response was to restore from backup. That is where the second failure surfaced: the studio’s backup system had quietly stopped working correctly for some time, so the tapes that should have held a clean copy were not usable. The safety net that everyone assumed existed was not there.
What saved the production was an accident of circumstance. Galyn Susman, a technical director on the film, had recently had a baby and had been working from home, and a copy of the film’s database had been living on a computer at her house so she could keep contributing during her leave. When the team realized her machine might hold the only intact copy, they retrieved it with extreme care. In the Pixar retelling, the computer was wrapped, cradled, and moved slowly, because a single jolt to the hard drive could have destroyed the last surviving version of the movie.
The home copy was not perfectly current, so the team still had to reconstruct recent work, but it gave them a foundation to rebuild from instead of starting over. The episode became one of Pixar’s most-told internal stories precisely because the company chose to tell it on the home video release rather than bury it, turning a near-catastrophe into a teaching anecdote.
The lessons are the ones every studio and engineering shop eventually learns the hard way: destructive commands on shared systems are dangerous, and backups that are never tested are not backups at all. A restore that has never been exercised is an assumption, not a guarantee. The accidental survival of a copy on one technical director’s home machine is exactly the kind of luck that good practice, including disciplined version-control and verified recovery, is supposed to make unnecessary.
The story is also a reminder of how thin the margin can be on landmark creative work. A film that went on to be a major success came within one untested backup of vanishing, saved less by process than by a copy that happened to exist where no one had planned for it to be.