Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Putting Document Libraries on separate server?

  Asked By: Jarrod    Date: Mar 02    Category: Sharepoint    Views: 10279

I'd like to put the document libraries for my SPS site on another
server - a win2k server. Are there any considerations I should be
aware of? I'm fairly new at using SPS, so any advice would be
greatly appreciated.

Share: 

 

14 Answers Found

 
Answer #1    Answered By: Larry Gonzales     Answered On: Mar 02

Are planning to run SPS2001 on both servers? ...or, for example, SPS2001 on one server  and SPS2003 on the other?

 
Answer #2    Answered By: Lamont Tran     Answered On: Mar 02

I have 2003 running on my primary server  - all I have right now on
the server I want to actually hold the documents (a storage server)
is SQL. Its a Win2k machine, so I can't load SPS on it ... my
question is what do I have to load on it and how do I configure it?

 
Answer #3    Answered By: Orlando Silva     Answered On: Mar 02

If you have SQL server  2000 running on the W2K server, you can use it with your SPS 2003 as your content database server (checkout the SPS 2003 admin online help for the small server farm configuration).

 
Answer #4    Answered By: Dana Hodges     Answered On: Mar 02

Thanks ... I've been pouring over that, the SPS User Guide, and the
WSS Admin Guide all day and to be honest its a bit over my head.
Where I've got the main SPS does not have the hard drive space (I
want to store entire movies and such). If I make the Content Server
the win2k  Server, but still install the Doc Library server  on the
same server, won't all the documents I put  in the document  library
still go into my win2k3 server?

Thanks again for your help!

 
Answer #5    Answered By: Kent Harmon     Answered On: Mar 02

Documents go into the content DB in SQL. Wherever that DB is - that is
where your disk space consumption will occur.

 
Answer #6    Answered By: Alexis Pearson     Answered On: Mar 02

So in SPS, what's the difference between the Content DB and
the Document DB that I install as an optional component?

Also, any chance you can move your DC workshop up to, oh I don't know,
this week?

 
Answer #7    Answered By: Hugo Park     Answered On: Mar 02

Content DBs are SQL Server-based and the native document  library store for sps  2003 (and WinSS).

A (backward compatbile) Document Library (BCDL) database is an upgraded version of the Web Storage System document library that is compatible with Windows 2003 Server and SPS 2003.

MS has also been working on a set of migration tools call the SharePoint Portal Server 2003 Document Library Migration Tools for migrating content from the SPS2001 and SPS2003 Web Storage System document libraries  to the SPS 2003 document libraries (based on SQL Server). More information on these tools will be available later this month.

 
Answer #8    Answered By: Sterling Allison     Answered On: Mar 02

There is no document  DB. There are document libraries  that have their
content held in a content DB in SQL. The backwards-compatible document
library is the 2001 web storage system which you can install with WPW
2003 if you want/need the elementary workflow in that library.

Does this help?

 
Answer #9    Answered By: Jessie Burton     Answered On: Mar 02

It is starting to make sense. Does that mean the new SQL based content
DB no longer has the ability to do versioning or document  templates for
meta-data, which is only talked about in the BCDL section of the admin
guide? I remember reading somewhere that the Content DB was what MS was
moving towards and that the Web Storage System is what they were moving
away from, but I can't remember where I read that. Am I missing any
benefits if I don't install the Backwards Compatible Doc Lib, given that
I'm starting from scratch? Is it worth the effort to install the
Content Management Server? I apologize for what must be novice
questions - I'm trying to get an understanding of how all these
components relate to each other and fit (or don't fit) together.
Thanks!

 
Answer #10    Answered By: Kristopher Morales     Answered On: Mar 02

It's best to read the "Migrating from SharePoint Team Services and SharePoint Portal Server 2001 to Microsoft SharePoint Products and Technologies" white paper to get the full story. You can find the link at bottom of http://www.parallelspace.net/sharepoint/.

Brief answers are provided below.

 
Answer #11    Answered By: Marquis Ortega     Answered On: Mar 02

I loaded a new instance of SPS on a server  and set another SQL server as my content database, however now it tells me that this is not a support topology. What's going on!? Thanks!

 
Answer #12    Answered By: Javier Hawkins     Answered On: Mar 02

I had those roles on the server  that is hosting the SPS, and only the content DB on the other server. Are you saying I need all of them to be on the other server?

 
Answer #13    Answered By: Tracy Bass     Answered On: Mar 02

To my knowledge, as long as you have a server  (any server) running
each of the componants, it should be a supported configuration. If
you have set your

"Global e-mail server"
"Config DB Server"
"Content DB Server"
"Componant settings DB server"
and have set the Web, Search, Index, and Job services to be running,
then it should be a valid configuration. The only times I recieved
the error for an invalid conifguration is when I was missing one of
the above. Sorry if i wasn't much help.

 
Answer #14    Answered By: Rodolfo Tate     Answered On: Mar 02

Make sure that when you are “Configuring server  Topology” that you include all job roles (Document Library Server being the only optional server). I ran into that problem when I only had my front end servers connected to my SQL server. I had to go back and add the “Index” and “Job” roles to the server farm.

 
Didn't find what you were looking for? Find more on Putting Document Libraries on separate server? Or get search suggestion and latest updates.

Related Topics:



Tagged:          

 
 
 

Related Post