Unfortunately, this is a bug related to TAR's incremental feature. TAR stores files that are excluded from a backup in the snapshot file (snar file) as 'Not included'. If this exclusion is no longer valid in later backups, TAR does not include such 'new' files since it treats them as not changed since the last backup. The TAR algorithm (version 1.22) is not able to distinct between
1) file was 'Not included' because it is on the excludes list and
2) file was 'Not included' because it hasn't changed since tha last backup.
Conclusion: hard to fix and probably won't fix in nssbackup 0.2.
Unfortunately, this is a bug related to TAR's incremental feature. TAR stores files that are excluded from a backup in the snapshot file (snar file) as 'Not included'. If this exclusion is no longer valid in later backups, TAR does not include such 'new' files since it treats them as not changed since the last backup. The TAR algorithm (version 1.22) is not able to distinct between
1) file was 'Not included' because it is on the excludes list and
2) file was 'Not included' because it hasn't changed since tha last backup.
Conclusion: hard to fix and probably won't fix in nssbackup 0.2.