Hi Dustin,
Good work releasing beta3. Few thing that come to my mind while testing amvault
regarding slections of dumps.
- latest dump with --src-timestamp latest
- all dumps without specifying --src-timestamp
- parts by specifying dates eg. --src-timestamp 20100926-20101008
I would likte
Hi Jon,
We identified a bug in ZWC about missing result for C drive in x
response. We have fixed the issue and I am testing it before releasing the
next Community edition version 3.1.3.
In the meanwhile, have the backups worked after changing the estimate to
client?
Regards,
Prashant
On
I went and reset my block size to 1024k and relabeled my tapes 1017 and 1018.
define changer c4 {
tpchanger chg-robot:/dev/changer/0
changerfile chg-zd-mtx-state
property tape-device 0=tape:/dev/rmt/0cbn
property
I'm vaulting from config hansa and I'm getting parse error about hansa-vault
config ?
parse error: could not open conf file
/etc/opt/amanda/hansa-vault/amanda.conf: No such file or directory
amdevcheck: errors processing config file at /opt/sfw/sbin/amdevcheck line 113.
parse error: could
these well enough? Or are they not
working for you?
- latest dump with --src-timestamp latest
Works fine.
- all dumps without specifying --src-timestamp
Works fine.
- parts by specifying dates eg. --src-timestamp 20100926-20101008
You can specify a range of *dump* timestamps (the dates
On Fri, Oct 8, 2010 at 8:40 AM, McGraw, Robert P rmcg...@purdue.edu wrote:
Dustin, thanks very much for your help in resolving this.
Sure thing. Jean-Louis has, in the interim, fixed the problem of not
being able to eject when a fatal error occurs in the tape device. So
this one is fixed twice
On Fri, Oct 8, 2010 at 9:01 AM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
I'm vaulting from config hansa and I'm getting parse error about hansa-vault
config ?
Does such a configuration exist? I thought your config was named HANSA?
Dustin
--
Open Source Storage Engineer
Dustin,
Just installed 3.1.2 to replace a 2.6.1 on Solaris 10x86.
Worked as well as could be expected, given that I told it to
force level 0 on everything. A mistake since its 2 or 3 Tbytes
of data an 'only' 2 LTO4 tapes per run.
Thank you - I've noted the % indicated on the amflush, I'd often
ok this will vault all full dumps in my configuation but can I select only the
most resent for each filesystem ?
amvault --dry-run --fulls-only --dst-changer vault \
--label-template EMS1-7% --autolabel volume-error hansa
What does most recent version mean in this case?
Thanks Gunnar
Thanks for the tip about --autolabel any, by the way. I accidentally
implemented it as --autolabel all. The fix is easy :)
On Fri, Oct 8, 2010 at 11:17 AM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
ok this will vault all full dumps in my configuation but can I select only
the most
On Fri, Oct 08, 2010 at 05:52:51PM +0530, Prashant Joshi wrote:
Hi Jon,
We identified a bug in ZWC about missing result for C drive in x
response. We have fixed the issue and I am testing it before releasing the
next Community edition version 3.1.3.
In the meanwhile, have the backups
On Fri, Oct 8, 2010 at 10:24 AM, Brian Cuttler br...@wadsworth.org wrote:
Feature request (?) - There are checks for DLE tape, seems almost
silly but a check for
SUM(DLEs) (tape_capacity * runtapes)
One DLE with a full size larger than available
On Fri, Oct 08, 2010 at 11:06:40AM -0500, Dustin J. Mitchell wrote:
On Fri, Oct 8, 2010 at 10:24 AM, Brian Cuttler br...@wadsworth.org wrote:
Feature request (?) - There are checks for DLE tape, seems almost
? ? ? ? ? ? ? ? ? ? ?silly but a check for
? ? ? ? ? ? ? ? ? ? ? ? SUM(DLEs)
I have a client with an amandad that has been running since Sep 23...
backup 97592 0.0 0.1 26780 7016 ?? Ss 23Sep10 40:30.43 amandad
Most of the backups on that client still work fine. But two DLEs
fail nightly. On the server, you get:
1286525084.841860: chunker: getcmd: START
Is this because amvault is considered a flush ?
Tape usage statistic is rather odd as well.
Otherwise is seems to work quite well - good work !
Thanks Gunnar Gunnarsson
*** THE DUMPS DID NOT FINISH PROPERLY!
The dumps were vaulted to tape EMS1-71.
The next 2 tapes Amanda expects to use are:
On Fri, Oct 8, 2010 at 1:11 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
Is this because amvault is considered a flush ?
Tape usage statistic is rather odd as well.
Can you send the trace log that generated this report?
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
On Fri, Oct 8, 2010 at 12:26 PM, Brian Cuttler br...@wadsworth.org wrote:
I realize that there IS NO Solution within amanda. This is a capacity
planning issue for the humans to solve, but amanda can warn via the
amdump report, that problems are imminent and that human capacity
planning is
On Fri, Oct 8, 2010 at 1:07 PM, John Hein jh...@symmetricom.com wrote:
I have a client with an amandad that has been running since Sep 23...
..
2000 APPLICATION 36
|;auth=BSD;compress-fast;index;exclude-file=.no-amanda-backup;exclude-file=.nobak;exclude-file=.noback;exclude-file=.nodump;
On Fri, Oct 8, 2010 at 1:11 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
Is this because amvault is considered a flush ?
..
*** THE DUMPS DID NOT FINISH PROPERLY!
No, it was a bug - amvault didn't write the FINISH driver line
before calling amreport, so amreport didn't think it was
No I was wrong about it only delayed the flushing until at the end. Is that a
new behaviour in versioh 3.2.0 ?
The only problem I got was on the client side for the root filesystem zfs.
/-- hansabck / lev 1 FAILED [/usr/local/bin/tar exited with status 2: see
On Fri, Oct 8, 2010 at 5:42 PM, Gunnarsson, Gunnar
gunnar.gunnars...@svk.se wrote:
No is a HP Ultrium LTO 3 tape drive:
Yes I think the data was written to tape I will verify that next week.
OK. You should adjust the length in your tapetype definition, then -
your tape appears to be at least
can anyone recommend a good, inexpensive taper for a startup? I don't
need terabytes of storage, so something in the low gb count, but fairly
quick, widely available, and highly inexpensive would be best.
22 matches
Mail list logo
