merge replication and disaster recovery (SQL 2005)

Once a merge relationship is established, what happens when either the
publisher restores a previous backup, or the subscriber restores a previous
backup? How is this handled? Will the latest data will be restored from
the database that didn't crash?
--Troy
If a publisher is restored to an earlier state, data which is in the
subscriber is detected as new (even if it came from the publisher originally
before the crash) and fills in the publisher. If the subscriber is restored
to a previous state, data flows from the publisher back to the subscriber to
sync it up.
This process will continue as long as you are within your retention
settings.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Troy Wolbrink" <wolbrink@.ccci.org> wrote in message
news:%23UjcBWJ9FHA.1020@.TK2MSFTNGP15.phx.gbl...
> Once a merge relationship is established, what happens when either the
> publisher restores a previous backup, or the subscriber restores a
> previous backup? How is this handled? Will the latest data will be
> restored from the database that didn't crash?
> --Troy
>
|||As long as your within your retention settings, would new deletes be
included? Or would the restored record be seen as a new record and then
reinserted?
--Troy

> If a publisher is restored to an earlier state, data which is in the
> subscriber is detected as new (even if it came from the publisher
> originally before the crash) and fills in the publisher. If the subscriber
> is restored to a previous state, data flows from the publisher back to the
> subscriber to sync it up.
> This process will continue as long as you are within your retention
> settings.
[vbcol=seagreen]