Bristol, United Kingdom

Joshua Peck

This inventor holds 1 USPTO granted patent. Top assignee: Hewlett Packard Enterprise Development LP. Active years: 2026.

IDiyas Innovation Intelligence. (2026). Inventor Profile: Joshua Peck. Retrieved from https://idiyas.com/inventor/joshua-peck-onl1n5td

Data source: USPTO (United States Patent and Trademark Office) public patent records. Weekly synchronization. How IDiyas builds this profile

Calculating rank

Average Co-Inventor Count = 1.0


Company Filing History:


Years Active: 2026

Loading Chart...
1 patent (USPTO):Explore Patents

Title: Joshua Peck: Inventor in Data Storage

Introduction

Joshua Peck is an inventor based in Bristol, Great Britain, associated with Hewlett Packard Enterprise Development LP. His work includes an invention addressing data integrity in deduplication storage systems.

Latest Patents

Peck is associated with 1 patent: “Snapshot Repair in a Deduplication Storage System.” The patent describes methods for repairing a corrupt data unit in a snapshot. The system identifies a manifest and container index associated with the corrupt unit, then searches candidate manifests for one with the strongest match to the original manifest. If the best-matching manifest does not reference the corrupt unit, the system can replace the corrupt reference with a reference to a non-corrupt data unit.

Career Highlights

Peck’s patent work focuses on storage-system reliability and snapshot repair. The described approach uses manifest comparisons to locate a suitable non-corrupt data unit for recovery.

Collaborations

The provided information names Jack Smith and Richard Phillip Mayo as Peck’s coworkers at Hewlett Packard Enterprise Development LP.

Conclusion

Joshua Peck’s patent describes a method for improving data integrity by repairing corrupt references in deduplicated storage snapshots.

Profile summary based on public USPTO records.
Data Sources: USPTO Patent Grant XML, Patent Center, EPO & CIPO • Normalized by IDiyas Innovation Graph. Methodology & provenance architecturePlease report any incorrect information to [email protected]
Loading…