Greetings,
Is it acceptable to use ssh from an admin host to run ndmpcopy and vol copy
commands?
It seems to work initially, but both seem to die after varying periods of
time with no useful explanations in the log files. I found a KB about
someone connecting to the filer and running ctrl-c thinking the console is
idle, but that doesn't apply here unless an ssh command from a cron job or
something has the same effect. ndmpd status and vol copy status verify
that there are no copies running.
All filers are 8.1.2P4, source is a 6080, destination is a 6290, 10G
networking on both.
I'm doing restore time tests of entire volumes using various methods and
these 2 are part of the list. The vol copy ran for ~10 minutes out of the
466 estimated, then stopped. No errors on the command line. It does run,
so all the host.equiv entries and permissions are good. I'm sure it did
not do the 11TB in 10 minutes :-)
The ndmpcopy command ran for ~80 minutes and silently quit. It restored
217G, almost all are in smaller directories. The larger directories
didn't show up and there are no abort messages in the logs. They just quit
logging.
For the ndmpcopy I had a script do an ndmpcopy for each directory (9
total). It looked like multiple ones were running at the same time which
seems OK. I was hoping to use parallel threads to speed things up.
Any ideas on the silent failures?
Thanks,
Jeff
--
Jeff Cleverley
Unix Systems Administrator
4380 Ziegler Road
Fort Collins, Colorado 80525
970-288-4611