I am running Window Sharepoint Service 3.0 on windows 2003. I did a backup with this command: "%commonprogramfiles%\microsoft shared\web server extensions\12\bin\stsadm.exe" -o backup -directory c:\backup -backupmethod full I am trying to perform a restore with this command: "%commonprogramfiles%\microsoft shared\web server extensions\12\bin\stsadm.exe" -o restore -restoremethod overwrite -directory c:\backup The problem is that it is hanging at the "[Search instance] 50 percent complete." step (see last few lines of the log file below). [7/10/2008 10:51:21 PM]: Verbose: Starting object: WSS_Administration.[7/10/2008 10:51:21 PM]: Progress: [WSS_Administration] 50 percent complete.[7/10/2008 10:51:21 PM]: Verbose: Starting object: Windows SharePoint Services Search.[7/10/2008 10:52:51 PM]: Progress: [Windows SharePoint Services Search] 50 percent complete.[7/10/2008 10:52:51 PM]: Verbose: Starting object: Search instance.[7/10/2008 10:52:51 PM]: Progress: [Search instance] 50 percent complete. I have read several other reports that this was a problem - supposedly affected by DST. I have tried this: "%commonprogramfiles%\microsoft shared\web server extensions\12\bin\stsadm.exe" -o execadmsvcjobs but it doesn't seem to help. This appears to be a very common problem, but I haven't found any fix. Any ideas?

How many web applications do you have on your server? If they are few, can you try using following command: stsadm-o backup -directory c:\backup -backupmethod full -item "web app name example Sharepoint - 80" similarly back up all the web apps. And then restore them one by one using following command: stsadm -o restore -directory c:\backup -backupid c9ad0554-72d6-408d-913d-d034a8ef120e -restoremethod overwrite You can check for back up ids using following command: stsadm -o backuphistory -directory c:\backup Usually restore takes a lot of time. So try doing one app at a time.

Arpit Goyal: Thanks. I am using the command lines (..doing a lot of testing...). Sometimes the restore will work, sometimes it fails with an error similar to this: [7/11/2008 10:57:36 AM]: Warning: [WSS_Content_9d5d449bd9de4df2999b2f6b9e4c9084] Content database failed to be added to SharePoint, please try and detach the original database then re-attach this database. The test scenarios are consistent but the results vary. Sometimes the restore is succesful, but more times there are failures (above). I am doing a "full" backup and a "replace" restore. I have looked for a comprehensive DR plan for Sharepoint (excluding 3rd party solutions). But according to the Sharepoint DR Guide from MS, the stsadm restore command is NOT supported for "Configuration and Central Administration content databases". From what I can tell, these have to protected via SQL backup. As well, any customizations aren't backed up (...or are they?) Also stsadm "Does not produce a full-fidelity backup; includes content only. Does not include customizations and settings such as workflow, alerts, and properties." So - what good is stsadm?? It seems there is risk of an incomplete backup if you rely solely on stsadm. IS THERE A COMPLETE BACKUP SOLUTION FOR SHAREPOINT THAT DOESN'T REQUIRE 3RD PARTY LICENSING? (I know about DPM - but that is not an option.) Thanks, -Kevin

Hi Kevin, Use the SiteCollection backup with STSADM for backup and restore. Here also while restoring it wont restore the custom apps to the new destination site. If you are restoring to the same site then it will be inplace. If ur restoring to new site, then u need to apply all the custom solution packages to the restored site if any are there.

Hi, I suggest you to use STSADM export and import for the same. Delete the site created at your destination location after taking a backup of it. Then create a new one using STSADM createsite. Do not use any template in the command syntax. Then take the contents of the site using STSADM export command and then import the same by using STSADM import command. I hope thsi will help you out. Thanks, Rahul Rashu