Restore

I have two way transactional replication between Hq and other partner
countries. I want to create same enviornment in a lab for testing for
upgrade from SQL7.0 to 2000. Transactional replication is replicating same
tables and same rows and columns both ways;subscriptions are not updatble.
Now I have to take backup of all databases and restore them in the lab
enviornment and then run replicatioln script to create replication in the lab
enviornment. My question is in which order I should backup databases to keep
them synchonized. Shold I backup the HQ first or partner countries? Both
are publisher as well as subscriners for the same tables.
thanks
unless you can kick all of your users off both databases you can't. If you
are interested in a proof of concept, I would take the publication database,
restore it to the lab publisher and lab subscriber and re-run the
replication scripts.
If you do attemp to do the backups you will start from inconsistent
databases which is not the end of the world, you just have to fight with
the data consistency errors which may occur.
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
"Mintu" <Mintu@.discussions.microsoft.com> wrote in message
news:08C1C282-A281-4E73-8645-FE7DAC1F6899@.microsoft.com...
> I have two way transactional replication between Hq and other partner
> countries. I want to create same enviornment in a lab for testing for
> upgrade from SQL7.0 to 2000. Transactional replication is replicating
same
> tables and same rows and columns both ways;subscriptions are not updatble.
> Now I have to take backup of all databases and restore them in the lab
> enviornment and then run replicatioln script to create replication in the
lab
> enviornment. My question is in which order I should backup databases to
keep
> them synchonized. Shold I backup the HQ first or partner countries? Both
> are publisher as well as subscriners for the same tables.
> thanks
|||What errors are most likely to occur and how do I resolve them? Should I use
sp_restartrepl or sp_resetrepl to let the replication continue even database
are not in consistance state?
thanks,
Mintu
"Hilary Cotter" wrote:

> unless you can kick all of your users off both databases you can't. If you
> are interested in a proof of concept, I would take the publication database,
> restore it to the lab publisher and lab subscriber and re-run the
> replication scripts.
> If you do attemp to do the backups you will start from inconsistent
> databases which is not the end of the world, you just have to fight with
> the data consistency errors which may occur.
> --
> 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
> "Mintu" <Mintu@.discussions.microsoft.com> wrote in message
> news:08C1C282-A281-4E73-8645-FE7DAC1F6899@.microsoft.com...
> same
> lab
> keep
>
>
|||Is anybody aware of common problems with this approch and how to resolve them?
thanks,
Mintu
"Hilary Cotter" wrote:

> unless you can kick all of your users off both databases you can't. If you
> are interested in a proof of concept, I would take the publication database,
> restore it to the lab publisher and lab subscriber and re-run the
> replication scripts.
> If you do attemp to do the backups you will start from inconsistent
> databases which is not the end of the world, you just have to fight with
> the data consistency errors which may occur.
> --
> 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
> "Mintu" <Mintu@.discussions.microsoft.com> wrote in message
> news:08C1C282-A281-4E73-8645-FE7DAC1F6899@.microsoft.com...
> same
> lab
> keep
>
>