Thanks, and indeed my investigations into possible a/m/ctime problems
were a red herring. Something learned.
Regards, Charles
On Sun, 2 Mar 2014 18:48:03 -0500
Nathan Stratton Treadway natha...@ontko.com wrote:
On Tue, Feb 25, 2014 at 10:53:07 +0100, Charles Stroom wrote:
I than repeated
When installing suse 13.1, there is the option to encrypt the
particular LV in its entirety. That is what I selected. This was done
for several LVs used, not for the root volume and /boot. As my
knowledge of linux is not very deep, that is all I can tell you. On
the other hand, if it was only
On Monday 03 March 2014 11:16:52 Nathan Stratton Treadway did opine:
On Mon, Mar 03, 2014 at 07:23:33 +0200, Sergey Poznyakoff wrote:
Nathan Stratton Treadway natha...@ontko.com ha escrit:
(So presumably the correct fix is to get Amanda updated to
recognize/handle the new warning
3) I had figured that when restoring, amrestore has to read in a
complete
dump/tar file before it can extract even a single file. So if I have a
single DLE that's ~2TB that fits (with multiple parts) on a single
tape,
then to restore a single file, amrestore has to read the whole
Yes thanks, this is what I do. I've had some complication running the
restore from the backup server rather than the client, but I'll worry about
that later.
On Fri, Feb 28, 2014 at 1:47 PM, Debra S Baddorf badd...@fnal.gov wrote:
one small comment inserted below
On Feb 27, 2014, at 11:33
Comments on questions that are at the very bottom.
On Mar 3, 2014, at 1:47 PM, Michael Stauffer mgsta...@gmail.com
wrote:
3) I had figured that when restoring, amrestore has to read in a complete
dump/tar file before it can extract even a single file. So if I have a
single DLE that's
On Mon, Mar 03, 2014 at 02:47:53PM -0500, Michael Stauffer wrote:
...
Any thoughts on how I can approach this? If amanda can't do it, I
thought I
might try a script to create DLE's of a desired size based on
disk-usage,
then run the script everytime I wanted to do a new level 0
