Backupstrategy for Database with Merge-Push Replication.

I have a database on a MSSQL 2000 Server which is replicated by a merge push
replication to approximately 20 Notebooks running MSDE.
backup on the Server is done once per night.
If I decide to go back one night on the server, changes which have been
replicated on the notebooks since then will be reapllied.
Is there a strategy better then stopping publication to all notebooks ,
restoring the backup on the server and repushing the publication to the
clients afterwards?Norbert,
Your plan sounds good to me, can't think of a better way.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
Kraft, Norbert wrote:
> I have a database on a MSSQL 2000 Server which is replicated by a merge push
> replication to approximately 20 Notebooks running MSDE.
> backup on the Server is done once per night.
> If I decide to go back one night on the server, changes which have been
> replicated on the notebooks since then will be reapllied.
> Is there a strategy better then stopping publication to all notebooks ,
> restoring the backup on the server and repushing the publication to the
> clients afterwards?
>
>|||Sounds to be a very cumbersom procedure if done by hand. Anyone who had
prepared a sql-DMO script for a similar case ?
"Mark Allison" <mark@.no.tinned.meat.mvps.org> wrote in message
news:%23wQQT%23T$EHA.3588@.TK2MSFTNGP10.phx.gbl...
> Norbert,
> Your plan sounds good to me, can't think of a better way.
> --
> Mark Allison, SQL Server MVP
> http://www.markallison.co.uk
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602m.html
>
> Kraft, Norbert wrote:
> > I have a database on a MSSQL 2000 Server which is replicated by a merge
push
> > replication to approximately 20 Notebooks running MSDE.
> > backup on the Server is done once per night.
> > If I decide to go back one night on the server, changes which have been
> > replicated on the notebooks since then will be reapllied.
> > Is there a strategy better then stopping publication to all notebooks ,
> > restoring the backup on the server and repushing the publication to the
> > clients afterwards?
> >
> >
> >