---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool application server
---------------------------------------------------------------------------
----- Original Message -----
From: "David Kerber" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Sunday, October 14, 2007 9:49 PM
Subject: Re: Copying large files around
Pid wrote:
Johnny Kewl wrote:
---------------------------------------------------------------------------
HARBOR: http://coolharbor.100free.com/index.htm
Now Tomcat is also a cool application server
---------------------------------------------------------------------------
----- Original Message ----- From: "David Kerber" <[EMAIL PROTECTED]>
To: "Tomcat Users List" <users@tomcat.apache.org>
Sent: Sunday, October 14, 2007 2:56 AM
Subject: Re: Copying large files around
If it Postgresql you using, a while a go I wrote a replication system
for
Postgres, and its a TC servlet. So what you could to is make a real time
back up, ie as one transaction happens on the main dB its replicated on
the
other and visa versa.... dB has to be designed for it, but they always
aligned.
If you interested, just yell.
If it was Postgres*, slaving it is possible and that is definitely more
efficient/safe.
p
* Apparently not, as 'cost' has been referred to and the OS is Windows,
which makes a commercial DB more likely.
Correct observation.
Yes... all true, question has come along way from what initialy looked like
a TC query, but yes if the user could consider replication and the required
dB design, much better than moving GB files around. For a newbie it may be a
little overwhelming and I just want to point out that there are many levels
of replication, Microsofts replication is not like Postgres's master - slave
replication, and thats a little different to my master - master replication
system as well.
If it is web based work that is generating these huge dB's... ie its TC that
is talking to the dB, and replication is not an option on this dB, I would
even look at something like a customized dB pool that duplicates
transactions to a backup dB... anything to avoid huge dB backups.
Then also, if it was postgres, and that was not possible.... even
considering incremental transaction logs would be better, ie backing up a
days work and not the whole dB... something like that... good luck.
D
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
