Bacula

On Wed, 27 Dec 2006, Ryan Novosielski wrote:

> FileSet {
>  Name = "Everything"
>  Include {
>    File = /
>    Options {
>      onefs = no
>    }
>  }
> }
>
> I'm guessing something in /var/adm is messing me up...

At first I think it's best to backup every filesystem individually, 
instead of just marking "everything". That way you are also safe you do 
not backup duplicate mounted filesystems, cdroms, ...

Also, exlude the /proc tree. You can also find it in the standard exclude 
that comes with the example configs. /proc is a memory filesystem, so 
you're backing up your memory too, which is not what you want :-)

K.

Is it possible that this is your second run of the full backup and you
merely just adding more data to the volume?

Ryan Novosielski wrote:
> I am looking for a little help on how to solve this problem. I'm running
> Bacula 1.38.11 and attempting to run a full system backup.
>
> The result (I canceled it):
>
> 1933  Full    121,193 52,702,244,286 Cancel   27-Dec-06 17:37 SystemArchive
>
> ...however, supposedly, the files are only 24 GB.
>   

Check whether you have any sparse files
(http://en.wikipedia.org/wiki/Sparse_file). Set the approriate option
(sparse = yes) and try again. I use the following FileSet as a default;
it automatically excludes /tmp (tmpfs-based), /proc (procfs).

FileSet {
  Name = "Full Set"
  Include {
    Options {
        aclsupport = no # I believe this will speed up the most common case

        sparse = yes
        compression = GZIP
        signature = MD5
        OneFS  = no

        FSType = ext2  # ext3 as well
        FSType = jfs
        FSType = reiserfs
        FSType = xfs
        FSType = jfs
    }
}

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Vladimir Doisan wrote:
> Is it possible that this is your second run of the full backup and you
> merely just adding more data to the volume?

Nope, I'm running a special archive run before I re-install the OS and
software on it -- the tape had been empty.

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | | Ryan Novosielski - Systems Programmer III
|$&| |__| |  | |__/ | \| _| | novosirj@... - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFk9NQmb+gadEcsb4RAsLTAKC9NiR97hTpI4ZmNkPLYckJ7fApowCgli9w
Rw5OVDIYKCq8DHcS5ZkM1SA=
=cpEi
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Per Andreas Buer wrote:
> Ryan Novosielski wrote:
>> I am looking for a little help on how to solve this problem. I'm running
>> Bacula 1.38.11 and attempting to run a full system backup.
>>
>> The result (I canceled it):
>>
>> 1933  Full    121,193 52,702,244,286 Cancel   27-Dec-06 17:37
>> SystemArchive
>>
>> ...however, supposedly, the files are only 24 GB.
>>   
> 
> Check whether you have any sparse files
> (http://en.wikipedia.org/wiki/Sparse_file). Set the approriate option
> (sparse = yes) and try again. I use the following FileSet as a default;
> it automatically excludes /tmp (tmpfs-based), /proc (procfs).

I had considered this, and it DOES appear that UFS has support for
sparse files... the trouble is, I don't have any experience with them --
how would I go about finding one on my system (the UFS entry in Wiki
does not mention sparse in its text at all)?

> FileSet {
>  Name = "Full Set"
>  Include {
>    Options {
>        aclsupport = no # I believe this will speed up the most common case
> 
>        sparse = yes
>        compression = GZIP
>        signature = MD5
>        OneFS  = no  
>        FSType = ext2  # ext3 as well
>        FSType = jfs
>        FSType = reiserfs
>        FSType = xfs
>        FSType = jfs
>    }
> }

Would this Fileset not also exclude UFS? I was looking at the manual
yesterday and UFS does not appear to be a valid value for the FSType
directive, but perhaps it was just left out of the docs?

- --
- ---- _  _ _  _ ___  _  _  _
|Y#| |  | |\/| |  \ |\ |  | | Ryan Novosielski - Systems Programmer III
|$&| |__| |  | |__/ | \| _| | novosirj@... - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.| IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFk9Vwmb+gadEcsb4RAgVoAJ9lOvCBdxjoAyYAT/bmzo/SOk3f9QCg28XK
vXfzznfOoaNzAyZu6BMLs1U=
=HyHA
-----END PGP SIGNATURE-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Kshatriya wrote:

> Also, exlude the /proc tree. You can also find it in the standard exclude 
> that comes with the example configs. /proc is a memory filesystem, so 
> you're backing up your memory too, which is not what you want :-)
> 
> K.

Looks like that did it -- the backup was around 23/24 GB without /proc.

Thanks very much for the assistance!

- --
 ---- _  _ _  _ ___  _  _  _
 |Y#| |  | |\/| |  \ |\ |  | |Ryan Novosielski - Systems Programmer III
 |$&| |__| |  | |__/ | \| _| |novosirj@... - 973/972.0922 (2-0922)
 \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFk/wkmb+gadEcsb4RAsQAAKCRC6DWv7Ujb7yLXjIUIG9m9Xk5KwCgm9ZO
UxwXYVpo6sxvV928ovr13HE=
=Z3RB
-----END PGP SIGNATURE-----

>>>>> On Thu, 28 Dec 2006 09:32:16 -0500, Ryan Novosielski said:
> 
> Per Andreas Buer wrote:
> > Ryan Novosielski wrote:
> >> I am looking for a little help on how to solve this problem. I'm running
> >> Bacula 1.38.11 and attempting to run a full system backup.
> >>
> >> The result (I canceled it):
> >>
> >> 1933  Full    121,193 52,702,244,286 Cancel   27-Dec-06 17:37
> >> SystemArchive
> >>
> >> ...however, supposedly, the files are only 24 GB.
> >>   
> > 
> > Check whether you have any sparse files
> > (http://en.wikipedia.org/wiki/Sparse_file). Set the approriate option
> > (sparse = yes) and try again. I use the following FileSet as a default;
> > it automatically excludes /tmp (tmpfs-based), /proc (procfs).
> 
> I had considered this, and it DOES appear that UFS has support for
> sparse files... the trouble is, I don't have any experience with them --
> how would I go about finding one on my system (the UFS entry in Wiki
> does not mention sparse in its text at all)?

I would do it by assuming that they will look large when using ls, do use
something like

find / -xdev -size +100000 -ls

You can detect when a file is sparse by comparing the (byte) size printed by
ls with the (kbyte size) printed by du -ak.

__Martin