Backup Strategy

Does anybody have any commnets on a backup strategy with Merge replicated
databases.
What happens when you restore a subscription database will changes previosly
propagated to it be reapplied.
Is there any point doing transaction log backups, what will happen if the
publisher is restored to a point in time will the subscribers drop data
inserted after the restore date or will the data come back from the
subscriptions to the publication after the restore date.
Any comments regarding backups and replication would be appreciated as we
begin to plan our backup strategy.
Cheers.
Yes, merge replication will detect what is missing in the restored backup
and resend what's missing.
You can do transaction log backup on the publisher and subscriber to bring
both back to a point in time and then let the merge agent merge both copies
to consistent states.
--
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
"MB" <dontev@.ntry.it> wrote in message
news:emuCqZrPFHA.2252@.TK2MSFTNGP15.phx.gbl...
> Does anybody have any commnets on a backup strategy with Merge replicated
> databases.
> What happens when you restore a subscription database will changes
previosly
> propagated to it be reapplied.
> Is there any point doing transaction log backups, what will happen if the
> publisher is restored to a point in time will the subscribers drop data
> inserted after the restore date or will the data come back from the
> subscriptions to the publication after the restore date.
> Any comments regarding backups and replication would be appreciated as we
> begin to plan our backup strategy.
> Cheers.
>
>
|||So am I right in thinking that you would have to bring all backups to the
same point in time?
Also if a publisher is restored will it all work again OK or will the
subscriptions then be invalid?
Cheers
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OWUriorPFHA.3788@.tk2msftngp13.phx.gbl...
> Yes, merge replication will detect what is missing in the restored backup
> and resend what's missing.
> You can do transaction log backup on the publisher and subscriber to bring
> both back to a point in time and then let the merge agent merge both
> copies
> to consistent states.
> --
> --
> 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
> "MB" <dontev@.ntry.it> wrote in message
> news:emuCqZrPFHA.2252@.TK2MSFTNGP15.phx.gbl...
> previosly
>
|||You would want to bring at least the publisher back to the latest point in
time. If the subscriber is brought back to the same point - great. If not
transactions originating on the subscriber are lost, and the transactions
originating on the publisher will be back filled to the subscriber.
"MB" <dontev@.ntry.it> wrote in message
news:Oby2i8sPFHA.1088@.TK2MSFTNGP14.phx.gbl...
> So am I right in thinking that you would have to bring all backups to the
> same point in time?
> Also if a publisher is restored will it all work again OK or will the
> subscriptions then be invalid?
> Cheers
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OWUriorPFHA.3788@.tk2msftngp13.phx.gbl...
>
sql