ADIC 1.3 Operating System, Description, Component Affected, Click Configure drives independently

Operating System/		Description
Component Affected
Solaris	On Solaris, by default, the /usr/lib/fs/nfs/nfsfind script is run
	nightly by the cron daemon. This script contains a find command that
	traverses any local file system that is exported (shared) via NFS. If the
	running of this script is interfering with the performance of processes
	accessing StorNext file systems, it can be modified to skip them. To do so,
	add the following line to the find command in the script:
	'(' -type d -fstype cvfs -prune ')' -o
	The final find command should look like this:
	find $dir '(' -type d -fstype cvfs -prune ')' -o -type f
	-name .nfs\* -mtime +7 -mount -exec rm -f {} \;
Windows	Windows-based SNFS clients do not support symbolic links that point to a
	file system outside of SNFS. Symbolic links are created either by a UNIX/
	Linux client or by a Windows client (and are referred to as junctions).
	If you are using the StorNext client software with Windows 2000, Windows
	Server 2003, or Windows XP, turn off the Recycle Bin in the StorNext file
	systems mapped on the Windows machine, so the file systems will work
	properly.
	1	On the Windows client machine, right-click the Recycle Bin icon on your
		desktop and click Properties.
	2	Click Global.
	3	Click Configure drives independently.
	4 Click Local Disk onto which you have mapped StorNext.
	5	Select the Do not move files to the Recycle Bin. Remove files
		immediately when deleted check box.
	6	Click Apply and OK.
Windows	Virus-checking software, such as McAfee Virus Scan, can severely
	degrade SNFS performance. If you have anti-virus software running on
	your Windows 2000/Windows Server 2003/Windows XP machines, ADIC
	recommends you configure the software so that it does NOT check SNFS.
All	Hot re-zoning of SAN fabrics is not supported.
	StorNext is incompatible with CXFS.
	StorNext File System is incompatible with third-party portmappers.

April 2006, ADIC 19