Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Not Answered
  • Replies replies
    3
  • Subscribers subscribers
    3
  • Views views
    323
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Second Agent not being delegated to

MigrationDeletedUser
Hi All,

Running NSM 3.1.1.15 here. I've been doing some Cross-Empire, Folder-to-Folder migrations. To speed things up and spread the load, I setup another server 2012R2 server and installed the agent on there. The agent is authorized and visible in the NSMAdmin. Heartbeat is OK and the log doesn't indicate any failures. However, somehow no jobs are being delegated to this agent. I somehow had gotten this to work yesterday for one of the migrations, but as of today whatever I try it always goes to the first agent (which is also running the engine,etc). Even when the queue gets high enough that the first agent cant process that many events at the same time anymore, the second agent does not come into play and the jobs stay queued until there is room available.

I tried forcing it to use the second agent in several ways; de-authorizing the 1st agent, setting allowed copy jobs on the first agent to '0', Setting the target to be proxied only by the second agent, etc. No matter what I do, nothing gets delegated anymore.

Anybody have any ideas whats going on here and how to fix it?
  • 0
    On 7/17/2014 5:26 AM, Intellium wrote:
    >
    > Hi All,
    >
    > Running NSM 3.1.1.15 here. I've been doing some Cross-Empire,
    > Folder-to-Folder migrations. To speed things up and spread the load, I
    > setup another server 2012R2 server and installed the agent on there. The
    > agent is authorized and visible in the NSMAdmin. Heartbeat is OK and the
    > log doesn't indicate any failures. However, somehow no jobs are being
    > delegated to this agent. I somehow had gotten this to work yesterday for
    > one of the migrations, but as of today whatever I try it always goes to
    > the first agent (which is also running the engine,etc). Even when the
    > queue gets high enough that the first agent cant process that many
    > events at the same time anymore, the second agent does not come into
    > play and the jobs stay queued until there is room available.
    >
    > I tried forcing it to use the second agent in several ways;
    > de-authorizing the 1st agent, setting allowed copy jobs on the first
    > agent to '0', Setting the target to be proxied only by the second agent,
    > etc. No matter what I do, nothing gets delegated anymore.
    >
    > Anybody have any ideas whats going on here and how to fix it?
    >
    >

    Intellium,

    Since you're trying to use this agent for CEDM folder-to-folder
    migrations, does that agent server have the Novell Client installed?

    -- NFMS Support Team
  • 0 in reply to 
    NSRDevelopment;2326178 wrote:

    >
    >

    Intellium,

    Since you're trying to use this agent for CEDM folder-to-folder
    migrations, does that agent server have the Novell Client installed?

    -- NFMS Support Team


    Ofcourse the Novell client is installed.

    I've now got it working to the point that if I force proxy the target to the second agent, it works. But to balance all the migrations I'll have to do this manually by switching between the agents, submit a job, switch to the other agent, etc.
    Anyway to have the system automatically determine a free agent and utilize it? Perhaps even split out the threads among the available agents? Or is there a way to force / re-assign a running job to a different agent?
  • 0 in reply to 
    On 7/17/2014 10:36 AM, Intellium wrote:
    >
    > NSRDevelopment;2326178 Wrote:
    >>
    >>>
    >>>
    >>
    >> Intellium,
    >>
    >> Since you're trying to use this agent for CEDM folder-to-folder
    >> migrations, does that agent server have the Novell Client installed?
    >>
    >> -- NFMS Support Team
    >
    > Ofcourse the Novell client is installed.
    >
    > I've now got it working to the point that if I force proxy the target to
    > the second agent, it works. But to balance all the migrations I'll have
    > to do this manually by switching between the agents, submit a job,
    > switch to the other agent, etc.
    > Anyway to have the system automatically determine a free agent and
    > utilize it? Perhaps even split out the threads among the available
    > agents? Or is there a way to force / re-assign a running job to a
    > different agent?
    >
    >
    Intellium,

    NSM's agents are designed to localize data copies to a server or LAN
    segment, reducing network traffic and load on the NSM Engine. When data
    is being moved to a particular server (whether through normal NSM
    lifecycle operations or CEDM), the Engine will delegate the data copy
    task only to an agent running on the target server or to an agent
    specifically designated as a proxy for that server.

    If you're having to manually switch agents, that suggests that the proxy
    target list for your agents needs to be adjusted, or that an agent needs
    to be installed on the target Windows server.

    -- NFMS Support Team

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.