We have customers running UniData on a SAN and very pleased with the
results. The snapshotting really isn't as practical as they'd have you
believe was probably the biggest negative surprise - their users were
unwilling to deal with a 15-30 second 'DBPAUSE' more than once or twice a
day, so the id
Well, this would be a not-so-good way to go.
The big sticking point in this particular scenario is that you're sharing
the SAN. I know, that's part of the point of having one. But what happens is
that UniVerse is requesting relatively small I/O from the OS, typically 4,
8, or 16K per request, and
tting Universe on a SAN
re SAN's and Universe:
DELETE.FILE and RESIZE.FILE will not work on dynamic files that are
NFS mounted. (Universe keeps the DATA.30 file open while trying to
delete the enclosing directory. This will fail on an nfs mounted
directory.) Override the VOC entry wit
re SAN's and Universe:
DELETE.FILE and RESIZE.FILE will not work on dynamic files that are
NFS mounted. (Universe keeps the DATA.30 file open while trying to
delete the enclosing directory. This will fail on an nfs mounted
directory.) Override the VOC entry with your own version.
Do not
