Sync with Linked Cycles in a D2D2T Scenario
Posted by Sven Koester, Last modified by Andre Kuehnemund on 10 August 2012 14:32

When using Synchronize in a Disk-to-Disk-to-Tape scenario, it is recommended not to use the linked cycles in Synchronize.

Previous data can be kept in Synchronize as snapshots stored in a __CYCLES folder. These snapshots (or cycles) can be created using hard links for unchanged files. In case the synchronize target data is subject to subsequent Backups or Synchronize jobs, a side effect appears due to these file links. In case a snapshot is created or deleted, a new hardlink for a file is created or an old hardlink is deleted. Any such operation changes the ctime stamp of the original file because the files inode is changed. Subsequent jobs will take that as sign that the file has changed and will save it again.

As a result, a sync job with active cycle control may cause subsequent jobs on the target to save all files again.

(1 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name:
CAPTCHA Verification 
Please enter the text you see in the image into the textbox below (we use this to prevent automated submissions).