"Create Baseline" function does not work?

Same for me Lufa, I never managed it to correctly create the baseline, so I'm going to switch to Flyback.

Thank you, Romuald.

I mus figure, that for "smaller" directories it worked great.

I have the same problem here too. The Baseline button does nothing. I noticed that in /etc/timevault.conf there is a Baseline setting that was set to False. So I manually changed it to True and restarted TimeVault. Still nothing. No Baseline of my original files.

I've always had this problem, and so did not bother to install it on my new computer until just today.
Then I did something I hadn't done before, just clicked Baseline on the default etc directory. The notifier icon correctly changed to have the small clock, which means there are changes in the backup queue. Then I saved and closed my preferences as normal, but the small clock disappeared!
Basically, it seems that you MUST leave the preferences dialog open while working on a baseline. And as far as only handling small numbers of files, I always thought that was also a problem, but right now I am working on a > 183,000 file, 80gb baseline of my /home/ directory, so something must be fixed in the 0.7.5-1_i386 version.
Hopefully I was able to help /someone/ with my random find.

Thanks Dan. Yes you have to click on the directory entry you want to Baseline (on the Include tab) and then hit the baseline button. Now TimeVault is copying everything.

So right click on the TimeVault notifer, go to the include tab, click the Add button, select your new directory in the list, click baseline and wait until everything finishes.
The next trick is when you want to enable automated snapshots with more than 8192 directories. This comment from beagle-project.org/Troubleshooting brings some light to our problem with inotify.

The default number of watches is 8192. 16384 is a good value for most people, and 32768 is probably more than enough. Using additional watches does increase the amount of memory used inside the kernel, but increasing the number does not affect the amount of memory if they aren't used.

To change the limit:

sudo echo 16384 > /proc/sys/fs/inotify/max_user_watches

I think the reason why this is happening is because a save event triggers a configuration reload, thus 'resetting' TimeVault and removing the baseline. I'll take a look when I have time.

I can't get this to work at all. I click the "Baseline" button after adding my home directory. Then I hit save and CPU goes up to 100% but no new files are actually added to the "Pending Snapshots". Then after a while, CPU usage goes down again to 0%. The backup dir only contains a very small portion of my home directory (mostly config/log files which often change).

/var/log/timevault.log reveals a lot of lines like the following:
Aug 12 02:49:59 Snap@1788: 3 processed, 0 taken (3 failed)
Aug 12 02:52:02 Snap@1911: 2 processed, 0 taken (1 failed)

What's wrong? This isn't intended behavior? I'm using the timevault_0.7.5-1_i386.deb from LP.

I click on "baseline" while having selected a directory that I wish to back up, and then click on "ok" in the next dialog. I keep the preferences window opened and I "tail -f" the logfile, but *nothing* happens, the dialog disappears and that's all. What can be happening?

Sorry for offtopic but SBackup is what I was searching for... It just work!

( http://www.ubuntugeek.com/backup-and-restore-your-ubuntu-system-using-sbackup.html )