<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SC Server to agent ratio in Data Protection</title>
    <link>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53424#M3845</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since a given SC config can only have one agent meaning a backup involves 1 agent there are no limitations, you could have 1000s of agents. The scServer will never talk to more than one agent at a single point in time within a config. It was designed this way to avoid scalability issues &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.0.8/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One area we caution against is backups against the same agent/host. The scAgent in 3.3.0 is single threaded and can only handle one response at a time, it will queue everything else. This means that if you run the same backup config or backup configs at same time that hit same agent/host you will run into timeout issues due to excessive queueing. The workaround in 3.3.0 is to increase the timeout or run multiple agents on a host which also isn't great since it means multiple ports. In SC 3.4.0 the next release we are adding option to start agent in multi-threaded mode but there are some limitations like it isn't supported and wont work on windows and with our domino and mysql plugins.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Keith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 28 Apr 2011 14:01:37 GMT</pubDate>
    <dc:creator>ktenzer</dc:creator>
    <dc:date>2011-04-28T14:01:37Z</dc:date>
    <item>
      <title>SC Server to agent ratio</title>
      <link>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53419#M3844</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hey Guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are there any guidelines or limitations on how many agents should be managed from a single SC server?&amp;nbsp; I understand a lot depends on frequency of scheduling but was wondering if there any quidelines or hard limitations.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Paul Winkel &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:55:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53419#M3844</guid>
      <dc:creator>winkel</dc:creator>
      <dc:date>2025-06-05T06:55:37Z</dc:date>
    </item>
    <item>
      <title>Re: SC Server to agent ratio</title>
      <link>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53424#M3845</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Paul,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since a given SC config can only have one agent meaning a backup involves 1 agent there are no limitations, you could have 1000s of agents. The scServer will never talk to more than one agent at a single point in time within a config. It was designed this way to avoid scalability issues &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.netapp.com/4.0.8/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One area we caution against is backups against the same agent/host. The scAgent in 3.3.0 is single threaded and can only handle one response at a time, it will queue everything else. This means that if you run the same backup config or backup configs at same time that hit same agent/host you will run into timeout issues due to excessive queueing. The workaround in 3.3.0 is to increase the timeout or run multiple agents on a host which also isn't great since it means multiple ports. In SC 3.4.0 the next release we are adding option to start agent in multi-threaded mode but there are some limitations like it isn't supported and wont work on windows and with our domino and mysql plugins.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Keith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Apr 2011 14:01:37 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53424#M3845</guid>
      <dc:creator>ktenzer</dc:creator>
      <dc:date>2011-04-28T14:01:37Z</dc:date>
    </item>
    <item>
      <title>Re: SC Server to agent ratio</title>
      <link>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53429#M3846</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, there's any timing on the release of SC 3.4.0?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 May 2011 21:46:30 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53429#M3846</guid>
      <dc:creator>f_duranti</dc:creator>
      <dc:date>2011-05-05T21:46:30Z</dc:date>
    </item>
    <item>
      <title>Re: SC Server to agent ratio</title>
      <link>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53432#M3847</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It is planned for end of June timeframe.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Keith&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 06 May 2011 07:19:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Data-Protection/SC-Server-to-agent-ratio/m-p/53432#M3847</guid>
      <dc:creator>ktenzer</dc:creator>
      <dc:date>2011-05-06T07:19:50Z</dc:date>
    </item>
  </channel>
</rss>

