Categories
Latest News

How an Award-Winning Film Editing Studio Cut Outage Downtime from 3 Days to 30 Minutes with NAS Redundancy 

This is the story of how a team of editors rethought data security: it isn’t only about protecting files, but about protecting the team’s ability to keep working.

Case Study at a Glance

  • Who: Director Shieh Meng-ju, founder of ZABA Studio in Taiwan. He won Best Film Editing at the 58th Golden Horse Awards, the 61st Golden Bell Awards and the 2018 Taipei Film Festival. His directorial debut, Mudborn, was Taiwan’s highest-grossing horror film of 2025.
  • The studio: Three editors sharing one storage system, delivering roughly four feature films and three TV series a year.
  • The result: Time to resume work after a storage failure dropped from 2–3 days to 30 minutes (measured in an in-house test).
  • How: A QNAP TVS-h1688X running Hybrid Backup Sync 3 (HBS 3) syncs data every day during off-peak hours, creating a redundant copy with the same folder structure as the primary workspace. If the primary system fails, editors switch to the NAS and keep editing.
  • The mindset shift: From “keep the data safe” to “minimize downtime” to “let it run itself.”
  Before QNAP NAS After QNAP NAS
Storage architecture A single Fibre Channel SAN SAN + QNAP TVS-h1688X NAS
Time to resume work after a failure 2–3 days 30 minutes (in-house test)
What editors can do during a failure Stop work and wait for the SAN to rebuild Switch to the NAS and keep editing
Ingesting external media Manual transfers and hand-delivered drives Automatic daily cloud downloads, verified before transfer
Remote and cross-company collaboration Not possible Assistants work from home; shared folders across companies

RAID 6 Saved Every File, but the Studio Still Lost a Week

On the evening of March 3, 2022, a major power outage hit Taiwan. The studio’s uninterruptible power supply (UPS) did its job at first. But Shieh was away and couldn’t get back in time to shut the system down properly. About an hour later the UPS battery ran out, and the SAN lost power. When the team powered it back on the next morning, one hard drive had failed.

Not a single file was lost. RAID 6, a disk array that can survive two simultaneous drive failures, kept every media and project file intact. The real problem was that the whole studio depended on that one storage system. While the failed drive was replaced and the array rebuilt, the three editors had nowhere else to work, and editing stopped for two to three days. The team spent the following week working four extra hours a day to catch up, and they still missed their delivery deadline.

The post-incident review led to one key conclusion: RAID and a UPS provide fault tolerance, not redundancy. Fault tolerance keeps the system running; redundancy keeps people working.

“A UPS doesn’t sell you security. It sells you time—and someone has to be there during that time.” — Shieh Meng-ju

Fault tolerance protects the hardware and the data. If one drive fails, no data is lost; if the power drops for a few minutes, equipment keeps running. Redundancy & failover protect the workflow and the team’s productivity. While the primary storage is being recovered or its array rebuilt, a second working environment is ready to take over immediately. That night, ZABA Studio had fault tolerance but no redundancy.

That realization shaped everything that followed. Shieh didn’t need a more powerful SAN. He needed a second option: first, a standby workspace next to the SAN so the team could get back to work right away; then, using that same NAS, a bridge to people outside the studio.

Figure: The Evolution of ZABA Studio’s Storage Architecture · Three Stages

Build a Backup Editors Can Actually Work From

The original goal of adding the QNAP TVS-h1688X was simple: make a copy. The studio scheduled HBS 3 to sync every day during off-peak hours so backups wouldn’t compete with daytime editing for bandwidth.

The next step is what truly changed how the studio thinks about storage. If the NAS folder structure matches the SAN exactly, the backup becomes a working copy. Editors can unmount the SAN, mount the NAS, and let Adobe® Premiere relink every media file at once using the same relative paths.

To make that possible, the studio set a shared naming convention for everyone involved. The SAN, the NAS, assistants working from home and partner companies all use the same top-level folders: 01_Project / 02_Dailies / 04_Music / 05_SFX. It may seem like the least technical part of the setup, but the studio considers it the key to quick transitions: “Hardware can be replaced, but inconsistent folder structures cannot be fixed by swapping hardware.”

Connect the Same NAS to the Cloud and Stop Moving Files by Hand

QNAP HBS 3 supports one-way, two-way and active sync, and it works with most major public cloud services. Since the NAS was already syncing with the SAN, the studio connected it to public cloud storage as well.

The NAS is split into two volumes:

  • Volume A (50 TB): external sync. Handles cloud-to-local transfers, file sharing with other companies and media verification.
  • Volume B: internal redundancy. Mirrors the SAN folder structure exactly, so editors can resume work immediately.

With dual 10GbE, internal editing and external sync each run on their own network path.

The daily workflow for dailies now looks like this:

  1. The crew uploads footage from the set to the cloud.
  2. HBS 3 syncs it to the NAS.
  3. Local scripts verify the files and transfer them to the SAN.
  4. Footage is ready for editing.

Remote assistants can work from home, exchanging project files, sound effects and music through shared cloud folders.

Figure: ZABA Studio Storage Architecture: Data Flow and Mounting Redundant Storage

The most representative case study is Pigsy, winner of Best Animated Feature at the 60th Golden Horse Awards. The animation studio producing Pigsy and the editing team at ZABA Studio each ran their own NAS, synced to the same cloud folder. The editors first set the length of each shot from the animatic, which guided the production team’s animation and voice-over work. For small changes, such as swapping a shot or revising a line of dialogue, the production team could open and edit the project directly, and the editors saw the update as soon as it synced.

Back Up by How Often Data Changes, Not by How Big It Is

