What security mechanism can an administrator use on an OSSV client to set permissions allowing backups to a SnapVault secondary system?

• A. Via /etc/hosts.equiv file
• B. QSM access list modifiable via svconfigurator
• C. Contents inside a file called access and located in OSSV /snapvault/etc
• D. MD5 based authentication between SnapVault primary and secondary, with changeable password

Answer: (B)

The important concept is that OSSV on a client uses a QSM access list to control which SnapVault primary systems are allowed to back up to that client and onward to the secondary. This access list is managed on the OSSV host with the svconfigurator tool, which lets you add or remove authorized SnapVault primaries. This client-side permission model is the mechanism that governs backups to the SnapVault secondary.

The other options don’t fit this mechanism: /etc/hosts.equiv is a generic Unix trust file not used for OSSV/SnapVault backup authorization; a file named access in the OSSV directory isn’t the documented configuration for this purpose; and MD5-based authentication between the SnapVault primary and secondary pertains to authentication between the NetApp systems themselves rather than permissions configured on the OSSV client.