Nectere Amphora

01The app

The mock is clickable. Sidebar items open each panel with sample data, and most dialog buttons (+ Add Store, Log, Edit) open their dialogs. Dialogs close only from × or Cancel.

Users is admin-only. Array sign-on removes it and Sign Out, since Array handles accounts.

02How the pieces fit

A store is where data lives. A transfer says what to take from one store and where to put it; each time it executes, that's a run, with its own log. A schedule runs a transfer on a timer.

The usual order

1. Object Stores: add source and destination. Test each one.
2. Explore: find the source folder.
3. Transfers: create the transfer, check its file list with Test criteria, save.
4. Test the saved transfer, read the log, then press Transfer.
5. Schedules: add one if the transfer recurs.

03Getting Amphora

Deployed from Nectere Array under Menu › Deploy › Nectere Amphora. The sign-in mode is picked at deploy time. Updates, restarts and logs are on the back of the tile once it shows Running.

Sign-in modes

04Sign-in and setup

Array sign-on skips this and opens on the dashboard. With Application sign-in, a new tile shows Initial Setup to create the admin account, and Sign In from then on.

Array sign-on

An expired Array session can land you on Amphora's Sign In form. There are no local accounts to use there. Reopen the tile from Array.

05Sidebar and notifications

06Dashboard

Four counts and the ten most recent runs.

1. 1Counts. Object stores, active transfers (running or pending), completed and failed runs. Run counts cover the last 100 runs.
2. 2Recent Transfers. The ten newest runs, manual or scheduled.
3. 3Name. Scheduled runs get (scheduled) after the name. Test runs have (test) in it.
4. 4Log and Cancel. Cancel appears only while a run is going. A run that failed before starting shows the reason on a grey line below it.

07Object Stores

Each store has a name, a type and that type's connection settings. Search matches name, type, description and visible settings like endpoint or bucket, so minio and corp.lab both work.

An empty list reads No object stores yet. Click "+ Add Store" to start moving data. and hides the search box.

The store form

The form shows the fields for the selected type, and changing type clears it. Required fields have an orange *. Where there's an Authentication dropdown, only the chosen method's fields are saved: switching from account key to SAS URL drops the key.

Store types

With Bucket (or Container) blank, Explore opens on every bucket the key can see and transfer paths start with the bucket name. Set it and the store is that one bucket. Base path pins the store to a folder inside it.

A Local / Mounted Volume root path has to be a folder made available to Amphora. Ask whoever runs the Array host which ones exist.

Saving and testing

Save checks required fields and shows Name is required or Required: … listing what's missing. Test in the dialog saves first, then tests, and leaves the dialog open for fixes, so a failed test still leaves a saved store. Test on a row checks the saved settings.

08Explore

Nothing loads until you pick a store and press Explore. Folder tools stay disabled until then, and switching stores clears the view.

The mock opens on Lab MinIO. Folders, breadcrumbs, the ↰ .. row and checkboxes all work, and buttons that raise a browser prompt show it.

Folder tools and row buttons

Selections

Ticking items brings up a bar with the count. Download fetches each item separately, Delete removes them all after one confirmation, Clear unticks. Changing folder also clears the selection.

Move / Copy… opens New Transfer with the source store filled in. One ticked item becomes the source path. With several, the current folder is the source path and the items go into Include patterns, folders with /** appended.

09Transfers

Nothing moves until a transfer runs. If one of its stores was deleted, the source → destination line shows the store's id instead of its name (see Old NAS sweep).

The transfer editor

Source on the left, filters in the middle, destination on the right. A blank path means the top of the store. Unnamed transfers get the date and time, e.g. Transfer 2026-10-26 14:05.

Criteria filters

Every filled-in filter must match. Blank ones are ignored, and Everything turns them all off.

Patterns match the path relative to the source path. * stays inside one folder name and ** crosses folders, so *.log only matches top-level logs and **/*.log matches at any depth. Check include and exclude combinations with Test criteria.

Test criteria

Scans the source with the editor's current filters, saved or not, and lists matches without copying anything. Only the first 1,000 are listed; the transfer still handles all of them.

10Runs

The log updates live and follows the tail while scrolled to the bottom. Scroll up and it holds still. The Run dropdown lists every run of the transfer, newest first, as run or test with status and start time. Cancel run shows while the selected run is active.

Reading the log

• The first === line gives the run, mode, dry-run flag and criteria.
• Then one line per file: Copied (new), Copied (replaced existing), Deleted (move and sync), or Skipped copy as --dry-run is set in a test. ERROR lines name the file and the reason the store gave.
• Progress every 5 seconds: amount moved, percent, speed, time left.
• The last === line has the result, OK or FAILED (exit n), with counts like (212 copied, 212 deleted, 3 failed).

The window holds the last 500 lines. The audit trail under Logs has every file.

11Schedules

Each schedule runs one saved transfer. Its runs show in the transfer's log like any other.

A schedule whose transfer was deleted reads (deleted transfer) and skips every time it comes due. Delete it or point it at another transfer.

The schedule editor

Set either Every N minutes (5 or more) or …or daily at. If both are set, minutes win. The day buttons in the mock toggle.

12Logs

Application log records what users and schedules did. Audit trail (per-file) has a line for every file a transfer copied, deleted, skipped or failed on, tagged with the run id. Both show today's entries, last 400 lines. Auto-refresh reloads every 5 seconds.

Empty views read (empty), or (no audit entries today - run a transfer) for the audit trail. Both reset at midnight server time. The tile's Logs button in Array shows the same entries.

13Users

Application sign-in only. An admin can do everything. A user can do everything but this panel, which still includes adding stores, running transfers and deleting files.

14Things to know

• Test before Sync and Move. Sync deletes at the destination, Move at the source.
• Runs are snapshots. Editing a transfer doesn't change what past runs show.
• Re-running is safe. Unchanged files already at the destination are skipped, so a re-run after a failure or cancel only moves what's missing.
• Deleting a store doesn't check its transfers. They fail on their next run with Destination store … not found or Source store not found.
• Folders in buckets. Object stores have no real folders, so New Folder writes a hidden .amphora_keep file to hold one open. Amphora hides it. Other tools may not.
• Renaming a big folder is slow. Each object is copied to the new name and the old one deleted.
• Upload and Download go through the browser. Use a transfer for anything large.
• Two clocks. Daily times follow the server clock in the sidebar, usually UTC. Next run and Last run are shown in browser time and can look a few hours off.

15Troubleshooting