UrBackup Server/Client 2.0.4 beta (with Mac OS X client); Restore 2.0.1

[uroni]

@avicho

when the backup activity (first full backup) stopped suddnely because of unplanned server shutdown (where the urbackup server installed) the backup process won’t start from the last place where it stopped. it will begin a new full backup directory… is it right? or there is something to do with it?

Yes that is by design. The server is assumed to not shut down suddenly so regularily that it makes sense optimizing for that case.

@Chluzz

I have a machine with symbolic links in the backup location that points to very large folders (time machine backup folders) outside the backup location. Even with the symbolic links set as excluded in the backup location settings, the indexing will try to index the very large time machine Backup folders. For some reason the indexing never finished. The only way to get it to backup was to delete the symbolic linksSecond point:

Is that time machine link always there? If yes we should compile in a exclusion for that…

@Chluzz

Even with the symbolic links set as excluded in the backup location settings

There is no such setting in UrBackup 2.0.x. If you are using the client with server 1.4.x you should upgrade as 1.4.x doesn’t backup the file metadata and has only rudimentary symlink handling.

With UrBackup 2.0.x server+client you can disable following symlinks by flags to backup directories.

I.e. if you set no flags the default flags are follow_symlinks,symlinks_optional,share_hashes
So if you do not want to follow symlinks outside of the backup dir you set e.g. default directories to backup to /|root/symlinks_optional,share_hashes (or add /symlinks_optional,share_hashes to name in the select directories dialog). I’ll have to add this to the GUI at some point.