- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- Disk Enclosures
- >
- Re: paircreate ends with PSUE status
Disk Enclosures
1752321
Members
5319
Online
108786
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2009 03:58 AM
тАО04-26-2009 03:58 AM
paircreate ends with PSUE status
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.
Thanks
Thanks
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2009 06:56 AM
тАО04-26-2009 06:56 AM
Re: paircreate ends with PSUE status
Hi,
This could help you:
http://docs.hp.com/en/B7660-90013/ch06s11.html
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01389226/c01389226.pdf
(page 142)
PSUE is suspend - The P-VOL detects a failure in the S-VOL or the link and suspends mirroring.
b) The P-VOL changes its paired volume status to PSUE and keeps track of data changes in a difference bitmap
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
├в vl, or pairresync command to update the P-VOL data by copying all data, or copying
differential data only).
This could help you:
http://docs.hp.com/en/B7660-90013/ch06s11.html
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01389226/c01389226.pdf
(page 142)
PSUE is suspend - The P-VOL detects a failure in the S-VOL or the link and suspends mirroring.
b) The P-VOL changes its paired volume status to PSUE and keeps track of data changes in a difference bitmap
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
├в vl, or pairresync command to update the P-VOL data by copying all data, or copying
differential data only).
the pain is one part of the reality
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2009 08:53 AM
тАО04-28-2009 08:53 AM
Re: paircreate ends with PSUE status
You might also check your horcm.conf files.
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.
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.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP