Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Archiving Old Sites?

  Asked By: Eliseo    Date: Oct 09    Category: Sharepoint    Views: 2036

We have sub-sites set up for each project that our organization
manages. Once the project closes, we want to be able to archive the
site. We still want the site available for historical purposes, but
not under the same site (because that is for current projects). Is
there a way to move sub-sites along with their DLs to another site?
If there are better ways of setting up an archive area, I'm open to
that, too.



3 Answers Found

Answer #1    Answered By: Osvaldo Winters     Answered On: Oct 09

We have sub-sites  set up for each project  that our organization
manages. Once the project closes, we want to be able to archive  the
site. We still want the site  available for historical  purposes, but
not under the same site (because that is for current  projects). Is
there a way to move  sub-sites along with their DLs to another site?
If there are better ways  of setting  up an archive area, I'm open  to
that, too.

Answer #2    Answered By: Alisha Itagi     Answered On: Oct 09

WSS v2 and DL meaning Document Library (sorry).

I'm new to SharePoint - is a site  collection it's own "domain" so to
speak? I have the project  webs set  up as
http://website.com/projects/projecta/default.aspx. I'm guessing
website.com referenced earlier is its own site collection and
something like website2.com would be another? I'm not sure if I'm
able to do that the way the guy set up our server - that'll be
another post sometime soon, I'm sure. ;)

How would I set them up as individual site collections? I have
about 20 or so projects  set up, but will gladly recreate to make
this easier down the road.

Answer #3    Answered By: Brianna Olson     Answered On: Oct 09

Site Collections are kind of like domains, in that they are
administrative boundaries, but not in the way you mentioned. The
concept of site  Collections and Webs (sites) is very confusing in
SharePoint, but you'll need to get a decent grasp of them before you
move too much further. I don't think I can explain it completely, but
here's a primer:

Imagine the URL
http://server.domain.tld/sites/SiteCollection/web01/web02." target="_blank" rel="nofollow">server.domain.tld/.../web02. In this
example "server.domain.old" is the Virtual Server in v2 (Called a 'Web
Application' in v3). "Sites" is what's called a Managed Path. In v2 a
Managed Path is web path that SharePoint handles. In v2 SharePoint
requires its own ISAPI filter, so if it grabs paths it's not supposed
to, it will break other applications. V3 handles this better, so you
have that to look forward to. "SiteCollection" in the example URL is
Site Collection. A Site Collection is a collection of sites, or in this
explanation a collection of webs. At the root of a Site Collection is a
web called the "root web" or the "top level site." The words "site" and
"web" are sometimes used interchangeably, but that can get you into
trouble. In the SharePoint Object Model Site Collections are called
"SPSite" and sites  or webs are called "SPWeb." If you're talking to a
bunch IT Pros like myself, we all think of sites and webs as the same.
If you bring a developer in they'll get all confused. Just remember to
keep your audience in mind.

We have the top level site at
http://server.domain.tld/sites/SiteCollection and you can put content
there. Like I said, the Site Collection is an administrative boundary,
and should be your unit of scale with SharePoint. Many galleries like
web part and template galleries are saved at the Site Collection level.
Quotas can only be applied at the Site Collection level. In v2, only
Site Collections can be backed up with full fidelity. Site Collections
can be in different content databases from each other, which helps
backup windows. These are things to consider when scaling. Under the
top level site we have a web web01 and it has a subweb, web02. They are
sites or webs. They are the collection of sites that a Site Collection
contains. They are good for subtopics of a main topic. Users can
create webs on their own without IT intervention. IT Pros can create
the Site Collection and walk away. Webs can't be backed up individually
as easily as site collections, and they are all part of the same quota
as the site collection. Why use webs, you may ask. It's easier for the
users. Navigating around sites in a Site Collection is much easier than
navigating around Site Collections on a Virtual Server, at least in v2.

I hope that made some sense. It's a confusing topic, so don't worry if
it doesn't all sink in right away. After you get a handle on what each
part is, you need to find the best compromise between administrative
functionality and ease of use for your users. This will be a moving
target as more people use your site, and you learn more about the
product. I still shake my head at decisions that I made just a year or
two ago.

Just knowing what I know about your situation so far I have a few
suggestions. First, consider moving to WSS v3 as soon as possible. If
you're just getting started with SharePoint I would spend a lot of time
getting up to speed on v2, now that v3 is out. It fixes so many of the
pain points in v2, it's a terrific product. Second, for your situation,
I would initially recommend setting  up each project  as its own Site
Collection. Then as the project winds down you can back it up and
delete it.

Didn't find what you were looking for? Find more on Archiving Old Sites? Or get search suggestion and latest updates.