Sharepoint 3.0 STSADM Site Collection

I have been using STSADM to backup and restore site collections onto another WSS 3.0 Server:

STSADM.exe -o restore -url  http://sharepoint/sites/Site1 -filename  \\Backups\Backups\backup.dat -overwrite

My question is if I am able to simply backup all site collections by replacing the URL http://sharepoint/sites/Site1 for http://sharepoint/?

This way, I restore everything in one single swoop. Thanks

fstincAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Ted BouskillConnect With a Mentor Senior Software DeveloperCommented:
Copying a top level site collection to a subsite collection works fine, however, the reverse doesn't work as well.  Be sure to backup the farm first though.  There is a bug with WSS 3.0 and MOSS 2007 when doing site collection backup/restores that will overwrite the default site collection.

Cheers
0
 
Ted BouskillSenior Software DeveloperCommented:
No.  You can backup the entire farm using STSADM or a specific site collection.

If you want to backup an entire web application you can use SQL backup on the content databases for the web application.  There is a technique to restore a web application using those backups.
0
 
fstincAuthor Commented:
Actually I did do it. I think this is the logic, looking through the hierarchy, //sharepoint/ is a site collection. //sharepoint/testsite is another site collection. Anything created under a site collection is a top level site. A web application would is essentially a whole new IIS site.

However, would you know if I am able to backup and restore individual sites using STS going from WSS 2.0 to WSS 3.0? I think it can only be done across the same version of WSS, but just want to get a confirmation? Thanks
Hierarchy-Sharepoint-Sites.png
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
fstincAuthor Commented:
I meant STSADM.EXE. : )
0
 
Ted BouskillSenior Software DeveloperCommented:
Just to be clear. The top level site is the 'Default' site collection which can have one or more sub-sites or site collections.  By default for example additional site collections are stored in the /sites/ sub folder.

For example:

http://webapplication.sharepoint.com/ - Top level site/site collection for a web application
http://webapplication.sharepoint.com/subsite1/ - A subsite
http://webapplication.sharepoint.com/sites/sitecollection1/ - Additional site collection location (by default)
http://webapplication.sharepoint.com/sites/sitecollection1/subsite1/ - A subsite for above

Advanced users might do the following:

http://webapplication.sharepoint.com/mappedpathsitecollection/ - Created using two steps.  First generating a mapped path, then assigning the site collection to the mapped path

http://hostheadersitecollection.sharepoint.com/ - Created using DNS and a host header site collection on a web application (very advanced)

No you cannot mix backups between versions of SharePoint.
0
 
fstincAuthor Commented:
Exactly right. My translation wasnt very clear. Top Level and Site Collections are essentially the same. Tomorrow I do a migration of the following.

SERVER1 (Top Site/Site Collection) = //webapplication.sharepoint.com/

migrating to subsite 1

SERVER2 = //webapplication.sharepoint.com/sites/Engineering

Is there a problem with placing a top level site under a subsite 1? Thanks for the help. Ill close the question, just want to get another quick conformation on this before I start my migration tomorrow? Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.