Warnings trying to backup nionexisting directories

[Josef Weisskopf]

Hello,

is there a possibility to get rid of the warnings if directories don´t exist?

I read the onefs option should do that ("This configuration will silently skip non-existing folders without generating warnings") but it doesn´t work in my case.

Do I miss something?

kr

[Bruno Friedmann (bruno-at-bareos)]

Hi Josef, without example I a bit clueless how to help you.

OneFS allow the fact skip subdir when they are a different filesystem, like /proc /dev /sys when you give File=/ to backup.
If you give /data/subdir and subdir is missing you will have a warning because it is expected to be there.

If you have that much warning, maybe another approach is needed to build the list to be backuped like dynamic scripting.

[Josef Weisskopf]

Hello Bruno,

thanks for your answer, eg a fileset like this (regarding Windows). I would like to use one fileset for all Windows Data-Folders , however I don´t know which Data folder exist. It could be just one or all three.

FileSet {
  Name = "winsrv-cbx-fs"
  Enable VSS = yes
  Include {
    Options {
      Drive Type = fixed
      IgnoreCase = yes

      OneFS = yes

    }
     File = "C:/Data"

     File = "D:/Data"

     File = "E:/Data"

     Exclude Dir Containing = .nobackup
  }
}

If a warning cannot be suppressed, I have to split the fileset up and use different filesets for Windows Servers which make the setup more complex and even more difficult to understand (more filesets, more jobs,...). Surely these approach has also advantages in my case I would just prefer a "general" fileset.

kr

[Bruno Friedmann (bruno-at-bareos)]

I believe it such variable case it would be better to implement a script or a dedicated file read (or write) on the client so it's always the same fileset, but its content will vary.

See https://docs.bareos.org/Configuration/Director.html#config-Dir_Fileset_Include_File

Using either Type : “\\<includefile-client” or “\\|command-client”

File = "\\</etc/bareos/bareos-fd.d/file_to_include" 

Then each of your client fill up that file (or you management script)

File="\\|/var/lib/bareos/create_file_list.sh" 

With any scripting creating the list file to include.

[Josef Weisskopf]

Hello Bruno,

thanks for your suggestion which I already implemented in a working testing environment. It is really a great way to be very flexible.

The disadvantage is that it is hard(er) do understand for first level employees what is actually backed up.

kr J

[Bruno Friedmann (bruno-at-bareos)]

Well you can still teach them 

bconsole <<< "estimate job=XXX level=Full listing" | less

which will show the files that will be included

:-)