Re: DB architecture for WSS sites on SPS server

Thanks - Avepoint is looking better and better.....


--
Sandy Wood
Orange County District Attorney


"Steve Smith" wrote:

Yep Commvault is good as well, More costly than Avepoint if only being used
to backup1 Sharepoint server but if you want to use commvault for multiple
sharepoint servers or use it for other products such as SQL , Active
Directory , Exchange etc then Commvault is a great company solution as well.
Commvault will require a different server to be installed on ( you dont
install it on the sharepoint box ) whereas Avepoint can be installed on the
same machine.

Steve Smith
www.combined-knowledge.com


"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message
news:404E2D4F-59CE-40C4-B3FB-06FE5671F817@xxxxxxxxxxxxxxxx
Steve,

Thanks for the clarification and information. It all seems to make sense
to
me now. As we are not a very big SPS / WSS user, the 25GB limit shouldn't
be
an issue for us. We've only got about 10 WSS sites on our SPS now at just
under 1GB of content.

We had purchased the Veritas SharePoint backup agent to plug into our
Veritas 10d infrastructure, but were dissapointed to see that it didn't
offer
a document-level restore. Looks like we'll have to investigate some
third-party solutions for our backup and restore.

I just got the new Windows IT Pro magazine which did give a pretty go
review
of AvePoint as a solution. Commvault's Galaxy Backup & Restore got
Editor's
Choice and we may look in that direction also.

Once again, thanks for the help and information.
--
Sandy Wood
Orange County District Attorney


"Steve Smith" wrote:

By design it is a single database but practically it is very bad. If you
plan on going anywhere over 25GB of data and up to a max. of 50GB it is
recommended to create seperate databases for the content. This can be
achieved either by creating stand alone site collection which have their
own
databases as you mentioned or as Joe mentioned you can create additional
content databases in central admin for the virtual server. Note however
that
only Top level team sites are distributed amongst the databases and also
you
need to limit the amount of sites in the existing content database which
will say up to 15000 sites are allowed. So if you have 200 sites make the
max 200 sites and then create a new content database and all new top
level
team sites will go there.
As you are also correct this will affect backup and restore - you may
want
to look at products like avepoint to also help with that granular level
of
sites and libraries.

Steve Smith
www.combined-knowledge.com


"Sandy Wood" <sandy.wood@xxxxxxxxxx> wrote in message
news:849420E9-A67B-40B5-9898-377518A89BF7@xxxxxxxxxxxxxxxx
Thanks for the info. I'm just concerned that if I need to restore a
specific
WSS site, for example, I'll need to restore all the sites that are in
that
same content database. I suppose that's the way it is, but it does seem
unusual. I suppose I could manually create a new virtual server and
then
extend it into a WSS site. That would keep the databases apart.
--
Sandy Wood
Orange County District Attorney


"Joe" wrote:

Yes it is by design.

In Sharepoint Central Administration it is possible for you to create
another content DB that will be used to store data for any new site
collections.

Joe








.