File links, copy-on-write clones and independent movie backups
Two visible paths do not always represent two independent media copies. Hard links can refer to the same underlying file, while symbolic links, aliases or directory junctions can refer to another location. Copy-on-write clones have another sharing arrangement. Identify those relationships before editing a supposed duplicate or counting it as an off-device backup.
Open the relevant downloader · Platform tools and access limits
Determine whether a path contains media or references it
Inspect the source and intended receiving paths using the filesystem’s supported information tools. For a hard-link investigation, compare file identity within its device or volume rather than assuming equal inode numbers across unrelated filesystems prove anything. Changes to a shared hard-linked file can affect the content reached through its other names.
A symbolic link, Finder alias or directory junction has a reference role rather than being an ordinary independent copy of every target movie. Their resolution behavior and supported scope differ. Determine the actual target and whether it remains available before treating a tiny reference artifact as archived audiovisual bytes.
Review how the chosen backup handles each relationship
Check whether a copy operation follows a link, preserves a reference or copies the target resources. For a directory reference, keep the traversal scope deliberate so it does not unexpectedly include an unrelated library or private folder. Do not infer behavior solely from two similar folder icons.
Where supported, a copy-on-write clone can have separate logical file identity while initially sharing data blocks. That is not the same mutation arrangement as a hard link, but it is also not proof of an independent storage device. Verify the actual copy method and failure boundary instead of counting displayed file sizes as independent physical protection.
Verify a recoverable copy without modifying originals
Open the intended saved movie at its verified destination and check content, duration and companions. Record whether it depends on another path, account or storage device. If the task requires an independent backup, verify a copy in the intended separate recovery location and keep the original during that test.
Do not overwrite a hard-linked supposed duplicate as an experiment on your only retained source. Use supported inspection and a separate safe copy. A reference that stops resolving after its target moves needs a dependency investigation; changing a video extension or re-encoding the alias cannot create missing target bytes.
Worked example
An editor sees two hard-linked movie names and plans to overwrite one as a separate working copy. Inspection shows that both names reference the same underlying file. The editor makes an appropriate separate derivative first. A clone that shares blocks under copy-on-write is evaluated differently, and neither same-device arrangement is advertised as an independently recoverable off-device backup.
Related guidance
Sources and verification
Reviewed 2026-10-12. Product behavior is limited to available source formats and provider access; it is not a promise that every public link works.