Enabling the vol options nvfail option on a volume provides database file protection by detecting NVRAM failure at boot time.
If this option is enabled and problems are found, it warns database administrators of NVRAM problems by
You can provide additional protection to specific database LUNs by adding them to an optional file you create called /etc/nvfail_rename. When you enable nvfail and Data ONTAP detects NVRAM errors at bootup, Data ONTAP renames any database LUNs specified in the nvfail_rename file by appending .nvfail to the original name. When Data ONTAP renames a database LUN, the database cannot restart automatically. This gives you the opportunity to examine it for inconsistencies before you remove the .nvfail extension and make it accessible again.
LUNs accessed over CIFS, NFS or FCP can be entered in /etc/nvfail_rename. This causes a LUN rename upon boot after an NVRAM failure. This process is described in more detail in the NVRAM chapter of the Data ONTAP 6.4 System Administration Data Protection Guide.
Caution
NVRAM failure can lead to possible data inconsistencies. Upon a reboot after an NVRAM failure, all LUNs are taken offline and are no longer exported over FCP. You need to bring the LUNs online (and reexport) each LUN manually to the initiator after data recovery.
To enable the NVFAIL option on WAFL volumes, complete the following step.
| 1 |
vol options volume-name nvfail on |
To create the nvfail_rename file, complete the following steps.
Copyright © 1994-2003, Network Appliance, Inc. All rights
reserved.
Part No. 210-00570
File: c5data12.htm
Last updated: 09/03/03 17:13:53