Store stores encrypted file data across its storage network. The service also keeps file records so your app can organize your files and find the data needed to retrieve them.
From upload to a usable copy
You choose a file in a supported Store app or the web app. Keep the original while you check the stored copy.
The service stores encrypted fragments across the network. Extra fragments help it reconstruct a file when enough valid data remains available.
File records connect the stored data to the files and folders shown in your account.
When you retrieve a file, Store needs the required data and valid access to rebuild a usable copy.
File contents and the information used to operate the service are different. For the current encryption and service-data explanation, read how encryption protects Store files.
Check the result with one file
Choose a small file whose contents you know and keep the original. Follow the first-file guide to upload it.
Check whether the upload finishes and the file appears in Store. Record any error.
Download a separate copy without overwriting the original, then open it in the app it needs.
Record three results: the file is listed, a separate copy downloads and that copy contains what you expect. If one fails, record the app, time and error for Support.
A filename in the list or a preview does not show that the complete file is usable. File-integrity checks explain how to check retrieved contents.
Keep separate copies
Distributed storage is not a substitute for another usable copy of important files. Use the backup test guide and keep working access while checking your files.
If you are offered a change to Protocol V2, keep working access and usable copies outside Hivenet. Ask Hivenet Support which process applies to your account and what it changes before agreeing to it.
Compute instances and S3 object storage follow different workflows. For the broader product distinction, read Understand Hivenet's distributed cloud.