Comments on: thrust into the world of sharepoint http://blog.loftninjas.org/2006/11/09/thrust-into-the-world-of-sharepoint/ Sat, 21 Jan 2012 06:46:54 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: btm http://blog.loftninjas.org/2006/11/09/thrust-into-the-world-of-sharepoint/comment-page-1/#comment-78 btm Mon, 13 Nov 2006 17:44:00 +0000 http://blog.loftninjas.org/?p=43#comment-78 I only had a ntbackup full disk backup from which to do a restore. Sharepoints stored in a MSSQL db, so I restored the database files and attached the database using Enterprise Manager. I tried to create a new virtual server (IIS Manager), then 'extend' it to a sharepoint site using the sharepoint administrator, then add it as a content database. This was successfull, but the database uses a ton of guids and the configuration database had one guid for both the restored content and the online content, and I don't think it liked that. Somewhere around this point I kept hosing the production site. Of course I had backed up the two production databases (the content and sharepoint config database). Simply restoring the content database and running 'iisreset' for good measure would bring things back to normal whenever I bought the farm.<br/><br/>After playing with this for two days, I was pretty unimpressed with it come Friday night, until I stumbled upon the <a HREF="http://mindsharpblogs.com/james/archive/2005/01/20/189.aspx" REL="nofollow">Sharepoint Database Explorer</a>. This utility connects directly to a database (that is, to sql, it doesn't have to be a content database configured in sharepoint) and lets you browse files, and save files, including revisions, to disk. Apparently the storage structure is based on sites but not folders, so the http paths for the files I was looking for didn't match the structure in sharepoint explorer, but I did find what I was looking for.<br/><br/>Now I just need to setup a real backup schedule and figure out this whole WSS isn't SPS thing, since the SPS utilities seem nowhere to be found I only had a ntbackup full disk backup from which to do a restore. Sharepoints stored in a MSSQL db, so I restored the database files and attached the database using Enterprise Manager. I tried to create a new virtual server (IIS Manager), then ‘extend’ it to a sharepoint site using the sharepoint administrator, then add it as a content database. This was successfull, but the database uses a ton of guids and the configuration database had one guid for both the restored content and the online content, and I don’t think it liked that. Somewhere around this point I kept hosing the production site. Of course I had backed up the two production databases (the content and sharepoint config database). Simply restoring the content database and running ‘iisreset’ for good measure would bring things back to normal whenever I bought the farm.

After playing with this for two days, I was pretty unimpressed with it come Friday night, until I stumbled upon the Sharepoint Database Explorer. This utility connects directly to a database (that is, to sql, it doesn’t have to be a content database configured in sharepoint) and lets you browse files, and save files, including revisions, to disk. Apparently the storage structure is based on sites but not folders, so the http paths for the files I was looking for didn’t match the structure in sharepoint explorer, but I did find what I was looking for.

Now I just need to setup a real backup schedule and figure out this whole WSS isn’t SPS thing, since the SPS utilities seem nowhere to be found

]]>