> Any UniData Journaling users out there? > > We are considering using journaling as a way to keep a near real-time > backup of our primary system. We would be journaling > hundreds of files > on a system with over 1000 users. > > We have lots of questions, like: > Has anyone used journaling on that scale before? > How much of a performance hit is there with journaling? > Are there any options recommended, or to be avoided? > What tricks can we use to avoid any know problems? > > If anyone has any experiences or critiques to share, I would > appreciate them, either here or off list ( [EMAIL PROTECTED] ).
I've only ever looked at Journaling as a poor-man's RFS. In that capacity it really didn't cut the mustard. I have, however, successfully set up RFS for use in a DR scenario - archive logs regularly and automatically copied to a backup machine and replayed there automatically each morning via mediarec. This is running well at decent sized production site, but nothing like the user population you are talking about - 100 to 150 users, not 1000 like you have. In an ideal world, IBM would publish the format of the archive logs so one could write a tool to allow transactions to be picked out of these and replayed over to a remote system without stopping it and doing a mediarec rollforward, but with UniData having replication built-in using an entirely different approach, I doubt they'll ever allow that. Do you have version issues which would prevent you using replication for this purpose Dean, or have you identified issues that prevent it from working for you? Cheers, Ken ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
