<?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 Syncing SAS Deployment Agent over Multiple Levs in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450230#M12776</link>
    <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I'm interested to know how you have configured the SAS Deployment agent when you have a single compute tier hosting multiple levs but separate metadata and mid tier hosts for each lev.&amp;nbsp; Essentially what I'm seeing is that the most recent lev configuration on the compute tier has altered the Deployment Agent and Remote Deployment Agent keystores and passwords on the compute tier causing the SAS Backup Manager to fail with the other levs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried using the the Deployment Wizard to manage the agent communication however this is failing to resolve the issue on the older levs.&amp;nbsp; The steps I've performed have been;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; Run the deployment wizard to set communication options for the new lev.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; Log onto to the metadata and mid tier hosts for the new lev and download the client and trust store config for each host.&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; From the compute tier upload deployment agent config to each other lev's metadata.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; From the metadata and mid tier hosts for the other levs download the client and trust store config to each host.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The other levs had backups operating successfully prior to the new lev install and config so it must be possible.&amp;nbsp; Do I need to create my own keystore files?&amp;nbsp; Any help is appreciated.&lt;/P&gt;</description>
    <pubDate>Sun, 01 Apr 2018 11:49:44 GMT</pubDate>
    <dc:creator>foobarbaz</dc:creator>
    <dc:date>2018-04-01T11:49:44Z</dc:date>
    <item>
      <title>Syncing SAS Deployment Agent over Multiple Levs</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450230#M12776</link>
      <description>&lt;P&gt;Hi Everyone,&lt;/P&gt;&lt;P&gt;I'm interested to know how you have configured the SAS Deployment agent when you have a single compute tier hosting multiple levs but separate metadata and mid tier hosts for each lev.&amp;nbsp; Essentially what I'm seeing is that the most recent lev configuration on the compute tier has altered the Deployment Agent and Remote Deployment Agent keystores and passwords on the compute tier causing the SAS Backup Manager to fail with the other levs.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried using the the Deployment Wizard to manage the agent communication however this is failing to resolve the issue on the older levs.&amp;nbsp; The steps I've performed have been;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; Run the deployment wizard to set communication options for the new lev.&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; Log onto to the metadata and mid tier hosts for the new lev and download the client and trust store config for each host.&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; From the compute tier upload deployment agent config to each other lev's metadata.&lt;/P&gt;&lt;P&gt;4.&amp;nbsp; From the metadata and mid tier hosts for the other levs download the client and trust store config to each host.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The other levs had backups operating successfully prior to the new lev install and config so it must be possible.&amp;nbsp; Do I need to create my own keystore files?&amp;nbsp; Any help is appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 01 Apr 2018 11:49:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450230#M12776</guid>
      <dc:creator>foobarbaz</dc:creator>
      <dc:date>2018-04-01T11:49:44Z</dc:date>
    </item>
    <item>
      <title>Re: Syncing SAS Deployment Agent over Multiple Levs</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450434#M12787</link>
      <description>&lt;P&gt;Hi Cameron,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Knowing the way the SAS Deployment Agent credentials are set across the tiers of a deployment what you are describing is a more complex situation.&amp;nbsp; I would recommend that you open a track with SAS Tech Support.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Michele&lt;/P&gt;</description>
      <pubDate>Mon, 02 Apr 2018 19:09:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450434#M12787</guid>
      <dc:creator>michele_sas</dc:creator>
      <dc:date>2018-04-02T19:09:20Z</dc:date>
    </item>
    <item>
      <title>Re: Syncing SAS Deployment Agent over Multiple Levs</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450903#M12794</link>
      <description>Hi Michele,&lt;BR /&gt;Completely agree. It's a really puzzling scenario.&lt;BR /&gt;&lt;BR /&gt;Cam</description>
      <pubDate>Tue, 03 Apr 2018 22:02:28 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Syncing-SAS-Deployment-Agent-over-Multiple-Levs/m-p/450903#M12794</guid>
      <dc:creator>foobarbaz</dc:creator>
      <dc:date>2018-04-03T22:02:28Z</dc:date>
    </item>
  </channel>
</rss>

