Hi Carl,
The TR-3322 that you mentioned in your email is a great start and has basic fundamentals of NFS protocol but it is rather an outdated one.
For the current and latest mount options recommendations, please refer to the following URLs - these options are well tested and have been validated with Oracle.
NetApp Database Portal FAQ available from the NOW site: http://now.netapp.com/NOW/knowledge/docs/bpg/db/oracle_faq.shtml
NOW site (recommended mount options): http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb7518
Oracle Metalink: metalink doc for mount options: -- note 359515.1
https://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_ database_id=NOT&p_id=359515.1
Regarding protocol performance comparison - please check out:
TR-3496: ORACLE 10g PERFORMANCE - PROTOCOL COMPARISON ON SUN SOLARIS http://www.netapp.com/library/tr/3496.pdf
Regarding more information on forcedirectio or llock on Solaris - please refer to: http://now.netapp.com/Knowledgebase/solutionarea.asp?id=kb6570
According to our experts: You should use DirectIO for the REDO Logs as it reduces CPU overhead on the host. There is no benefit by using llock and caching REDO Log IO. Bypassing the FS cache for REDO traffic is a good thing, especially for high SPARC CPU count systems and any AMD based systems even as of Solaris 10 U2. It has to do with CPU DTLB tear downs, etc. Using llock in addition to forcedirectio does not gain anything on Solaris, thus it's EITHER-OR.
We are also in the process of merging the content of TR-3322 with TR-3496 and we will remove TR-3322 from the web to avoid any further confusion.
Please let us know if you have any questions.
Thanks,
Shanthi Adloori Sr. Manager, Oracle Alliance Engineering 408.822.7828 | Network Appliance | shanthi@netapp.com
------------------------------------------------------------------------ -------- From: Sto Rage(c) [mailto:netbacker@gmail.com] Sent: Wednesday, May 02, 2007 11:31 AM To: Carl Howell Cc: toasters@mathworks.com Subject: Re: Solaris Oracle NFS mount options
Yeah, the Netapp documents are not consistent. This is what we have for our oracle mounts: nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,forcedirectio,l lock <<--- For all data files, redo logs and arch log volumes. and no forceddirectio for the Oracle binaries volume nfs 2 yes rw,bg,vers=3,proto=tcp,hard,intr,rsize=32768,wsize=32768,llock
Is this correct? It seems to be working OK for us now, we are yet to go into production though, its only a few developers working on the database. BTW, we are on Solaris 10. -G
On 5/2/07, Carl Howell chowell@uwf.edu wrote: In TR-3322 it says that the mount point for the redo logs should have the forcedirectio option on and the mount point for the data files should have it off. KB7518, which appears to be more recent, doesn't say anything about mount options for redo log volumes, but I assume you should have either forcedirectio or llock on both the mount points for your redo logs and data files. Is this correct?
Thanks,
- Carl
Hello all,
We are about to start testing Oracle 9i (single instance) with NetApp NAS (6070) filers. We currently have Oracle running on Solaris 9 with SAN storage attached and VERITAS.
We know that Oracle is supported on NAS, and we should have a great success potential. We also plan to synchronously mirror the data to another NAS system (R200). My question is following, can we put the database in a hot backup mode, then take a snapshot of the database file system. We will then break the mirroring, and start the database on another server that is mounting the database file system from the R200?
Any recommendations or suggestions are welcome.
Thanks.......
Hi,
we are allready running what you describe....Oracle 10 on SLES9 with FAS6070 in the background.
We have a script which puts the database into backup-mode and then creates a snapshot which is mirrored asynchronus onto a nearstore.
Nevertheless if your database has high randomload and suffers from high RTT than you will not be very lucky with running it on a nearstore but as a disaster-plan it is OK.
Best regards
Jochen
-----Original Message----- From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Hussain, Zaki H. Sent: Sunday, May 06, 2007 8:38 AM To: toasters@mathworks.com Subject: Oracle on NetApp NFS
Hello all,
We are about to start testing Oracle 9i (single instance) with NetApp NAS (6070) filers. We currently have Oracle running on Solaris 9 with SAN storage attached and VERITAS.
We know that Oracle is supported on NAS, and we should have a great success potential. We also plan to synchronously mirror the data to another NAS system (R200). My question is following, can we put the database in a hot backup mode, then take a snapshot of the database file system. We will then break the mirroring, and start the database on another server that is mounting the database file system from the R200?
Any recommendations or suggestions are welcome.
Thanks.......
Hello Zaki,
First of all you should carefully consider if you really want to synchronously mirror the data. Especially if the target of mirror is R200 with SATA disks. Such a configuration would introduce huge performance degradation as compared to unmirrored config, especially in terms of write latency and IOPS.
You have 2 options: 1. use FC-disk as target, performance impact will be lowered significantly This way you can avoid IOPS bottleneck of SATA drives 2. use semi-sync or async replication if your RPO (recovery point objective) allows it If properly designed can lower perf impact to +0 even with SATA as target
In any case you can put database in hot backup mode and take snapshots of all data volumes on primary system. When you should take snapshot of archive redo logs volume. In this case Oracle will recover database successfully on secondary site even if data files placed on different aggregates and/or FAS-systems. The only difference between 1 and 2 is how quickly this snap will pop out on secondary system. Also in sync mode you will get crash consistent copy (all committed transactions are in place) of data on secondary site in case of disaster, in async/semi-sync mode you will probably lose some recent transactions.
BR, Alexander.
Network Appliance Simplifying Data Management
Alexander Fakanov tel: +7 495 937 8791 Project Manager fax: +7 495 771 7149 mob: +7 495 765 8475
Regus Business Center,750 Smolenskaya Square,3 alexander.fakanov@netapp.com 121099 Moscow, Russia
-----Original Message----- From: Hussain, Zaki H. [mailto:zaki.hussain@aramco.com] Sent: Sunday, May 06, 2007 10:38 To: toasters@mathworks.com Subject: Oracle on NetApp NFS
Hello all,
We are about to start testing Oracle 9i (single instance) with NetApp NAS (6070) filers. We currently have Oracle running on Solaris 9 with SAN storage attached and VERITAS.
We know that Oracle is supported on NAS, and we should have a great success potential. We also plan to synchronously mirror the data to another NAS system (R200). My question is following, can we put the database in a hot backup mode, then take a snapshot of the database file system. We will then break the mirroring, and start the database on another server that is mounting the database file system from the R200?
Any recommendations or suggestions are welcome.
Thanks.......
-
Adloori, Shanthi -
Fakanov, Alexander -
Hussain, Zaki H. -
Willeke, Jochen