<?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 paircreate ends with PSUE status in Disk Enclosures</title>
    <link>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408197#M30958</link>
    <description>I have succesfully created many pairs but I have three taht end up with a state of PSUE (Initial Copy failure). I can't work out why this is happening...The pvol and svol are identical...The interesting thing is that they are all in the same CU. All other paircreates are fine except those in CU 5.&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
    <pubDate>Sun, 26 Apr 2009 10:58:57 GMT</pubDate>
    <dc:creator>Paul Hawkins</dc:creator>
    <dc:date>2009-04-26T10:58:57Z</dc:date>
    <item>
      <title>paircreate ends with PSUE status</title>
      <link>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408197#M30958</link>
      <description>I have succesfully created many pairs but I have three taht end up with a state of PSUE (Initial Copy failure). I can't work out why this is happening...The pvol and svol are identical...The interesting thing is that they are all in the same CU. All other paircreates are fine except those in CU 5.&lt;BR /&gt;Thanks&lt;BR /&gt;</description>
      <pubDate>Sun, 26 Apr 2009 10:58:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408197#M30958</guid>
      <dc:creator>Paul Hawkins</dc:creator>
      <dc:date>2009-04-26T10:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: paircreate ends with PSUE status</title>
      <link>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408198#M30959</link>
      <description>Hi,&lt;BR /&gt;This could help you:&lt;BR /&gt;&lt;A href="http://docs.hp.com/en/B7660-90013/ch06s11.html" target="_blank"&gt;http://docs.hp.com/en/B7660-90013/ch06s11.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01389226/c01389226.pdf" target="_blank"&gt;http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01389226/c01389226.pdf&lt;/A&gt;&lt;BR /&gt;(page 142)&lt;BR /&gt;&lt;BR /&gt;PSUE is suspend - The P-VOL detects a failure in the S-VOL or the link and suspends mirroring.&lt;BR /&gt;&lt;BR /&gt;b) The P-VOL changes its paired volume status to PSUE and keeps track of data changes in a difference bitmap&lt;BR /&gt;&lt;BR /&gt;c. after the S-VOL or the link recover from the failure, the updated P-VOL is fed back to the S-VOL (pairsplit â  S, paircreate&lt;BR /&gt;â  vl, or pairresync command to update the P-VOL data by copying all data, or copying&lt;BR /&gt;differential data only).&lt;BR /&gt;</description>
      <pubDate>Sun, 26 Apr 2009 13:56:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408198#M30959</guid>
      <dc:creator>IBaltay</dc:creator>
      <dc:date>2009-04-26T13:56:58Z</dc:date>
    </item>
    <item>
      <title>Re: paircreate ends with PSUE status</title>
      <link>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408199#M30960</link>
      <description>You might also check your horcm.conf files.&lt;BR /&gt;&lt;BR /&gt;I have a typo in one of mine that esentially defined the same svol for two different pvols in the same group, which caused the same error.&lt;BR /&gt;</description>
      <pubDate>Tue, 28 Apr 2009 15:53:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/disk-enclosures/paircreate-ends-with-psue-status/m-p/4408199#M30960</guid>
      <dc:creator>Bill Rothanburg</dc:creator>
      <dc:date>2009-04-28T15:53:34Z</dc:date>
    </item>
  </channel>
</rss>

