Method and system for validating data integrity

Abstract

A method of validating data between a first system and at least one second system, wherein the first and second systems have corresponding data volumes, the method comprising isolating first and second data volumes in the first and second systems respectively, wherein the first and second data volumes comprise the corresponding data volumes; generating a checksum for the first and second data volumes; comparing the checksum between the first and second data volumes; and indicating an error if the checksum between the first and second data volumes is different; and inserting results into a database for reporting, for event monitoring or for statistical analysis.

What is claimed is: 
     
         1 . A method of validating data between a first system and at least one second system, wherein said first and second systems have corresponding data volumes, said method comprising:
 (a) isolating first and second data volumes in said first and second systems respectively, wherein said first and second data volumes comprise said corresponding data volumes;   (b) generating a checksum for said first and second data volumes;   (c) comparing said checksum between said first and second data volumes; and   (d) indicating an error if said checksum between said first and second data volumes is different; and   (e) inserting results into a database for reporting, for event monitoring or for statistical analysis.   
     
     
         2 . The method of  claim 1 , wherein, in step (a), isolating data comprises freezing a business copy, said business copy comprising said first and second data volumes. 
     
     
         3 . The method of  claim 1 , wherein said first and second data volumes comprise any presentable storage partitions, groups, logical unit numbers (LUNs), or sub-groupings (LUSE). 
     
     
         4 . The method of  claim 3 , wherein, in step (b) said corresponding data volumes comprise one or more LUNs in said first system and one or more corresponding LUNs in said second system. 
     
     
         5 . The method of  claim 1 , wherein step (a) comprises scanning said first and second data volumes for available LUNS. 
     
     
         6 . The method of  claim 1 , wherein said corresponding data comprises headers, and wherein step (b) comprises generating a checksum for at least one corresponding header of each of said first and second data volumes, and step (c) comprises comparing said checksum for said corresponding header between said first and second data volumes. 
     
     
         7 . The method of  claim 6 , wherein step (b) comprises reading just a minor portion of said first and second data volumes LUN and writing said checksum to a table. 
     
     
         8 . The method of  claim 6 , wherein step (b) comprises writing said checksum to an internal structure along with other pertinent data, such as LUN name, LUN size, etc. 
     
     
         9 . A system for validating data between a first system and at least one second system, wherein said first and second systems have corresponding data volumes, said system comprising:
 (a) a processor;   (b) a data store;   (c) interconnection to said first and second systems;   (d) memory operatively connected to said processor and configured to instruct said processor to execute the following steps:
 i. isolating first and second data volumes in said first and second systems respectively, wherein said first and second data volumes comprise said corresponding data volumes; 
 ii. generating a checksum for said first and second data volumes; 
 iii. comparing said checksum between said first and second data volumes; 
 iv. indicating an error if said checksum between said first and second data volumes is different; and 
 v. inserting results into a database for reporting, for event monitoring or for statistical analysis.