This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
other:win10_syncback [2020/04/20 14:25] jypeter [Suggested filters when backing up your Windows folder] |
other:win10_syncback [2020/04/20 15:13] jypeter [The side effect of filters] Added instructions |
||
---|---|---|---|
Line 81: | Line 81: | ||
==== The side effect of filters ==== | ==== The side effect of filters ==== | ||
+ | If you use a filter to specify that something in the //Source// folder should not be backed up to the //Destination// folder, SyncBack will also ignore it in the Destination folder, and it will stay in //Destination// **forever**, unless you remove it by hand! | ||
+ | |||
+ | If you have time, you may want to review the custom filters you have added, and **remove the //filtered// folders/files in Destination by hand**... | ||
+ | |||
+ | **Detailed example:** | ||
+ | * you execute a backup profile, and one of the mirrored folders (in Source) is called ''datareporting''\\ => ''datareporting'' exists in both Source and Destination | ||
+ | * you add a ''%%*\datareporting\%%'' filter that will skip the ''datareporting'' folders the next times you execute the backup profile\\ => ''datareporting'' still exists in both Source and Destination | ||
+ | * The ''datareporting'' content in Source may change but will be ignored by SyncBack (that's what you want!) | ||
+ | * **The ''datareporting'' content in //Destination// will stay there and never change** (the //side effect//...) | ||
+ | * The only way to get rid of ''datareporting'' in Destination is to **remove it by hand** | ||
/* standard page footer */ | /* standard page footer */ |