#Emcopy for linux full#
#Emcopy for linux software#

#Emcopy for linux software#

In addition, there is no long-term commitment to our data migration system once the data is copied and validated on the target and the applications have been reconfigured and tested our software is removed from the environment and the Centera can be retired.

#Emcopy for linux full#

Our migrations are designed to be fast (3TB to 6+TB transferred per day, or even more for high-volume migrations), compliant (retention propagation to FLR/SmartLock and full chain-of-custody reporting), safe (no production impact or outage required during data transfer) and application transparent (we handle reconfiguring the Centera applications to вЂseeвЂ™ the migrated NAS data as if it had always lived on NAS). We have a sweet spot in migrating data from EMC Centera to Isilon (along with other EMC targets such as VNX and Data Domain). My company, Interlock Technology, is an EMC service partner located in Waltham MA that specializes in CAS-to-NAS migrations. ItвЂ™s imaginable that they could develop a migrationtool for extracting data out of Centera into a filesystem рџ‰ They have written a powerful administration and migrating tool with which data could be migrated between CenteraвЂ™s. ThereвЂ™s a small company in belgium called Datadobi who are the real experts in Centera. The alternative is that the application needs to read each stored object from centera and rewrite it on a filesystem.

If a migration from Centera to a filesystem like Isilon is planned, the CA must be replaced by a pathname or URL so that an application could access previous data as if it has written it always into a filesystem. The idea of putting these things together into Isilon is seductive рџ‰ Unfortunately there is one specific feature with the data written into Centera: Centera returns a contentaddress (CA) to the application which is the reference for future access to the data. I would urge the reader that posed the question to approach their EMC account team and/or partner with the questions and they can then work together to make this a successful migration.Д¬entera is running into an ambigous future due to the big disks today and hence needs at least an alternative for a better scalable system which could store filesystem and contentadressed data in one system. Again, dependent on the applications and use cases for the systems. Migrating from Centera can be complex due to the nature of the system, itвЂ™s is an object storage system first and foremost, which means that the applications that store their objects on them needs to be adapted in the process so that they understand where to go looking for the objecs upon recall.ДЄlso, Centera is frequently used as a compliance storage system, which in turn means that there might be chain of custody for objects involved as well.ДЄll of it is rather multi-dimensional and not really easy to give an answer to off the bat.ДЇor Celerra on the other hand, itвЂ™s вЂњjustвЂќ files, and they can be migrated as per more standardized practices, generally by copying over the network(s) involved and then pointing over the exports/file shares to that. I have a hard time understanding what is so perverse in that this isnвЂ™t a click-click process.

Migrations can be tricky subjects and itвЂ™s best to try and understand all aspects of it, both technology, process and business. Hi, I work for EMC and can try to bring some insight into this.