This is what the drill wrote down: the restore into a throwaway database, the tables counted, the row counts estimated from the restored catalogue, the timings, and the verdict. It is published as it was produced, unedited, so a bad run would read as badly here as a good one reads now. The one drill published so far was started by hand on 24 July 2026 at 21:40 UTC, which is why its timestamp is a Friday evening rather than the Sunday morning the timer is set for.
# nsfleet storage verify-restore — 28 July 2026 13:41 UTC — database identifiers removed [OK ] client database tables=495 rows~=39059 age=11.1h 6.3s [OK ] client database tables=435 rows~=27736 age=11.1h 4.9s [OK ] client database tables=444 rows~=28016 age=11.1h 4.6s [OK ] client database tables=467 rows~=29526 age=11.1h 4.7s [OK ] client database tables=445 rows~=28825 age=11.1h 4.5s [OK ] client database tables=482 rows~=30348 age=11.1h 4.5s [OK ] client database tables=436 rows~=27276 age=11.1h 4.2s [OK ] client database tables=433 rows~=30786 age=11.1h 4.4s [OK ] client database tables=434 rows~=27089 age=11.1h 4.4s [OK ] client database tables=409 rows~=25510 age=11.1h 3.9s [OK ] client database tables=399 rows~=25092 age=11.1h 3.9s [OK ] client database tables=505 rows~=32296 age=11.1h 5.0s [OK ] client database tables=636 rows~=252102 age=11.1h 11.6s [OK ] client database tables=403 rows~=25576 age=11.1h 4.3s [OK ] client database tables=411 rows~=26053 age=11.1h 4.0s [OK ] client database tables=1021 rows~=65647 age=11.1h 10.8s restore-drill: tested=16 failed=0 stale=0
The free recoverability review restores an export you send us on a throwaway database and gives you this kind of log about your own data. No charge, and no follow-up call unless you ask for one.