We currently have Arev 3.12 running on a W2K server with the 1.5 Service installed. We've been in great shape for a long time like this, with the exception of occasional disk space cramps.

Since it isn't broken , the IT group wants to move us to a SAN they have purchased. I wondered if there were any issues involved in running Arev applications on a SAN?

Don't know if I have the terminology right, but they tell me that there will be two SAN "heads"; one primary and the other for failover. They will have a "virtual server" name that we will use for mapping drives, and that will point to the currently active SAN "head".

My uninformed gut feel is that we should be able to install the service on the SAN heads and operate normally as we have in the past. I wouldn't think there would be any "physical" service license contention problems since the SAN heads won't be operating (servicing users) simultaneously. There may be a "legal" licensing issue and we will check in with Revelation Software if we find that we won't have any operational problems with this configuration.

Thanks for any advice, input, warnings, requests for more info, etc. you might be able to offer.

Jim

Well, never got any responses. We winged it anyway (after testing as best we could), and have been running for 4 days now.

So far, no problems, GFE's, etc. (vigorously knocking on wood). I/O has vastly improved. No problem entries in the log from the LH service.

Hope we're not living on borrowed time…

Jim

View this thread on the forum...