Many studios assume that the bigger the files, the more often they need backing up. ZABA Studio does the opposite: it chooses a backup method based on how often the data changes.

Data type Size How often it changes Backup method Acceptable lag
Daily media (proxies, audio, continuity sheets) 2–10 TB Rarely, once ingested HBS 3, off-peak schedule One day
Active projects (Premiere Productions) Tens of MB Every minute Local + SAN + Adobe® Cloud (three locations) Near real time

The trade-off is deliberate. The studio gives up real-time media sync in exchange for being able to resume work immediately. If a day’s worth of media is lost, the production crew can supply another copy. But two or three days without editing is creative time that can never be recovered.

Inside the 30-Minute Recovery Test – Switching Storage Took Just Five Minutes; the Rest Was Spent Rebuilding the Premiere Cache

Under the new setup, the two to three days of downtime from that power outage shrinks to 30 minutes.

The studio measures recovery from the moment editors can actually work again, not when the hardware comes back. In its test, after confirming the SAN could no longer be mounted:

  • Minute 2: All three editing workstations switched to NAS Volume B.
  • Minute 5: Premiere Productions repointed the source folders and relinked all media at once via relative paths.
  • Minute 10: The timeline was ready for playback.
  • Minutes 10–30: Premiere rebuilt its cache.

In other words, the storage switch itself took about five minutes; most of the rest was cache rebuilding.

“Recovery time should be measured not just by when the system is restored, but by when people can get back to work.” — ZABA Studio’s guiding principle

Figure: Post-SAN Failure Recovery Timeline: 30-Minute Recovery in Actual Testing

The NAS also adds several layers of protection that RAID alone cannot provide. Snapshots allow accidentally deleted or overwritten files to be restored to a previous state. UPS integration enables the NAS to shut down safely upon detecting a power outage, preventing the same scenario that occurred during the previous outage from happening again on the NAS side. With the SAN and NAS each holding a copy of the data, an additional independent copy of the data is maintained beyond RAID. Because snapshots and the original data reside on the same device, a two-copy storage architecture is still required to provide comprehensive data protection.

What’s Next: Off-Site Backup and a Storage System That Runs Itself

ZABA Studio is candid about what’s still missing. Right now the cloud holds copies of media files only, not project files. An off-site NAS is planned to protect against site-level disasters such as natural disasters. On the SAN side, which runs on two Mac mini metadata controllers (MDCs) and a storage array rack, UPS-triggered shutdown is still being worked out. Further ahead, the studio wants semantic search for media, automatic transcription of continuity sheets and dialogue, and automated archiving that clears Volume A one month after a shoot wraps.

The studio sums up its journey in one line: the design goal moved from “keep the data safe” to “minimize downtime,” and the next stage is “let it run itself.” What started as an extra layer of insurance became a studio that keeps running even when the person in charge isn’t in the room.

If your team relies on a single primary storage system, start with one question: if your primary workspace goes down, do your editors have a second place to keep editing?

Feel free to contact the QNAP team to discuss practical use cases and arrange a trial based on your workflow.

Frequently Asked Questions

1. What is the difference between RAID, backup and redundancy?

They solve different problems. RAID keeps data intact when drives fail, backup lets you recover lost or encrypted data, and redundancy with failover lets people keep working when the primary system goes down.

Mechanism Question it answers What it handles What it doesn’t handle
RAID If a drive fails, is my data still intact? Failure of one or two drives Accidental deletion, ransomware, or failure of the whole device
Backup Can I recover lost or encrypted data? Accidental deletion, device damage, ransomware Downtime while you restore
Redundancy & failover If the primary system fails, can people keep working? Downtime caused by a primary storage failure On its own, it doesn’t replace versioning or off-site protection

At ZABA Studio, the QNAP NAS acts as both backup and redundancy: it holds a copy of the SAN with an identical structure, so editors can work directly from it. Editors switch over manually at their workstations.

2. Do post-production studios that already have RAID 6 and a UPS still need a second NAS?

Yes. At ZABA Studio, RAID 6 prevented any data loss, but editors still stopped work for two to three days because there was nowhere else to work while the SAN rebuilt. A second NAS provides both a data backup and work continuity: if the primary storage is rebuilding or data is accidentally lost, editors switch to the NAS and keep going.

3. How should Adobe® Premiere project files be backed up?

Project files are small and change every minute, so ZABA Studio keeps them in three places at once (local storage, the SAN and Adobe® Cloud) for near-real-time protection. Premiere Productions’ project locking ensures only one person can write to a given project at a time.

4. How can a NAS backup be ready to use immediately?

Make the folder structure on the NAS redundancy volume match the primary workspace exactly. ZABA Studio uses QNAP HBS 3 to sync its SAN to NAS Volume B every day during off-peak hours. If primary storage fails, editors mount Volume B, and Premiere relinks the files in bulk using the matching folder names and relative paths.

5. How can two companies sync media and projects for collaborative editing?

On the animated feature Pigsy, the animation studio and ZABA Studio each used their own NAS, synced to the same cloud folder with an identical directory structure. When the production team updated a project file, the editing team saw the change as soon as it synced.

6. What role does the QNAP NAS play at ZABA Studio?

The QNAP TVS-h1688X is both a second working path if the primary SAN fails and a hub for external collaboration. It handles daily cloud-to-local transfers of dailies from the set, supports assistants working from home, and synced with the animation studio’s NAS to complete the edit of Pigsy, winner of Best Animated Feature at the Golden Horse Awards.

 

AI Disclosure: Some images and text in this article were created or refined with the assistance of Artificial Intelligence (AI) and reviewed by human editors.

Leave a comment

Your email address will not be published. Required fields are marked *