Things are beginning to run smoothly. Amanda has caught up with full backups, and last nights run
completed by 7:57am this morning with a total of 5.2TB of dumps and no problems.
Two issues came up in the final stages of getting this working.
*1.* After adding a PSEUDO tape type with a length
On 01/09/17 03:16 PM, Chris Hoogendyk wrote:
hmm. That is kind of a problem. I should have more than sufficient
space now, but the allocation of
where it goes could overflow if the planning is blind to the storage
allocations. Maybe that is
something to be developed?
As I already wrote, It is
hmm. That is kind of a problem. I should have more than sufficient space now, but the allocation of
where it goes could overflow if the planning is blind to the storage allocations. Maybe that is
something to be developed?
As to where to report the storage use, the Amanda report doesn't have
On 01/09/17 02:10 PM, Chris Hoogendyk wrote:
OK.
So, how does the planner plan for what goes on each storage?
It doesn't, it use the size and plan to dump less than that.
That is, if I set up a pseudo tapetype
for global and give it a length of, say, 12.5TB; how will it know that
the
OK.
So, how does the planner plan for what goes on each storage? That is, if I set up a pseudo tapetype
for global and give it a length of, say, 12.5TB; how will it know that the uncompressed DLEs are
targeted to the LTO7 and the compressed DLEs are targeted at the LTO6? What if the
Thank you!
I'll see how things run tonight. Unfortunately, I have one researcher who has been shuffling
terabytes of data from one array to another. So, I've also had to chase that down as well, and those
will end up being fulls.
So, for example,
localhost
On 30/08/17 11:55 AM, Chris Hoogendyk wrote:
Not quite there yet.
I think I got the tapes labeled properly. I can see that the
parameters that got invoked on my previous attempt with the "-o
tpchanger=" were not correct. Thus, an error in block size on the re
labeling. But I think I at
On 29/08/17 02:37 PM, Chris Hoogendyk wrote:
Thank you! I've got that set up now.
I tried labeling tapes. I thought it was working. e.g.:
You should never use the '-o tpchanger=' argument, it is always better
to use '-ostorage='
That will set the storage and the pool correctly.
Thank you! I've got that set up now.
I tried labeling tapes. I thought it was working. e.g.:
amanda@marlin:~/daily$ amlabel -f -o tpchanger=NEO200x48 -o
'labelstr="^Bio-Research-[0-9][0-9][0-9]*$"' daily "Bio-Research-001" slot 1
Reading label...
Found label 'amtapetype-206980288'
Chris,
Everything looks good except the 'define changer' should be before the
'define storage'.
define changer NEO200x48 {
tpchanger
"chg-robot:/dev/tape/by-id/scsi-1BDT_FlexStor_II_00MX64200626_LL0" #
your changer device file (T48)
property "tape-device"
I haven't found any examples of Amanda configurations using storage definitions. Having read through
the man pages, I've come up with a modification of my amanda.conf that I think should work, and I'm
looking for comments and feedback.
I had temporarily set up a separate Amanda configuration
11 matches
Mail list logo
