Semi-OT: Help Needed W/ Bareos

Home » CentOS » Semi-OT: Help Needed W/ Bareos
CentOS 8 Comments

I’ve got it installed on a 6.7 server, and can back up and restore for Linux. Now I’m trying to do it for some users’ WinDoze boxes. Trouble is, all I keep finding on the Web are “how to set it up on Linux”, “how to install on Windoze”, and how to restore….

First question: how do you *see* a list of the files that have been backed up (you’re not going to tell me that’s a PostgreSQL thing, are you?)?

Second: I’ve been looking, and am having trouble finding examples of configuring the bareos-dir for a win client. I *think* I did it right, but I get warnings. For the fileset, I have FileSet {
Name = “set”
Include {
Options {
Signature = MD5 # calculate md5 checksum per file
}
File = “c:\Users”
}
}

But the logs *seem* to be saying it only copied one file.

Clues for the poor?

mark

8 thoughts on - Semi-OT: Help Needed W/ Bareos

  • Great – thanks (I’ll try it when I get into work). Any clues as to whether I’ve got the FileSet correct – say, is the slash correct, or should it be a Linux forward slash, rather than a WinDoze backslash?

    mark

  • I can not help with bareos, I use bacula, but assuming bareos kept the same definitions, then it is forward slash (Unix or Linux style ;-). Here is a portion of my config for Windows 7 client (Server is FreeBSD 9.3, bacula version is 5.2.12):

    FileSet {
    Name = “Ping Set”
    Enable VSS = yes
    Include {
    Options {
    signature = MD5
    }
    Options {
    exclude = yes
    Ignore Case = yes
    wilddir = “C:/Temp”
    wilddir = “C:/Windows/Temp*”
    wilddir = “*Temporary Internet Files*”
    }

    File = C:/
    }

    }

    Don’t try to make sense of the word “Ping” – that is just funny machine name ;-)

    Good luck!

    Valeri

    ++++++++++++++++++++++++++++++++++++++++
    Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247
    ++++++++++++++++++++++++++++++++++++++++

  • IP wrote:

    Maybe I’ve been reading that, and it has zero suggestions for if I only want to back up c:\Users and the the contents. Maybe I’ve already *said*
    I’d been googling, and not finding enough info. Maybe I even said that in my first paragraph of my original post.

    mark

  • Mark, did you receive my earlier post (reply to earlier e-mail in this thread)? I pasted there portion of my bacula config. Im my case (bacula
    5.x.x) it is forward slash for Windows clients as well. I know one way to test it: make a backup, then restore, then compare. (It is always a good idea for the first new type of client when not sure the config is correct…)

    I hope, this helps.

    Valeri

    ++++++++++++++++++++++++++++++++++++++++
    Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247
    ++++++++++++++++++++++++++++++++++++++++

  • Valeri Galtsev wrote:
    for Linux. Now I’m trying to do it for some users’ WinDoze boxes.

    thread)? I pasted there portion of my bacula config. Im my case (bacula
    5.x.x) it is forward slash for Windows clients as well. I know one way to test it: make a backup, then restore, then compare. (It is always a good idea for the first new type of client when not sure the config is correct…)

    I most *certainly* did, made the fix, and restarted the bareos-dir service, and ran my backup before lunch. Just did the list files jobid

  • W dniu 03.09.2015 o 17:48, m.roth@5-cent.us pisze:
    Above is evidence, that you didn’t read bareos doc, as i suggested in my early post. When you did that, you could see, that there are Linux
    (Unix) slashes:

    # from bareos doc

    8.5.4 Windows FileSets
    <http://doc.bareos.org/master/html/bareos-manual-main-reference.html#QQ2-1-161>

    If you are entering Windows file names, the directory path may be preceded by the drive and a colon (as in c:). However, the path separators must be specified in Unix convention (i.e. forward slash
    (/)). If you wish to include a quote in a file name, precede the quote with a backslash (\). For example you might use the following for a Windows machine to backup the ”My Documents” directory:

    FileSet{
    Name=”WindowsSet”
    Include{
    Options{
    WildFile=”*.obj”
    WildFile=”*.exe”
    exclude=yes
    }
    File=”c:/MyDocuments”
    }
    } # end from bareos doc But you are smarter, so keep going …

    Irens Yeah, you probably read bareos doc with pink glases …