Hello Toasters,
We are going to move some disk shelf chains that contain aggregates to new heads. The old heads are a CF pair of FAS3050s running 7.3.1.1 and the new heads are a CF pair of FAS3170s running 7.3.2. We will not replace the existing root volumes on the 3170s.
I am planning to shut everything down and reconnect the shelf chains.
When I power everything back up, the new heads will boot and find a lot more disks. Will they recognize the aggregates? From the aggr man page it looks like the aggregates will be recognized as "foreign" and I will need to run "aggr online".
The 3050 does not use software disk ownership, each head owns entire disk shelf chains. The 3170 uses software disk ownership. Any issues there? Do I need to disable disk.auto_assign on the 3170s beforehand and manually assign the disks to the correct heads? Then reboot?
Instead I could connect each shelf chain to just the 3170 head that will own it, and boot the 3170s. They should find their new disks, take ownership, and see the new aggregates. Then I could shut down, connect the shelf chains to both heads, and boot back up. Seems easier, but will it work?
Am I missing anything important?
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
What I suggest you first is to disable the software disk ownership (the option you've stated): it has caused me some issue due to "confusion" over all in a/a pairs. It's better to manually look for new disks with disk show and manually assign to the correct loop (if any different from 0) and controller.
Prior to attach the new controller/disks upgrade and align the releases to the ones present on 3170s.
Once connected (I suggest you to do it with 3170 up and running and attaching all the shelves belonging to the same aggregate/loops once at time to the right controller) and assigned the disks (disk assign...) you'll find offlined aggregates if the old have the same name of some other present in the 3170 and renamed to something like 'aggr0 (2)' or because foreign. Once renamed to what you like you will be able to bring them online and perform the ops you need.
Regards
-----Messaggio originale----- Da: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] Per conto di Steve Losen Inviato: lunedì 23 agosto 2010 13:39 A: toasters@mathworks.com Oggetto: Moving disk shelves to new controller
Hello Toasters,
We are going to move some disk shelf chains that contain aggregates to new heads. The old heads are a CF pair of FAS3050s running 7.3.1.1 and the new heads are a CF pair of FAS3170s running 7.3.2. We will not replace the existing root volumes on the 3170s.
I am planning to shut everything down and reconnect the shelf chains.
When I power everything back up, the new heads will boot and find a lot more disks. Will they recognize the aggregates? From the aggr man page it looks like the aggregates will be recognized as "foreign" and I will need to run "aggr online".
The 3050 does not use software disk ownership, each head owns entire disk shelf chains. The 3170 uses software disk ownership. Any issues there? Do I need to disable disk.auto_assign on the 3170s beforehand and manually assign the disks to the correct heads? Then reboot?
Instead I could connect each shelf chain to just the 3170 head that will own it, and boot the 3170s. They should find their new disks, take ownership, and see the new aggregates. Then I could shut down, connect the shelf chains to both heads, and boot back up. Seems easier, but will it work?
Am I missing anything important?
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support