<?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: WAAS and Backupexec in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649376#M47682</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Cora. Please mark this as &lt;STRONG&gt;Answered &lt;/STRONG&gt;if this the solution works for you and also for other people to use it as reference.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 08 Feb 2011 19:53:29 GMT</pubDate>
    <dc:creator>Bhavin Yadav</dc:creator>
    <dc:date>2011-02-08T19:53:29Z</dc:date>
    <item>
      <title>WAAS and Backupexec</title>
      <link>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649373#M47679</link>
      <description>&lt;P&gt;We are implementing backup exec between two of our datacentres (simple inline setup between the two datacentres)&amp;nbsp;&amp;nbsp; The traffic is by default being classified as&amp;nbsp; ** map default ** and is having full LZ/DRE/TFO applied.&amp;nbsp; We do not want DRE applied.&amp;nbsp; The software seems to run on random ports and I am not sure "how" I am to classify this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Questions&lt;/P&gt;&lt;P&gt;For ease (so I am not "hacking" the windows system), is there a way to remove DRE on&amp;nbsp; ** map default ** traffic?&amp;nbsp; I cannot seem to see the application or the classifier?&lt;/P&gt;</description>
      <pubDate>Tue, 08 Feb 2011 16:50:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649373#M47679</guid>
      <dc:creator>cwehrstedt</dc:creator>
      <dc:date>2011-02-08T16:50:33Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS and Backupexec</title>
      <link>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649374#M47680</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Cora,&lt;/P&gt;&lt;P&gt;Yes, you can bypass DRE on WAAS y modifying policy / creating a new policy.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To modify the policy, you need to find which policy is being used for that connection. This is little tricky and can afect the pother traffic, too.&lt;/P&gt;&lt;P&gt;The safe bet is to create a new policy. I believe you have the server ip addresses. You can create a new classifier using a server ip address, put two reverse conditions in the classifier and apply it to the WAE.&lt;/P&gt;&lt;P&gt;Here is the document help to create a new policy and new classifier. Let me know if you want me to paste the options to create a policy.&lt;/P&gt;&lt;P&gt;&lt;SPAN class="content"&gt;&lt;/SPAN&gt;&lt;A href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configuration/guide/policy.html#wp1133454"&gt;Creating a New Traffic Application Policy&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configuration/guide/policy.html#wp1133454"&gt;http://www.cisco.com/en/US/docs/app_ntwk_services/waas/waas/v431/configuration/guide/policy.html#wp1133454&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;Bhavin.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 17:01:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649374#M47680</guid>
      <dc:creator>Bhavin Yadav</dc:creator>
      <dc:date>2011-02-08T17:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS and Backupexec</title>
      <link>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649375#M47681</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I didnt even think of using a policy based on IP, and I think that would work for us. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 18:16:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649375#M47681</guid>
      <dc:creator>cwehrstedt</dc:creator>
      <dc:date>2011-02-08T18:16:55Z</dc:date>
    </item>
    <item>
      <title>Re: WAAS and Backupexec</title>
      <link>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649376#M47682</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Cora. Please mark this as &lt;STRONG&gt;Answered &lt;/STRONG&gt;if this the solution works for you and also for other people to use it as reference.&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 08 Feb 2011 19:53:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/waas-and-backupexec/m-p/1649376#M47682</guid>
      <dc:creator>Bhavin Yadav</dc:creator>
      <dc:date>2011-02-08T19:53:29Z</dc:date>
    </item>
  </channel>
</rss>

