View Source

h1. {page-title}

# Using the CDP Server web interface a user browses the files and folders on their Agent's hard disk.  They select (check boxes) next to the files and folders they want to include in their backup.
 
# User optionally adds complex exclude rules allowing them to define rules that exclude files by pattern.  For example \*.logs or \*.mp3 (really simple examples).
 
# The user's selected folders and exclude rules are communicated to the CDP Agent at the beginning of every backup operation (aka synchronization in 3.0)
 
# CDP Agent (Windows and Linux) takes a point-in-time block level snapshot (VSS on Windows and /dev/cdp on Linux) of the backup target (e.g. hard disk / RAID array / ISCSI / software RAID etc)
*THE MAGIC IS THIS POINT-IN-TIME SNAPSHOT in CDP 3.0 IS READ / WRITE\!   *
*Note: CDP 2.0 Linux Snapshots and MS VSS snapshots (Without CDP 3.0) are READ-ONLY\!*
* *
# *The CDP Agent mounts the virtual snapshot device.  E.g. X: drive in Windows or /mnt/snapshot (Linux). *
_Note: don't worry we have special tricks for making these mounts invisible in a way they won't ever conflict with other mount points or drives_
_  _
# According to the selected files/folders and exclude rules the Agent proceeds to delete all exclude (opposite of included) files and folders from the writable snapshot using simple user space delete methods.  (Think "rm \-Rf /unwanted/directory" or "find "exclude-patern" \-exec rm {}\;")
_Note: This deleting is only done in your point-in-time snapshot and in no way affects your real disk volume and data\!  Get it?  Its Magic\!_

h3.


h3. R1Soft Writable Volume Shadow Copy Device Driver Design

\\ !Writeable-VSS-Disgram.png!\\

h3.  


h3. R1Soft Writable Linux Snapshot Device Driver Design

\\ !Writable-Linux-Snapshots.png!\\
\\
\\