Re: Backup Strategy
- From: "Hilary Cotter" <hilary.cotter@xxxxxxxxx>
- Date: Mon, 11 Apr 2005 13:18:11 -0400
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@xxxxxxx> wrote in message
news:emuCqZrPFHA.2252@xxxxxxxxxxxxxxxxxxxxxxx
> 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.
>
>
>
.
- Follow-Ups:
- Re: Backup Strategy
- From: MB
- Re: Backup Strategy
- References:
- Backup Strategy
- From: MB
- Backup Strategy
- Prev by Date: Re: How can implement these simple scenario
- Next by Date: Re: How can implement these simple scenario
- Previous by thread: Backup Strategy
- Next by thread: Re: Backup Strategy
- Index(es):
Relevant Pages
|
