EMC SourceOne Bandwidth Issues

Posted on 2011-02-25
Last Modified: 2012-06-27
I have a customer that recently implemented EMC SourceOne Archiving solution. In all sites, but one the client is running great. Unfortunately the office having the issues houses the CFO, CEO and President of the company. The office has a 1.5M T1 connection to the remote site housing the Exchange Server, as well as the SourceOne Management Server.

In this particular office when SourceOne is running we see a 100% saturation of the 1.5M T1 line causing other applications in the office to have latency issues. On a normal day to day basis without SourceOne running, the connection hovers around 500 to 600k.

There are 4 clients is this office that require SourceOne. Currently just a single client can cause the results mentioned above. Has anyone seen this type of behavior before? The mailboxes were cached at the remote site housing the Exchange Server, as well as the SourceOne Management Server before bringing them online in the office they were to be used. Unfortunately we are still seeing SourceOne doing something in the background to cause network latency.

We are currently working with EMC, but unfortunately we have not seen any progress. I apologize if my description is not very clear. If more information is needed I would be glad to provide it. I will also say that I know next to nothing about SourceOne aside from the minimal exposure during the troubleshooting efforts. Any help would be greatly appreciated.


Question by:MWPxerom
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 2

Accepted Solution

LITUP earned 500 total points
ID: 34982535
Is letting it run continuously over a weekend an option? I'd say your archiving solution wants to finish some kind of sync operation and its using all the bandwidth to try and do so. Perhaps if your office is closed Sat-Sun it may have enough time to complete.

Author Comment

ID: 34982680

I did fail to mention that we have tried this as well with no results. We have tried to let the machines sync at night, as well as on the weekends with no results. The issues does not happen every day nor does it happen on the same days. It really is a hit or miss type issue that makes it difficult to reproduce for EMC support.

Thanks for the comment.


Expert Comment

ID: 34982759
Very strange...

Well. Until you know what process is using the bandwidth and where the remote data is going there’s not a whole lot you can do.

Tools like Microsoft systernals tcpview and Process Monitor running while the issue is occurring may shed some light on these unknowns.

But without any information you could try this.

If you are able to identify the target where the data is being sent to/from, and the process creating the connection is using DNS then you could try a trick like editing the host file of the server to give the DNS target a dummy IP address. This way each time the process attempts to start (causing all the bandwidth to get used) It will not be able to connect to the remote host and fail.

Online Training Solution

Drastically shorten your training time with WalkMe's advanced online training solution that Guides your trainees to action. Forget about retraining and skyrocket knowledge retention rates.


Author Comment

ID: 34982866
We do know that the target the remote hosts are connecting back to is the primary exchange server. The problem is that we have been unable to identify what process is causing this connection to utilize the full 1.5M T1 connection.

We also have not noticed any sort of updating on the client side that can help with the identification when the bandwidth is being crushed. We have tried enabling logging on the client side as directed by EMC, but unfortunately EMC has not been able to determine anything from the logs.


Author Comment

ID: 35128397

It appears that S1 was functioning properly and that the T1 connection just could not handle S1 as well as the rest of their applications. Being that what you mentioned first in this thread is what we did at first to limit the replication impact of S1 on our network, I will give you the points. Thanks for your comments.

Author Closing Comment

ID: 35128421
This does limit the initial bandwidth impact S1 would have when archiving emails. It turns out the network connection we are running on can not support this application as is.

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
In this video we show how to create a Contact in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Contact ta…
how to add IIS SMTP to handle application/Scanner relays into office 365.
Suggested Courses
Course of the Month3 days, 19 hours left to enroll

630 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question