- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- HPE EVA Storage
- >
- Re: Mirror required status with Storage Mirroring
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
тАО03-31-2008 01:03 AM
тАО03-31-2008 01:03 AM
Mirror required status with Storage Mirroring
We have an installation of HP Storage Mirroring 4.5.0.1653.2 version. We have some Replication Sets enabled but one of them has the "Target Data State" as "Mirror Required" for ever.
Even if we empty the destination and the mirror finish again, the status of "Mirror Required" appears, but the "Replication Set" status is with their green check mark as if it was correct.
Is there a cosmetic issue or may be it a serious problem? How can we clear this error?
Thanks in advance!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2008 04:26 AM
тАО03-31-2008 04:26 AM
Re: Mirror required status with Storage Mirroring
I am not clear Ur question, could U pls inform me Ur system H/W, OS & Storage model. Then I will help U.
Thanks--Yaqub
HP Support!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-31-2008 06:12 AM
тАО03-31-2008 06:12 AM
Re: Mirror required status with Storage Mirroring
Part Number: AE452A
H/W: DL380 Storage Server SAN
OS: MS Windows 2003 Storage Server
HP Storage Mirroring: 4.5.0.1653.2
And I attach two ".jpg" into one zip file, one showing the Mirror Status, and the other showing an error from the Event Viewer if it is appliable to clarify the error.
Thank you again!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-16-2008 06:02 AM
тАО04-16-2008 06:02 AM
Re: Mirror required status with Storage Mirroring
We have a Windows 2003 SP1 Server with Storage Mirroring 4.5.0.1653.2.S. We have different server with no problems, but 2 have always the target data state "mirror required". What can we do?
Thanks for the reply.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-21-2008 08:33 AM
тАО10-21-2008 08:33 AM
Re: Mirror required status with Storage Mirroring
Are you using a seperate replication set because you want it to replicate during a different time?
If that is the reason then it appears that you will not get it to work. From what I can see setting the time window for replication is like setting it for the server to server communication and not setting it for each individual repication set. Once you create two replication sets each with different time windows it either breaks one or the other or both replication sets.
To test remove one replication set and make sure the other is working fine. then remove that replication set and make sure the other one is working fine. But both will not work together.
I wonder if this is/was changed in v5 of the software as it would make sense that people would want multiple replication sets to replicate during different times.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-18-2009 02:32 PM
тАО08-18-2009 02:32 PM
Re: Mirror required status with Storage Mirroring
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-01-2011 08:32 AM
тАО07-01-2011 08:32 AM
Re: Mirror required status with Storage Mirroring
I have the same issue... but I have the 5.2.2.2 storage Mirroring version with Full server failover option, the mirror completes because I monitored from the Replication Management Console, but when reached to 100% it change the Target data status to "Mirror Required" but on the Status it appears IDLE.
I have done all the troubleshooting for these issue that I know, start a re-mirror, run a verify, delete the replication set and create all over again, restart the target server and restart the storage mirroring service on the source.
and the same message appears when complete the mirror.
Any others ideas?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-23-2011 01:07 AM
тАО09-23-2011 01:07 AM
Re: Mirror required status with Storage Mirroring
i am facing the same issue...it seems HP feels we are missing on something...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО12-30-2011 06:46 AM
тАО12-30-2011 06:46 AM
Re: Mirror required status with Storage Mirroring
we have same problem. "Mirror Reguired" , when mirror start it's came to normal till 0.3 % after it's give "Mirror Reguired" error remain.
have any one find the solution :(