home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.databases
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!eff!world!edwards
- From: edwards@world.std.com (Jonathan Edwards)
- Subject: Re: Hot Standby DBMS's
- Message-ID: <BtpKqr.Kz1@world.std.com>
- Organization: IntraNet, Inc.
- References: <BtI4Bv.D8r@cup.hp.com> <BtI9KD.MAv@world.std.com> <1992Aug25.063147.2764@anasaz>
- Date: Fri, 28 Aug 1992 19:28:02 GMT
- Lines: 29
-
- In article <1992Aug25.063147.2764@anasaz> briand@anasaz (Brian Douglass) writes:
- >>As journal data is received and written at the remote system, it is
- >>asynchronously being recovered there, just like a normal journal (roll-forward)
- >>recovery. Thus the remote system can recover and take over in a few minutes
- >>from the production system.
- >
- >I think a difference lies in that while I suggest transactions
- >are processed as they are received on the remote system, Mr. Edwards system
- >seems to roll forward only upon primary failure, or I suppose nightly. If
- >I am wrong in this, please clarify.
- No, the remote system is recovering (rolling forward) on the fly.
- That's what the HOT in Remote Hot Standby means.
-
- >What type/size systems is this operation implemented on? If you can say.
- >Large Unix OLTP operations are still a rarity compared traditional mainframe
- >solutions, and I love to hear what others are doing.
-
- VAX/VMS - the whole size range. The database itself is written in VAX
- assembler and mostly runs in kernel mode to pull off some nice stuff.
- The basic code is 10 years old, though it has evolved considerably.
- By modern standards it is a white elephant, but will still blow the doors
- off anything else. But it seems the market is willing to buy 10 times as
- much hardware (literally!) in order to get a relational solution...
-
-
-
- --
- Jonathan Edwards edwards@intranet.com
- IntraNet, Inc 617-527-7020
-