Posted by Jim Guerber on October 25, 2010 at 08:34:42:
I wanted to post this email from Richard Neer about his testing of Comet Connectivity to NAS boxes using iSCSI. As you may be aware, simple NAS boxes using networking connections have not been usable. This is the solution to that problem.
Jim
Here is the message from Rich:
Hi Jim & Barb,
I just wanted to let you know that my test was successful. Until now, the Comet file system directories could only be installed on any local (unmapped) drive of the file server. As I suspected, the appropriate configuration and implementation of a business-class NAS connected via iSCSI on the network should be perceived by the Comet file system as a local drive since that is how the OS sees it. Via iSCSI, this appears to work flawlessly so far. Response time is superb. I've copied whole directories via Comet Explorer from one location on a local physical drive into a directory on the NAS connected via iSCSI in the blink of an eye. Bear in mind, I'm using a true high-end commercial NAS, not some cheap unit you can pick up at Best Buy. Those don't even have the software capability to support iSCSI, much less the processing power and memory to handle the throughput appropriately. The server has dual gig-nics, as does the NAS, configured as load-balanced. Both are connected via a gig switch. I did need to tweak some settings on the server to get rid of some pesky errors relating to the iSCSI timeout and the connection dropping, but all appears to be running like a raped ape now.
My next set of tests will be to see if I can have offsite live data on a NAS in my office connected to the client's network thru a dedicated VPN and connected to their server via iSCSI. I suspect the data access will meet some potential delay, but I can't surmise to what extent. It will only be impacted by the throughput of our respective internet connections (T1's). If this works, it will allow my office to be an offsite backup of their data by simply copying from one Comet directory at their site to one at my location, accessed simply by the directories configured in Comet on their local server, with the ones physically located in my office connected via iSCSI.
This really opens up possibilities for storing/accessing Comet data on other physical devices in other physical locations other than the limited local server drives only. (You're sure this is OK with you, licensing-wise, right?) This has been an obstacle for years, with really now way around it. I can't believe I'm the only one who thought enough about this to actually attempt to implement it successfully. Hopefully others will notice my post on the forum and try it as a solution to some of their data storage problems.
I wish I could've made it to the conference this year, specially with this new solution under my belt. It would have been a good item to present. Perhaps you could mention it for me on my behalf. I'm stuck here working on a complete network upgrade and implementation of a new multi-state VoIP phone system for my largest client, for which this testing and solution is for. Hold a conference in Chicago next time and I'll definitely be there. It's been too long!
I'll keep you posted of my progress.
Each file can be a maximum of 1MB in length Uploaded files will be purged from the server on a regular basis.