MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Best Practic question, upgrading moss from a small server farm

  Asked By: Virendra    Date: Feb 18    Category: MOSS    Views: 2528

I am going to have to do this soon, I just wanted to find out what the
sharepoint comunity thinks first.
I have a single sever small farm setup, I want to keep the current server the
WFE, and add another WFE to it.
Is the best thing to do backup the DB using central admin, and then run it on
the new DB servers on the back end, or should I detach the content DB from the
WFE, and then reatach it to the back end, and re-run the MOSS wizzard and
connect to an existing DB?
I would also love to find out some if the pitfalls some of you may have run into
when doing this.



10 Answers Found

Answer #1    Answered By: Cristopher Gould     Answered On: Feb 18

I have a subsite created under a parent site.Initially i used unique
permissions for this subsite (Not inheriting from parent).

Now by mistake one of the previleged user unknowingly clicked on inherit
permissions from parent.

Is there a way to revert back  to unique permissions.?

Answer #2    Answered By: Selena Glenn     Answered On: Feb 18

Yes, go to the site in question  and then from Site Actions choose Site
settings. From there under the Users and Permissions section select the
Advanced Permissions link. This will take you to the Permissions page where
under the Action menu you can select Edit permissions and then break
inheritance again and set your permissions how you would like them.

Answer #3    Answered By: Jonathon Palmer     Answered On: Feb 18

If this is MOSS you should be able to point your second WFE at the
config database on your first WFE. So you would not want to create a
new farm, or move any databases around.

Answer #4    Answered By: Aastha Patel     Answered On: Feb 18

My question  on this is "how did you do your initial install?" did you choose
a basic install or single server  install? If so, then you are running on
MSDE and can't do what Todd is suggesting. BTW - this is one reason we tend
to recommend never doing the Basic or single  server install options of
SharePoint, no scalability. If, however, you installed SharePoint using the
Advanced, complete options, then as Todd points out, simply install
SharePoint on the new server, run  the configuration wizard and have it join
your current farm  by pointing it to your configuration database.

Which method of install did you run?

Answer #5    Answered By: Akshay Gupta     Answered On: Feb 18

He mentioned MOSS which installs SQL Express during a Basic install. I
know SQL Express supports external connections, so unless the MOSS
install stops that somehow he should be able to point another WFE at it.
WSS used WID (Windows Internal Database, also called SQL 2005 Embedded)
and it does not support external connections.

Also, I don't think Advanced > Complete installs the database server.
That just installs all the SharePoint components. The third option,
Stand-alone will, but it's exactly the same as Basic on the page before.

Either way, I agree with you, Basic is normally a bad idea.

Answer #6    Answered By: Trinity Scott     Answered On: Feb 18

With the Basic or Stand alone installs you cannot scale your farm  beyond the
single server. Advanced> Complete does not install any database, correct.
You need to install a separate SQL server, or already have SQL running
somewhere in your network.

Answer #7    Answered By: Constance Guerrero     Answered On: Feb 18

I did do the advanced install, so I have a real small  farm install, not using

Answer #8    Answered By: Chandrabhan Konwar     Answered On: Feb 18

I agree that a basic install is not the way to go.
I have SQL installed on the same server  that has MOSS, and it is congured via
the advanced settings, so it is a real small  farm. I have to move the DB portion
to anouther server that is a SQL Server only server.
Can I just make a copy of the content  DB on the small farm, attach it to the new
SQL server and then rerun my advanced config and point it to the copy of the
content DB that I just moved to the new server?
Does that sound ok?

Answer #9    Answered By: Tina Owens     Answered On: Feb 18

at a high level, this is what I recommend:

1. have the new sql server  ready
2. backup  your farm  using central  admin
3. disconnect the current  servers from the farm
4. run  SPT config wizard to create a new farm, start required services
5. restore the backup made on step 1, using central admin
6. add  additional WFEs to the new farm as necessary
7. you may need to do a full indexing

Answer #10    Answered By: Tiana Whitaker     Answered On: Feb 18

That is exacly what I was looking for, thanks a lot.