A typical / traditional CDP works this way:
install driver+client software on the system to be protected
driver copies segments of data from HDD/volume to target /storage for the first time
the incrementals are captured by the driver by monitoring the HDD for any write requests coming in
to provide application level consistency -- the application calls OS and OS inturn calls VSS to flush data from memory to disk
Now the proposed change
what if the changes are directly copied from memory to disk, first replicated and then verify for data integrity from source,
1) we are not making use of VSS, which also works at application level
2) if VSS is hung, we need to restart services
3) we dont work at application at all
4) all applications are at kernel level, cos of which foot print is very less
install driver+client software on the system to be protected
driver copies segments of data from HDD/volume to target /storage for the first time
the incrementals are captured by the driver by monitoring the HDD for any write requests coming in
to provide application level consistency -- the application calls OS and OS inturn calls VSS to flush data from memory to disk
Now the proposed change
what if the changes are directly copied from memory to disk, first replicated and then verify for data integrity from source,
1) we are not making use of VSS, which also works at application level
2) if VSS is hung, we need to restart services
3) we dont work at application at all
4) all applications are at kernel level, cos of which foot print is very less
