Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

WSS Replication

  Asked By: Lacy    Date: Mar 06    Category: MOSS    Views: 1195

I'm looking for some software that will replicate a WSS installation to
other servers in other physical sites for a client of mine that needs a
low cost Intranet solution. What options are available?

Share: 

 

8 Answers Found

 
Answer #1    Answered By: Vinay Thakur     Answered On: Mar 06

I didn't get any response on this - is it too hard? Are there no
products out there?

 
Answer #2    Answered By: Kristie Hardy     Answered On: Mar 06

There are some products that will do replication  of SharePoint Sites, but
none of them are "Low Cost" solutions. Check out

MOSS2007 Content Deployment

Syntergy Replicator

iOra Accelerator

 
Answer #3    Answered By: Faith Delgado     Answered On: Mar 06

If you are only looking at replicating content or sites  then out of the
box options:-

1) Content publishing. Most of examples of this are for pushing
content from a staging farm to a farm in a dmz hosting the production
internet website.

2) Or down and dirty with batch jobs & stsadm {import/export}......

Not sure what you are trying to achieve here?

Is that your client  has an intranet  with a small WAN (eg several sites,
low bandwidth between them) and you want to replicate  the intranet to
each site so that access is quick for each site?

We previously used replication  with livelink document mgmt system. It
works but has its problems. For us not good at 2 way sync , conflicts
with checkin/out etc.

If this is the case my best recommendation would be to stick to a
central farm then use a network acceleration solution.

We have rolled out Juniper WXC devices. They are providing excellent
results, 35-45% reduction of SMTP traffic 70-90% reduction of HTTP
traffic.

(accelerators are poor at helping encrypted (HTTPS) or previously
compressed traffic (zip files,etc)).

The best thing about network accelerators is that they fix EVERYTHING
not just sharepoint.

Cost wise, well it depends on the licenese which is based on bandwidth.
I would have thought that each accelerator would come in under the
additional server hardware plus windows O/S, sql server, sharepoint
server licenses.

 
Answer #4    Answered By: Alisha Itagi     Answered On: Mar 06

The scenario is that we have a client  with 350 users. The users are
spread across around 50 sites, of which 16 have existing servers  with
W2003 and Exchange 2003. 4 years back we built an intranet  based on
content that was stored in Exchange Public Folders - this handled the
data replication  nicely and didn't require additional CAL's beyond what
they had already. The Intranet runs locally on each of the servers
giving users fast access to the data on it. Some of the files are 10MB
PDF files, so we have a large desire to continue hosting locally where
possible. We need to redevelop the intranet solution  as we wrote all
the code for it ourselves. With Microsoft deprecating Public folder
(heck they even withdrew support for saving Word files to webdav if you
have Office SP2 on a PC) combine with us commencing deployment of
Exchange 2007, we have the need to rebuild from scratch. WSS v3.0 has a
large number of features that we have in the intranet right now and we
think is a good platform to base the intranet on moving forwards. The
big issue we need to solve is that of content replication between sites.
The headoffice is primarily the source of all the content, so we really
only need 1 way replication. The current data size stored on the
intranet is 1.6GB therefore we had considered doing a scheduled STSADM,
but pushing 1.6GB out to all sites  each night is too much.

We only want to use WSS 3.0 if we can, but if we need to have Sharepoint
Portal 2007 in head office then we could consider that.

We're trying to steer away from the large license fees that MS charge
for Sharepoint and SQL and instead use those funds for development of
the intranet.

Hope that makes sense. Further comments would be appreciated.

 
Answer #5    Answered By: Judy Pittman     Answered On: Mar 06

Thats a lot sites  to cover. Our org is the same in site numbers but
around 6000 staff so the economics are quite a bit different for us.

I have another idea but only If your intranet  is anonymous access only
(or at least major chunks of it).

(also I've not tried this and would need some investigation / proof of
concept)



Do you use some sort of proxy servers  at each site (eg Microsoft ISA)?



MOSS with its web content mgmt feature has some control over the caching
of pages and objects (eg docs).

To use this you need to enable the "publishing infrastructure feature"
(If I'm wrong on this, can someone correct me please).

You would want this feature anyhow for doing the web content mgmt of
your intranet pages.

I don't think you can do this with just WSS.



With the publishing feature on you can configure the output cache
profile.



In this instance if you configure the access to the intranet as
anonymous (public internet in the drop down),

And configure the disk based caching for blobs (add pdf etc, to the file
types).

office.microsoft.com/.../HA101762841033.aspx

This way all content published should have a cache control of public.
Thats the key thing.

Your proxy should be able to cache your intranet and therefore serve
most of the content locally.

Additionally with ISA you could setup a caching rule and even consider
active caching of the intranet URL's at night.

I'm not too sure with the active caching logic but hopefully its smart
enough to determine that if the 10mb pdf hasn't changed (HTTP result
304) and matches whats in the ISA cache then it should not download it
again.

Pros:-

- Only a single sharepoint DB to manage.

- Not continually replicating the content only whats changed (i
hope)

- Using MOSS web content mgmt features.

Cons

- Managing TTLs(age) on cacheable content can be complex and
downstream proxies/browsers can serve out of date content.

 
Answer #6    Answered By: Christian Waters     Answered On: Mar 06

Great ideas - but it won't work for this scenario. The private WAN
connects all sites  together back to head office. Headoffice has a
single ISA server through which all internet access is obtained. We
could put ISA on the larger sites and use it for caching only, but then
we "could" have an issue of out of date information which is a big
problem for us.

 
Answer #7    Answered By: Virendar Bahudur     Answered On: Mar 06

checkout www.iora.com for SharePoint server to server replication.

 
Answer #8    Answered By: Ashish Kanoongo     Answered On: Mar 12

Hi,

Is there a way we could have a quick call to discuss more on your requirements. I am sure we can propose you a cost  effective way to do this.

Thanks,
Ashish
+1 415 658 6070
akanoongo@gmail.com

 
Didn't find what you were looking for? Find more on WSS Replication Or get search suggestion and latest updates.




Tagged: