Hey,
So I've noticed that sometimes Amanda will fill up a tape with more than 400gb
(LTO3) - I'm assuming this is down to compression? Is there another way to
limit this from happening apart from turning hardware and software compression
off?
Thanks,
DLE that is larger than the physical tape
would be without compression, else amanda would report that the
DLE was larger than the tape...
What goal/outcome are you seeking ?
Brian
On Wed, Jan 05, 2011 at 11:34:47AM -0500, rory_f wrote:
Hey
choogendyk wrote:
On 1/5/11 12:00 PM, rory_f wrote:
I want to ensure tapes are filled 100% each time where possible. I've
written a script in python to look at directory, figure out size, and
create a disklist which will ensure a round about size for each disklist
file - so
Charles Curley wrote:
On Wed, 05 Jan 2011 13:19:42 -0500
rory_f amanda-forum at backupcentral.com wrote:
Perhaps what i'm looking to do is guarantee the most economical way
of filling the tapes.
Which is more valuable, a few terabytes of tape space, or your time
Gene Heskett wrote:
On Tuesday 09 March 2010, rory_f wrote:
Absolutely no, amanda ignores that. It is for your edification only.
One other question: Did you take note of whether or not the drive was
streaming steadily, or was it 'shoe shining' occasionally? One can normally
hear
Gene Heskett wrote:
On Tuesday 09 March 2010, rory_f wrote:
If the card is wide scsi, perhaps a cabling issue or termination issue has
caused it to fall back to scsi-II width and speeds? I have read that some
cards do this, and a reboot once the problem is solved, might bring back
Gene Heskett wrote:
On Monday 08 March 2010, rory_f wrote:
Please do. It could be something I missed, or it could be a brand new
phenomenon to file away in my trivia file.
gene,
ama...@backup tor]$ amtapetype -o -f /dev/nst0 -e 400G
Writing 1024 Mbyte compresseable data: 31 sec
Dustin J. Mitchell wrote:
On Tue, Mar 9, 2010 at 9:55 AM, rory_f amanda-forum at
backupcentral.com wrote:
One question; i don't have to run amtapetype every time i do this do i? For
instance, say the speed problems are resolved, will amdump pick up on this
automatically or does
Gene Heskett wrote:
On Saturday 06 March 2010, Jon LaBadie wrote:
Because the scsi buss is a transmission line, and demands a decent VSWR,
there are 2 things to remember when dealing with scsi.
1.A list of pre-requisites that must be met if it is to work:
1.a: termination
[quote=Gene Heskett]On Monday 08 March 2010, rory_f wrote:
Gene Heskett wrote:
In your case, two things. Is it the last drive on the cable?, and is it
terminated properly? And I would certainly check the 5 volt line of the host
computer to see if its sagging in its old age. 4.85 volts
Gene Heskett wrote:
On Monday 08 March 2010, Dustin J. Mitchell wrote:
On Mon, Mar 8, 2010 at 9:55 AM, Gene Heskett gene.heskett at
verizon.net
wrote:
Be my guest if you have write privileges.
It's a wiki - everyone has write privileges (including, to my dismay,
anyone?
i'm doing a tape run now, using the original tapetype definition, and it has
filled a tape to around 238gb and moved onto the next one (well it has changed
tapes,it's still waiting to write to tape)
is this normal?
Dustin J. Mitchell wrote:
On Fri, Mar 5, 2010 at 9:17 AM, rory_f amanda-forum at
backupcentral.com wrote:
i'm doing a tape run now, using the original tapetype definition, and it
has filled a tape to around 238gb and moved onto the next one (well it has
changed tapes,it's still
the new one..
On Fri, Mar 05, 2010 at 12:21:32PM -0500, rory_f wrote:
Dustin J. Mitchell wrote:
On Fri, Mar 5, 2010 at 9:17 AM, rory_f amanda-forum at
backupcentral.com wrote:
i'm doing a tape run now, using the original
Jon LaBadie wrote:
On Fri, Mar 05, 2010 at 02:57:01PM -0500, rory_f wrote:
Hey guys. Thanks
I checked my library GUI and for the tape run i was just talking about,
where it was stopping around 230gb, it seems compression WAS on. I turned
it off via mt and now the gui says off
Jon LaBadie wrote:
On Fri, Mar 05, 2010 at 02:57:01PM -0500, rory_f wrote:
Hey guys. Thanks
I checked my library GUI and for the tape run i was just talking about,
where it was stopping around 230gb, it seems compression WAS on. I turned
it off via mt and now the gui says off
[ama...@backup tor]$ amtapetype -o -f /dev/nst0 -e 400G
Writing 1024 Mbyte compresseable data: 31 sec
Writing 1024 Mbyte uncompresseable data: 32 sec
Estimated time to write 2 * 409600 Mbyte: 25600 sec = 7 h 6 min
wrote 6684672 32 Kb blocks in 51 files in 5871 seconds (No space left on
Currently we are using this:
03:0c.0 SCSI storage controller: Adaptec AIC-7892A U160/m (rev 02)
And it is throwing up hardware errors every now and again so we want to grab
another one to put in there. I understand it could also be cabling which is
causing this and we'll address that too
rory_f wrote:
Hi,
amrecover sethost archive2.win.mrxfx.com
200 Dump host set to archive2.win.mrxfx.com.
amrecover setdisk /array/sata-1/xxx/WS039
200 Disk set to /array/sata-1/xxx/WS039.
but in the log for it, amidxtaped reports this:
1241720675.702638: amidxtaped: disk
Hi,
amrecover sethost archive2.win.mrxfx.com
200 Dump host set to archive2.win.mrxfx.com.
amrecover setdisk /array/sata-1/xxx/WS039
200 Disk set to /array/sata-1/xxx/WS039.
but in the log for it, amidxtaped reports this:
1241720675.702638: amidxtaped: disk =
[r...@backup tor]# cat amidxtaped.20090417114001.debug
1239982801.291428: amidxtaped: pid 3896 ruid 790 euid 790: start at Fri Apr 17
11:40:01 2009
1239982801.291510: amidxtaped: amidxtaped: version 2.6.0p2
1239982806.292428: amidxtaped: FEATURES=9ffe00
1239982806.294173:
hi,
we're trying to organise back up logs for our users to interface with and tell
us when they need files restored from tape.
i've created all the listings from the index/ directory, made a copy, gzip -d'd
them to get the filelisting for each entry - but i'm trying to find a way to
figure
Dustin J. Mitchell wrote:
On Thu, Feb 19, 2009 at 11:41 AM, rory_f amanda-forum at
backupcentral.com wrote:
i know i can `amadmin tor find | grep DLE` to find the amanda tape, and
then compare that to changer-barcodes - but its a bit of a long process
I think that's
Dustin J. Mitchell wrote:
On Thu, Feb 19, 2009 at 11:41 AM, rory_f amanda-forum at
backupcentral.com wrote:
i know i can `amadmin tor find | grep DLE` to find the amanda tape, and
then compare that to changer-barcodes - but its a bit of a long process
I think that's
Dustin J. Mitchell wrote:
On Thu, Feb 19, 2009 at 2:52 PM, rory_f amanda-forum at
backupcentral.com wrote:
how hard would it be to migrate our naming convention over to match our
labels ? is there any way of doing it?
Well, the Amanda label is written on each tape
Frank Smith wrote:
rory_f wrote:
Dustin J. Mitchell wrote:
how hard would it be to migrate our naming convention over to match
our labels ? is there any way of doing it?
If you're talking about changing barcodes to match Amanda's tape label,
couldn't you just replace
rory_f wrote:
Dustin J. Mitchell wrote:
On Thu, Feb 19, 2009 at 2:52 PM, rory_f amanda-forum at
backupcentral.com wrote:
how hard would it be to migrate our naming convention over to match our
labels ? is there any way of doing it?
Well, the Amanda label is written
As amanda uses tar, you surely can restore a tape (or a portion of a tape,
perhaps just a dle?) using the command line 'tar' command, right ?
Is it just the same as a normal extract ? tar -xvf /dev/nst0 ?
Or do you have to do other things to ensure this works properly.
Nothing is wrong with
Dustin J. Mitchell wrote:
On Wed, Nov 12, 2008 at 10:26 PM, rory_f amanda-forum at
backupcentral.com wrote:
i have a feeling it might be hardware too. im gonna try with _brand_ new
tapes tomorrow, to see if i cannot reproduce this..
It looks like it might be a changer problem
Hi,
Amanda hasnt been acting as it should. See the output of a failed dump below:
STATISTICS:
Total Full Incr.
Estimate Time (hrs:min)0:04
Run Time (hrs:min) 3:07
Dump Time (hrs:min)
Dustin J. Mitchell wrote:
On Wed, Nov 12, 2008 at 7:01 PM, rory_f amanda-forum at
backupcentral.com wrote:
Amanda hasnt been acting as it should. See the output of a failed dump
below:
This actually looks like two other bugs we're in the process of
chasing -- but may turn out
the question again then i guess?
hi guys.
we're run amcheckdump on a backup we just did and it has given us a few outputs
we're not sure about -whether it is tar being non-understanding of a backup
using spanned tapes, or something else? we're a bit lost so hopefully someone
can help
ps.
Jon LaBadie wrote:
On Wed, Nov 05, 2008 at 09:39:36AM -0500, rory_f wrote:
the question again then i guess?
hi guys.
we're run amcheckdump on a backup we just did and it has given us a few
outputs we're not sure about -whether it is tar being non-understanding of
a backup
Paul Bijnens wrote:
Indeed, use a changer and set runtapes to something greater than 1.
Amanda will write a tape until she hits End Of Tape (signaled by a write
error actually), and then move to a new tape. The whole backup image
will be restarted on the next tape. (With using
rory_f wrote:
Paul Bijnens wrote:
Indeed, use a changer and set runtapes to something greater than 1.
Amanda will write a tape until she hits End Of Tape (signaled by a write
error actually), and then move to a new tape. The whole backup image
will be restarted on the next tape
Hi guys,
any ideas??
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--
hi guys.
we're run amcheckdump on a backup we just did and it has given us a few outputs
we're not sure about -whether it is tar being non-understanding of a backup
using spanned tapes, or something else? we're a bit lost so hopefully someone
can help
ps. ignore the file paths below, i just
Hey guys,
How can this (see title) be done?
We need to have a full list of all directories sent to the tape for easy and
quick restore process.
Would a simple `dd if=/dev/nst0 bs=32k skip=1 |/bin/gtar -tvf -` output a
full listing?
Is there a program within amanda to do so?
I know
This is an edited version of a previous post
Hi,
We managed to up our speed of dumping and writing a whole lot by using a
holding disk, which is great. However, the data we wrote, around 245gb, failed
a amcheckdump and i couldnt, therefore, not amrestore anything.
After the
39 matches
Mail list logo
