zfs.resource.snapshot.clone =========================== Clone a ZFS snapshot to create a new filesystem or volume, of the type the snapshot was taken of. A validation error is raised when: - ``snapshot`` is not a snapshot path or ``dataset`` is one (``EINVAL``) - a property does not apply to the type of the clone, or its value is refused (``EINVAL``) - a user property name or value is invalid (``EINVAL``) - the source snapshot does not exist (``ENOENT``) - ``dataset`` already exists (``EEXIST``) - either path is a protected path (``EACCES``) A filesystem clone that cannot be mounted is kept, and the error names it. Examples: Clone a snapshot to a new dataset: .. code:: json {"snapshot": "tank/data@backup", "dataset": "tank/data_clone"} Clone with properties: .. code:: json { "snapshot": "tank/data@backup", "dataset": "tank/data_clone", "properties": {"compression": "lz4", "quota": "10G"}, "user_properties": {"org.truenas:origin": "backup"} } .. raw:: html
Clone parameters for cloning ZFS snapshots.
No Additional PropertiesSource snapshot path to clone (e.g., 'pool/dataset@snapshot').
Must be at least 1 characters long
Destination dataset path for the clone (e.g., 'pool/clone').
Must be at least 1 characters long
ZFS properties to set on the cloned dataset.
Each additional property must conform to the following schema