We are working with a client installing a SAN. Our UniData database is up and running on SAN - quite peppy. We are using dbpause/dbresume to do snapshots every 30 minutes on the database. Less than 10 seconds to generate the snapshot! UniData doesn't even 'know' that the files are not attached to the local "D" drives any longer - that "D" drive is now an iSCSI attachment to a SAN drive across a gigibit connection. So the move to the SAN was transparent - not even a VOC pointer had to be touched. VERY cool.
Next database up is the UniVerse machine's files. But there is no 'dbpause' in UniVerse (that I can find) -- how do we accomplish the same thing in UniVerse we do in UniData with dbpause/dbresume - that is, stop/pause writes to the database (albeit in a potentially incomplete state) so that we can snapshot the disk and then resume the writes? Thanks for any hints here! David Wolverton ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
