Hey folks, I have an old filer that I can't do a firmware upgrade on (it's being replaced in the next 6 months) where I need to move data from a qtree to its own volume. I would like to investigate the ndmpcopy command for this, however when I do this, the one CLI interactive session that the filer has is taken up. We can't do any more interactive commands on the filer, and if we press ctrl-c, the ndmpcopy is killed.
I don't want to test this on my prod box and my nonprod boxes are all running newer firmware, but does anyone know whether we can kick off an ndmpcopy using a non-interactive command? Would we be able to cancel it after starting it?
Thanks,
Basil
Hi Basil,
* Yes you can kick off ndmpcopy via rsh or ssh. You can check the progress by
*ndmpd probe [session]*
as usual, there's the general info without giving it the session and more info with the session mentioned. And then there's
*ndmpd kill 'session' *
and
*ndmpd killall*
to cancel things...
* If you have a SP/BMC/RLM on your system (and configured) and have '*options telnet.distinct.enable on*', you can open a second session to your system. Just log into your SP/BMC/RLM with a user that has login-sp capabilities (member of the local admin group, 'naroot' with root password, if all else fails...) and issue 'system console'...
Hope that helps
Sebastian
On 11/27/2014 7:57 PM, Basil wrote:
Hey folks, I have an old filer that I can't do a firmware upgrade on (it's being replaced in the next 6 months) where I need to move data from a qtree to its own volume. I would like to investigate the ndmpcopy command for this, however when I do this, the one CLI interactive session that the filer has is taken up. We can't do any more interactive commands on the filer, and if we press ctrl-c, the ndmpcopy is killed.
I don't want to test this on my prod box and my nonprod boxes are all running newer firmware, but does anyone know whether we can kick off an ndmpcopy using a non-interactive command? Would we be able to cancel it after starting it?
Thanks,
Basil
Toasters mailing list Toasters@teaparty.net http://www.teaparty.net/mailman/listinfo/toasters
Thanks for the help :) As for my rlm, I think it's broken. I used to be able to get in with naroot, but while the rlm IP address still pings, I can't ssh to it any more. I'll be very happy when I'm onto the new system and can do firmware updates again.
On Fri, Nov 28, 2014 at 3:01 AM, Sebastian Goetze spgoetze@gmail.com wrote:
Hi Basil,
- Yes you can kick off ndmpcopy via rsh or ssh. You can check the progress
by
*ndmpd probe [session]*
as usual, there's the general info without giving it the session and more info with the session mentioned. And then there's
*ndmpd kill 'session' *
and
*ndmpd killall*
to cancel things...
- If you have a SP/BMC/RLM on your system (and configured) and have '*options
telnet.distinct.enable on*', you can open a second session to your system. Just log into your SP/BMC/RLM with a user that has login-sp capabilities (member of the local admin group, 'naroot' with root password, if all else fails...) and issue 'system console'...
Hope that helps
Sebastian
On 11/27/2014 7:57 PM, Basil wrote:
Hey folks, I have an old filer that I can't do a firmware upgrade on (it's being replaced in the next 6 months) where I need to move data from a qtree to its own volume. I would like to investigate the ndmpcopy command for this, however when I do this, the one CLI interactive session that the filer has is taken up. We can't do any more interactive commands on the filer, and if we press ctrl-c, the ndmpcopy is killed.
I don't want to test this on my prod box and my nonprod boxes are all running newer firmware, but does anyone know whether we can kick off an ndmpcopy using a non-interactive command? Would we be able to cancel it after starting it?
Thanks,
Basil
Toasters mailing listToasters@teaparty.nethttp://www.teaparty.net/mailman/listinfo/toasters
-
Basil -
Sebastian Goetze