This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
other:win10_syncback [2020/04/20 14:07] jypeter [Suggested filters when backing up your Home folder] |
other:win10_syncback [2020/04/20 15:14] jypeter Added groups section |
||
---|---|---|---|
Line 67: | Line 67: | ||
Default Windows folder: ''C:\Users\your_login'' | Default Windows folder: ''C:\Users\your_login'' | ||
- | * Remove WSL+Linux from backup: ''%%*\AppData\Local\Packages\Canonical*Ubuntu*\%%'' | + | * Remove [[other:win10wsl|WSL+Linux]] from backup: ''%%*\AppData\Local\Packages\Canonical*Ubuntu*\%%'' |
+ | * It's probably better to use [[other:win10wsl#restoring_a_wsl_backup|wsl export/import]] for saving/restoring a full WSL installation, or a //tar// file for saving only the Linux ''home'' directory | ||
+ | * Remember that WSL+Linux can access Windows directories using ''/mnt/some_drive/some_directory''. You can put your data files in ''some_drive:\some_directory'' and use SyncBack to save the content! | ||
* Remove the backup of all the settings saved in AppData\Local\Packages: ''%%*\AppData\Local\Packages\%%'' | * Remove the backup of all the settings saved in AppData\Local\Packages: ''%%*\AppData\Local\Packages\%%'' | ||
* Try to remove all the cache files: ''*cache*\''\\ This should take care of cache folders like: | * Try to remove all the cache files: ''*cache*\''\\ This should take care of cache folders like: | ||
Line 76: | Line 78: | ||
* Remove misc. files: ''%%*\ntuser*%%'', ''%%*\NTUSER*%%'', ''%%*\AppData\Local\Google\Chrome\User Data\Default\Current*%%'' | * Remove misc. files: ''%%*\ntuser*%%'', ''%%*\NTUSER*%%'', ''%%*\AppData\Local\Google\Chrome\User Data\Default\Current*%%'' | ||
* Remove misc. directories: ''%%*\AppData\Local\Comms\%%'', ''%%*\AppData\Roaming\Adobe\%%'' | * Remove misc. directories: ''%%*\AppData\Local\Comms\%%'', ''%%*\AppData\Roaming\Adobe\%%'' | ||
+ | |||
+ | ==== 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** | ||
+ | |||
+ | ===== Using groups of profiles ===== | ||
+ | |||
/* standard page footer */ | /* standard page footer */ |