device 120 and a copy of the transactions be stored on the secondary storage device 130 for security and data integrity reasons the secondary storage device 130 is preferably at a remote location relative to the replication manager 110 and the primary storage device 120 and connected to the replication manger 110 by way of a network communications link 104 the replication manager 110 may be integrated into the primary storage device 120 or may be a separate unit the replication manager 110 includes interfaces 112 a 112 b and 112 c through which it communicates and exchanges data with the host s 102 and the primary and secondary storage devices 120 and 130 the replication manager 110 further includes a memory 114 and a processor 116 for executing instructions stored in the memory 114 as will be described below the replication manager 110 may also include metadata 118 which may be stored in the memory 114 referring to fig2 and the flow chart of fig3 an embodiment of the present invention will be described a block 200 of data transactions is transferred from the host s 102 to the replication manager 110 for storage and replication storage step 300 five such transactions tr 1 tr 5 are shown in fig2 although a larger number would typically be transferred the replication manager 110 logs the time at which the beginning of each.