New Server and replication

Have a look at 'replication, backup and restore
operations' in BOL. Provided the new server and the old
server have the same name, this is possible. You'll need
to take copies of all the publisher/distributor databases
involved - the publishing database, MSDB, distribution
and master. BTW, prevent anyone from accessing the
publishing database and stop all replication jobs inc the
cleanup agent before starting the backup procedures.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
Thanks for your reply. The new server has the same name as of old. But
eventually I'll have to change the name of the old server since two machines
with same name cannot belong to the same domain.
How do i set up the subscribers to replicate the data on the old server that
will sit in the branch and then replicate the data on the new server that
has the publisher?
Thanks
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:046901c53435$c318f170$a601280a@.phx.gbl...
> Have a look at 'replication, backup and restore
> operations' in BOL. Provided the new server and the old
> server have the same name, this is possible. You'll need
> to take copies of all the publisher/distributor databases
> involved - the publishing database, MSDB, distribution
> and master. BTW, prevent anyone from accessing the
> publishing database and stop all replication jobs inc the
> cleanup agent before starting the backup procedures.
> HTH,
> Paul Ibison SQL Server MVP,
> www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||I'm not too sure I follow the last bit. As I understand,
you have an existing publisher that will be replaced by a
new publisher server. The new server will have the same
name and the old server taken offline. Form the point of
view of the subscribers, they won't know any difference,
unless they are using IP addresses for registration of
the publisher.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I am sorry If I confused you. You are absolutly correct till now. What I
intend to do now is put our old server in one of our branches. I'll call it
Server1. Server1 is going to be a member of the domain if it makes sense.
Earlier managers used to replicate directly on to the publisher server but
now I want a bunch of managers to replicate to Server1 and rest of them to
Server0 i.e. my new server (Domain Controller). And I want Server1 to
replicate everything onto Server0. Server1 should pickup any relevant
changes from Server0 and pass onto subscribers replicating on Server1.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:108301c53502$00b05510$a501280a@.phx.gbl...
> I'm not too sure I follow the last bit. As I understand,
> you have an existing publisher that will be replaced by a
> new publisher server. The new server will have the same
> name and the old server taken offline. Form the point of
> view of the subscribers, they won't know any difference,
> unless they are using IP addresses for registration of
> the publisher.
> HTH,
> Paul Ibison SQL Server MVP,
> www.replicationanswers.com/default.asp
> (recommended sql server 2000 replication book:
> http://www.nwsu.com/0974973602p.html)
>
|||Thanks for the clarification. What you are referring to
is 'republishing'. There isn't a huge amount of
information in BOL but there is some. If you are using
merge replication, the same effect could be achieved by
using alternative synchronization partners.
HTH,
Paul Ibison SQL Server MVP,
www.replicationanswers.com/default.asp
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

New fresh 2005 cluster and SCC error

I am trying to setup an active/passive cluster (everything on 32bit
plateforme) on a virtualized environment. I followed several docs provided by
microsoft especially the one on /prodtechnol/virtualserver/deploy/cvs2005.mpx.
Regarding the w2k3 itself it seems everything is correct, I did all
necesary tests for testing the failover from one node to another and
evrything works correctly.
When I launch SQL 2005 setup on node1 (node 2 of course is on), Setup stops
indicating that some requirements are not met, an SCC Error.
I have an AMD Athlon 64 proc 3000 2.00GHz with and each VM was granted 512 G
of Ram.
I understand that min req is 600Htz for Procs and 512. When I open the
summary.txt file I have the following :
********************************************
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
Service Pack 1 (Build 3790)
Time : Sat Mar 31 15:55:30 2007
SQLCLUST11 : The current system does not meet minimum hardware requirements
for this SQL Server release. For detailed hardware requirements, see the
readme file or SQL Server Books Online.
SQLCLUST11 : There was an unexpected failure during the setup wizard. You
may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in
%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time : Sat Mar 31 15:55:59 2007
List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core(L ocal).log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Datast ore.xml
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core.l og
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0 LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows
Installer.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows Installer
LangPack.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Suppor t.log
C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_SCC.lo g
************************************************** ***
In fact I remember that I had an alert (! inside Yellow triangle) in the
final step of adding the second node. So the alert indicated the following :
**************************
Reanalyzing cluster
sqlclust12: c omparing cluster and node configurations...
sqlclust12: Collecting managed resources...
Triangle yellow : Status 0x00138f: The cluster resource could not be found
*****************************
As said, the cluster works like a charm (several failover tests)
Thank you for your help
"SalamElias" wrote:

> I am trying to setup an active/passive cluster (everything on 32bit
> plateforme) on a virtualized environment. I followed several docs provided by
> microsoft especially the one on /prodtechnol/virtualserver/deploy/cvs2005.mpx.
> Regarding the w2k3 itself it seems everything is correct, I did all
> necesary tests for testing the failover from one node to another and
> evrything works correctly.
> When I launch SQL 2005 setup on node1 (node 2 of course is on), Setup stops
> indicating that some requirements are not met, an SCC Error.
> I have an AMD Athlon 64 proc 3000 2.00GHz with and each VM was granted 512 G
> of Ram.
> I understand that min req is 600Htz for Procs and 512. When I open the
> summary.txt file I have the following :
> ********************************************
> Microsoft SQL Server 2005 9.00.1399.06
> ==============================
> OS Version : Microsoft Windows Server 2003 family, Enterprise Edition
> Service Pack 1 (Build 3790)
> Time : Sat Mar 31 15:55:30 2007
> SQLCLUST11 : The current system does not meet minimum hardware requirements
> for this SQL Server release. For detailed hardware requirements, see the
> readme file or SQL Server Books Online.
> SQLCLUST11 : There was an unexpected failure during the setup wizard. You
> may review the setup logs and/or click the help button for more information.
>
> SQL Server Setup failed. For more information, review the Setup log file in
> %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
>
> Time : Sat Mar 31 15:55:59 2007
>
> List of log files:
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core(L ocal).log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Datast ore.xml
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Core.l og
> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework 2.0 LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Upgrade Advisor
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows
> Installer.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_.NET Framework Windows Installer
> LangPack.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_Suppor t.log
> C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0007_SQLCLUST11_SCC.lo g
> ************************************************** ***