What should a solutions architect recommend?
Set up AWS Storage Gateway to connect with the backup applications using the NFS interface.
Set up an Amazon EFS file system that connects with the backup applications using the NFS interface.
Set up an Amazon EFS file system that connects with the backup applications using the iSCSI interface.
Set up AWS Storage Gateway to connect with the backup applications using the iSCSI-virtual tape library (VTL) interface.
Explanations:
AWS Storage Gateway using NFS does not provide a tape library solution, which is essential for retaining existing backup workflows that rely on tape. It is better suited for file-based applications rather than traditional backup solutions.
Amazon EFS can be used for file storage but does not support existing backup workflows that rely on tape-based solutions, and it may not seamlessly integrate with the backup applications that expect a block storage or tape library interface.
While Amazon EFS can be connected using the NFS interface, it does not support iSCSI, which is not applicable here. Furthermore, EFS is not designed for backup applications that require tape emulation, leading to compatibility issues.
AWS Storage Gateway using the iSCSI-VTL interface allows existing backup applications to continue using the tape backup workflows while leveraging cloud storage, preserving the company’s investment in current applications and simplifying infrastructure by eliminating physical tapes.
My best guess is:
Set up AWS Storage Gateway to connect with the backup applications using the iSCSI-virtual tape library (VTL) interface.
I reckon the answer is:
Set up AWS Storage Gateway to connect with the backup applications using the iSCSI-virtual tape library (VTL) interface.