Replication Newbie

[MikeSr]

I must admit, I am completely confused regarding this replica concept. I have read everything I can get my hands on. Here is what I need to do.
1)Have host system collect data over the internet at a remote site. ( This is done and works well).
2)Have a PC at the remote site running the same program, less the interface and collect data at the same time, or when the the other PC is down. ( What ever my options might be?)
3)If either PC goes down for what ever reason, the syncronization methods that I have read about will allow the failed system to maintain same data records.

I just can't seem to find this Replica option in my Access 2007, even after I converted the Data base to an .mdb. I have tried splitting the database as well.

I need some guidance on this subject. I can't seem to get my arms around this.

Thanks in advance.

 

[dfenton]

1)Have host system collect data over the internet at a remote site. ( This is done and works well).

Not sure what you mean by this.

Is the host system a web server? Are you using an ASP or PHP web app to edit a Jet/ACE database on the web server? Or is it a Windows server that you happen to have access to across a VPN that happens to go across the Internet?

2)Have a PC at the remote site running the same program, less the interface and collect data at the same time, or when the the other PC is down. ( What ever my options might be?)

What program? A web app? An Access app? A VB app?

3)If either PC goes down for what ever reason, the syncronization methods that I have read about will allow the failed system to maintain same data records.

I just can't seem to find this Replica option in my Access 2007, even after I converted the Data base to an .mdb.

I don't have A2007 here to check, but if you use HELP to search for REPLICATION it should tell you where it is on the ribbons.

I have tried splitting the database as well.

You shouldn't use replication for anything *but* a split database, and only on the data tables.

I need some guidance on this subject. I can't seem to get my arms around this.

Thanks in advance.

Jet replication's purpose is not for backup. It sounds to me as though you don't need Jet replication at all, but you need a system that copies your data from the host machine to the backup machine on a regular basis, so that you always have a copy on the backup machine. There's no need to muck about with Jet replication when you don't need to edit the data in both locations.

If you haven't read all the documentation listed on the Resources page of the Jet Replication Wiki, that would be a good place to start:

http://dfenton.com/DFA/Replication/index.php?title=Resources

 

[MikeSr]

I have an access application that is collecting data from a remote site
I use "Kepserver" on the same PC. This collects the data from a remote site (Accross the internet) and puts the data directly into the appropriate access table.

I would like to have a PC at the remote site collecting the very same data. The idea is to prevent data loss. If My PC (Server) is disconnected from the internet for any reason, I would like to have the (Client, at remote site) and my PC (Server) syncronize the data.

My (Server) will connect to servera Remote Sites (Clients) to collect data.
I anylize that data from the sites for alarms and notify the site if a problem occurs. Most importantly The (server, Access 7 app) produces reports at various time intervals and emails them to the appropriate person.

Goal, If the (Server) looses the internet connection, I need a way to still capture the data at the (Client) remote site(s). When the connection is active, I need to capture the lost data.
Any suggestions would be helpfull.

Kepware site is http://www.kepware.com

Sorry for the lack of correct terminology. I appreciate your help

 

[dfenton]

I have an access application that is collecting data from a remote site I use "Kepserver" on the same PC. This collects the data from a remote site (Accross the internet) and puts the data directly into the appropriate access table.

I would like to have a PC at the remote site collecting the very same data. The idea is to prevent data loss.

What you describe wouldn't work with replication, because you'll end up with duplicated data. A synch between two replicas synchronizes all additions/updates from BOTH replicas, so if the data is collected in both places, you'll have it twice.

If you're collecting the data in two locations, the other location is merely a backup, and not a replica, and at fallover time, you'd just use that data file. When the main site is back up, you'd copy the remote file to the main site and replace the data file that's been out of commission (i.e., not collecting data).

If My PC (Server) is disconnected from the internet for any reason, I would like to have the (Client, at remote site) and my PC (Server) syncronize the data.

How do you do that if the connection between the two sites is down? Or is the connection between the main machine and the backup machine on the local LAN instead of across the Internet?

My (Server) will connect to servera Remote Sites (Clients) to collect data.
I anylize that data from the sites for alarms and notify the site if a problem occurs. Most importantly The (server, Access 7 app)

Do you mean Access 2007? I ask because Access "7" was Access 95, the worst version of Access ever, and completely obsolete in all senses.

produces reports at various time intervals and emails them to the appropriate person.

Goal, If the (Server) looses the internet connection, I need a way to still capture the data at the (Client) remote site(s). When the connection is active, I need to capture the lost data.

Replication has no possible role here.

What you are looking for is redundant collection of the data, which means you have two independently-created copies of your data.

When something goes wrong with the main database, you want to switch to the other database. How you do this depends entirely on a bunch of things you haven't explained, such as how there can be communication with the remote site when the Internet is down. Only if the backup database is on the same LAN where you're working would this be viable in any scenario I can think of.

Is what you're doing with the data analysis or are you editing it?

 

[MikeSr]

What you describe wouldn't work with replication, because you'll end up with duplicated data. A synch between two replicas synchronizes all additions/updates from BOTH replicas, so if the data is collected in both places, you'll have it twice.

Understood.

If you're collecting the data in two locations, the other location is merely a backup, and not a replica, and at fallover time, you'd just use that data file. When the main site is back up, you'd copy the remote file to the main site and replace the data file that's been out of commission (i.e., not collecting data).



How do you do that if the connection between the two sites is down? Or is the connection between the main machine and the backup machine on the local LAN instead of across the Internet?

The only internet connection is to my PC. The remote site has the other PC on there LAN.



Do you mean Access 2007? I ask because Access "7" was Access 95, the worst version of Access ever, and completely obsolete in all senses.


Access 2007

Replication has no possible role here.

What you are looking for is redundant collection of the data, which means you have two independently-created copies of your data.

When something goes wrong with the main database, you want to switch to the other database. How you do this depends entirely on a bunch of things you haven't explained, such as how there can be communication with the remote site when the Internet is down. Only if the backup database is on the same LAN where you're working would this be viable in any scenario I can think of.

Each Site has its own LAN. That PC would be on that LAN. The only connection over the internet is my PC where the data is being examined.

Is what you're doing with the data analysis or are you editing it?

I don't edit the data , Just analysis view custom reporting.

I am trying to come up with an option that will guarantee data is recorded when my PC ( over the internet ) looses the connection to the remote sites. So, I thought having a PC at each remote site would be the solution. Perhaps I could have a handshake between My PC and the remote site PC (Access Application) that says if the handshake doesn't exist for a period then the remote Site PC would start logging the data.
I would still have to pick up that data when the Internet connection is re-established.
Does this make any sense?

 

[dfenton]

I don't know what the proper solution is, but I can gurantee Jet replication won't be part of it.