WSS2.0 restore not complete


I just using "stsadm -o restore" utility to restore WSS2.0 sharepoint site to my test lab server.  The restore is done but when I compared it with the original production WSS 2.0 server, not every document restored.  And some sites are not able to access.  For exceple, there is a site for IT but I do not see it in my test server.

I created a short cut link to this site

but this site is not in my test server.

Also, the DavWWWRoot cannot be found on my test server, does it make sense?  Is it because I am using two different version of sql on production and test server?

On production server, I am using SQL 2000 on Windows 2003 32-bit.

On my test server, I am using SQL2500 on Windows 2003 R2 x64.

Also, when I use "stsadm -o enumsites -url http://companyweb" to list what is my sites in server but I got this result only, however; I have a lot of sub-sites, am I using the wrong command?

<Sites Count="1">
  <Site Url="http://companyweb" Owner="WEB\administrator" />
Who is Participating?
irinucConnect With a Mentor Commented:
Now, I think you may encounter other issues on this path.
And I wonder if maybe it would be easier to create a backup of the batabase and attach it to the test farm.

See this thread for some more details. They talk about upgrading to Sharepoint 2007, indeed, but the basics are the same: backup the database, restore to the test SQL server and attach it to the test farm.

When you restored the site collection did you get any error/warning? Did you create the backup with a prod farm account? Did you restored with a test farm account?

stsadm enumsites displays only the site collections, not all the sites in the environment.
I would suggest you connect with a test farm account on http://companyweb and check the site hierarchy link. You can navigate to it from Site Settings->Go to site administration->View Site hierarchy.
Or directly: http://companyweb/_layouts/1033/vsubwebs.aspx
This should display the list of all sites.

Also, one thing to consider: the two farms have similar settings? Like for example are the same users defined, are the same third party tools installed or they are in completelly different configurations?
KANEWONGAuthor Commented:
there is no error during restore, just taking 10 hours to complete.  My test server is joined to the same domain as the production sharepoint server.  so, all accounts is the same.

Yes, I found out that I have to use "stsadm -o enumsubwebs -url ...." command to list all sub-sites, not enumsites switch.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

So there is a single subsite restored?

The differences between the 2 servers may cause this; specially since the database structure was changed from one version to another.
I have never tried this type of backup/restore so I am not entirelly sure if this works; i need to check some more on web; one thing that i would check is that the dabatase is set to be compatible (should be 80, not 90)
KANEWONGAuthor Commented:
I think, I did to set the database to be compatible with SQL2000.  Because this is a test server, I can retry many times as I want.

May be, I try one more time to see what is the difference and making sure that the compatibility option is enable.

Do I need to make the STS_config database to be compatible with SQL2000 too?
KANEWONGAuthor Commented:
thanks for your link.    Now, I started another round for using stsadmin -o restore to restore my site and see how it work.  If still no luck, I will try the steps in link.

If it still not working, I will post another question. So, I close this question first and don't hold up long.
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.