I am still learning my way to use bacula and could need some explanations.

One goal of my customer is to backup an old Windows Server VM with ~15 shares.

My bacula-server is a Debian-VM with bacula-13.0.3, and baculum-11.0.6

I have a config running, writing to a HP changer with 8 tapes etc

My current approach:

I have a JobDef for that server, with pre/post-scripts to mount the share "C$" (kind of a catchall-approach for the start):


JobDefs {
  Name = "Server_S01"
  Type = "Backup"
  Level = "Incremental"
  Messages = "Standard"
  Storage = "loader1"
  Pool = "Default"
  Client = "debian1-fd"
  Fileset = "S01_Set1"
  Schedule = "WeeklyCycle"
  WriteBootstrap = "/var/lib/bacula/%c.bsr"
  SpoolAttributes = yes
  Runscript {
    RunsWhen = "Before"
    RunsOnClient = no
    Command = "/etc/bacula/scripts/cifs_mount_s01.sh"
  }
  Runscript {
    RunsWhen = "After"
    RunsOnClient = no
    Command = "/usr/bin/umount /mnt/bacula/s01/c_dollar"
  }
  Priority = 10
}

# fstab

//192.168.0.11/C$ /mnt/bacula/s01/c_dollar cifs ro,_netdev,users,noauto,credentials=/var/lib/bacula/.smbcreds_s01 0 0

# scripts/cifs_mount_s01.sh

/usr/bin/mountpoint -q /mnt/bacula/s01/c_dollar || /usr/sbin/mount.cifs //192.168.x.y/C$ /mnt/bacula/s01/c_dollar -o credentials=/var/lib/bacula/.smbcreds_s01


A Fileset, that doesn't look very elegant to me. I edited it for privacy .. you get the picture:

Fileset {
  Name = "S01_Set1"
  Include {
    File = "/mnt/bacula/s01/c_dollar/A"
    File = "/mnt/bacula/s01/c_dollar/B"
    File = "/mnt/bacula/s01/c_dollar/C"
    Options {
      Signature = "Md5"
    }
  }
  Exclude {
    File = "/mnt/bacula/s01/c_dollar/Backu*"
    File = "/mnt/bacula/s01/c_dollar/Dokumente*"
    File = "/mnt/bacula/s01/c_dollar/pagefile.sys"
    File = "/mnt/bacula/s01/c_dollar/Prog*"
    File = "/mnt/bacula/s01/c_dollar/Reco*"
    File = "/mnt/bacula/s01/c_dollar/System*"
    File = "/mnt/bacula/s01/c_dollar/Windows"
    File = "/mnt/bacula/s01/c_dollar/WSUS"
  }
}

--

Is that OK or is there a more elegant way to do this?

The Job runs right now, and copies files, OK

My CIFS-user should have admin rights, but for example I seem not to have read permissions when doing this:

# ls /mnt/bacula/s01/c_dollar/A

I let the job finish and check contents of backups later in the GUI.

Sure, that's more of a Samba/CIFS-question -> permissions of users. Maybe we should add my user to the various shares as a read-user via ACLs or so.

Being member of admins seems not enough.

-

I'd appreciate suggestions how to backup multiple CIFS-shares.

One job per share? I would need pre/post-scripts for each of them?

thanks in advance! Stefan







_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to