On Wed, Dec 27, 2017 at 17:26:04 -0500, Jean-Louis Martineau wrote:
> 'amadmin tape' list the oldest reusable label, it doesn't use the
> taperscan algorithm and it doesn't check what is currently loaded in the
> changer.
> 'amcheck' and 'amtape' run the taperscan algorithm and verify they are
Hello,
i have DLEs which are bigger than a single tape now. And i thought the solution
would be to change the following in my amanda.conf
runtapes 2
holdingdisk hd1 {
comment first holding disk
directory /mnt/amanda-holding # where the holding disk is
chunksize 50Gb # size
On 06/07/2012 05:47 AM, Karsten Fuhrmann wrote:
Hello,
i have DLEs which are bigger than a single tape now. And i thought the solution
would be to change the following in my amanda.conf
runtapes 2
holdingdisk hd1 {
comment first holding disk
directory /mnt/amanda-holding # where
Thanks,
but how do i tell amanda that i changed the tape when the backup is run through
a cronjob each night?
On 07.06.2012, at 14:11, Jean-Louis Martineau wrote:
On 06/07/2012 05:47 AM, Karsten Fuhrmann wrote:
Hello,
i have DLEs which are bigger than a single tape now. And i thought the
On 06/07/2012 08:53 AM, Karsten Fuhrmann wrote:
Thanks,
but how do i tell amanda that i changed the tape when the backup is run through
a cronjob each night?
configuring chg-manual is the old way to do it, it is better to
configure and interactivity module:
# amanda.conf
# define an
On Thu, Jan 07, 2010 at 18:28:05 +0100, Geert Uytterhoeven wrote:
On Thu, Jan 7, 2010 at 00:31, brnn8r amanda-fo...@backupcentral.com wrote:
This is my first post on this forum and I'm a bit of a Amanda newb.
At my company we have a Weekly backup regime and after each weekly backup
the
On Thu, Jan 7, 2010 at 00:31, brnn8r amanda-fo...@backupcentral.com wrote:
This is my first post on this forum and I'm a bit of a Amanda newb.
At my company we have a Weekly backup regime and after each weekly backup the
tape is sent offsite for storage and the next Weekly tape is brought in.
Hi All,
This is my first post on this forum and I'm a bit of a Amanda newb.
At my company we have a Weekly backup regime and after each weekly backup the
tape is sent offsite for storage and the next Weekly tape is brought in.
I've just come back from holiday and Amanda is expecting our next
brnn8r wrote:
Hi All,
This is my first post on this forum and I'm a bit of a Amanda newb.
At my company we have a Weekly backup regime and after each weekly
backup the tape is sent offsite for storage and the next Weekly tape is
brought in.
I've just come back from holiday and Amanda
I don't want to disagree with Steve's assessment. Mostly I think
he's right-on with his comments. However ...
I have on perhaps 5 occassions used 'amrmtape' followed by
'amlabel' to force-clear a tape so that it could re-cycle
early. Mostly this has occurred in the (thankfully rare) case
of
On Thu, Sep 17, 2009 at 4:08 AM, Dominik Schips domi...@s235.de wrote:
The error message in the amanda status report is:
dump to tape failed: driver: [writing file: No space left on device]
Can you attach the trace log so we can see what happened after that?
And also the taper's debug log.
Hello,
I did an upgrade from Amanda 2.4.4p3-3 (Debian sarge) to Amanda
2.5.2p1-4 (Debian lenny).
After this upgrade Amanda didn't take a new tape if a DLE failed because
of emty space on the current tape.
With Amanda 2.4.4 it took the next tape if it reaches the end of one
tape.
I changed some
Hi,
I am getting confused (so what's new) about the first three lines a
report emailed by amdump sends me. I did several dumps in a row and
got these results.
These dumps were to tape DAILY-3.
The next tape Amanda expects to use is: DAILY-14.
The next new tape already labelled is: DAILY-4
about amadmin tape but there sometimes seems to be a
difference as to what amadmin and amdump use for the next tape.
Thanks
_
Robert P. McGraw, Jr.
Manager, Computer System EMAIL: [EMAIL PROTECTED]
Purdue
.
tape daily:100016 or a new tape.
tape daily:100017 or a new tape.
tape daily:100018 or a new tape.
The next new tape already labelled is: daily:100015.
The next tape numbers are correct
new tape already labelled is: daily:100015.
The next tape numbers are correct and the tapes are labeled.
Why do I get a new tape as one of the next 4 tapes that will be used.
You did not show the tapelist. My guess is that you do not have
28 tapes (your tapecycle) showing as used at least
How do I query amanda for the next tape?
I run my backups on my home server; at times I am away from home so I
can't feed the tapes in daily.
I would like to be emailed a reminder telling me which tape is next.
Right now amanda tells me which tape it expects when it completes a
successful
On Thu, Dec 01, 2005 at 06:53:31AM -0800, Yan Seiner enlightened us:
How do I query amanda for the next tape?
I run my backups on my home server; at times I am away from home so I
can't feed the tapes in daily.
I would like to be emailed a reminder telling me which tape is next.
Right
Yan Seiner wrote:
How do I query amanda for the next tape?
I run my backups on my home server; at times I am away from home so I
can't feed the tapes in daily.
I would like to be emailed a reminder telling me which tape is next.
Right now amanda tells me which tape it expects when
2005 15.54
A: amanda-users@amanda.org
Oggetto: Next tape?
How do I query amanda for the next tape?
I run my backups on my home server; at times I am away from home so I
can't feed the tapes in daily.
I would like to be emailed a reminder telling me which tape is next.
Right now amanda tells me
On Thu, 1 Dec 2005 at 6:53am, Yan Seiner wrote
How do I query amanda for the next tape?
I run my backups on my home server; at times I am away from home so I can't
feed the tapes in daily.
I would like to be emailed a reminder telling me which tape is next. Right
now amanda tells me which
that will check what tape I have in the drive.
*** A TAPE ERROR OCCURRED: [not an amanda tape].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: DailySet104.
Here is the message when I run amverify
Defects file is /tmp
of made a mistake.
Is there a amanda program that will check what tape I have in the drive.
*** A TAPE ERROR OCCURRED: [not an amanda tape].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: DailySet104.
Here is the message
amanda tape it is as I assume when
labelling I may of made a mistake.
Is there a amanda program that will check what tape I have in the drive.
*** A TAPE ERROR OCCURRED: [not an amanda tape].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape
to flush them to tape.
The next tape Amanda expects to use is: DailySet104.
Here is the message when I run amverify
Defects file is /tmp/amanda/amverify.20028/defects
amverify DailySet1
Mon Jun 27 15:41:39 BST 2005
Using device /dev/nst0
Waiting for device to go ready...
Rewinding...
Processing label
Vicki Stanfield wrote:
Sorry. I didn't notice that in your earlier email. How about using dd to
read the header info off the tape?
Umm, please, no ... at least NOT YET ...
Chuck, why not simply use amcheck -s conf? It checks if the inserted
tape is the one to write to as well ...
Stefan
break their files,
some 250+ Gig, into both /usr5/joy and the new /usr5/joy2) we have
the added problem of limited work area.
Because the DLE dumps direct-to-tape beccause of limited work area
we will likely hit EOF and amanda will have to restart the tar after
advancing to the next tape
Greets everyone;
Last nite, my backup went a bit too close to EOT, and hit it while
trying to write the last 75 megs worth of indices and configs.
This drive is supposed to be able to hit EOT, load the next tape and
keep going, but I've never seen it work, nor is there a lot of docs
available
The dumps were flushed to tape Indyme014.
The next tape Amanda expects to use is: a new tape.
[EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist
20030303 Indyme014 reuse
20030228 Indyme013 reuse
20030227 Indyme012 reuse
20030227 Indyme011 reuse
20030226 Indyme010 reuse
20030225 Indyme009
[Posted and Cc'ed]
On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote:
The dumps were flushed to tape Indyme014.
The next tape Amanda expects to use is: a new tape.
[EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist
20030303 Indyme014 reuse
20030228 Indyme013 reuse
On Mon, 3 Mar 2003 at 9:20am, John Oliver wrote
The dumps were flushed to tape Indyme014.
The next tape Amanda expects to use is: a new tape.
[EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist
20030303 Indyme014 reuse
20030228 Indyme013 reuse
20030227 Indyme012 reuse
20030227
On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote:
The dumps were flushed to tape Indyme014.
The next tape Amanda expects to use is: a new tape.
[EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist
20030303 Indyme014 reuse
20030228 Indyme013 reuse
20030227 Indyme012 reuse
On Mon, Mar 03, 2003 at 05:57:14PM +, Simon Young wrote:
On Mon, Mar 03, 2003 at 09:20:22AM -0800, John Oliver wrote:
The dumps were flushed to tape Indyme014.
The next tape Amanda expects to use is: a new tape.
[EMAIL PROTECTED] root]# cat /etc/amanda/DailySet1/tapelist
20030303
On Mon, Feb 03, 2003 at 01:07:51PM -0500, Joshua Baker-LePain wrote:
On Mon, 3 Feb 2003 at 12:26pm, John wrote
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda
overwrite active tape Daily01].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
Is there a way to make it use the existing 7 remaining tapes instead of
throwing a new tape at it? It's mostly a time thing for getting
On Mon, 3 Feb 2003 at 12:26pm, John wrote
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda expects to use is: a new tape.
Is there a way to make it use the existing
On Mon, Feb 03, 2003 at 01:07:51PM -0500, Joshua Baker-LePain wrote:
On Mon, 3 Feb 2003 at 12:26pm, John wrote
*** A TAPE ERROR OCCURRED: [cannot overwrite active tape Daily01].
Some dumps may have been left in the holding disk.
Run amflush to flush them to tape.
The next tape Amanda
tape Amanda expects to use is: a new tape.
Is there a way to make it use the existing 7 remaining tapes instead of
throwing a new tape at it? It's mostly a time thing for getting a new
tape, but it'd be nice to be able to go on with the next tape in the
cycle.
Change your tapecycle to match how
I still get the same message.
I note that tapelist still shows tape Daily04 as 'reuse', even though I
amrmtape 'd it.
Provided you changed your amanda.conf so that it is now expecting 7 tapes,
you could edit the tapelist file and remove the bad tape from it.
tape should be. the last entry is the next tape. Assuming you have
entered a new tape number 4, you might ensure that is the last entry,
and the first field (date field) is the oldest date (the number zero
ought to do it!) you can use amcheck to test.
It's unfortunate that your tape drive
the first dump is
complete, Amanda says The next tape Amanda expects to use is Daily12.
Why isn't it asking for a new tape?
Don't know without seeing your tapelist and knowing what your tapecycle
is set to.
Ben
John R. Jackson, Technical Software Specialist, [EMAIL PROTECTED]
Hi.
How does Amanda decide which tape to use next -- such as when mentioning
it in mailed backup reports?
The next tape Amanda expects to use is ..
I ask because I have labelled a dozen tapes and, after the first dump is
complete, Amanda says The next tape Amanda expects to use is Daily12
Juanjo wrote:
After doing some checks, I'm gonna let amanda do a first backup, about 180
Gigs of data.
Well, after those checks, the pointer is at tape 3, how can I tell amanda
to start with tape 1?
I've tried launching:
amrmtape confname tapelabel
but it says something about
After doing some checks, I'm gonna let amanda do a first backup, about 180
Gigs of data.
Well, after those checks, the pointer is at tape 3, how can I tell amanda
to start with tape 1?
I've tried launching:
amrmtape confname tapelabel
but it says something about preserving original
If you don't wish to preserve that data you could remove the tapelist
fileswhich would be recreated during backup
Juanjo wrote:
After doing some checks, I'm gonna let amanda do a first backup, about 180
Gigs of data.
Well, after those checks, the pointer is at tape 3, how can I tell
One simple way would be to do this a few hours before the real
amdump run:
amadmin config tape | Mail -s Amanda tapes needed whoever
I choose to do that using amcheck instead
I see several advantages: it emails automatically, check the tape
status, check the clients...
I taught my guys to
to
check for next tape name. I was just pointing out how the what tape
is next information (without the whole Amanda daily report) could be
sent to his operators so they would know what to mount.
And if they don't get the normal run mail, they also won't get the amcheck
I didn't like that tape mail so
1) How can I use gtar to backup directories with symbolic links ? For
example, \ in directory A, there are 3 symbolic links pointing to C,
D, E directories. Is \ it possible to backup those files in C, D, E?
Add a disk list entry for the absolute path at C, D and E
Hopefully tar will NEVER
schedule to change tape manually. They
will not receive amanda email to check for next tape name.
Different operations handle things in different ways, but it sounds to
me like it would be a good idea to let them know for sure what Amanda
is going to want. Otherwise Amanda is going to refuse the tape
manually. They will not
receive amanda email to check for next tape name.
Regards,
Edward.
I just got this in my report today:
The dumps were flushed to tape TAPE25.
The next tape Amanda expects to use is: a new tape.
STATISTICS:
Total Full Daily
.
.
.
tapecycle is set to 25 in my
51 matches
Mail list logo
