Easy ReviewDOP-C02
SDLC Automation9

FSx for NetApp ONTAP

Use managed ONTAP storage with multiple protocols, availability options and replication.

Este conteúdo de estudo ainda não foi traduzido, então aparece em inglês. Ajude a traduzir

Multiprotocol storage and availability

Amazon FSx for NetApp ONTAP provides managed shared storage for applications that need NetApp features and multiple access protocols. A volumeAn isolated container for files, directories or iSCSI storage units. is an isolated container for files, directories or block storage units.

How it works

  1. Choose Single-AZ or Multi-AZ. Both use active and standby file servers. Single-AZ keeps them in one Availability Zone; Multi-AZ places them in different zones and synchronously replicates writes.
  2. Create volumes for the data.
  3. Use Network File SystemA protocol for accessing shared files over a network. (NFS) or Server Message BlockA protocol for accessing shared files over a network. (SMB) for file access; both can access the same volume at once. Internet Small Computer Systems InterfaceA protocol for accessing shared block storage over a network. (iSCSI) and NVMe over TCP provide block access, where clients see storage devices rather than shared files.
  4. When a server fails, FSx automatically promotes the standby. NFS and SMB clients retain the endpoint IP; iSCSI and NVMe clients need multipathingUsing multiple client paths to storage servers so a client can switch paths on failure., meaning multiple client paths to the servers, for transparent failover.
  5. For a separate disaster recovery copy, schedule NetApp SnapMirror volume replication to another file system, including in another Region.
Access or storage choice Use
SSD Sub-millisecond file-operation latency.
Capacity poolAn elastic storage tier for data that can tolerate higher latency than SSD storage. Lower-cost tier with latency of tens of milliseconds.
SnapMirror Scheduled volume replication to another ONTAP file system.

Exam cues

  • If the question says Windows and Linux clients need shared SMB and NFS access across zones, think Multi-AZ FSx for ONTAP, because it supports both protocols and replicates writes across zones.
  • If the question says recover a volume in another Region, think SnapMirror, because it schedules cross-Region volume replication.

Remember

  • Failover typically completes in less than 60 seconds.
  • iSCSI supports file systems with up to six high-availability pairs; NVMe over TCP also requires a second-generation file system.

Trap: Multi-AZ synchronous replication is within one Region. It is not synchronous cross-Region SnapMirror replication.

Multi-AZ storage and failover
Availability Zone AAvailability Zone B12ClientActive serverStandby server
  1. The client accesses data through the storage virtual machine endpoint.

  2. Writes are synchronously replicated to the standby in another Availability Zone; FSx fails over to it if needed.

Da documentação da AWS (16)
  • FSx for NetApp ONTAP is a managed shared file storage service based on the NetApp ONTAP file system.
  • FSx for ONTAP supports NFS and SMB file access and iSCSI and NVMe over TCP block access.
  • iSCSI is available on file systems with six or fewer high-availability pairs; NVMe over TCP requires a second-generation file system with six or fewer pairs.
  • FSx for ONTAP supports concurrent NFS and SMB access to the same volume.
  • A volume is an isolated container for files, directories or iSCSI storage units; its junction path is its location in the storage virtual machine file tree.
  • Single-AZ deployments place active and standby file servers in separate fault domains within one Availability Zone and replicate data within that zone.
  • Multi-AZ deployments place standby and active servers in different Availability Zones in the same Region and synchronously replicate writes across them.
  • Single-AZ and Multi-AZ deployments automatically fail over to standby; failover typically completes in less than 60 seconds.
  • NFS and SMB failovers are transparent because the endpoint IP remains the same; transparent iSCSI and NVMe over TCP failover requires client multipathing.
  • Single-AZ NFS, SMB and management endpoints can be accessed using VPC peering, Direct Connect or Site-to-Site VPN without requiring Transit Gateway.
  • SSD storage provides sub-millisecond file-operation latency; capacity pool storage has latency of tens of milliseconds.
  • FSx for ONTAP can automatically tier infrequently accessed data to a lower-cost storage tier.
  • FSx for ONTAP supports snapshots, clones and replication.
  • NetApp SnapMirror schedules volume replication to or from another file system in the same Region or a different Region, as frequently as every five minutes.
  • FSx for ONTAP supports volume-level SnapMirror but not synchronous SnapMirror or storage virtual machine disaster recovery replication.
  • FSx for OpenZFS supports NFS, snapshots and clones, and can move ZFS or Linux file server data to AWS.

Client access and replication

