Madness after importing FBackup4 jobs to 5
Posted: Tue Nov 19, 2013 11:32 am
I had 2 backup jobs defined on FBackup4, "Even Months" and "Odd Months".
Before running "Odd Months" for the first time, I got a message that FBackup5 is available, so I downloaded it (Build 242) and imported my jobs into FBackup5 from FBackup4.
To start with, I ran "Even Months", which I am assuming (see later) just found a few changes and added them to the backup created last month. It certainly was over quite quickly, which is what I would have expected.
In between, I updated iTunes.
Now for the weird stuff: I ran "Odd Months" for the first time ever and it found 2 files (the changed iTunes control files), backed them up and finished!
What I had expected was that it would back up everything, to give me a second copy of all my files, so I could flip-flop between them.
Looking at the log, it had used the "Even Months" catalog, instead of creating a new one for "Odd Months", so had just copied the changes since "Even Months" had run.
Does this happen intentionally? I can't think it should.
Was it because I had imported a job with no existing catalog data, or can I expect this situation to reoccur in everyday running? That would make it hard to trust FBackup to do a proper job of keeping my backup files up to date.
Hoping that it was just an import error, I deleted the "Odd Months" job and recreated it, which seemed to be working OK (until, part way through testing the copied files, it gave me an IPC server error and stopped - I have just reported this in a different thread).
Before running "Odd Months" for the first time, I got a message that FBackup5 is available, so I downloaded it (Build 242) and imported my jobs into FBackup5 from FBackup4.
To start with, I ran "Even Months", which I am assuming (see later) just found a few changes and added them to the backup created last month. It certainly was over quite quickly, which is what I would have expected.
In between, I updated iTunes.
Now for the weird stuff: I ran "Odd Months" for the first time ever and it found 2 files (the changed iTunes control files), backed them up and finished!
What I had expected was that it would back up everything, to give me a second copy of all my files, so I could flip-flop between them.
Looking at the log, it had used the "Even Months" catalog, instead of creating a new one for "Odd Months", so had just copied the changes since "Even Months" had run.
Does this happen intentionally? I can't think it should.
Was it because I had imported a job with no existing catalog data, or can I expect this situation to reoccur in everyday running? That would make it hard to trust FBackup to do a proper job of keeping my backup files up to date.
Hoping that it was just an import error, I deleted the "Odd Months" job and recreated it, which seemed to be working OK (until, part way through testing the copied files, it gave me an IPC server error and stopped - I have just reported this in a different thread).