Sounds like a case for Support at Netapp.
I haven't used the jndmpcopy version yet so I'm not familiar with what you describe as "infinite incremental capabilities".
Mike Smith Escalations jerk.
----- Original Message ----- From: "Jeffrey Krueger" jkrueger@qualcomm.com To: "Mike Smith" mikesmit@netapp.com Cc: "Stephen Manley" stephen@netapp.com; "Jeff Kennedy" jlkennedy@amcc.com; jasf@lanl.gov; toasters@mathworks.com Sent: Friday, April 06, 2001 7:07 PM Subject: Re: Data Copy from Filer to Filer
The last time we tried incremental ndmpcopy, it corrupted files on the destination. We were running 5.3.4R3P2 on both filers. We did one level
0
and then a level 1. When complete, the engineers showed us many files
that
we were trashed. The appeared to be "concatenated into themselves" in random locations (my best description). We ended up rsync'ing everything to fix it.
Has anyone else seen that behavior or is it a registered bug? If so has
it
been fixed or is there a work-around? We love using ndmpcopy and would really like to use it incrementally.
Also, are there any plans to make the C source version of ndmpcopy have "infinite incremental" capabilities as the jndmpcopy version does? By
this
I mean it allows for more than 9 incremental copies.
-- Jeff
On Fri, Apr 06, 2001 at 05:57:19PM -0700, Mike Smith wrote:
One other nice feature of the ndmpcopy utility is that it allows you to run a level zero and then a level 1 once services have been shut off on the source filer. This makes for a nice almost-no interrupt transition from one system to another. One last feature to brag about is that you can ndmpcopy by tree or directory or subdirectory.
Mike Smith Escalations Jerk
----- Original Message ----- From: "Stephen Manley" stephen@netapp.com To: "Jeff Kennedy" jlkennedy@amcc.com Cc: jasf@lanl.gov; toasters@mathworks.com Sent: Friday, April 06, 2001 4:44 PM Subject: Re: Data Copy from Filer to Filer
Hi Jessica,
I'm curious why you would think filesystem fragmentation would prevent the use of NDMPcopy?
NDMPcopy, by its nature, acts as a natural file system defragmenter -- that is, the system that is the destination of the NDMPcopy has pretty much an ideal file system layout for performance.
And because the NDMPcopy data stream generator is integrated into the filer, it should be able to read a fragmented file system better than rsync...
Is your experience different than my theory, or am I missing something blindingly obvious?
Stephen Manley DAM and NDMP Circus Clown
I would imagine the most efficient method is to use snapmirror. However, if you have the problem I do which is wanting to copy
specific
data from one volume to another you use something like ndmpcopy. My particular case is special and ndmpcopy doesn't work for me either
due
to filesystem fragmentation so rsync is my only option.
~JK
Jessica Fernandez wrote:
What are your recommendations of copying data from one filer to another?
I have estimated time of 28 hours to transfer 70 GB via a copy
command
on the host machine.
I have tried to copy via CIFS accessing from NT servers using drag
and
drop. Encountered errors which halted the copy process due to
files
that were linked to incorrect locations. Unix files in the users desktop were linked to other machines and the path was invalid.
Did a
grep to locate these linked files in the user folders, and found
too
many to change one by one.
The vol copy command is only useful when copying from volume to
volume
on the same filer, correct?
I am looking for the most efficient way to move data.
Any suggestions would be great!
Jessica
JESSICA A. S. FERNANDEZ ESA-FM Facility Management E-mail: jasf@lanl.gov TA-16-661-101, MS-C933 Voice: 505-665-8051 Los Alamos National Laboratory Pager: 104-6707 Los Alamos, New Mexico
87545
FAX: 505-665-9490
--
Jeff Kennedy Unix Administrator AMCC jlkennedy@amcc.com