Amazon FSx for NetApp ONTAP uses storage virtual machines (SVMs) to provide Network File SystemA protocol for accessing shared files over a network. (NFS) and Server Message BlockA protocol for accessing shared files over a network. (SMB) endpoints for volumeAn isolated container for files, directories or iSCSI storage units. access. NetApp SnapMirror provides scheduled volume replication to another file system. Client access | SnapMirror replication

How it works

  1. For a client in the same virtual private cloud (VPC) and account, mount the volume using the SVMA virtual storage server with endpoints used to access and manage its data. DNS name and the volume junction for NFS or the SMB share for SMB.
  2. For NFS, SMB or management access from a peered network to a Multi-AZ file system, use AWS Transit Gateway unless using a documented cache alternative. These endpoints use floating IP addresses.
  3. Schedule SnapMirror volume replication to or from another file system in the same Region or another Region. FSx for ONTAP supports volume-level replication, while synchronous SnapMirror and SVM disaster recovery replication are unsupported.

Exam cues

  • If the question says an EC2 client in the same VPC and account needs to mount a volume, think SVM DNS name plus the NFS junction or SMB share, because these identify the endpoint and volume access path.
  • If the question says a peered VPC needs NFS access to a Multi-AZ file system without a cache, think Transit Gateway, because the NFS endpoint uses a floating IP address.
  • If the question says replicate a volume across Regions, think scheduled SnapMirror volume replication, because FSx for ONTAP supports it between Regions.

Remember

  • SnapMirror replication can run as often as every five minutes.
  • Synchronous SnapMirror and SVM disaster recovery replication are unsupported.

Trap: A cross-Region SnapMirror schedule does not provide synchronous replication. FSx for ONTAP supports scheduled volume-level replication.

Da documentação da AWS (5)
  • A storage virtual machine provides NFS and SMB endpoints for clients to access its volumes.
  • A client in the same VPC and account can mount a volume using the storage virtual machine DNS name and the volume junction or SMB share.
  • FSx for ONTAP supports volume-level SnapMirror but not synchronous SnapMirror or storage virtual machine disaster recovery replication.
  • NetApp SnapMirror schedules volume replication to or from another file system in the same Region or a different Region, as frequently as every five minutes.
  • Multi-AZ NFS, SMB and management endpoints use floating IP addresses and external peered networks require Transit Gateway unless using the documented cache alternatives.

Flashcards

toque para virar
Resposta

·

Todos os 9 flashcards em lista

When should a team choose FSx for NetApp ONTAP or FSx for OpenZFS?

Choose ONTAP for NFS, SMB and iSCSI access and NetApp features. Choose OpenZFS for NFS storage with OpenZFS snapshots and clones.

An application needs shared SMB and NFS access to storage across Availability Zones. Which FSx for NetApp ONTAP deployment fits?

Multi-AZ. It supports both protocols and synchronously replicates writes to a standby server in another Availability Zone.

What latency should a team expect from FSx for NetApp ONTAP SSD storage and capacity pool storage?

SSD file operations have sub-millisecond latency; capacity pool storage has tens of milliseconds of latency.

A team needs cross-Region disaster recovery for an FSx for NetApp ONTAP volume. Which replication feature should it use?

NetApp SnapMirror volume replication. It can schedule replication to a file system in another Region.

What happens when an FSx for NetApp ONTAP Multi-AZ active file server fails?

FSx automatically fails over to the standby. Failover typically completes in less than 60 seconds.

What must an iSCSI client configure for transparent failover on FSx for NetApp ONTAP?

Client-side multipathing, so the client can switch between file servers.

How does an EC2 client in the same VPC and account mount an FSx for NetApp ONTAP volume over NFS or SMB?

Use the storage virtual machine DNS name and the volume junction for NFS or the SMB share for SMB.

Does FSx for NetApp ONTAP support synchronous SnapMirror replication between Regions?

No. Synchronous SnapMirror is not supported. Use scheduled volume-level replication.

A client in a peered VPC needs NFS access to an FSx for NetApp ONTAP Multi-AZ file system without a cache. What routing component is required?

AWS Transit Gateway, because Multi-AZ NFS endpoints use floating IP addresses.

Você concluiu todos os tópicos da DOP-C02!

Seu badge ficou dourado. Próximo passo: agendar a prova na AWS. Depois de passar, adicione-se ao Quem passou.

Compartilhar

Conte que você concluiu esta certificação

Concluí todos os tópicos da AWS Certified DevOps Engineer - Professional (DOP-C02) no Easy Review. Venha estudar também!