Easy ReviewDOP-C02
SDLC Automation9

FSx for OpenZFS

Managed NFS file storage with OpenZFS snapshots, clones, and backup options.

FSx for OpenZFS provides shared file storage with point-in-time snapshots and writable copies for recovery and testing.

NFS, snapshots, and clones

Amazon FSx for OpenZFS provides managed shared file storage for clients using Network File SystemA protocol that lets clients access files over a network. (NFS), a protocol for accessing files over a network. It supports point-in-time snapshotsA read-only image of a volume at a point in time. and writable copies of a dataset.

How it works

  1. Create a file system and volume, a named portion of its storage. Clients mount the volume through NFS; volume export settings determine which clients can access it and with what permissions.
  2. Take a snapshot, a read-only image of the volume at a point in time. It stays on the file system and uses capacity for changed portions of files.
  3. Create a cloneA writable volume initialized from and dependent on a snapshot. from a snapshot for an almost immediate writable copy. It initially consumes no additional capacity.
  4. Use backups for a separate backup copy, including copies across Regions. Choose Multi-AZ when failover across Availability Zones is required.

Exam cues

  • If the question says a test needs a quick writable copy, think clone, because it starts from a snapshot without initially using additional capacity.
  • If the question says preserve a copy in another Region, think cross-Region backup copy, because snapshots are local to the file system.
  • If the question says failover across Availability Zones, think Multi-AZ, because Single-AZ HA keeps its primary and standby in one zone.

Remember

  • NFS versions 3, 4.0, 4.1, and 4.2 are supported.
  • Multi-AZ replicates across Availability Zones; Single-AZ HA keeps its primary and standby in one zone.
  • A snapshot is read-only; a clone is writable and initially consumes no additional capacity.

Trap: A snapshot is not a cross-Region backup. It is stored on the same file system.

From the AWS docs (6)
  • FSx for OpenZFS provides managed file storage accessible using NFS versions 3, 4.0, 4.1, and 4.2 from Linux, Windows, and macOS clients.
  • Each volume has NFS exports that specify permitted clients and their access options.
  • A snapshot is a read-only point-in-time image of a volume, stored on the file system, that consumes capacity for changed file portions.
  • A clone is a writable volume initialized from a snapshot; it is created almost instantly and initially consumes no additional capacity.
  • FSx backups are stored in S3 and support cross-Region backup copies, while snapshots are stored locally on the file system.
  • Multi-AZ file systems replicate data and support failover across Availability Zones in the same Region; Single-AZ HA uses a primary and standby in one Availability Zone.

Snapshot recovery and volume capacity

Amazon FSx for OpenZFS supports snapshot-based volume copies and individual file recovery. Copy type determines whether the new volume depends on the snapshotA read-only image of a volume at a point in time.; capacity settings determine whether space is limited or guaranteed.

How it works

  1. A cloneA writable volume initialized from and dependent on a snapshot. depends on its source snapshot. The snapshot cannot be deleted while the clone is in use. A full-copy volumeA volume copied from a snapshot without an ongoing dependency on that snapshot. is independent and writable, but takes longer to create than a clone.
  2. While snapshot data is being copied to a full-copy volume, the volume is read-only.
  3. To restore an individual file, a client copies it from the hidden .zfs/snapshot directory. The volume’s NFS exportsA volume setting that determines which clients can access it and their NFS options. must include crossmnt.
  4. A volume quotaA limit on the amount of storage a volume can use. limits capacity, while a reservationA specified amount of storage guaranteed to a volume. guarantees space for the volume.

Exam cues

  • If the question says a writable copy must be independent of its snapshot, think full-copy volume, because a clone depends on its source snapshot.
  • If the question says restore one file, think .zfs/snapshot, because a client can copy the file from that directory when the NFS exports include crossmnt.
  • If the question says a volume needs guaranteed space, think reservation, because a quota only limits capacity.

Remember

  • A full-copy volume is read-only while its data is copied.
  • A source snapshot cannot be deleted while a dependent clone is in use.
  • A quota does not guarantee space; a reservation does.

Trap: A full-copy volume is independent of its source snapshot, but it is not writable during the copy.

From the AWS docs (5)
  • A clone depends on its source snapshot, which cannot be deleted while the clone is in use.
  • A full-copy volume is an independent writable copy of a snapshot; copying the data takes longer than creating a clone.
  • A full-copy volume is read-only while its data is being copied.
  • Clients can restore individual files by copying them from the hidden .zfs/snapshot directory; the volume's NFS exports must include crossmnt.
  • A volume quota limits capacity but does not guarantee space; a reservation guarantees space for the volume.

Flashcards

tap to flip
Answer

·

All 9 cards as a list

Which managed file service provides OpenZFS features and NFS access on AWS?

Amazon FSx for OpenZFS. It supports NFS access and OpenZFS snapshots and clones.

What is an Amazon FSx for OpenZFS snapshot?

A read-only point-in-time image of a volume, stored on its file system.

A team needs an almost immediate writable copy of an FSx for OpenZFS dataset for testing. What should it create?

Create a clone volume from a snapshot. It initially consumes no additional capacity.

A team needs an FSx for OpenZFS backup copy in another AWS Region. Are local snapshots sufficient?

No. Use a cross-Region backup copy; snapshots are stored locally on the file system.

A team needs FSx for OpenZFS to fail over across Availability Zones. Which deployment should it choose?

Multi-AZ. Single-AZ HA keeps its primary and standby in one Availability Zone.

Can a team delete an FSx for OpenZFS snapshot while a clone that depends on it is in use?

No. The clone depends on its source snapshot.

A team needs a writable FSx for OpenZFS volume that is independent of its source snapshot. What should it create?

A full-copy volume. It is read-only while the snapshot data is copied.

How can a client restore one file from an FSx for OpenZFS snapshot?

Copy it from the hidden .zfs/snapshot directory. The volume's NFS exports must include crossmnt.

Does an FSx for OpenZFS volume quota guarantee that the volume has that much space available?

No. A quota sets a limit; a reservation guarantees space.

You finished every topic of DOP-C02!

Your badge turned gold. Next step: book the exam on AWS. Once you pass, add yourself to Who passed.

Share

Share that you finished this certification

I finished every topic of AWS Certified DevOps Engineer - Professional (DOP-C02) on Easy Review. Come study too!