Am 26.02.2014 17:41, schrieb Stefan G. Weichinger:
> A script could check: if week-number is even, make sure to mount disk2
> ... if week-number is not even, mount disk1 ...
>
> disk1 contains vtapes 1-10 ... (as example), disk2 contains vtapes 11-20
> ... then amvault stuff from config daily to
Testing my problem has taken nearly 2 weeks, also because my quick
tests with tar options but on smaller directories do not produce the
erroneous results as the full amdumps do, which take long times. The
tests were also rather haphazard.
I might try to identify the problems, but will do so more
>
> Can one amanda-config have two (or more) vaulting changers?
>
> S
I don't see why not. You should be able to specify the proper changer in your
amvault command line with --dst-changer. If you want to use more than one
during the same vault run, I suppose you'll have to use something like
Amanda 3.3.4
Hi,
Seems like I'm having trouble getting amanda to use my holding disk.
Here's my setup in amanda.conf:
define holdingdisk holdingdisk1 {
directory "/mnt/amanda-holdingdisk1/"
use 4500Gb
chunksize 100Gb
}
define dumptype gui-base {
global
program "GNUTAR"
I don't believe amanda attempts to write to the holding disk.
Who owns it?
On Thu, Feb 27, 2014 at 03:09:20PM -0500, Michael Stauffer wrote:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingd
* Michael Stauffer [20140227 15:10]:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingdisk holdingdisk1 {
> directory "/mnt/amanda-holdingdisk1
Michael,
You define the holdingdisk but you don't tell amanda to use it.
Add:
holdingdisk "holdingdisk1"
after the define
Jean-Louis
On 02/27/2014 03:09 PM, Michael Stauffer wrote:
Amanda 3.3.4
Hi,
Seems like I'm having trouble getting amanda to use my holding disk.
Here's my setup in am
On Thu, Feb 27, 2014 at 03:09:20PM -0500, Michael Stauffer wrote:
> Amanda 3.3.4
>
> Hi,
>
> Seems like I'm having trouble getting amanda to use my holding disk.
>
> Here's my setup in amanda.conf:
>
> define holdingdisk holdingdisk1 {
> directory "/mnt/amanda-holdingdisk1/"
> use 4500Gb
>
My config merely has
holdingdisk hd1 { yada yada yada
}
Does it work because I didn't DEFINE it but merely declared it to be?
Just wondering. It works fine…. I've left the param in the dump type out,
so I guess I'm getting the "auto" for yes, do use it.
Deb
On Feb 27, 2014, at
Great, thanks - that's the trick. I figured it was something like this but
FWIW, this isn't in the amanda.conf docs.
-M
On Thu, Feb 27, 2014 at 3:21 PM, Jean-Louis Martineau
wrote:
> Michael,
>
> You define the holdingdisk but you don't tell amanda to use it.
>
> Add:
> holdingdisk "holdingdi
Yes, it's 4.5TB.
I's not clear to me from the docs whether a level 0 dump gets written fully
to holding disk before it gets streamed to tape, or if streaming starts
once one or more chunks have been written to the holding disk - anyone
know? I'd prefer the latter for performance reasons. If the fo
I believe the whole dump has to be done before it starts to write to tape.
This prevents incomplete dumps from wasting space on the tape.
I try to have numerous smaller DLEs, so that it takes several DLEs to fill a
tape. Thus, when any one of them is finished, it can start going
to tape. If
Amanda 3.3.4
Hi,
I'm guessing the answer is no since I haven't read about this, but maybe...
I'm hoping amanda might be able to auto-size DLE's into sub-DLE's of an
approximate size, say 500GB.
My understanding is this:
1) if I have multiple DLE's in my disklist, then tell amdump to perform a
I see, I think then that's why there's a separate disk cache option
(tapetype:part-cache-type)?
So if have a very large DLE and I use disk for cache, it will spool chunks
to disk and starting streaming to tape before the whole DLE is written to
disk? I want to avoid memory cache since I'd end up wi
Amanda 3.3.4
Hi,
Another long post from me - thanks to anyone who has time to read it.
I've been reading various docs and posts about dumpcycle, runspercycle,
tapecycle, runtapes online, but still can't figure out how I should set
things up for my needs.
I've got:
- ca. 30TB of data to backup
-
Amanda 3.3.4
Hi,
I just finished an amrecover test. The run's debug file shows this at the
end:
Thu Feb 27 20:47:14 2014: thd-0x25f1590: amrecover: stream_read_callback:
data is still flowing
Thu Feb 27 20:47:25 2014: thd-0x25f1590: amrecover: stream_read_callback:
data is still flowing
Thu Feb
Muchael,
> 1) if I have multiple DLE's in my disklist, then tell amdump to perform a
> level 0 dump of the complete config, each DLE gets written to tape as a
> separate dump/tar file (possibly in parts if the tar is > part-size). Is
> that right?
Yes
> 2) If multiple DLE's are processed in a si
On Thu, Feb 27, 2014 at 04:44:13PM -0500, Michael Stauffer wrote:
> Yes, it's 4.5TB.
>
> I's not clear to me from the docs whether a level 0 dump gets written fully
> to holding disk before it gets streamed to tape, or if streaming starts
> once one or more chunks have been written to the holding
Oliver already provided good answers, I'll just add a bit.
On Fri, Feb 28, 2014 at 10:35:08AM +0700, Olivier Nicole wrote:
> Muchael,
>
...
>
> > 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
>
On Thu, Feb 27, 2014 at 07:19:24PM -0500, Michael Stauffer wrote:
> Amanda 3.3.4
>
> Hi,
>
> Another long post from me - thanks to anyone who has time to read it.
>
> I've been reading various docs and posts about dumpcycle, runspercycle,
> tapecycle, runtapes online, but still can't figure out
20 matches
Mail list logo
