Saving database / Replication

BenjaminTheBlue

Registered User.
Local time
Today, 04:36
Joined
Dec 14, 2006
Messages
14
Hi there,

Would anyone know an easy way to save a database to 2 different places automatically when shut down.

Regards Ben
 
Do you mean when the application shuts down or the computer?
Do you *really* want replication?
 
Reply

Yes Just when the database shuts down or it is saved. I need to save it to 2 different domains for contingency purposes, but dont know if it can be done without complicated code. Sory I dont mean a whole new database to be created, just save any amendments to copy 1 and copy 2. Thanks in advance Andy
 
Yes Just when the database shuts down or it is saved. I need to save it to 2 different domains for contingency purposes, but dont know if it can be done without complicated code. Sory I dont mean a whole new database to be created, just save any amendments to copy 1 and copy 2.

It's not clear what you mean by "to 2 different domains." Is the other domain accessible via SMB networking, or only across the Internet? If SMB, is it on the local LAN or across a WAN/VPN? If it's on the LAN, then you could use Jet replication (assuming your back end is Jet, and not SQL Server) very easily, with very little code. I have some clients with replicated apps where they synch with a backup replica every time they shut down the app. But that replica is local to their LAN.

Replication is more complicated over WAN/VPN, because you have to do indirect (or Internet) replication (I don't recommend Internet replication), and that adds a lot of dependencies and is much harder to program and keep running reliably.

If the other domain is accessible only via Internet, then the only way Jet replication would be an option is if you could set up a VPN connection across the Internet and use indirect replication.

If you mean a different Windows domain, then you'd only be able to do any of this with a username that was trusted across the two domains (if you wanted to use Jet replication).

Jet replication requires no programming to keep two replicas in synch with each other -- any two replicas are always only one synch operation away from containing identical data. Programming the same functionality is very hard, unless the database is edited only transactionally (i.e., records are added, but never edited or deleted).

Some people have successfully programmed their own synchronization, but I've done minor attempts at the same thing myself, and it's incredibly complicated.

Another option might be to use NT file system replication between the two domains (assuming they are NT domains, instead of Internet domains). But that's beyond my expertise -- it's just something that might solve your problem.

My Jet Replication Wiki is here:

http://dfenton.com/DFA/Replication/
 

Users who are viewing this thread

Back
Top Bottom