<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">I had to do this twice too. Once i had to copy a 4 PB filesystem as fast as possible when NSD disk descriptors were corrupted and shutting down GPFS would have led to me loosing those files forever, and the other was a regular maintenance but had to copy similar data in less time.
<div><br /></div>
<div>In both the cases, i just used GPFS provided util scripts in /usr/lpp/mmfs/samples/util/  . These could be run only as root i believe. I wish i could give them to users to use.</div>
<div><br /></div>
<div>I had used few of those scripts like tsreaddir which used to be really fast in listing all the paths in the directories. It prints full paths of all files along with there inodes etc. I had modified it to print just the full file paths.</div>
<div><br /></div>
<div>I then use these paths and group them up in different groups which gets fed into a array jobs to the SGE/LSF cluster.</div>
<div>Each array jobs basically uses GNU parallel and running something similar to rsync -avR . The \u201c-R\u201d option basically creates the directories as given. </div>
<div>Of course this worked because i was using the fast private network to transfer between the storage systems. Also i know that cp or tar might be better than rsync with respect to speed, but rsync was convenient and i could always start over again without checkpointing or remembering where i left off previously.</div>
<div><br /></div>
<div>Similar to how Bill mentioned in the previous email, but i used gpfs util scripts and basic GNU parallel/rsync, SGE/LSF to submit jobs to the cluster as superuser. It used to work pretty well.</div>
<div><br /></div>
<div>Since then - I constantly use parallel and rsync to copy large directories.</div>
<div><br /></div>
<div>Thank you,</div>
<div>Lohit</div>
</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
On Mar 8, 2019, 7:43 AM -0600, William Abbott <babbott@rutgers.edu>, wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">We had a similar situation and ended up using parsyncfp, which generates<br />
multiple parallel rsyncs based on file lists. If they're on the same IB<br />
fabric (as ours were) you can use that instead of ethernet, and it<br />
worked pretty well. One caveat is that you need to follow the parallel<br />
transfers with a final single rsync, so you can use --delete.<br />
<br />
For the initial transfer you can also use bbcp. It can get very good<br />
performance but isn't nearly as convenient as rsync for subsequent<br />
transfers. The performance isn't good with small files but you can use<br />
tar on both ends to deal with that, in a similar way to what Uwe<br />
suggests below. The bbcp documentation outlines how to do that.<br />
<br />
Bill<br />
<br />
On 3/6/19 8:13 AM, Uwe Falke wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">Hi, in that case I'd open several tar pipes in parallel, maybe using<br />
directories carefully selected, like<br />
<br />
tar -c <source_dir> | ssh <target_host> "tar -x"<br />
<br />
I am not quite sure whether "-C /" for tar works here ("tar -C / -x"), but<br />
along these lines might be a good efficient method. target_hosts should be<br />
all nodes haveing the target file system mounted, and you should start<br />
those pipes on the nodes with the source file system.<br />
It is best to start with the largest directories, and use some<br />
masterscript to start the tar pipes controlled by semaphores to not<br />
overload anything.<br />
<br />
<br />
<br />
Mit freundlichen Grüßen / Kind regards<br />
<br />
<br />
Dr. Uwe Falke<br />
<br />
IT Specialist<br />
High Performance Computing Services / Integrated Technology Services /<br />
Data Center Services<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
IBM Deutschland<br />
Rathausstr. 7<br />
09111 Chemnitz<br />
Phone: +49 371 6978 2165<br />
Mobile: +49 175 575 2877<br />
E-Mail: uwefalke@de.ibm.com<br />
-------------------------------------------------------------------------------------------------------------------------------------------<br />
IBM Deutschland Business & Technology Services GmbH / Geschäftsführung:<br />
Thomas Wolter, Sven Schooß<br />
Sitz der Gesellschaft: Ehningen / Registergericht: Amtsgericht Stuttgart,<br />
HRB 17122<br />
<br />
<br />
<br />
<br />
From: "Oesterlin, Robert" <Robert.Oesterlin@nuance.com<br />
To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org<br />
Date: 06/03/2019 13:44<br />
Subject: [gpfsug-discuss] Follow-up: migrating billions of files<br />
Sent by: gpfsug-discuss-bounces@spectrumscale.org<br />
<br />
<br />
<br />
Some of you had questions to my original post. More information:<br />
<br />
Source:<br />
- Files are straight GPFS/Posix - no extended NFSV4 ACLs<br />
- A solution that requires $?s to be spent on software (ie, Aspera) isn?t<br />
a very viable option<br />
- Both source and target clusters are in the same DC<br />
- Source is stand-alone NSD servers (bonded 10g-E) and 8gb FC SAN storage<br />
- Approx 40 file systems, a few large ones with 300M-400M files each,<br />
others smaller<br />
- no independent file sets<br />
- migration must pose minimal disruption to existing users<br />
<br />
Target architecture is a small number of file systems (2-3) on ESS with<br />
independent filesets<br />
- Target (ESS) will have multiple 40gb-E links on each NSD server (GS4)<br />
<br />
My current thinking is AFM with a pre-populate of the file space and<br />
switch the clients over to have them pull data they need (most of the data<br />
is older and less active) and them let AFM populate the rest in the<br />
background.<br />
<br />
<br />
Bob Oesterlin<br />
Sr Principal Storage Engineer, Nuance<br />
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Furldefense.proofpoint.com%2Fv2%2Furl%3Fu%3Dhttp-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss%26d%3DDwICAg%26c%3Djf_iaSHvJObTbx-siA1ZOg%26r%3DfTuVGtgq6A14KiNeaGfNZzOOgtHW5Lm4crZU6lJxtB8%26m%3DJ5RpIj-EzFyU_dM9I4P8SrpHMikte_pn9sbllFcOvyM%26s%3DfEwDQyDSL7hvOVPbg_n8o_LDz-cLqSI6lQtSzmhaSoI%26e&amp;data=02%7C01%7Cbabbott%40rutgers.edu%7C8cbda3d651584119393808d6a2358544%7Cb92d2b234d35447093ff69aca6632ffe%7C1%7C0%7C636874748092821399&amp;sdata=W06i8IWqrxgEmdp3htxad0euiRhA6%2Bexd3YAziSrUhg%3D&amp;reserved=0=<br />
<br />
<br />
<br />
<br />
<br />
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgpfsug.org%2Fmailman%2Flistinfo%2Fgpfsug-discuss&amp;data=02%7C01%7Cbabbott%40rutgers.edu%7C8cbda3d651584119393808d6a2358544%7Cb92d2b234d35447093ff69aca6632ffe%7C1%7C0%7C636874748092821399&amp;sdata=Pjf4RhUchThoFvWI7hLJO4eWhoTXnIYd9m7Mvf809iE%3D&amp;reserved=0<br />
<br /></blockquote>
_______________________________________________<br />
gpfsug-discuss mailing list<br />
gpfsug-discuss at spectrumscale.org<br />
http://gpfsug.org/mailman/listinfo/gpfsug-discuss<br /></blockquote>
<div></div>
</div>
</body>
</html>