Restore a table through Stage with DUMP/LOAD TABLE

On the MatrixOne server, create a new, empty /tmp/mo-cookbook-dump directory and check that the service can write there. DUMP TABLE refuses to overwrite an existing full/manifest.json; use a fresh path when repeating the exercise. This is suitable for copying an experiment table; use the formal backup workflow for production recovery.

CREATE DATABASE cookbook_dump;
CREATE STAGE cookbook_dump_stage URL='file:///tmp/mo-cookbook-dump/';
CREATE TABLE cookbook_dump.src(id INT PRIMARY KEY, amount INT);
INSERT INTO cookbook_dump.src VALUES (1,10),(2,20);
SELECT mo_ctl('dn','flush','cookbook_dump.src');
CREATE TABLE cookbook_dump.dst(id INT PRIMARY KEY, amount INT);
DUMP TABLE cookbook_dump.src TO 'stage://cookbook_dump_stage/full';
LOAD TABLE cookbook_dump.dst FROM 'stage://cookbook_dump_stage/full';
SELECT COUNT(*) AS rows_restored, SUM(amount) AS amount_sum FROM cookbook_dump.dst;
DROP DATABASE cookbook_dump;
DROP STAGE cookbook_dump_stage;

Expect rows_restored=2 and amount_sum=30. The underlying files may remain after dropping the Stage; verify the experiment directory before removing them. See the source table export and restore test for metadata-only mode.