Re: 'labelstr' param in amanda.conf
Since others have diverted into providing answers for your tape type, I'll resurrect this question and give some sort of an answer. Yes, you probably need just one configuration and one group of tapes labelled per 'labelstr'. You create a list of DLEs to make smaller than tarp sized chunks. node /diskname dumpname [spindle Local ] (optional) node /disk2/aDir tar-type-dumpname [...] node /disk2/another tar-type-dumpname [...] node2 /diskname dumpname [spindle Local ] (optional) node2 /disk2/aDir tar-type-dumpname [...] node2 /disk2/another tar-type-dumpname [...] Etc Then, optimally, you create a cron job for each night (or maybe only week nights), something like this: 21 00 * * * amdump myconfig And let Amanda shuffle your DLEs into a similarly sized amount each night. Stop reading here, for the simplest setup. --- If perchance the manager of nodeN insists on checking his dumpdates log on the same day each week, you CAN force nodeN with another cron entry & script: "If Wednesday then amadmin myconfig force nodeN * " Or perhaps only amadmin myconfig force nodeN /usr Things like that. It forces Amanda to do a level 0 THAT day, on whatever DLEs you do it for. It messes up Amanda's balancing, but if you have a lot of DLEs it'll even out somewhat. You also CAN do a force on all DLEs ( * * ) on the day that you want a whole set of level 0's. But that really messes up the balancing & isn't the best idea. - I personally DO run a second configuration (archive) and a second set of tapes (same tape drive) so that I can get an archive tape. I set it "no record" so it doesn't change the dumpdates, and so it doesn't stop other level 0's from being done in the normal configuration . I do a "force" on all my DLEs and run it once a month. These tapes go offsite, so I want my daily configuration to have its own set of level 0's. Level 0's at least once a week (my dumpcycle) but then I keep 5-6 weeks of tapes before I recycle and start overwriting those level 0's. Deb On Jan 16, 2014, at 5:01 PM, "Michael Stauffer" mailto:mgsta...@gmail.com>> wrote: Thanks for the reply. I don't have multiple configurations, I'm just trying to figure out how to set things up. So it sounds like I can have a single configuration that uses the same group of tapes as defined by 'labelstr', and I use the DLE lists to break things up into manageable chunks. Then with amdump, I can specify the individual DLE's to be dumped? -M On Thu, Jan 9, 2014 at 1:58 PM, Jean-Louis Martineau mailto:martin...@zmanda.com>> wrote: On 01/09/2014 01:47 PM, Michael Stauffer wrote: Hi, I'm setting up amanda 3.3.4. Regarding 'labelstr' in amanda.conf: The documentation says: "If multiple configurations are run from the same tape server host, it is helpful to set their labels to different strings (for example, "DAILY[0-9][0-9]*" vs. "ARCHIVE[0-9][0-9]*") to avoid overwriting each other's tapes." Does this mean that if I have multiple configurations in order to break up a large 30TB data set into managable chunks, each configuration will have to have a particular set of tapes assigned to it? That seems very awkward if so. yes Why do you have multiple configurations? You should do it with one configuration and multiple dle. Jean-Louis
amidxtaped running amok
Hi, I'm setting up amanda 3.3.4. My server is bogged down with 5 amidxtaped processes taking up a big chunk of my cpu's, and just about all of my 32 gigs of RAM. I haven't been running anything for a while, as I'm slowly working my way through the setup process. Here's all the amandabackup proc's. Any ideas what may have happened or how to investigate further? I haven't killed the procs yet since I don't need the machine to be running properly right now. [amandabackup@cback root]$ ps -u amandabackup PID TTY TIME CMD 14215 ?00:00:00 screen 14216 pts/200:00:00 bash 17927 ?00:00:00 amandad 17929 ?00:00:00 amandad 17943 ?37-02:16:31 amidxtaped 17944 ?00:00:00 amandad 18243 ?00:00:00 amandad 18245 ?00:00:00 amandad 18256 ?44-14:54:42 amidxtaped 18257 ?00:00:00 amandad 24530 pts/000:00:00 bash 24598 pts/000:00:00 ps 26646 ?00:00:00 amandad 26648 ?00:00:00 amandad 26665 ?32-16:04:27 amidxtaped 2 ?00:00:00 amandad 27180 ?00:00:00 amandad 27182 ?00:00:00 amandad 27189 ?32-11:27:04 amidxtaped 27190 ?00:00:00 amandad 27279 ?00:00:00 amandad 27281 ?00:00:00 amandad 27285 ?32-11:25:30 amidxtaped 27286 ?00:00:00 amandad Thanks! -M
Re: tapetype for IBM ULTRIUM-TD5?
On 17/01/14 10:55, Jon LaBadie wrote:
> On Thu, Jan 16, 2014 at 06:04:14PM -0500, Michael Stauffer wrote:
>> Hi,
>>
>> I'm setting up amanda 3.3.4. I can't find a definiton for changer's drives
>> (IBM ULTRIUM-TD5 LTO-5) in /etc/amanda/template.d/tapetypes
>>
>> Can someone point me to a source for this, or to where I can learn how to
>> determine the params I need for the drives? Thanks
>>
> The command amtapetype should be in your amanda server installation.
> It can be used to determine the values for your site.
>
> The only tapetype parameter amanda actually uses is capacity.
> So you could hand create a definition and be close enough
> for government work.
>
> Jon
Created on OmniOS v11 r151006:
$ amtapetype -f -b 524288 -t ULT3580-TD5 /dev/rmt/0b 2>&1 | tee
/etc/opt/csw/amanda/weekly/tapetype-512k-block
Checking for FSF_AFTER_FILEMARK requirement
Applying heuristic check for compression.
Wrote random (uncompressible) data at 85721088 bytes/sec
Wrote fixed (compressible) data at 295261525.33 bytes/sec
Compression: enabled
Writing one file to fill the volume.
Wrote 1519480995840 bytes at 85837 kb/sec
Got LEOM indication, so drive and kernel together support LEOM
Writing smaller files (15194390528 bytes) to determine filemark.
device-property "FSF_AFTER_FILEMARK" "false"
define tapetype ULT3580-TD5 {
comment "Created by amtapetype; compression enabled"
length 1483868160 kbytes
filemark 868 kbytes
speed 85837 kps
blocksize 512 kbytes
}
# for this drive and kernel, LEOM is supported; add
# device-property "LEOM" "TRUE"
# for this device.
I ran amtapetype for a number of different block sizes (32k, 256k, 512k and
2048k) but I found that
block sizes over 512 kbytes gave me driver issues and no LEOM capability. My
amdump reports show
fairly reasonable tape streaming speeds:
Avg Tp Write Rate (k/s) 143476 143842 5723.0
If you have a different system just run amtapetype and be patient. It will be
worth the wait.
Regards,
Tom
Tom Robinson
IT Manager/System Administrator
MoTeC Pty Ltd
121 Merrindale Drive
Croydon South
3136 Victoria
Australia
T: +61 3 9761 5050
F: +61 3 9761 5051
E: tom.robin...@motec.com.au
signature.asc
Description: OpenPGP digital signature
Re: tapetype for IBM ULTRIUM-TD5?
On Thu, Jan 16, 2014 at 06:04:14PM -0500, Michael Stauffer wrote: > Hi, > > I'm setting up amanda 3.3.4. I can't find a definiton for changer's drives > (IBM ULTRIUM-TD5 LTO-5) in /etc/amanda/template.d/tapetypes > > Can someone point me to a source for this, or to where I can learn how to > determine the params I need for the drives? Thanks > The command amtapetype should be in your amanda server installation. It can be used to determine the values for your site. The only tapetype parameter amanda actually uses is capacity. So you could hand create a definition and be close enough for government work. Jon -- Jon H. LaBadie j...@jgcomp.com 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (609) 477-8330 (C)
tapetype for IBM ULTRIUM-TD5?
Hi, I'm setting up amanda 3.3.4. I can't find a definiton for changer's drives (IBM ULTRIUM-TD5 LTO-5) in /etc/amanda/template.d/tapetypes Can someone point me to a source for this, or to where I can learn how to determine the params I need for the drives? Thanks -M
Re: 'labelstr' param in amanda.conf
Thanks for the reply. I don't have multiple configurations, I'm just trying to figure out how to set things up. So it sounds like I can have a single configuration that uses the same group of tapes as defined by 'labelstr', and I use the DLE lists to break things up into manageable chunks. Then with amdump, I can specify the individual DLE's to be dumped? -M On Thu, Jan 9, 2014 at 1:58 PM, Jean-Louis Martineau wrote: > On 01/09/2014 01:47 PM, Michael Stauffer wrote: > >> >> Hi, >> >> I'm setting up amanda 3.3.4. >> >> Regarding 'labelstr' in amanda.conf: >> >> The documentation says: "If multiple configurations are run from the same >> tape server host, it is helpful to set their labels to different strings >> (for example, "DAILY[0-9][0-9]*" vs. "ARCHIVE[0-9][0-9]*") to avoid >> overwriting each other's tapes." >> >> Does this mean that if I have multiple configurations in order to break >> up a large 30TB data set into managable chunks, each configuration will >> have to have a particular set of tapes assigned to it? That seems very >> awkward if so. >> >> > yes > > Why do you have multiple configurations? > You should do it with one configuration and multiple dle. > > Jean-Louis >
