<?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 SSSU question - Continuous Access SUSPEND / NOSUSPEND in Storage Software</title>
    <link>https://community.hpe.com/t5/storage-software/sssu-question-continuous-access-suspend-nosuspend/m-p/3534459#M567</link>
    <description>We would like to script the daily resync of a Continuous Access (DRM) pair on our EVA5000. We are running VCS 3025.&lt;BR /&gt;&lt;BR /&gt;On our XP arrays, this can be easily accomplished using HORCM, but there doesn't seem to be the same level of robustness with SSSU. For example, how do we know that the CA pairs have reached 100% pair status before suspending them again? In HORCM, we would issue a command as follows:&lt;BR /&gt;&lt;BR /&gt;"pairresync -g CAPAIR -l"&lt;BR /&gt;"pairevtwait -g CAPAIR -s PAIR -t 15"&lt;BR /&gt;"pairsplit -g CAPAIR -l"&lt;BR /&gt;&lt;BR /&gt;These three statements will resync the pairs, wait until all disks reach PAIR status (checking every 15 seconds), then suspend the CA. &lt;BR /&gt;&lt;BR /&gt;I do see that I can run 'set DR_group "\Data Replication\dr001" SUSPEND (or NOSUSPEND)- but how can I tell using a script at 3am when to re-suspend the pairs?&lt;BR /&gt;&lt;BR /&gt;I guess I am looking for an equivalent set of commands for SSSU - and looking for error checking and error handling logic. &lt;BR /&gt;&lt;BR /&gt;Anyone?</description>
    <pubDate>Thu, 28 Apr 2005 19:00:12 GMT</pubDate>
    <dc:creator>Chris Bennett_9</dc:creator>
    <dc:date>2005-04-28T19:00:12Z</dc:date>
    <item>
      <title>SSSU question - Continuous Access SUSPEND / NOSUSPEND</title>
      <link>https://community.hpe.com/t5/storage-software/sssu-question-continuous-access-suspend-nosuspend/m-p/3534459#M567</link>
      <description>We would like to script the daily resync of a Continuous Access (DRM) pair on our EVA5000. We are running VCS 3025.&lt;BR /&gt;&lt;BR /&gt;On our XP arrays, this can be easily accomplished using HORCM, but there doesn't seem to be the same level of robustness with SSSU. For example, how do we know that the CA pairs have reached 100% pair status before suspending them again? In HORCM, we would issue a command as follows:&lt;BR /&gt;&lt;BR /&gt;"pairresync -g CAPAIR -l"&lt;BR /&gt;"pairevtwait -g CAPAIR -s PAIR -t 15"&lt;BR /&gt;"pairsplit -g CAPAIR -l"&lt;BR /&gt;&lt;BR /&gt;These three statements will resync the pairs, wait until all disks reach PAIR status (checking every 15 seconds), then suspend the CA. &lt;BR /&gt;&lt;BR /&gt;I do see that I can run 'set DR_group "\Data Replication\dr001" SUSPEND (or NOSUSPEND)- but how can I tell using a script at 3am when to re-suspend the pairs?&lt;BR /&gt;&lt;BR /&gt;I guess I am looking for an equivalent set of commands for SSSU - and looking for error checking and error handling logic. &lt;BR /&gt;&lt;BR /&gt;Anyone?</description>
      <pubDate>Thu, 28 Apr 2005 19:00:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/sssu-question-continuous-access-suspend-nosuspend/m-p/3534459#M567</guid>
      <dc:creator>Chris Bennett_9</dc:creator>
      <dc:date>2005-04-28T19:00:12Z</dc:date>
    </item>
    <item>
      <title>Re: SSSU question - Continuous Access SUSPEND / NOSUSPEND</title>
      <link>https://community.hpe.com/t5/storage-software/sssu-question-continuous-access-suspend-nosuspend/m-p/3534460#M568</link>
      <description>Chris,&lt;BR /&gt;&lt;BR /&gt;Why do you want to resync ???? Are you using the remote site for backup purposes or something like that ?&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;Erwin van Londen</description>
      <pubDate>Wed, 15 Jun 2005 02:32:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/storage-software/sssu-question-continuous-access-suspend-nosuspend/m-p/3534460#M568</guid>
      <dc:creator>Erwin van Londen</dc:creator>
      <dc:date>2005-06-15T02:32:31Z</dc:date>
    </item>
  </channel>
</rss>

