This is quite an extensive request! As you can probably guess data migrations are often a major project and each one is approached as a unique set of challenges. We have an expert team of Professional Services folks who work with our customers and partners to ensure the success of their migrations. Your list is spot on as the initial list of tools, but the full range of considerations, challenges, opportunities and details are too extensive to clearly summarize here.
If you are looking at performing a migration or offering migration assistance, I would recommend you speak to someone on our Professional Services team to see how we can best meet your needs!
TeraCopy is handy if you like Windows GUI. Can be set to verify CRC after copy. Free version does not produce written log, but will show CRC errors so you can go back and re-copy bad files. Will copy empty files, which are not a good thing on an Isilon that creates 128K minimum file sizes. Try to filter those out first.
Clarification to davek's post - OneFS does not 'create 128K minimum file sizes'. That's a myth, unfortunately perpetuated for FUD purposes by competitors. It's untrue.
The minimum POSIX file size on OneFS is zero bytes. Essentially, this is a file containing metadata but no data. OneFS will allocate and consume inodes (512 bytes or 8K bytes, inode extension block) as required by the protection level as well as data blocks (8K), similarly. For example, a file of 7,168 bytes (7KB) actual POSIX size will consume (3*512) +(3*8K) = 25.5K on disk at the default 2:1 protection level.
Too many people conflate the default disk stripe size of 128KB with the file size. They are two completely different things.
Now, as far as the 'best' data migration tools, that's a value judgment. Bottom line is this; any migration tool must deliver the exact same metadata and data from the source to the target, and be verifiable as well. Some tools are better at insuring correctness of metadata than others, while 'slower'; other tools are 'faster', i.e. can deliver higher throughput from source to target due to techniques like threading or parallelization, but lack complete metadata transfer. As in many IT endeavors, YMMV.
cadiletta
1 Rookie
•
106 Posts
0
April 30th, 2014 14:00
This is quite an extensive request! As you can probably guess data migrations are often a major project and each one is approached as a unique set of challenges. We have an expert team of Professional Services folks who work with our customers and partners to ensure the success of their migrations. Your list is spot on as the initial list of tools, but the full range of considerations, challenges, opportunities and details are too extensive to clearly summarize here.
If you are looking at performing a migration or offering migration assistance, I would recommend you speak to someone on our Professional Services team to see how we can best meet your needs!
dynamox
9 Legend
•
20.4K Posts
0
April 30th, 2014 17:00
plug to sell PS services on customer support forum ?
david_knapp
1 Rookie
•
122 Posts
0
May 2nd, 2014 07:00
TeraCopy is handy if you like Windows GUI. Can be set to verify CRC after copy. Free version does not produce written log, but will show CRC errors so you can go back and re-copy bad files. Will copy empty files, which are not a good thing on an Isilon that creates 128K minimum file sizes. Try to filter those out first.
peglarr
99 Posts
0
May 3rd, 2014 07:00
Clarification to davek's post - OneFS does not 'create 128K minimum file sizes'. That's a myth, unfortunately perpetuated for FUD purposes by competitors. It's untrue.
The minimum POSIX file size on OneFS is zero bytes. Essentially, this is a file containing metadata but no data. OneFS will allocate and consume inodes (512 bytes or 8K bytes, inode extension block) as required by the protection level as well as data blocks (8K), similarly. For example, a file of 7,168 bytes (7KB) actual POSIX size will consume (3*512) +(3*8K) = 25.5K on disk at the default 2:1 protection level.
Too many people conflate the default disk stripe size of 128KB with the file size. They are two completely different things.
Now, as far as the 'best' data migration tools, that's a value judgment. Bottom line is this; any migration tool must deliver the exact same metadata and data from the source to the target, and be verifiable as well. Some tools are better at insuring correctness of metadata than others, while 'slower'; other tools are 'faster', i.e. can deliver higher throughput from source to target due to techniques like threading or parallelization, but lack complete metadata transfer. As in many IT endeavors, YMMV.
chjatwork
2 Intern
•
356 Posts
0
March 7th, 2017 04:00
/bump