Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
synchronizing new computer |
Thu, Nov 4 2010 2:11 PM | Permanent Link |
David Cornelius Cornelius Concepts | EDB 2.03b23 (probably moving to 2.04 in the near future)
In a bi-directional replication scenario, where several users of a database edit locally and sync to a remote server, what is the best way to get a new computer's database up-to-date with all the data and synchronizing? Is the following scenario sensible? 1. Backup remote server 2. Copy backup to local machine 3. Restore to new local database 4. Unpublish local database 5. Re-publish local database (to get new publish GUIDs) 6. Start editing and send/receiving updates like other users I noticed that when I backed up the remote server and restored it locally, all the tables were published with the same GUIDs as the servers. Since I understand that replication relies on each table's "publish" GUID to be unique for determining where the updates come from, I figure steps 4 and 5 above are required. Does that make sense? David Cornelius Cornelius Concepts |
Thu, Nov 4 2010 4:12 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | David,
<< I noticed that when I backed up the remote server and restored it locally, all the tables were published with the same GUIDs as the servers. Since I understand that replication relies on each table's "publish" GUID to be unique for determining where the updates come from, I figure steps 4 and 5 above are required. >> You are exactly correct. I will hopefully have a new clause for the BACKUP DATABASE statement soon that will allow one to exclude all published information about the tables being backed up, so you won't have to do the extra steps anymore on the target database. -- Tim Young Elevate Software www.elevatesoft.com |
Thu, Nov 4 2010 4:27 PM | Permanent Link |
David Cornelius Cornelius Concepts | Thank you!
David Cornelius Cornelius Concepts "Tim Young [Elevate Software]" wrote in message news:90B9F864-A754-43F5-9044-04A9C303F398@news.elevatesoft.com... David, << I noticed that when I backed up the remote server and restored it locally, all the tables were published with the same GUIDs as the servers. Since I understand that replication relies on each table's "publish" GUID to be unique for determining where the updates come from, I figure steps 4 and 5 above are required. >> You are exactly correct. I will hopefully have a new clause for the BACKUP DATABASE statement soon that will allow one to exclude all published information about the tables being backed up, so you won't have to do the extra steps anymore on the target database. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Monday, May 6, 2024 at 12:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |