- Community Home
- >
- Storage
- >
- Midrange and Enterprise Storage
- >
- StoreVirtual Storage
- >
- Problem with P4500 Volume move between Clusters in...
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
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
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
05-09-2014 09:22 AM - last edited on 05-11-2014 07:23 PM by Lisa198503
05-09-2014 09:22 AM - last edited on 05-11-2014 07:23 PM by Lisa198503
Problem with P4500 Volume move between Clusters in the same Management Group
I have one Management Group with 2 clusters (4 nodes each). One Cluster is 9.5, other is 11.0.
When i edit the volume to move it from one cluster to another, immediately one of the dbs on SQL server 2008R2 on the client where the volume is attached to, becomes "Suspect". It is not in any particular order which database becomes suspect. There is SQL thread doing log flushes is at that database which fails and makes the db suspect.
I am looking for answers from HP or anyone faced with this issue and if there is a way around it or a DSM patch to get around this situation.
P.S. This thread has been moved from Storage Area Networks (SAN) (Small and Medium Business) to HP StoreVirtual Storage / LeftHand. -HP Forum Moderator