Indexless Partial File Restore
Restore the clip you need.
Retrieve selected sections of your original media from cloud storage, network servers, or tape archives. Transfer less data, reduce restore times, and deliver a new clip ready for production.
Start with Indexless PFR, without preparing separate index files. Existing RTIN indexed workflows are fully supported.
| Windows, Windows Server |
|
| |
| Red Hat/CentOS or Ubuntu |
|
| |
| macOS 14 Sonoma - macOS 26 Tahoe |
|
| |
|
|
|
|
|
|
| |||
|
|
|
|
|
S3 and S3-compatible storage • HTTPS • FTP • Microsoft Azure • Google Cloud Storage • LTO and tape archives
- Indexless PFR
- The Challenge
- Capabilities
- PFR for S3
- PFR for Quantum
- Benefits
- How it Works
- Use Cases
- FAQ
- Videos
- Compare

Start with the media you already have.

Restore only the file or object you need — without full restore, index rebuild, catalog rebuild, or database overhead.
Indexless Partial File Restore lets you recover a single file, object, or byte range from large S3 and Quantum ActiveScale backups without restoring the entire dataset, rebuilding an index, rebuilding a catalog, or running a restore database.
Net-X-Code PFR is designed for S3-compatible object storage and Quantum ActiveScale environments where restoring a single file or object can be slow, expensive, or impractical. It allows you to restore a single file, object, or byte range from backup archives without the pain of restoring the entire bucket, rebuilding an index, or running a catalog/database restore process.
![]()
Why single-file restore is difficult in S3 and Quantum ActiveScale environments
Object storage environments are not traditional file systems. A bucket can contain millions of objects, prefixes, versions, metadata records, and retention rules. Restoring one file or object can become a major operation if the restore process requires:
-
Full dataset restore
- Index rebuild
- Catalog rebuild
- Restore database
- Backup server agent
- Full bucket restore
- Long restore windows
- Extra storage for temporary restore
- Performance impact on production storage
- Manual search through object metadata
- Compliance or legal-hold exposure
Restore only what you need, as fast as possible, without unnecessary overhead.
![]()
What Indexless Partial File Restore can do
-
Restore a single file from a large backup or archive.
- Restore a single object from S3-compatible object storage.
- Restore a single object from Quantum ActiveScale.
- Restore only the needed file or object, not the entire bucket.
- Restore partial files where supported by the backup format.
- Restore without full restore when only one file, object, or byte range is needed.
- Restore without rebuilding an index.
- Restore without rebuilding a catalog.
- Restore without a restore database or catalog database.
- Restore to the original location or to an alternate location.
- Restore to local storage, cloud storage, S3-compatible storage, Quantum ActiveScale, tape, archive, or disaster recovery target where supported.
- Use object metadata, version information, checksums, and backup archive records to locate and recover the needed file/object.
- Reduce restore time for single-file or single-object recovery.
- Reduce storage overhead by avoiding full restore operations.
- Reduce operational complexity by avoiding index/catalog/database restore workflows.
- Improve disaster recovery flexibility for single-file, single-object, legal-hold, audit, or corrupted-file scenarios.
![]()
Why Indexless Partial File Restore matters for S3
Amazon S3 and S3-compatible object storage are excellent for data lakes, archives, cold storage, compliance, retention, and hybrid cloud. But S3 restores can be inefficient when the customer needs to recover only one file or object.
Traditional backup restore tools often require:
-
- Full restore
- Catalog rebuild
- Index rebuild
- Restore database
- Backup server
- Agent-based restore
- Full bucket restore
- Temporary storage space
- Long restore windows
Indexless Partial File Restore is better suited for S3 environments because S3 already uses object metadata, bucket structure, prefixes, object names, versions, and retention policies. Instead of forcing a catalog/index/database model, the product can work with object metadata and backup archive records to restore only what is needed.
For S3 customers, the value is not “restore everything.” The value is “restore one file or object without restoring the whole bucket.”
![]()
Why Indexless Partial File Restore matters for Quantum ActiveScale
Quantum ActiveScale is commonly used for:
-
- S3-compatible object storage
- Erasure-coded storage
- Data lakes
- Active archives
- Hybrid cloud
- Immutable storage
- WORM retention
- Legal hold
- Compliance
- Disaster recovery
- Large-scale object storage
- Cold storage
- Long-term retention
Quantum ActiveScale customers often have very large object stores. Restoring a single file or object can be difficult if the backup tool requires a full restore, catalog rebuild, index rebuild, or database restore.
Indexless Partial File Restore is a strong fit for Quantum ActiveScale because it can reduce restore complexity:
-
- No full restore required for a single file/object recovery.
- No index rebuild required.
- No catalog rebuild required.
- No restore database required.
- No unnecessary temporary storage required.
- No performance impact from restoring the entire dataset.
- No long restore window for one file.
Quantum ActiveScale customers need a restore model that matches object storage — not a traditional file-system catalog model.
![]()
Benefits for S3 and Quantum ActiveScale customers
-
- Faster single-file restore
- Faster single-object restore
- Lower restore overhead
- Lower temporary storage requirements
- Lower storage cost
- Lower backup server impact
- Lower catalog/index storage
- Lower database overhead
- Lower risk of accidental full restore
- Lower operational complexity
- Better disaster recovery flexibility
- Better legal-hold and audit support
- Better compliance workflows
- Better performance for large object stores
- Better fit for S3-compatible storage
- Better fit for Quantum ActiveScale
![]()
How Indexless Partial File Restore works
Indexless Partial File Restore uses a straightforward series of steps:
-
- Backup or archive data is stored in an S3-compatible or Quantum ActiveScale environment.
- Object metadata and backup archive records identify the file, object, version, retention, or location.
- The restore process identifies only the needed file, object, or byte range.
- The product restores only what is needed, instead of restoring the entire bucket or dataset.
- The file/object can be restored to the original location, alternate location, cloud storage, local storage, tape, archive, or disaster recovery target where supported.
- No index, catalog, or database rebuild is required for the restore operation.
View the Explainer Video
![]()
Use cases
-
- Single corrupted file recovery
- Accidental deletion recovery
- Ransomware single-file recovery
- Legal-hold file recovery
- Audit file recovery
- Forensic evidence recovery
- Data lake single-object recovery
- Archive single-file recovery
- Cold storage single-file recovery
- Hybrid cloud single-file recovery
- Quantum ActiveScale single-object recovery
- S3 single-object recovery
- Tape archive single-file recovery
- Backup archive single-file recovery
- Version restore
- Byte-range restore
- Restore to alternate storage
- Restore to production storage
- Restore to disaster recovery storage
![]()
Frequently Asked Questions
What is indexless partial file restore?
Can I restore a single file from S3?
Can I restore a single object from Quantum ActiveScale?
Do I need an index or catalog to restore a single file?
Do I need to restore the whole bucket?
Can it restore partial files?
Is it compatible with S3-compatible object storage?
Is it compatible with Quantum ActiveScale?
Can it restore to an alternate location?
How much faster is single-file restore?
![]()
View the Explainer Video
![]()
Indexless Partial File Restore vs. traditional full restore
| Feature | Traditional full restore | Indexless Partial File Restore |
| Restore scope | Full dataset or full bucket | Single file, object, or byte range |
| Index required | Often yes | No index rebuild required |
| Catalog required | Often yes | No catalog rebuild required |
| Database required | Often yes | No restore database required |
| Full restore required | Often yes | No, when only one file/object is needed |
| Restore speed | Slower for large object stores | Faster for single-file/object recovery |
| Storage overhead | Higher | Lower |
| Backup server impact | Higher | Lower |
| Operational complexity | Higher | Lower |
| Best fit | Full restore workflows | Single-file/single-object recovery |
| S3 fit | Requires catalog/index/database model | Better fit for object metadata model |
| Quantum ActiveScale fit | May require full restore/catalog workflows | Better fit for object storage restore |
Quantum ActiveScale is great for storing objects. Indexless Partial File Restore is better for recovering only the object you need.
Net-X-Code API (includes PFR, Net-X-Convert, Net-X-Copy)
Trademarks, Registered Trademarks, and CopyrightsTrademarks, Registered Trademarks, and Copyrights
Amazon Web Services, Inc. - Amazon, AWS and Smile Logo, Powered by AWS Logo, AWS Co-Marketing Tools, the Partner Logo, the Program Marks, Amazon Web Services, AWS, AWS S3, and the names of AWS products, services, programs, and initiatives are trademarks or registered trademarks of Amazon Web Services, Inc.
Apple Inc. - Apple, the Apple logo, Final Cut, Final Cut Pro, Apple TV, iOS, iPad, iPhone, iPod touch, iTunes, Mac, Mac OS X, macOS, Shake, Final Cut Pro, ProRes, High Sierra, Mojave, M1, M2, and QuickTime are trademarks of Apple Inc., registered in the U.S. and other countries.
Avid Technology, Inc. - Avid Media Composer®, Avid MediaCentral®, Avid Interplay®, and Avid NewsCutter® are either trademarks or registered trademarks of Avid Technology, Inc. or its subsidiaries in the United States and/or other countries.
Blackmagic Design Pty. Ltd. - DaVinci Resolve, DaVinci Fusion, UltraStudio, DeckLink, Intensity Pro 4K, UltraScope, and RED are either trademarks or registered trademarks of Blackmagic Design Pty. Ltd. or its subsidiaries in the United States and/or other countries.
Drastic Technologies, Ltd. – trademarks specified here.
Evertz Technologies Limited - Evertz is a registered trademark of Evertz Technologies Limited
Google LLC – YouTube, Google, Google Cloud, Google.meet.com, and Android are registered trademarks of Google LLC
Grass Valley - Grass Valley®, GV®, the Grass Valley logo, and EDIUS® are trademarks or registered trademarks of Grass Valley USA, LLC, or its affiliated companies in the United States and other jurisdictions.
Harris Corporation - Harris, and Leitch Technology Corp. are registered trademarks of Harris Corporation
Kinefinity Inc. - KINEFINITY is a trademark of Kinefinity Inc.
Magic Lantern - Magic Lantern is a registered trademark of Magic Lantern
Microsoft Corporation – Microsoft: Windows®, Video For Windows (VFW), DirectShow, Microsoft, Skype, Microsoft Azure, Microsoft Teams, Wave Mapper, Microsoft, Windows NT|2000|XP|XP Professional|Server 2003|Server 2008 |Server 2012, Windows 7, Windows 8, Media Player, Media Encoder, Windows Defender, Microsoft Office, .Net, Internet Explorer, SQL Server 2005|2008|2012|2014, Windows Media Technologies and Internet Explorer are trademarks of Microsoft Corporation.
Red Hat, Inc. - Red Hat, and the Red Hat logo are trademarks or registered trademarks of Red Hat, Inc. or its subsidiaries in the United States and other countries
Sony Corporation – Sony, Sony DVD Architect, DVD, Catalyst, and Vegas are trademarks of Sony Corporation and/or its affiliates.
Tektronix, Inc. - Tektronix® and all identified Tektronix trademarks and logos are the property of Tektronix, Inc. or its wholly-owned subsidiaries
VideoLAN Non-profit Organization - VideoLAN, VLC, VLC media player and x264 are trademarks internationally registered by the VideoLAN non-profit organization
All other trademarks are the property of their respective owners.













