On an N3400 active/active w/DOT 7.3.5.1P1:
I need to move vol0 from aggr0 to aggr1 on node A (so I can nuke its aggr0).
I've done this kind of thing on a single independent node - it's fairly well-documented in the "Storage Management Guide".
Basically:
1. Create a newvol0 on the destination aggregate of adequate size
2. ndmpcopy /vol/vol0/etc over to newvol0
3. vol options newvol0 root
4. reboot
But in this situation, there's stuff on aggr1 I'd like to keep serving during this transition. I'd like it very much if I could use failover to do that.
Is it possible to pull this off with a takeover/giveback?
It seems it might be problematic what with the takeover node presumably using /vol/vol0 as the root vol and the other node booting up using /vol/newvol0 as the root vol. Would the giveback work OK?
It seems there's room here to really hose things up.
Any advice?
Anyone seen documentation on such a procedure?
R
I've done this a couple of times (although it's been on DOT 8.0.X). No problems whatsoever.
//Johan
From: "Cotton, Randall" <recotton@uif.uillinois.edumailto:recotton@uif.uillinois.edu> Date: Mon, 28 Nov 2011 12:14:13 +0100 To: "toasters@teaparty.netmailto:toasters@teaparty.net" <toasters@teaparty.netmailto:toasters@teaparty.net> Subject: moving vol0 from one aggregate to another with zero downtime using failover?
On an N3400 active/active w/DOT 7.3.5.1P1:
I need to move vol0 from aggr0 to aggr1 on node A (so I can nuke its aggr0).
I’ve done this kind of thing on a single independent node – it’s fairly well-documented in the “Storage Management Guide”.
Basically:
1. Create a newvol0 on the destination aggregate of adequate size
2. ndmpcopy /vol/vol0/etc over to newvol0
3. vol options newvol0 root
4. reboot
But in this situation, there’s stuff on aggr1 I’d like to keep serving during this transition. I’d like it very much if I could use failover to do that.
Is it possible to pull this off with a takeover/giveback?
It seems it might be problematic what with the takeover node presumably using /vol/vol0 as the root vol and the other node booting up using /vol/newvol0 as the root vol. Would the giveback work OK?
It seems there’s room here to really hose things up.
Any advice?
Anyone seen documentation on such a procedure? R
https://kb.netapp.com/support/index?page=content&id=1010991
As long as you are only serving NFS, this works REALLY well. I have used it a bunch of times.
Real easy. Step-by-step Instructions.
--tmac Tim McCarthy Principal Consultant
RedHat Certified Engineer 804006984323821 (RHEL4) 805007643429572 (RHEL5)
On Mon, Nov 28, 2011 at 6:29 AM, Johan Gislén johan.gislen@bareapp.sewrote:
I've done this a couple of times (although it's been on DOT 8.0.X). No problems whatsoever.
//Johan
From: "Cotton, Randall" recotton@uif.uillinois.edu Date: Mon, 28 Nov 2011 12:14:13 +0100 To: "toasters@teaparty.net" toasters@teaparty.net Subject: moving vol0 from one aggregate to another with zero downtime using failover?
On an N3400 active/active w/DOT 7.3.5.1P1:****
I need to move vol0 from aggr0 to aggr1 on node A (so I can nuke its aggr0).****
I’ve done this kind of thing on a single independent node – it’s fairly well-documented in the “Storage Management Guide”.****
Basically:****
Create a newvol0 on the destination aggregate of adequate size***
ndmpcopy /vol/vol0/etc over to newvol0****vol options newvol0 root****reboot****
But in this situation, there’s stuff on aggr1 I’d like to keep serving during this transition. I’d like it very much if I could use failover to do that.****
Is it possible to pull this off with a takeover/giveback?****
It seems it might be problematic what with the takeover node presumably using /vol/vol0 as the root vol and the other node booting up using /vol/newvol0 as the root vol. Would the giveback work OK?****
It seems there’s room here to really hose things up.****
Any advice?****
Anyone seen documentation on such a procedure?****
R****
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Yes, it is possible to do using failover.
In your example partner will use “newvol0” as root.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Cotton, Randall Sent: Monday, November 28, 2011 3:14 PM To: toasters@teaparty.net Subject: moving vol0 from one aggregate to another with zero downtime using failover?
On an N3400 active/active w/DOT 7.3.5.1P1:
I need to move vol0 from aggr0 to aggr1 on node A (so I can nuke its aggr0).
I’ve done this kind of thing on a single independent node – it’s fairly well-documented in the “Storage Management Guide”.
Basically:
1. Create a newvol0 on the destination aggregate of adequate size
2. ndmpcopy /vol/vol0/etc over to newvol0
3. vol options newvol0 root
4. reboot
But in this situation, there’s stuff on aggr1 I’d like to keep serving during this transition. I’d like it very much if I could use failover to do that.
Is it possible to pull this off with a takeover/giveback?
It seems it might be problematic what with the takeover node presumably using /vol/vol0 as the root vol and the other node booting up using /vol/newvol0 as the root vol. Would the giveback work OK?
It seems there’s room here to really hose things up.
Any advice?
Anyone seen documentation on such a procedure? R
https://kb.netapp.com/support/index?page=content&id=1010097
The guide walks through both stand-alone and HA configurations regarding the reboot. I've followed it to a T numerous times across both 7.x and 8.x without issue.
Takeovers and givebacks work just fine for the reboot. You'll see the new mailbox disks be marked on both the partner and active filer consoles once you give your new vol0 the root option.
Also, this may not be an issue since you're running 7.x, but I ran into an issue with 8.0.1GA specifically on IBM N-Series in the past where it would act like there is no RC or Hosts file after the reboot, even though you could verify that they were present before and after the ndmpcopy. I had to use vol copy instead to resolve the issue, although this wouldn't work moving from a 32-bit to 64-bit aggregate which you can't do anyways in 7.x.
Here's my Communities post on the issue: https://communities.netapp.com/message/51023#51023
Note that I've never run into this problem on FAS boxes running the same version of code, or any other version of code for that matter - newer or older.
From: toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net] On Behalf Of Borzenkov, Andrey Sent: Monday, November 28, 2011 5:44 AM To: Cotton, Randall; toasters@teaparty.net Subject: RE: moving vol0 from one aggregate to another with zero downtime using failover?
Yes, it is possible to do using failover.
In your example partner will use "newvol0" as root.
--- With best regards
Andrey Borzenkov Senior system engineer Service operations
From: toasters-bounces@teaparty.netmailto:toasters-bounces@teaparty.net [mailto:toasters-bounces@teaparty.net]mailto:[mailto:toasters-bounces@teaparty.net] On Behalf Of Cotton, Randall Sent: Monday, November 28, 2011 3:14 PM To: toasters@teaparty.netmailto:toasters@teaparty.net Subject: moving vol0 from one aggregate to another with zero downtime using failover?
On an N3400 active/active w/DOT 7.3.5.1P1:
I need to move vol0 from aggr0 to aggr1 on node A (so I can nuke its aggr0).
I've done this kind of thing on a single independent node - it's fairly well-documented in the "Storage Management Guide".
Basically:
1. Create a newvol0 on the destination aggregate of adequate size
2. ndmpcopy /vol/vol0/etc over to newvol0
3. vol options newvol0 root
4. reboot
But in this situation, there's stuff on aggr1 I'd like to keep serving during this transition. I'd like it very much if I could use failover to do that.
Is it possible to pull this off with a takeover/giveback?
It seems it might be problematic what with the takeover node presumably using /vol/vol0 as the root vol and the other node booting up using /vol/newvol0 as the root vol. Would the giveback work OK?
It seems there's room here to really hose things up.
Any advice?
Anyone seen documentation on such a procedure? R
-
Borzenkov, Andrey -
Chris Muellner -
Cotton, Randall -
Johan Gislén -
tmac