Database restore, both from same and different server

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Here's the problem.

Production WSS is working, but a web part has a memory leak. In order
to try and debug, I am trying to restore content database from
production to a development server. Development server is fairly new
and only had a few test sites created by hand, not the 3-4 hundred in
production. I've had all kinds of problems trying to restore this
data. Here is the setup.

PRODUCTION
WSS SP1 with security fix on Server 2003 Standard with 1 virt server
running site (2GB memory 3.4 Xeon HP server)
SQL server 2000 exclusively for SharePoint

DEVELOPMENT
WSS SP2 on Server 2003, Pentium M laptop with 1GB memory and SQL Server
2000

Production is fine except for a poorly written web part. My problem is
restoring db from production to development. Here is what I have done
so far:
(SQL Server 2000 SP4 already installed)

1) Backed up both Config and Content database from production
2 Restored back up content db over top of a default content db created
when first virtual server extended (that virtual server was removed, so
just reused db) I'm not really familiar with SQL Server, so this might
have been a mistake
3) Installed WSS SP2
4) This automatically extended a default virtual server (fine)
5) I kept default config db (was this smart?) and just tried to add the
new content db that I just restored
5) Received the following error message

The account being used by Windows SharePoint Services to connect to
database 'STS_standard-zzwskt_1_25040' on server
'STANDARD-ZZWSKT\SharePoint' is not the database owner (DBO). For more
information, please refer to Knowledge Base article 841216 at
http://go.microsoft.com/fwlink/?LinkId=45207.

Looked over KB article. Searched group here and read about every
discussion about restoring databases. I am using an AppPool with
Windows Authentication and Network Service as the account. Since this
is the only thing running, I didn't see this as a big issue. The KB
article states as long as you give Network Service rights in SQL server
(which I did) this should work.

Then I remember (I was not in on initial production deployment so this
didn't cross my mind at first) that Production is SP1 and dev is SP2.
I attempt to use the stadmin to force the upgrade, but wait, the
database I want to upgrade is not attached to SharePoint so nothing
happens.

So, I start over and uninstall WSS SP2 and reinstall WSS SP1. When I
try and install security fix for SP1 (to get to same version as
production), it states that the fix is already installed. I look, and
somehow WSS is still SP2, not SP1 even though that is what I downloaded
and installed. During installation there were some files that were
being copied for which newer versions already existed, but I told it to
overwrite anyway. So, I'm still stuck with SP2 on dev and need to
restore my SP1 database.

Ok, now I decide to make sure that I can at least restore the backup I
made of the dev WSS content db before all this started. When I try and
restore this, I get the exact same error as above, even though this db
was created on this machine, is same version, and has dbo as
administrator.

I did all this work while as local administrator to the server. I'm
at a loss and banging my head against the wall since I can't even add
the content db that was made on this machine.

I have a feeling it has to do with the AppPool settings/ using Network
Services for the restore of db from same machine. However, the restore
from prod server could be something else.

I've only been working with SharePoint for about 3-1/2 months so
I'm still trying to understand all its little intricacies. If more
information is needed (I thought I would stop here since it's long
enough already), let me know and I'll provide. Thanks for all the
help.

Adam

.

Relevant Pages

  • Re: Best Way for restoring AD in a test lab
    ... Well do a backup and restore following most of the procedures outlined. ... Just do a backup on a production dc. ... > DC to the test lab with the same Server Name and this is our DR process. ... >> Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: test environment windows 2003
    ... an authorative restore after the demote and system state restore. ... This document was prepared for the building of a copy of the production ... Remove the physical cable for the new pc and build the member server ... Master Operation roles (FSMO and the File Replication service). ...
    (microsoft.public.windows.server.active_directory)
  • Re: duplicate AD in lab
    ... To start is simply install the Server than, use the backup set to restore ... lab to test AD and Exchange for the production environment do you know ...
    (microsoft.public.windows.server.active_directory)
  • Re: Restoring databases files on a brand new server
    ... When I've restored WSS to a different server I installed WSS and all the ... then restored ONLY the Content DBs. ... > We want to restore the Content DB and Config DB to WSSNew server. ...
    (microsoft.public.sharepoint.windowsservices)
  • Restore WSS sites after disaster
    ... I lost the system disk of a server with a couple of WSS ... The database files files were located on a different disk. ... It seems that in order to restore a WSS site (with stsadm -o restore etc. ...
    (microsoft.public.sharepoint.windowsservices)