Re: [Bacula-users] Bacula on Debian with Overland Powerloader

[Kern S. <ke...@si...>]

Hello,

On Fri, 2003-06-27 at 09:33, Meik Hellmund wrote:
> Hello and thanks for your explanations!
>=20
> Kern Sibbald <ke...@si...> writes:
>=20
> > > - In Debian/unstable, mysql includes SSL-support. I "patched" the=20
> > >   bacula configure script and added "-lssl -lcrypto" to SQL_LFLAGS,=20
> > >   otherwise there are unresolved references.=20
> >=20
> > This patch won't help you since Bacula does not yet support
> > ssl or any other encryption.
> It does help. Without it I can't make bacula. I need -lssl -lcrypto=20
> whenever I use -lmysqlclient_r, even if I don't use the ssl stuff.

Oh, I see. Thanks. I'll add that to the manual.

>=20
> > >           ERR=3DInput/output error.
> >=20
> > This is typical of an autochanger that needs a bit of time
> > to settle down after changing cassettes.  The autochanger
> > chapter of the manual discusses how to test this, and
> > if you have loaded version 1.31, all the code is already
> > in the autochanger script just waiting to be turned on.
>=20
> OK, thank you. I should have tried this first.=20
>=20
>=20
> > > snapshot support
> > I don't think so because I have no idea what LVM snapshorts or fssnap
> > are.
>=20
> from "man fssnap_ufs" on solaris:
>     The fssnap command queries, creates, or deletes a temporary
>     snapshot of a UFS file system. A snapshot is a point-in-time=20
>     image of a file system that provides a stable and unchanging=20
>     device interface for backups. When creating a file system=20
>     snapshot, you must specify the file system to be captured=20
>     and the backing-store file. The backing-store file is one in=20
>     which the snapshot subsystem saves old file system data before=20
>     it is overwritten. The destination path must have enough free=20
>     space to hold the backing-store file, whose size varies with=20
>     the amount of activity on the file system. This location must=20
>     be different from the file system that is being captured in a snapsho=
t.
>=20
> from "man lvmcreate" on Linux:
>     -s, --snapshot
>        Create a snapshot logical volume (or snapshot) for an  existing,
>        so  called  original logical volume (or origin).  Snapshots pro-
>        vide a 'frozen image' of the contents of the  origin  while  the
>        origin  can still be updated. They enable consistent backups and
>        online recovery of removed/overwritten data/files. The  snapshot
>        does  not  need  the same amount of storage the origin has. In a
>        typical scenario, 15-20% might be enough.=20
>=20
>=20
> Both commands create new devices (something like /dev/fssnap/0)=20
> by which one can access the snapshot.=20
> And, of course, at the end of the backup this should be switched off.
>=20
> So it would be great if the client daemon has hooks to call scripts befor=
e and
> after backup. The script should create the snapshot and mount it somewher=
e,
> let's say the snapshot from /home at /snap_home, and this is used as path=
 in
> the fielset resource.

Interesting programs. I suspect that it is possible to back up those
devices (or pseudo file systems) with Bacula, but it would take some
experimentation. If these devices are FIFO's then Bacula can be made to
read them on backup and write them on restore using the readfifo=3Dyes
Include option and by explicitly naming the device in the Include list.
See readfifo under:

http://www.bacula.org/html-manual/dirdconf.html#FileSetResource

for more details.

If the device is a block device, Bacula can read/write it by simply
explicitly mentioning the device in the Include.

Please let us know about any experiments you may try.

Best regards,

Kern