On Sun, May 20, 2012 at 00:20:10 +0300, Toomas Aas wrote:
Jean-Louis wrote:
It might be a feature/bug with level 1 backup, try a full of /storage.
I did, and the dump of /storage did not include files under
/storage/lists. So it *might* be a bug with level 1 backup, but in
that case it's
Hello all,
Just to keep the amount of messages down, I'll respond to several
questions at once.
Robert wrote:
Is tar on the OP system actually GNUTar? On *Linux* systems it generally
is, but I am not certain about *commercial* UNIX systems...
It is true that 'standard' tar on FreeBSD is
At Thu, 17 May 2012 12:37:24 -0400 amanda-users@amanda.org wrote:
On Thu, May 17, 2012 at 03:17:32PM +0300, Toomas Aas wrote:
Thu, 17 May 2012 kirjutas Christopher X. Candreva ch...@westnet.com:
One file system means just that. Unless /storage/lists is a separate
partition mounted at
On 05/18/2012 12:33 AM, Toomas Aas wrote:
Hello Nathan!
What exactly happened that convinced you the contents of /storage/lists
was still getting included in the dump for /storage ?
First I noticed in the e-mail report that level 1 backup of /storage
was just a little bit bigger than
On Fri, May 18, 2012 at 07:33:31 +0300, Toomas Aas wrote:
First I noticed in the e-mail report that level 1 backup of /storage
was just a little bit bigger than level 0 backup of /storage/lists
(9703 vs 9120 MB). Then I looked at the index file of /storage DLE
on server for that day's amdump
On Thu, 17 May 2012, Toomas Aas wrote:
I had one big filesystem mounted on /storage which was backed up by a DLE
using comp-user-tar dumptype. Yesterday I split out one subdirectory,
/storage/lists, into separate partition and added another DLE for
/storage/lists, also using comp-user-tar
Thu, 17 May 2012 kirjutas Christopher X. Candreva ch...@westnet.com:
One file system means just that. Unless /storage/lists is a separate
partition mounted at that point, /storage is one file system, as you say
above. You need the explicit exclude.
That was exactly my point. Until day before
On Thu, 17 May 2012, Toomas Aas wrote:
Thu, 17 May 2012 kirjutas Christopher X. Candreva ch...@westnet.com:
One file system means just that. Unless /storage/lists is a separate
partition mounted at that point, /storage is one file system, as you say
above. You need the explicit exclude.
On Thu, May 17, 2012 at 07:02:51 +0300, Toomas Aas wrote:
Tonight's amdump run seems to have backed up the contents of
/storage/lists twice, once as /storage/lists DLE and once as part of
/storage DLE.
I thought that '--one-file-system' flag passed by Amanda to gtar is
supposed to prevent
On Thu, May 17, 2012 at 03:17:32PM +0300, Toomas Aas wrote:
Thu, 17 May 2012 kirjutas Christopher X. Candreva ch...@westnet.com:
One file system means just that. Unless /storage/lists is a separate
partition mounted at that point, /storage is one file system, as you say
above. You need the
Hello Nathan!
What exactly happened that convinced you the contents of /storage/lists
was still getting included in the dump for /storage ?
First I noticed in the e-mail report that level 1 backup of /storage
was just a little bit bigger than level 0 backup of /storage/lists
(9703 vs
Hello Jon!
Grasping at straws, any chance you also left the original files
in the directory lists after copying them to the new partition.
After mounting the new partition on /storage/lists they would be
masked and would not be accessible using file system semantics.
But dump-like programs
I had one big filesystem mounted on /storage which was backed up by a
DLE using comp-user-tar dumptype. Yesterday I split out one
subdirectory, /storage/lists, into separate partition and added
another DLE for /storage/lists, also using comp-user-tar dumptype.
Tonight's amdump run seems to
13 matches
Mail list logo
