Could just be that you're trying to run them to close together. Or more likely they're conflicting with a crawl schedule or other timer job. It' shard to find that window sometimes.
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, 16 September 2009 7:20 PM To: [email protected] Cc: [email protected]; [email protected] Subject: RE: Live server deployment Hi Tommy Thank you for the response. We are not using content deployment but we use stsadm tools to backup and restore the site. Funnily enough we have yet fail to restore the site when we run the command manually but those same commands are so unpredictable when we schedule it to run automatically. Tommy Segoro <tommy.seg...@l7. com.au> To Sent by: "[email protected]" ozmoss-boun...@oz <[email protected]> moss.com cc "[email protected]" <[email protected]> 09/16/2009 01:19 Subject PM RE: Live server deployment Please respond to [email protected] Chris, A lot of the times the failures are due to another process that may take place and bring the DB down such as DB backup, search crawling, etc. The DB may be down due to overloaded server resource. Another cause may be network connection issues. I'm not sure if your network uptime is 100% or not but I've been at client site where the network is down intermittently. The easiest way to do deployment is to ensure that both staging and live servers are synched (in terms of patch levels, a list of solutions deployed, etc). Therefore, when content is deployed/restored on production, none of them will break due to missing features, etc. I don't recommend you using OOTB CDT tool because you can only export/import content at a site level. Plus, you can't set too many deployment options with that (such as exclude dependency, etc) which are critical to the success of your content deployment process. I normally do content deployment using the SPImport and SPExport class of the object model. You can also set a whole range of deployment options through code. It's very-very easy to use, you can also turn on verbose mode which will give you logging exactly the same as the OOTB CDT tool does. Hope this helps, Tommy -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, 16 September 2009 10:27 AM To: [email protected] Cc: [email protected] Subject: Live server deployment Hi Guys I am wondering how you all deploy from staging server to production server. I think we are doing it the wrong way currently and would like to get some inputs/ideas from everyone. The way we do it at the moment is using stsadm command line tool to create backup file from staging server, ftp it to live server, then will use stsadm to restore the backup with overwrite option on live server. This is all batch script and has been scheduled to run everynight, the problem is, out of 5 days every week, at least it will fail once and bring the live server down. It looks like the restore process fails somehow and when we get to the office the next morning and run the task again, it will go through fine. We can't pinpoint the exact problem therefore just wondering if there is any better deployment solution Many thanks, Christian ===================================================================== Disclaimer: This message is intended only for the use of the person to whom it is expressly addressed and may contain information that is confidential and legally privileged. If you are not the intended recipient, you are hereby notified that any use, reliance on, reference to, review, disclosure or copying of the message and the information it contains for any purpose is prohibited. If you have received this message in error, please notify the sender by reply e-mail of the misdelivery and delete all its contents. Opinions, conclusions and other information in this message that do not relate to the official business of the Company shall be understood as neither given nor endorsed by it. _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss ===================================================================== Disclaimer: This message is intended only for the use of the person to whom it is expressly addressed and may contain information that is confidential and legally privileged. If you are not the intended recipient, you are hereby notified that any use, reliance on, reference to, review, disclosure or copying of the message and the information it contains for any purpose is prohibited. If you have received this message in error, please notify the sender by reply e-mail of the misdelivery and delete all its contents. Opinions, conclusions and other information in this message that do not relate to the official business of the Company shall be understood as neither given nor endorsed by it. _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss _______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
