flipkart3

SNAPDEAL OFFERS

filpkartflash

Monday, April 25, 2016

TECNIQUES AND TOOLS FOR DATA MIGRATION

ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM, NETAPP IS REGISTERED TRADEMARK OF NETAPP
http://aix-administration.blogspot.com/p/index-of-posts-available-in-this-blog.html


 I have  done few projects of data  migration on various platforms and sources and i feel to share the idea of migration and few tools involved .

PLANNING OF MIGRATION 

Planning a migration is a pain in A** job as no matter how much you plan there is always a possibility of errors in other words there is nothing like "I have planned every thing "

Few things that i like to consider .
IF THE BACKUP IS AVAILABLE
What kind of data i have to plan , or what kind of OS /Application/Database we have to migrate .
What kinds of tools and facilities present to deliver my migration .
What are zoning and connectivity requirements .
What are space constraints
What is the down time to complete this activity , always add 5 to 6 hours depending on complexity.
Do i have end to end picture clear .
Does the customer or i have right tools to perform activity .
Does the designed solution is tested or should i go create one .
What is roll back plan and if it is rock solid .

Few things i like to do before  migration .

Collect all configuration data .
Collect all information related to system
Never delete any file , directory or whatever it could be . If required rename or move to another place .
Create a excel sheet having all the details of the environment .
Create  all the commands to be run in a note pad 
Paste the created command from the notepad to command line and copy its output in separate notepad .


 
SO 

I classify data migration in three types 

1. The Disk to Disk migration .
2.The OS level  migration .
3.Application or configuration migration .

1. The Disk to Disk migration of data involves a well defined OEM product or procedure , which is well documented or a tool which can be used to replicate disk at block level .

generally the above mentioned migration is between a Storage device to another Storage device typically of same OEM .
But if they are of different OEMS then it is a common practice to Virtualize Storage into another .
For example IBM SVC or V series , EMC V series and so on .

This is typically a movement of data from one device or location to another .It should not be confused with replication or coping of data from one source to destination .

The basic concept to migrate data from old storage is pretty simple .

a) Zone Storage A with B .
b)Create a host in Storage A  for Storage B .
c)Provide or map luns to the newly create host meant for migration .
d)Migrate luns in Storage B .

There are few proprietary tools like Netapp Snapmirror or Snapvault which can also be used to move data from one Storage to another , or Hitachi True copy or so on .

So far i have worked on IBM V series SVC and Netapp to migrate old data in my few assignments and they all wok pretty well , and simple to use and configure .

2. The hard part  "OS level  migration " 

The OS level migration may depend on whole lot of things as 
What kind of OS is being migrated
Whether it is a windows OS it is a unix OS
Os is installed in local disk or it is booted from SAN .
Does We have enough resources to test and verify .
Os has cluster or any critical application running on it .

For windows OS i found Amoei Backupper is a very good tools we had migrated windows OS and data successfully in enterprise at few places .
The other tools which i have checked are below .

http://software.lsoft.net/DiskImageTrialSetup.exe

http://www.farstone.us/download/DriveClone/DCS-11.10-GM-En-20150827.exe

For unix there are many tools to create clone or copy but i strongly believe on dd
many people complaint that dd does not shows progress but if u just put a pv in between dd command u will get progress also  for example

dd if=source path |pv|dd of=destination path 

other popular tools can be 

pv 
ddrescue and so on 

We can also use mirror and unmirror commands to migrate disk , linux as pvmove command , Aix has replacepv command and so on  .

The third type of migration cannot be limited to few lines so that i will discuss later .

 




 


Tuesday, April 5, 2016

THE ART OF TROUBLESHOOTING

ALL DOCUMENT ARE PROPERTY OF SHIVAKANT , DO NOT COPY 
IBM , AIX , HACMP , ARE REGISTERED TRADE MARK OF IBM, 
NETAPP IS REGISTERED TRADEMARK OF NETAPP
http://aix-administration.blogspot.com/p/index-of-posts-available-in-this-blog.html

 Its been 18 years that i am working with various UNIX flavors , SAN , Backups , Server , Storage ,Migration , Replication So do i have mastered in technologies certainly not . 
And about each and every project i do there is some or the other that behaves differently or does not works the way it should .

So the question arises what is the exact approach to solve a issue , so here i am writing some thing that i feel can be shared for a better approach .

1. Check whatever is configured again and again step by step there has to be some thing that you left .
2. Dont try to find solution on google straight away read and gather as much knowledge regarding the subject or the failing component .
3. Check logs for example /var/log/messages in Linux , and errpt in Aix .
4.Check for other components related with the failing component.

Enhance debugging level of logs , syslog and see details of logs , find clues  from the logs .
Some times the errors in the logs will just give a clue , search that clue in google to know more about that error or condition .


Most application like ssh , comes with their own debugging switch use them to know more about 
the output of those application . .

Advance users can use tracing application to debug output of a failing component 

FOR example "truss" command in aix and "strace" in linux to get a detailed debugging



Amazon8

Total Pageviews