|
Home > Archive > Microsoft Content Management Server > September 2004 > Understanding how site deployment API works
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Understanding how site deployment API works
|
|
|
| Hi Stefan,
After deploying an MCMS site on online server (i.e. Backup and restore
the database from the production server to the online server)), what
is the next step in order to keep the online site updated.
I am using a service that uses the site deployment scripts, which
exports from the production server and imports in the online server
every N mins.
Now my problem is that how can i make the first successful export so
that all the consequent exports continue from that point.
When i try to export an sdo from the production server environment the
system returns with error after long time (say 3~4 hours). I updated
the machine.config so the asp_wp will not return an error till after
12 hours, and also the maximum Sdo file to 2GBytes... And i am waiting
now the result...
I wonder if there's a workaround to mark all the items as they have
been exported successfully! btw my database size is around 6 GBytes
only articles  ...
| |
| Stefan [MSFT] 2004-09-08, 5:49 pm |
| Hi Nezar,
sdo files cannot be bigger as a around 500 MB afaik. So this will not work.
You would have to deploy in smaller pieces (e.g. using SiteManager).
Future update then can be done using the SiteDeployment API by doing
incremental update.
Cheers,
Stefan.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
MCMS FAQ:
http://download.microsoft.com/downl...6a/MCMS+2002+-+(complete)+FAQ.htm
MCMS Blog: http://blogs.msdn.com/stefan_gossner/category/4983.aspx
MCMS Sample Code:
http://www.gotdotnet.com/community/...t+S
erver
MCMS Whitepapers and other docs:
http://blogs.msdn.com/stefan_gossne...2/07/41859.aspx
--------------------------------
"Nezar" <nezar001@hotmail.com> wrote in message
news:b9e660f4.0409080816.4d5dedae@posting.google.com...
> Hi Stefan,
> After deploying an MCMS site on online server (i.e. Backup and restore
> the database from the production server to the online server)), what
> is the next step in order to keep the online site updated.
> I am using a service that uses the site deployment scripts, which
> exports from the production server and imports in the online server
> every N mins.
> Now my problem is that how can i make the first successful export so
> that all the consequent exports continue from that point.
> When i try to export an sdo from the production server environment the
> system returns with error after long time (say 3~4 hours). I updated
> the machine.config so the asp_wp will not return an error till after
> 12 hours, and also the maximum Sdo file to 2GBytes... And i am waiting
> now the result...
> I wonder if there's a workaround to mark all the items as they have
> been exported successfully! btw my database size is around 6 GBytes
> only articles ...
|
|
|
|
|