DRD sync
Without DRD Sync
1.A system administrator creates a DRD clone on a Thursday
2.The administrator applies a collection of software changes to the clone on Friday using the drd runcmd command
3.On Friday, several log files are updated on the booted system
4.On Saturday, the clone is booted, however the log files are not up to date, so the administrator must copy over the log files and any other files from the original system that changed after the clone was created – for example,/etc/passwd
With DRD Sync
1.A system administrator creates a DRD clone on a Thursday
2.The administrator applies a collection of software changes to the clone on Friday using the drd runcmd command
3.On Friday, several log files are updated on the booted system
4.On Saturday, the clone is synced then booted – log files and other files that have changed on the original system have automatically been copied to the clone
29