It is possible to offline aggregate with volumes, but there is no point in doing it. Just reassign in maintenance mode and connect online to new filer. It will come up as foreign and offline anyway.
?????????? ? iPhone
2 ????. 2016 ?., ? 19:33, Douglas Siggins <siggins@gmail.commailto:siggins@gmail.com> ???????(?):
That looks about right, although I would just reassign in maint mode on the new head. I am not sure if its possible to offline an aggr while its volumes are online (save yourself the trouble).
Check the versions of 7-mode of both heads, its probably a good idea to have them be the same versions (or very close)!
On Tue, Feb 2, 2016 at 8:56 AM, Martin <martin@leggatt.me.ukmailto:martin@leggatt.me.uk> wrote: Hi,
I have one 7-mode Filer that I will be decommissioning which has data on it I need to migrate to another 7-mode Filer. We don't have space to mirror the data to the new Filer, want to reuse the shelves on the new Filer and this is a quicker cut over.
The four DS4243 shelves have a single aggregate (aggr0) with various volumes on it (exported via NFS) including the root volume for the controller (vol0).
I found the KB on moving shelves and aggregates between controllers but it doesn't mention what to do about a Filer that has vol0 and root aggr on the shelves.
My plan is:
1. Disable disk auto assign on both source and destination Filer on both controllers options disk.auto_assign off
1. Reboot the source controller into maintenance mode 2. Offline aggr0 aggr offline aggr0
3. Uknown the disks on the shelves on the source controller disk assign disk_name -s unowned -f
4. Shutdown the Source Filer and power off along with shelves
4. Power down the destination Filer and add SAS card to new Filer (not enough SAS ports for new loop)
5. Physically moves shelves from source Filer to destination Filer
6. Cable shelves and change shelf IDs along with a powercycle to ensure shelf IDs don't conflict
7. Assign the disks on the new Filer disk assign disk_name
8. As the aggregate is aggr0 and new Filer also has aggr0 it gets renamed to aggr0(1) and foreign
9. Check the status of the new aggregate aggr status aggr_name
10. Rename the new aggregate from aggr0(1) to aggr1
aggr rename aggr0(1) aggr1
11. Online the aggregate on the destination Filer as it is longer labelled as foreign aggregate.
aggr online aggr1
12. Check the aggregate status on the destination Filer
aggr status aggr1
13. Export the volumes on the destination Filer via /etc/exports and exportfs -r
-- View this message in context: http://network-appliance-toasters.10978.n7.nabble.com/Moving-shelves-with-ro... Sent from the Network Appliance - Toasters mailing list archive at Nabble.comhttp://Nabble.com. _______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
_______________________________________________ Toasters mailing list Toasters@teaparty.netmailto:Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters