- Community Home
- >
- Storage
- >
- Entry Storage Systems
- >
- MSA Storage
- >
- P2000 G3 - 'orphaned' replication destination volu...
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
01-23-2012 02:36 AM
01-23-2012 02:36 AM
P2000 G3 - 'orphaned' replication destination volumes
Hi,
Upgrading the firmware on my two P2000 G3s broke a couple of existing replication sets I had configured - no big deal, they were only test ones anyway. I found that the MSA the primary volumes were sitting on was erroring a lot because of the change to replication configuration, so I broke the replication at the source end, the errors stopped and I assumed everything was OK. I deleted the primary volumes as they were no longer required
I subsequently logged onto the destination MSA and found that the secondary volumes still exist, and that they still reference the remote primary volumes, even though they're actually offline because they don't exist anymore. I've tried re-running the 'detach replication set' from the destination end, which appeared to work but the remote primary volume and replication images are still listed. I can't delete the replication images or the snap pool, and I can't delete the volumes or vdisk containing them because the replication set still exists, as far as the the destination MSA is concerned. I've tried doing it via the CLI as well as through the SMU and get no different results.
Any ideas how I can get rid of these volumes?