The current ZFS configuration on server is: You need to backup the /data file system while the file system is active. Select the option that creates a full backup of the /data file system and stores…

Question

Exhibit

Options

• AMount -F nfs system: /backup / mnt
• BMount -F nfs systemB: /backup/mnt
• CZfs send pool1/data@Monday | ssh system zfs recv backup/monday
• DZfs snapshot pool1/data@Monday | ssh system zfs recv backup/monday

• A
  7% (2)
• B
  15% (4)
• C
  74% (20)
• D
  4% (1)

Explanation

zfs send pool1/data@Monday streams the snapshot data to stdout, and piping it through SSH to zfs recv backup/monday on the remote system writes that stream into the backup pool - this is exactly the ZFS native backup workflow for live, active filesystems.

Why the distractors fail:

• A & B use mount -F nfs, which mounts a remote NFS share as a local directory - that grants access to storage, not a backup of /data. Neither creates a copy of the data.
• D uses zfs snapshot, which only creates a local point-in-time snapshot and produces no stdout stream. You cannot pipe zfs snapshot output into zfs recv - there is nothing to receive.

Memory tip: Think "SEND streams, SNAPSHOT stays." zfs snapshot freezes data locally; zfs send is what actually moves that data across the wire. For remote backups, the pattern is always zfs send ... | ssh <host> zfs recv ....

No community discussion yet for this question.