Todd
Mon Apr 10 12:59:31 CDT 2006
We do all of our backups and restores and the content database level, so
you're not in unchartered territory. I've never used MSDE so there might be
some translation needed on our process, since it's SQL based.
1) Restore the content DB. If there's already a content DB with that name
there and there are site collections in that content DB that you don't want
to overwrite restore the database to a different name. I normally do DB
name _date so that I can keep instances straight.
2) If possible, install WSS on a different machine and attach the content DB
to that install. Then use STSADM to back the site up from the second
install and restore it to production.
3) If a second install is not possible you're going to incur some downtime.
You'll need to unmount your production content DB and mount the restored one
long enough to STSADM backup the site you want to restore. If you mount a
DB that has sites in it with the same name as sites in another mounted
content DB those sites go away. This problem is present even if the Content
DBs are mounted for different Virtual Servers in WSS. The machine only has
one Config DB and all the sites on that box are in the Sites table there.
You cannot get around this by simply creating a second Virtual Server.
You'll have to mount the restored DB, pull the site off, dismount it and
mount the production one back up and restore the site.
Good luck,
tk
"SharePointer" <jmedero@gmail.com> wrote in message
news:1144678898.998285.164440@t31g2000cwb.googlegroups.com...
> Hey guys,
>
> I have recently received the task of restoring a WSS website. The
> original server which contained the WSS top-level site has been moved
> to a new server (better hardware) and
> the only backup of the WSS site is a content Database STS_SERVER_1 and
> config database which I suspect we won't need. I know
> that you can add content DB's to an already extended WSS site but how
> do you then retrieve the old site content (documents, images etc..).
> The old URL was
http://companyName.... my best
> guess would be to extend a new
> website with the exact same URL (host header)? When I create a new
> website how would I exactly go about pointing that website to my old
> content database..(extend and map??) I am not sure how or where to
> access
> the old site content...
>
>
> My question is with only the WMSDE content Database (no stsadm.exe
> backup) how do I restore that and
> retrieve the content.
>
>
> Any help would be greatly appreciated!
>
>
> Thanks,
>