| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 849.1 | Probably issue between ARCServe and Cluster redirector | SUTRA::16.192.160.196::Bats | Speeding, speeding, I'm always speeding | Tue Jun 03 1997 03:18 | 8 | 
|  | 
	It could be that the ARCserve application has a problem with the Cluster 
	redirector. Why don't you apply the NT Cluster 1.1 SP1, so you can do away
	completely with the redirector, and use the normal Windows NT one?
	That should definitely put to bed these type of problems.
	Pjotrr
 | 
| 849.2 |  | MSE1::PCOTE | press one now for personal name | Tue Jun 03 1997 06:49 | 19 | 
|  | 
   To expand abit on .1
   Some customers have simply disabled the cluster file system driver
   from starting on the cluster servers. (control panel - devices - 
   cluster file system) This has eliminated various performance 
   issues with applications (on the servers) that are sensitive to
   timing issues when connecting to remote file shares or when
   conducting extensive remote file I/O. I believe that ARCServer 
   falls under this catagory. 
   The ramification is that you can not browse or connect to
   established cluster shares from the servers but this is generally
   something that the clients require, not the servers. 
   NT Cluster V1.1-SP1 now offers file share support via NetBIOS
   over TCP/IP (NetBT) which makes the cluster file system driver
   superfluous. (Providing of course that the clients are running
   TCP/IP as well)
 |