-
I like Incremental backup methodology, but it needs frequent full backups (as i understand from “grandfather,father,son” method), How to have version control where i only create full-backup only once ?
-
and I can choose to Delete changes older than 1 month.
-
How to Only backup Select Data, like only personal data,
-
and a “Ghost” for other data. Ghost is only filename and it’s metadata (also folder structure). Data selected for Ghost is from internet which can be downloaded.
Related
-
“file change tracker” to see summary of what files are moved/deleted/renamed.
-
“File History” where I see previous version of files.
how about a snapshot based system? snapshots treat all changes (inode level or in some deduplicating cases, block level) from some starting point, each snapshots only saves changes.
I know every one will say snapshots are not backups, and i fully agree, but you can also implement a full mirror of relevant dirs in some external snapshot-ting file system on some other media, and like once a day or week or month, keep making snapshots.
Snapshot ? is it same as differential ?
it does. I have snap shotting set for every hour, so every hour my file system creates a copy my main canonical file tree, and if some files changed in that hour, other than those files, all files are mapped to canonical file entries (same block data). for changed files, it points to their original blocks, so essentially changed files have copies. now you can write a command to delete certain amount of old backups, or oldest or however many, and there are multiple graphical implementations as well.
some example of snap shotting file systems are zfs and btrfs. in linux latter is better supported in general. zfs is a bsd project which has a openzfs implementation for linux and many distros support it too.