Thanks Michael. That's really good to know. By watching the real-time logs during a restore I've noticed that there are many operations still to run after the "Operation successful" message.
I had thought running execadmsvcjobs would do the trick on a single server farm? Regards, Paul Online Developer, ICT CEO Sydney From: [email protected] [mailto:[email protected]] On Behalf Of Michael Nemtsev Sent: Wednesday, 17 March 2010 1:59 PM To: 'ozMOSS' Subject: RE: Stsadm backup/restore lost content types That seems to be the case described in the link, when you need to run the Wizard. Propagation of the content types doesn't happen immediately after you restore backup, it takes some time, and as I understand it happens via the timer job (however I was not able to find the detailed process description under-the-hood) So it's recommended to run the Wizard after restoration of backup :) PS: it not always content type related. Alerts are tend to have the same symptoms WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com<http://www.sharepoint-sandbox.com/> http://msmvps.com/blogs/laflour From: [email protected] [mailto:[email protected]] On Behalf Of Zelda Leung Sent: Wednesday, 17 March 2010 1:52 PM To: ozMOSS Subject: RE: Stsadm backup/restore lost content types Hi Michael, That's pretty much the problem - the site looks fine, but when I tried to create a new page that uses any content types, it simply says that it can't find the content type. However! To be perfectly honest, I ran out of ideas for it yesterday (I didn't find that article you linked!) so I went home, but on coming back to the problem this morning, I discovered that all the content types had just "appeared". Everyone here swears they didn't touch it, and there are no content deployments to those servers. Nothing has happened on the SQL servers except their usual backup tasks. All I can think of is maybe a timer job ran in the background and did the trick or something else that Sharepoint may/may not do overnight. I wish I knew what it was for next time, but am still grateful it sorted itself out! Cheers, Zelda Zelda Leung | Principal Developer | IT Services | Legal Aid Queensland | p 3238 3626 ________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Michael Nemtsev Sent: Wednesday, March 17, 2010 12:38 PM To: 'ozMOSS' Subject: RE: Stsadm backup/restore lost content types What happens if you create the new page/item that uses the content types?! Can you post an error here? It seems to be this case http://naspinski.net/post/Content-type-0x01010007FF3E057FA8AB4AA42FCB67B453FFC100E214EEE741181F4E9F7ACC43278EE811-not-found-in-web.aspx WBR, Michael Nemtsev, Microsoft MVP http://www.sharepoint-sandbox.com<http://www.sharepoint-sandbox.com/> http://msmvps.com/blogs/laflour From: [email protected] [mailto:[email protected]] On Behalf Of Zelda Leung Sent: Tuesday, 16 March 2010 11:58 AM To: ozMOSS Subject: Stsadm backup/restore lost content types Hello, I'm really hoping someone's had this problem before and can help :( Basically, we use stsadm -o backup -url http://liveintranet -filename C:\intranet.bak to backup our live site. We then use stsadm -o restore -url http://dev<http://svmossdev/>intranet -filename C:\intranet.bak -overwrite to restore a copy to our development boxes to work on. Normally this works without a hitch. Except now, where the content types have been wiped out rather than restored. I've double checked that the content types are still okay on the live box (yes they are, phew), but going to the dev box, the entire content types list is empty, including the ones that are usually there by default. No errors were returned by either of the stsadm commands besides the usual "Operation completed successfully". Has anyone had this problem and how did you fix it? Otherwise, is there a way to quickly restore content types from another site?? Cheers, Zelda Zelda Leung Principal Developer | IT Services | Legal Aid Queensland p 3238 3626 | 44 Herschel Street DISCLAIMER: The contents of this email (including any attachments) are confidential and privileged and are intended only for the addressee. Any confidentiality or privilege is not waived or lost because this email has been sent to you by mistake. Any unauthorised use of the contents of this email is expressly prohibited. If you receive this email in error, please contact us, then delete the email. Emails may be interfered with, may contain computer viruses or other defects and may not be successfully replicated on other systems. We give no warranties in relation to these matters. If you have any doubts about the authenticity of an email purportedly sent by us, please contact us immediately.
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
