I'm certain Open Replicator supports all of the arrays listed (you may need to bump code levels if they are REALLY old) so supportability should not be an issue.
If you go under Documentation you should be able to find plenty of Open Replicator documentation or at least search and find white papers discussing how it works.
Selecting the tool comes down to the following factors (in my opinion):
1) Tolerance to outage time (can the host be down for 2 hours to migrate? 2) Tools available (do you own any of these tools today) - $$$ 3) Comfort level using tools (if you are not using Professional Services)
We went through a similar migration (few more hosts but similar mix) and used Open Replicator for a majority of the environments. The one downside in our view with Open Migrator is that you ended-up having to install something on each host which required reboots to install/uninstall.
With Open Replicator you sustain a slightly longer outage to get the copies rolling, but for the most part it is transparent to the host. For your UNIX hosts your paths will change, but a simple remove/rebuild device operation and/or export/import operations on your volume groups should do the trick. Your Windows and VM host should be fat, dumb and happy.
The big downside with Open Replicator is there is a lot of legwork to get all of the correct device mappings setup and going.
Hope this at least gives you a good start. I could attach some whitepapers for Open Replicator if you are unable to find any.
Open replicator supports wide range of storage arrays including third party vendor but the control will be always with VMAX (Symmetrix ) arrays so it will not fit for your setup .so you can use SAN copy to migrate data between Clariion's where open migrator is host based migration tool .
bodnarg
2 Intern
•
385 Posts
1
August 29th, 2008 05:00
If you go under Documentation you should be able to find plenty of Open Replicator documentation or at least search and find white papers discussing how it works.
Selecting the tool comes down to the following factors (in my opinion):
1) Tolerance to outage time (can the host be down for 2 hours to migrate?
2) Tools available (do you own any of these tools today) - $$$
3) Comfort level using tools (if you are not using Professional Services)
We went through a similar migration (few more hosts but similar mix) and used Open Replicator for a majority of the environments. The one downside in our view with Open Migrator is that you ended-up having to install something on each host which required reboots to install/uninstall.
With Open Replicator you sustain a slightly longer outage to get the copies rolling, but for the most part it is transparent to the host. For your UNIX hosts your paths will change, but a simple remove/rebuild device operation and/or export/import operations on your volume groups should do the trick. Your Windows and VM host should be fat, dumb and happy.
The big downside with Open Replicator is there is a lot of legwork to get all of the correct device mappings setup and going.
Hope this at least gives you a good start. I could attach some whitepapers for Open Replicator if you are unable to find any.
vamsi3
50 Posts
0
August 29th, 2008 06:00
spamulap
1 Rookie
•
28 Posts
0
September 12th, 2008 10:00
yashrajmohite
2 Posts
0
January 31st, 2017 04:00
Open replicator supports wide range of storage arrays including third party vendor but the control will be always with VMAX (Symmetrix ) arrays so it will not fit for your setup .so you can use SAN copy to migrate data between Clariion's where open migrator is host based migration tool .