Am Samstag, 23. Dezember 2017 14:25:51 UTC+1 schrieb [email protected]: > I accidentally renamed one of my file sets, which after reload of the config > created another instance of that file set in the database. From comparing the > two versions as they are in the database I know for sure they are identical > except for the name. > > In order to prevent a full backup to be triggered I know I could simply add > "Ignore File Set Changes = yes" to the file set in question (I use "accurate > = yes" already). However, I do not find it a clean solution and would do it > only if there is no other option. > > Would it be safe to rename the old file set in the database as well and > update the checksum accordingly? So I would have two identical changesets but > with a different primary key. Or would that totally mess up things? > > > Sebastian
Never mind. It doesn't matter anymore. The reason why my incremental job is copying all files again is that for the initial full backup no file signatures were stored in the database (all signatures are "0"). Hence all files are detected as changed. Now I just have to figure out why that happened. -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
