I've actually used the vol and aggr rename commands frequently, not in the process of migration. My current environment was\has been in disarray before my arrival and I'm trying to go back and standardize and clean up some things.
That said, in the pretext of migration, perhaps it should be an optional thing to rename the exports/shares?
Glenn
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of Glenn Dekhayser Sent: Thursday, February 08, 2007 2:48 PM To: René Bormann; toasters@mathworks.com Cc: Fox, Adam Subject: RE: moving data from trad -> flex vols
Rene:
I have seen this behavior and have been simarly frustrated when migrating CIFS volumes from Traditional to Flexvols.
In my opinion, Netapp should NOT be renaming CIFS shares when you change volume names. They do this automatically without warning you or logging.
I know they're doing it because they think they're being helpful; but really the only time I can forsee changing volume names is if you're doing a migration like you're doing. VERY frustrating indeed.
I found myself having to document all the existing shares, and write a script that deletes, then re-creates all the shares and their permissions on the new volume. Hours of work.
Netapp, is there a way to disable this "feature" prior to renaming a volume?
Glenn (the other one)
________________________________
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com] On Behalf Of René Bormann Sent: Thursday, February 08, 2007 12:41 PM To: toasters@mathworks.com Cc: René Bormann; Fox, Adam Subject: Re: moving data from trad -> flex vols
Hello Toasters,
well, the root vol now moved to the new DS14 flex-vol.
But this night I tried to move the data (shares / lun's / exports) from the old /vol/vol0 (trad) via "ndmpcopy -l 0 /vol/vol0 /vol/vol1" and some hour later, "ndmpcopy -l 0 /vol/vol0 /vol/vol1".
Everthing was copied. All Clients where offline, and than I renamed /vol/vol0 -> /vol/vol0old and /vol/vol1 /vol/vol0. Because I thought than after the reboot all shares and luns and nfs-exports are back on /vol/vol0 but now on the new DS14.
Well I failed, I found out that the vol rename also renamed the CIFS Shares Paths and also the LUN paths. So the CIFS clients where still reading from the old FC9 (/vol/vol0old now) and the iSCSI clients where too. Because I did't terminate CIFS and NFS and iSCSI. To be honest, cool renaming feature to prevent stupid germans from losing data ;-)
So, I though be smart forget about the LUNs, they are fine, care about the shares. "CIFS terminate" and replace vol0old -> vol0 in the /etc/cifsconfig_share.cfg. "CIFS restart". "Year! I am the master !" But I was too stupid again. Because now my CIFS Clients got the shares but they could not see any data. And I got no idea why!
So I "vol rename vol0 vol1" and "vol rename vol0old vol0"
And now the CIFS clients connect back to their shares on the old FC9 again.
So whats wrong about my proceedings? And the second question to save time, how to I move the iSCSI LUNs to the new volume?
Thanks,
Rene
René Bormann wrote:
Thanks to all how answered!
Just used my sleepless night here in germany to fix it. Took me half an hour!
- René
Fox, Adam wrote:
If you are using SecureAdmin/Secure FilerView/SSL, you need to restart the secureadmin services when you cross the 7.x line. There was a major code change starting in 7.0 and the service must be manually restarted (a reboot won't do it). Start here for docs: http://now.netapp.com/NOW/knowledge/docs/ontap/rel721/html/ontap/upgrade/con... -- Adam Fox adamfox@netapp.com -----Original Message----- From: René Bormann [mailto:bormann@bbtel.de] Sent: Tuesday, February 06, 2007 5:14 PM To: toasters@mathworks.com Subject: moving data from trad -> flex vols Hello, we are running an FAS920 with FC9 shelfs with data and new empty DS14 shelfs. On the FC9 we got one volume /vol/vol0 with root and data on it. Last week we upgraded from ONTAP 6.5.6 to 7.2.1 without problems. Now we want to move our data to the DS14 shelfs. We created one aggr1 with lots of drives. After that we created two new flex vols - /vol/root (20GB) and an /vol/vol1 (1TB) for the data. We copied the root data with no clients on the filer with "ndmpcopy -l0 /vol/vol0/etc /vol/root/etc". Worked fine in 7 minutes. Than we change the booting volume with "vol options /vol/root root". Booting from it, no problem -but now by requsting http://filer-ip/na_admin just the first page came and we were not able to start the FilerView Web-App. So so we switch the root vol again with "vol options /vol/vol0 root" and FilerView works fine. In the message file we found that one: Sat Feb 3 09:16:09 CET [httpd.socket.listener.create:error]: HTTPS Initialization failure; could not create listener socket. Nothing else. Can anybody help? Thanks, René -- ----------------------------------------- Telefonkonferenzen zum Festnetzpreis! Einfach kostenlos Konferenzraum anfordern http://www.talkyoo.net ----------------------------------------- René Bormann Geschäftsführer BB Tel GmbH Jungfernstieg 30, 20354 Hamburg Register: Amtsgericht Hamburg, HRB 86074 Geschäftführer: René Bormann Tel: +49 (0) 1805 - 65 777 777 * Fax: +49 (0) 1805 - 65 777 799 * http://www.bbtel.de ----------------------------------------- * (bbtel.de 14ct/min) ** (es entstehen die Kosten, die ihre Telefongesellschaft zu einer Hamburger Festnetz-Rufnummer berechnet.) -----------------------------------------
I've actually used the vol and aggr rename commands frequently, not in the process of migration. My current environment was\has been in disarray before my arrival and I'm trying to go back and standardize and clean up some things.
That said, in the pretext of migration, perhaps it should be an optional thing to rename the exports/shares?
Glenn
You can stop ONTAP from automatically editing /etc/exports with
options nfs.export.auto-update off
Then whenever you create, delete, or rename a volume you get a warning that /etc/exports needs to be edited, but ONTAP leaves it alone.
I would "exportfs -u" the old stuff before renaming anything. Then after renaming the volumes so that the new volume has the old name, I would "exportfs -a" to export the new stuff.
As for CIFS, I am pretty sure that you need to delete your old shares before renaming the volumes, rename, and then create the shares again.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
I do something like this:
Terminate all file sharing protocols Perform the update/replication/whatever do a global search/replace in the cifsconfig_share.cfg renaming all old vols to new vols. If needed, perform the same function in exports Turn on the protocols.
works fine without having to delete and re-add (sometime 10s to a hundred) shares back in
--tmac
On 2/9/07, Stephen C. Losen scl@sasha.acc.virginia.edu wrote:
I've actually used the vol and aggr rename commands frequently, not in the process of migration. My current environment was\has been in disarray before my arrival and I'm trying to go back and standardize and clean up some things.
That said, in the pretext of migration, perhaps it should be an optional thing to rename the exports/shares?
Glenn
You can stop ONTAP from automatically editing /etc/exports with
options nfs.export.auto-update off
Then whenever you create, delete, or rename a volume you get a warning that /etc/exports needs to be edited, but ONTAP leaves it alone.
I would "exportfs -u" the old stuff before renaming anything. Then after renaming the volumes so that the new volume has the old name, I would "exportfs -a" to export the new stuff.
As for CIFS, I am pretty sure that you need to delete your old shares before renaming the volumes, rename, and then create the shares again.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
the cifs config is stored in \filer\c$\etc\cifs_config.txt (or something similar).
I use it as a template when doing a lot of manipulating of cifs files. I wonder if you made it read-only if it would stop the auto rename process?
Stephen C. Losen wrote:
I've actually used the vol and aggr rename commands frequently, not in the process of migration. My current environment was\has been in disarray before my arrival and I'm trying to go back and standardize and clean up some things.
That said, in the pretext of migration, perhaps it should be an optional thing to rename the exports/shares?
Glenn
You can stop ONTAP from automatically editing /etc/exports with
options nfs.export.auto-update off
Then whenever you create, delete, or rename a volume you get a warning that /etc/exports needs to be edited, but ONTAP leaves it alone.
I would "exportfs -u" the old stuff before renaming anything. Then after renaming the volumes so that the new volume has the old name, I would "exportfs -a" to export the new stuff.
As for CIFS, I am pretty sure that you need to delete your old shares before renaming the volumes, rename, and then create the shares again.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
-
Glenn Walker -
Jack Lyons -
Stephen C. Losen -
tmac