Hi Ajay,

if the databases are separate this should be fine.
You should use a dedicated central admin server for the deploying import server 
which is not one of the WFEs of the farm - then the performance should not be 
affected to bad.
Main issue will be that the items updated through the import will be invalided 
in the various caches on the WFEs.

Cheers,
Stefan

Von: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] Im Auftrag von Ajay
Gesendet: Mittwoch, 4. März 2009 22:27
An: ozmoss@ozmoss.com
Betreff: Re: Content Deployment [SEC=UNCLASSIFIED]

Hi Stefan,

Hi Stefan,

Good to see the expert in this list.

In my current client engagement,, ultimately I will have 18 (or more) 
simultaneous deployment jobs running each in different source and destination 
database.
Do you think content deployment will be able to handle this?

These all be from Staging to Production,,, can you give some idea what kind of 
performance degradation (or not) of the Production box will be when it will 
importing content.


Cheers,
Ajay
On Wed, Mar 4, 2009 at 10:00 PM, Stefan Goßner 
<stef...@microsoft.com<mailto:stef...@microsoft.com>> wrote:

Hi Michael,



various different exceptions can occur. Depends on when the conflict occurs.

The issues usually show up as "random" errors. Means when you retry the same 
deployment it will either succeed or fail at a different place.



Cheers,



Stefan Goßner
Escalation Engineer | CSS SharePoint Products and Technologies | Microsoft GmbH 
| http://blogs.technet.com/stefan_gossner



Von: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] Im Auftrag von Michael 
Nemtsev
Gesendet: Mittwoch, 4. März 2009 09:55

An: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Betreff: RE: Content Deployment [SEC=UNCLASSIFIED]



Stefan,



What kind of exceptions to expect in logs, when you have multiple jobs run on 
the same source|destination database?



The question is actually how to detect such scenario by logs only?! Are there 
something specific which shows that they have multiple jobs on the same box.



Michael Nemtsev
Readify | Microsoft MVP

T: 0424 184 978 | E: 
michael.nemt...@readify.net<mailto:michael.nemt...@readify.net>

________________________________

From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[ozm...@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Stefan Goßner 
[stef...@microsoft.com<mailto:stef...@microsoft.com>]
Sent: Wednesday, 4 March 2009 7:48 PM
To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subject: AW: Content Deployment [SEC=UNCLASSIFIED]

You can run multiple jobs in parallel if you ensure that only one job runs per 
source and destination database.

As soon as multiple export jobs run on the same source database or multiple 
import job run on the same destination database you can expect exceptions.



Cheers,



Stefan Goßner
Escalation Engineer | CSS SharePoint Products and Technologies | Microsoft GmbH 
| http://blogs.technet.com/stefan_gossner



Von: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] Im Auftrag von Noja, Fadi
Gesendet: Dienstag, 3. März 2009 23:40
An: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Betreff: RE: Content Deployment [SEC=UNCLASSIFIED]



Here's the scenario:



The farm has 6 application in it, they want Content deployment every 30 
minutes.  It's fine cause each job only takes about 10 minutes, but if I set 
all six to be deployed at say 10:00, will it cause an issue.



________________________________

From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Michael 
Nemtsev
Sent: Wednesday, 4 March 2009 9:38 AM
To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subject: RE: Content Deployment [SEC=UNCLASSIFIED]



As I understand you end up with multiple items in destination site. AFAIK



Michael Nemtsev  | MOSS MCTS, MS MVP
Readify

B: http://msmvps.com/blogs/laflour/ T: +61 424 184 978 E: 
michael.nemt...@readify.net<mailto:michael.nemt...@readify.net>



From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Noja, Fadi
Sent: Wednesday, March 04, 2009 9:22 AM
To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subject: RE: Content Deployment [SEC=UNCLASSIFIED]



We have all those CU installed and content deployment is working.  I just want 
to know if there's any issues if 1 jobs is running and doesn't finish before 
the second job kicks off.



________________________________

From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Joshua Haebets
Sent: Wednesday, 4 March 2009 8:55 AM
To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subject: RE: Content Deployment [SEC=UNCLASSIFIED]



There are too many issues with content deployment to mention.



Make sure you have SP1, Infrastructure Update and Dec and Feb CU installed. 
These address a lot of the issues but not all



Cheers



Josh









From: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com> 
[mailto:ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>] On Behalf Of Noja, Fadi
Sent: Wednesday, 4 March 2009 8:53 AM
To: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subject: Content Deployment [SEC=UNCLASSIFIED]



Hi,



Has anyone had experience with Content Deployment?  We're trying to setup 
content deployment for multiple sites on the same farm and was wondering if 
there's issues with multiple deployments happening at the same time.  And if 
there is an issue, if you know of a work around.



Fadi

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________

Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>

Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>

Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>

List FAQ: http://www.codify.com/lists/ozmoss

Other lists you might want to join: http://www.codify.com/lists

________________________________
Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com<mailto:ozmoss@ozmoss.com>
Subscribe: ozmoss-subscr...@ozmoss.com<mailto:ozmoss-subscr...@ozmoss.com>
Unsubscribe: ozmoss-unsubscr...@ozmoss.com<mailto:ozmoss-unsubscr...@ozmoss.com>
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists

________________________________
Support procedure: https://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists
--------------------------------------------------------------------------------
Support procedure: http://www.codify.com/lists/support
List address: ozmoss@ozmoss.com
Subscribe: ozmoss-subscr...@ozmoss.com
Unsubscribe: ozmoss-unsubscr...@ozmoss.com
List FAQ: http://www.codify.com/lists/ozmoss
Other lists you might want to join: http://www.codify.com/lists

Reply via email to