RE: Large volume file move

I would expect to have object ownership issues when you move 20 million files owned by the same profile. Unless that's been fixed recently for the IFS.

Probably need to do a test perhaps. Perhaps multiple threads copying as well if you can break it down to a list of files. (perhaps list to a DB first.)

Also how do you know files don't get corrupted during copy. May need some sort of data comparison if those files are important to stay intact.

Save/restore to/from tape perhaps and then file comparison by hashing or reading bytes.

Or initial move to NAS/SAN as Rob mentioned.

Rsync also comes to mind.

Or.....leave them alone and back up your Windows server. IFS is not efficient with lots of small files.

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com


------------------------------
From: "Justin Taylor" <JUSTIN@xxxxxxxxxxxxx>
To: "MIDRANGE-L (midrange-l@xxxxxxxxxxxx)" <midrange-l@xxxxxxxxxxxx>
Date: 09/25/2018 12:55 PM
Subject: Large volume file move
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Our native document management system stores files on an external Windows
server in the same rack as our POWER7. As part of our POWER9 upgrade,
we're planning on moving those files into an iASP. We currently access
the files via an NFS share.

The obvious way to do the move is to use CPY and copy them locally over
the NFS share. Is there a better way to do this? Ballpark, we're looking
at about 20.7 million files (about 1 TB).

Also is there any way to gauge the time required? FWIW, both systems will
have dual NIC's going thru different gigabit switches.

TIA