In message <4a4122b1....@gmail.com>, Steve Romanow
<slestak...@gmail.com> writes
Kevin Gusler wrote:
Steve -
Why do you think this?
"The failure I see of this system is that even though the db is paused, it
is not in a "safe" state for backup."
Once you broke the mirror would it not be safe to backup that array??
Kevin Gusler
Applications Developer
Mortgage Builder Software, Inc.
Main: 800.850.8060 ext. 106
Fax: 248.304.0601
www.mortgagebuilder.com
The db is basically in "mid sentence". The commits are not atomic. If
you restore to the tape, you may in my case have "half an order" or an
invoice half processed. the unidata dbpause does not make people get
out of maitnenance screens or release locks, so records can be in an
uncommitted state. Risk is small, but it is present.
_______________________________________________
But that's a programming issue. It's easy to do exactly the thing with a
SQL database. It's just that because pretty much EVERY write to a SQL
database will corrupt integrity until the transaction is complete, SQL
programmers use transactions as a matter of necessity. Because in MV
database writes have traditionally often been complete transactions, we
don't have the same mindset.
Cheers,
Wol
--
Anthony W. Youngman <pi...@thewolery.demon.co.uk>
'Yings, yow graley yin! Suz ae rikt dheu,' said the blue man, taking the
thimble. 'What *is* he?' said Magrat. 'They're gnomes,' said Nanny. The man
lowered the thimble. 'Pictsies!' Carpe Jugulum, Terry Pratchett 1998
Visit the MaVerick web-site - <http://www.maverick-dbms.org> Open Source Pick
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
