Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi!
I have a bunch of vservers which are peered to a secondary site for snapvault.
I´m trying to delete two of them but keep getting error message telling me that I can´t delete a Vserver that is part of a Vserver peer or transition peer relationship.
But it´s not.
These are the steps I´ve taken.
* check and release snapmirror relationship on primary
* check and delete snapmirror relationship on secondary
* delete peer relationship (on both clusters)
* unmount namespace
* take all volumes related to vserver offline and then deleted them
* deleted the cifs server
* stopped the vserver.
But when I try to delete it , from System Manager or CLI, i get the message about peer.
When I do a vserver peer show, there is now peers on either cluster pointing to the vserver I intent to delete?
Solved! See The Solution
1 ACCEPTED SOLUTION
connoisseur has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may need to do
vserver peer transition delete -vserver vserver_anme -src-filer-name filer_name
try it and let me know
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
what does the vserver peer transition show ?
like this one ?
Cluster1::> vserver peer transition show Vserver Source Filer Multi Path Address ------- ------------ ----------------- vs1.example.com src1.example.com src1-e0b.example.com
connoisseur has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You may need to do
vserver peer transition delete -vserver vserver_anme -src-filer-name filer_name
try it and let me know
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you so very much.
This was a a legacy from a 7-mode transition we did last summer.
I checked the transition output and it pointed to an old 7-mode system.
Deleted it and now it works.
Thanks again
