7 Replies Latest reply: Dec 11, 2012 9:54 AM by JoeBidgood RSS

    Replication Tasks in parallel

    tbujnowski

      Is there a way to raise the number of replications task in parallel?

       

      When issue a replicate now command, no matter how many repositories I select, it only replicates six at a time.

       

      I found a document on the net that says that its replications concurrence is equal to number os CPUs x 6. And that matches my scenario.

       

      Is there a way to raise this number? (Besides raising the number os CPUs)

       

      Thanks in Advance!

        • 1. Re: Replication Tasks in parallel
          tbujnowski

          Found this on the forum regarding ePO 3.6.0

           

          repositories at the same time.

          This can be changed via the registry:

          [HKEY_LOCAL_MACHINE\SOFTWARE\Network Associates\ePolicy Orchestrator\Site Manager]

           

          Create a DWORD "NumReplicationThreads" and set the number to the concurrent threads you want epo to run.

           

           

          Is this still valid for ePO 4.6.4?

          • 2. Re: Replication Tasks in parallel
            JoeBidgood

            This is still valid, but I'd suggest experimenting with caution as setting this too high can have a performance impact on ePO when replications are running.

            Out of interest how many DRs are we talking about?

             

            HTH -

             

            Joe

            • 3. Re: Replication Tasks in parallel
              DonHanson

              Have you looked at using Super Agent repositories with Lazy Caching to see if they would fit your environment and needs?  

               

              Lazy caching turns the repository replication model from a push to a pull model.  It can save significant bandwidth transmission as only the files necessary to update your machines are pulled across the wire.  The main consideration is that updating of DR is no longer scheduled, so it can happen at any time of the day as machines look for updates.

              • 4. Re: Replication Tasks in parallel
                tbujnowski

                Thanks for the Reply Joe and Don!!

                 

                We're talking about 102 SA DR.

                 

                How long will Lazy caching keep the files?

                 

                I have location with realy low bandwidth. I'm talking about 64 and 128 KB.

                • 5. Re: Replication Tasks in parallel
                  JoeBidgood

                  I think the files are cached for 30 days, by default, so they will be removed 30 days after the last time a client requests them.

                  In the scenario you describe I definitely think you should be looking at lazy caching - replicating over 100MB of DAT file every day is not going to be an efficient use of that bandwidth, I feel.

                   

                  HTH -

                   

                  Joe

                  • 6. Re: Replication Tasks in parallel
                    tbujnowski

                    But Lazy Caching will download updates any time of the day a client requests it. Even during business hours... How large are the download updates using lazy caching?

                    • 7. Re: Replication Tasks in parallel
                      JoeBidgood

                      Whatever file is requested will be downloaded - so if all the machines downstream of the SA repo are only one day out of date, then all that will be downloaded is one incremental file.

                      However if a new machine is brought online, then it will request the full DAT.

                       

                      HTH -

                       

                      Joe