TerraMaster Forum

I was recently experimenting with the snapshot app, not having used it under Tos7. Is it correct that:

a) when using the Duplicate function, Snapshot on the destination machine is disabled?

b) if a Duplicate task fails (due, possibly, to insufficient destination space) the task cannot be deleted?

c) if a Duplicate task fails, the destination Snapshot app remains disabled?

I solved an instance of (b) by editing the task so that it could be re-run to completion.
Is the "Duplicate" function a misnomer? I say this because it does not really Duplicate a snapshot (ie something that already exists). Rather, it "Replicates" a folder onto another space/device. In the (b) case above the folder was over 200GB and took consequent time to complete. I fully understand why this happens, but would also understand why some users might be confused.

Sometime later:
Early hours of morning Temp spike on destination machine (82C) and system volume out of space. Looks like media indexer has found some remnants of the broken Duplicate task (video files) and has been looping disasterously on them. stopping MMS and rebooting has reduced the temp and cleaning out the /homes recycle bin plus the /Volume1/@videoframe has cleared some space. But 'Others' in disk usage still is higher than it should be.
Waiting to see what else happens after another re-start!

Gremlin wrote: ↑21 Sep 2026, 15:52

Thank you for the update. To clarify the expected behavior of the Snapshot app:

• Destination App Status: Using the Duplicate function does not disable the Snapshot app on the destination machine.

• Task Deletion: Failed tasks can be deleted. However, note that a remote duplicate task can only be deleted from the initiating side (the source machine).

• Behavior on Failure: If a task fails, the Snapshot app itself will not be disabled; only the specific task will display an abnormal/failed status.

• Folder Data & Terminology: You are correct—the feature indeed replicates the entire folder's data, not merely the snapshots. Your observation and suggestion regarding the naming are very accurate, and we have noted this to optimize the terminology in future releases.

Regarding the high disk usage and the media indexer issue, please let us know how the system behaves after your reboot!

In which case;
something broke the destination Snapshot app. Had to install Snapshot on destination machine to allow 'Duplicate' to run on source. (it complained). I had to enable destination Snapshot likewise. Duplication task failed. Destination Snapshot app was disabled when checking. I did not disable it.

I definitely could not delete the source duplicate task. I tried several times. As stated the only way I could "fix" was to edit to new details (with local destination), allow it to succeed and then it could be deleted.

I could not find a way to list "Duplications" performed (even successful). [as in "snapshot list"].

It has taken a long time to try and resolve the high disk usage on destination. Had to delve into terminal mode and manually access the /var/.../@snapshot folders. Could not remove everything due to "read only file system" errors which I am still not clear on as they appear to be writable directories.

'AI' suggests media indexer was trying to index possible media fragments and started looping.
Maybe I should get a radio to kill the video ****

In any case, Why would Media indexing start operating on a newly generated folder system that is not included in list of indexable folders?