<?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 Business Copy delay command problem in HPE MSA Storage</title>
    <link>https://community.hpe.com/t5/hpe-msa-storage/business-copy-delay-command-problem/m-p/442597#M893</link>
    <description>I have a business copy task configured that takes a snapclone and mounts this then has a 82000+ second delay (23hours) before the undo.&lt;BR /&gt;
&lt;BR /&gt;
On its first run the clone and mount works fine but when the undo runs 23 hours later it delays again for a 2nd 23hr period before finally completing the undo.&lt;BR /&gt;
&lt;BR /&gt;
The job is then scheduled in automation manager to run daily @ 10pm but on the second day it errors and sits pending with the following example process status:&lt;BR /&gt;
'&lt;APPLIANCE_NAME&gt;: not in time window. 10/22/2004 22:00:00 10/23/2004 06:59:00&lt;BR /&gt;
&lt;BR /&gt;
The task then runs each day @ 10pm but each time goes into a pending state.&lt;BR /&gt;
&lt;BR /&gt;
any ideas as to why it delays twice following the initial clone &amp;amp; mount?&lt;/APPLIANCE_NAME&gt;</description>
    <pubDate>Fri, 22 Oct 2004 08:35:18 GMT</pubDate>
    <dc:creator>CA1201697</dc:creator>
    <dc:date>2004-10-22T08:35:18Z</dc:date>
    <item>
      <title>Business Copy delay command problem</title>
      <link>https://community.hpe.com/t5/hpe-msa-storage/business-copy-delay-command-problem/m-p/442597#M893</link>
      <description>I have a business copy task configured that takes a snapclone and mounts this then has a 82000+ second delay (23hours) before the undo.&lt;BR /&gt;
&lt;BR /&gt;
On its first run the clone and mount works fine but when the undo runs 23 hours later it delays again for a 2nd 23hr period before finally completing the undo.&lt;BR /&gt;
&lt;BR /&gt;
The job is then scheduled in automation manager to run daily @ 10pm but on the second day it errors and sits pending with the following example process status:&lt;BR /&gt;
'&lt;APPLIANCE_NAME&gt;: not in time window. 10/22/2004 22:00:00 10/23/2004 06:59:00&lt;BR /&gt;
&lt;BR /&gt;
The task then runs each day @ 10pm but each time goes into a pending state.&lt;BR /&gt;
&lt;BR /&gt;
any ideas as to why it delays twice following the initial clone &amp;amp; mount?&lt;/APPLIANCE_NAME&gt;</description>
      <pubDate>Fri, 22 Oct 2004 08:35:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-msa-storage/business-copy-delay-command-problem/m-p/442597#M893</guid>
      <dc:creator>CA1201697</dc:creator>
      <dc:date>2004-10-22T08:35:18Z</dc:date>
    </item>
  </channel>
</rss>

