--- [EMAIL PROTECTED] wrote:
> On Sat, Jun 30, 2001 at 10:21:35AM -0400, David Green wrote:
> > Sounds like more of a database-specific question than a JBoss
> question.
> > For instance, with Progress, I think it's possible to halt updates
> to the
> > actual database files, all updates are temporarily stored in .ai
> (after
> > image files), which can be applied after the backup is complete.
>
> I'm not sure how transactions are implemented in Java. I'm paranoid
> enough, however, to think that it is possible that a Java transaction
> implementation uses several DB-native transactions per one of its own
> transactions. If so, then attacking this only at the database level
> could result in a logically invalid backup database.
I think you're being overly paranoid in this case. If the backup
scheme that the DB uses cannot gaurantee that the database is complete,
then tere is a bug in the software. I know for a fact that Sybase,
Informix and Oracle do not have to have clients disconnected before
backiing them up. It's a good idea to do the backups during a slow
time becuase they drastically affect performance.
As for transactions interfering with the backup... That makes no sense
at all. A backup routine reads a row, and writes it. Just like every
other process/client. If you could interfere with that read, by having
a transaction in progress.. you have far more severe problems then a
corrupted database.
=====
Grim Shieldsson (James A Barrows)
Acting Chieftain of Clan StormWolf
Barbarian Freehold Alliance
Oppurtunity doesn't knock. It only presents itself after you kick down the door.
--Kyle Chandler
__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/
_______________________________________________
JBoss-user mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-user
