Database protection using NVFAIL

The following section describes how Data ONTAP provides database protection using the nvfail option.

The nvfail option enables Data ONTAP to detect nonvolatile RAM (NVRAM) inconsistencies at boot time or while taking over in an active/active failover configuration. You use it to warn database administrators of NVRAM problems that can compromise database validity. If Data ONTAP finds any problems, database instances stop responding or shut down, and Data ONTAP sends error messages to the console to alert you to check the state of the database.

• How NVFAIL protects database files
  When booting up or while taking over in a failover configuration, Data ONTAP will either start the file service normally if there are no NVRAM errors or stop database instances from responding if NVRAM errors are detected.
• Enabling database file protection
  Use the nvfail option of the vol options command to configure Data ONTAP to find NVRAM problems, stop database instances from responding or shut down, and send error messages to the console to alert the database administrator to check the state of the database. The nvfail option detects NVRAM inconsistencies at boot time or while taking over in an active/active configuration failover.
• Adding additional database file protection
  In addition to protecting database files and LUNs using the nvfail option, you can have Data ONTAP rename database files and LUNs that you want protected. Renaming database files and LUNs prevent the database from restarting automatically and gives you an opportunity to examine the files for inconsistencies before clients can access them.
• Making LUNs accessible to the host after an NVRAM failure
  After an NVRAM failure, the host no longer has access to data on the LUNs. You must perform a number of actions before the database has access to the LUNs.