Single tier to two tier migration

[David Blair]

Hello - Currently have a Single Tier Project Server 2007 installation (SQL
2005; Analysis Services; WSS; Web and Application on single server). I want
to move to a 2-tier installation that has Project Server Web and Application
on one server and SQL and AS on the other. The question is 'What is the best
approach?' (easiest). A) install SQL and AS on Server B and Leave Project
Server on Server A and try to hook everything up. or, B) Install Project
Server on Server B and connect to the Databases on Server A that are already
there (can I connect to existing Project Server databases during provisioning
without losing data). Anyway, any suggestions and/or reference on this would
be helpful. Thanks.

 

[Christophe Fiessinger [MSFT]]

check ou this blog post from Steven Haden:
http://blogs.msdn.com/shaden/archiv...t-databases-to-a-new-sql-server-instance.aspx

 

[Paul Conroy]

The "easiest" approach will be to add a second server (web and app) to the
existing farm (assuming you have a farm and not a stand-alone install).

During install of farm, specify that you want this server to host the
central admin site.

Start the web app and project app services on the new server.

Check that Central Admin/SSP/PWA web site have propogated to new server

Change AAM for each site to point to new server name or DNS alias.

Stop web app and project app on old server

Test, Test and Test Again (roll back is to re-starts apps on old server)

Once satisfied that all works on the new server, remove the old server from
the farm.


--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[David Blair]

Thanks Paul for a quick reply - Maybe a bit of miscommunication, so here are
some clarifying answers... I intend to use the current single server within
the 2-server installation. So, single server (A) has everything already
installed. I have another server (B) that is ready to use, and it has a SQL
Server already installed as well. So, my choices seem to be either move the
databases and point to server (B) as the database server, or to, as you
suggest, configure a new farm on (B) and point (A) as the SQL server with
databases already on there. It would seem that your steps would work in the
second scenario and that the everything would 'propagate' to server (B) just
by making that the host of Central Admin, yes? And they would already map to
Server (A) databases so I wouldn't have to apply alternate mapping, yes
Sorry if I am missing something. Thanks again - David

 

[David Blair]

Hi Christophe,

Thank you for the reply and the link... I read through the blog and it
seems to be missing the what to do after you restore the databases to a new
SQL. I did a full backup and that worked fine. Point 4 in the blog is
unclear to me (sorry). It states I have to restore twice? And to select New
Configuration to chate the Database name - which database? Sorry to be
confused....

David

 

[Paul Conroy]

I'd keep SQL on Server A and Extend the Farm onto Server B (assuming both
servers are same spec).

The Alternate Access Mapping has nothing to do with SQL, but the URL's that
you use to access the web applications.

CUrrently you'll probably be access PWA with a URL similar to
HTTP://ServerA/PWA.

When the Web Application is moved to server B and the Web Server stopped on
Server A, you won't be able to use the same URL. You'll have to add an AAM
to allow browsing via HTTP://ServerB/PWA or to a DNS Alias such as
HTTP://MyProjectServerAlias/PWA.

HTH
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[David Blair]

Thanks again! - So, I will give this a go. It seems like I would just do a
Project Server installation on Server B but connect to an existing farm;
connect to existing Config database; create the Central Admin site on Server
B, and then start the services you mention. Then AAM the URL's to point to
Server B PWA. Will the sites propagate automatically? Then on Server A,
remove the farm from the server or just stop the services? Sorry, I'm just
new to this (but not new to Project Server)

Thanks again.... David

 

[Paul Conroy]

Sites will propogate automatically, witht the exception of Central Admin.
This in an advanced option to be selected when adding Server B to the Farm.

make sure central admin has come across before you do anything else. If it
doesn't come across, you've missed the option. Remove the server from the
farm and re-install.

Starting the Web Service and Project Service will bring the other sites
across.

Then change the AAM for the PWA and SSP sites.
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[Paul Conroy]

Stop the services on Server A from within Central Admin, whilst you test the
functionality on server B

Once your happy all is working, remove server A from the farm.

Of course you will take a full farm backup before trying any of these tasks.

Paul
--
Did this post help you. Consider passing on the good will by making a
donation this great charity.
http://www.fundraiseonline.co.nz/TheProjectServerGuru/

http://theprojectserverguru.spaces.live.com

 

[David Blair]

Hello again - Well, I gave it a try and got to Step 2 of installing the Farm
on Server B (I also saw the Advanced tab and selected to host the Central
Admin site) But... it "Failed to Connect to the Configuration Database". I
have tried several times and know that the database name is correct and it
retrieved the right config db name and I am using the correct Service account
and PW. The rest of the error message mentions: "An Exception of the type
System.Security.SecurityException was thrown. Additional Exception
information: Access Denied" It won't let me put in any other user name other
than the one used to create the original config db. I can access each
computer from the other fine. Do I need to somehow turn off Central Admin
from Server A? Any other ideas? Still trying.... Thanks, David

 

[David Blair]

OK - I found out why connecting to the configuration database failed... I
needed to update WSS with SP1 on ServerB even before I ran the configuration
wizard to connect. Had to run the Office Server 2007 SP1 for Project Server
as well. Thank you for all your help!