Could it be because of trying to fill tapes(vtapes in my case) to 100%?
following is configured in monthlyfull and weeklyfull amanda configuration,
flush-threshold-dumped100
flush-threshold-scheduled 100
taperflush100
autoflush yes
+
>>I assume you are using a recent release of amanda?
I am sure this is not latest because I went with OpenCSW repository available
for solaris platform instead of compiling amanda package myself from source.
3.1.1 is the version of amanda on this system, as shown below.
/opt/csw/bin/pkgutil -a
>Couple of questions:
>I assume, that as a test, the "monthly"full config is being run daily?
yes monthly full is being run daily.
>Does amoverview work on weeklyfull but not on monthlyfull?
no amoverview doesn't work on any of above. Always E.
>The amoverview output you show indicated errors
Yes it works with monthlyfull as well. It so happened that I just ran amadmin
on weeklyfull first so I posted o/p of weeklyfull in my last post while I
should have actually posted o/p for monthlyfull. Sorry for creating confusion.
/opt/csw/sbin/amadmin monthlyfull find
datehost
Thanks , I took a look at that man page just now. I tried some other
options/switches for amoverview , I always got E or EE while my amanda backup
reports were OK most of the times for all DLEs.
Just for the sake of trying I tried amadmin weeklyfull find and guess what !
this works a lot better
Thanks Jon and Brian
I will try amadmin, i did however try, amoverview. Do you know how to interpret
the o/p from amoverview?
/opt/csw/sbin/amoverview monthlyfull
date 02 02 02 02 02 02 02 03 03 03 03 03 03 03 03 03
03 03 03 03 03
host disk 22 23 24
Hello ,
I am wondering if there is anything in Amada that can give me information on
how old the backup of a DLE exists in the system and similar useful
information. I do receive daily AMANDA MAIL REPORT when a job is finished but
that doesn't tell me how old the backup of DLE is available for
Just an update.
The issue was resolved by modifying all of DLEs in disklist from /export/./abc
to /export/abc which means I removed '.' from all DLEs.
Now I can recover anyfile/directory using amrecover. Hope this is helpful for
people using '.' inside their DLEs.
Thanks
+--
Well, I have added one more partition in disklist file - > /etc . This sure
does not have '.' like /export/./local/
I have started to think that either tar/gtar or amrecove, one of that does not
work well with a . in the specified DLE. It may also be version on solaris
atleast.
I am going t
If I do grep manually from terminal, I see that file is available.
/opt/csw/bin/gzip -dc
/opt/csw/etc/amanda/weeklyfull/index/amclient.domain/_export_._local/2011011117_0.gz
| grep gcc-3.2-sol8-sparc-local
/local/gcc-3.2-sol8-sparc-local
+--
Hi,
I have been backing up using amanda for about 1 month and I agree that I should
have checked amrestore earlier. Now that I am trying to restore
files/directories using amrestore, there is always this error :
Not found in archive
tar: Exiting with failure status due to previous errors
Thi
Thanks for your quick advise Brian,
I still want to post my DLEs and their sizes, may be you or someone can throw
additional ideas.
weeklyfull ~ total size about 58GB
client.domain.com /export/./abc /export {12G
comp-tar
include "./abc"
} -1
client.domain.com /export/./def /ex
Thanks for your quick advise Brian,
I still want to post my DLEs and their sizes, may be you or someone can throw
additional ideas.
weeklyfull ~ total size about 58GB
pluto.ece.iit.edu /export/./abc /export {12G
comp-tar
include "./abc"
} -1
pluto.ece.iit.edu /export/./def /ex
Hello again,
I think I am starting to realize that something needs to be configured properly
in order to Fill the tapes to their MAX capacity. I'd like some advise on that.
I can create another thread for that however, it may be something to do with
existing configuration so I am continuing the
Thank you Jon and everyone who have helped me understand a lot of things in
Amanda. I have been able to split DLEs into multiple DLEs for the sake for
distributing them in proper schedule. I also tried using inparallel and maxdump
in amanda config and was successful only after configuring correc
Actually the reason I decided to split DLE into multiple DLEs because I
thought it is tar/gzipping 31GB data in one go and it might cause lower i/o
speed and also feared if it 'd use more server resources. Although , I am
actually looking to make best use of 16GB memory on amanda server and 8 G
Oh, it looks like when I add splitdisk_buffer, it shows me below error on
amcheck,
amcheck test
"/opt/csw/etc/amanda/test/amanda.conf", line 43: dumptype parameter expected
"/opt/csw/etc/amanda/test/amanda.conf", line 43: end of line is expected
amcheck: errors processing config file
Relevant p
#Congratulations on a successful amdump!
Wow, tell you what I am so happy to see those words! Thanks much!
By the time I saw your reply, I had impatiently split my single DLE into 9 DLEs
which also includes the last one for excluding all 8 DLEs on the top.
I did see same message again in the a
Ok guys, I got busier with other tasks so could not reply. sorry about that.
I did manage upgrading to Amanda 3.x version on solaris amanda server and
solaris amanda client.
I tried amcheck and it worked. So I tried amdump. However it seems to me I
really need to adjust the numbers because I go
Sorry for double reply. I pressed back button on Midori and forum
reposted/resent my reply earlier.
Thanks for that info JL. I was completely unaware of OpenCSW. I will try to
use Opencsw and see if I can get Amanda to 3.1.1 and proceed from there which
will be best thing to do. Anyhow I don't
Sorry for being late to reply as I was away from computer for last 5 days.
Has this system successfully passed an "amcheck configname"?
Yes, It works fine always. No errors found.
Here is the o/p
Holding disk /random//amanda/amandahold/test: 3881997 kB disk space available,
using 3881997 kB
Sorry for being late to reply as I was away from computer for last 5 days.
Has this system successfully passed an "amcheck configname"?
Yes, It works fine always. No errors found.
Here is the o/p
Holding disk /random//amanda/amandahold/test: 3881997 kB disk space available,
using 3881997 kB
Hi,
I just had to create those slots directories (29) and then I edited amanda.conf
and modified length as " length 10240 MB " in tapetype defination. After this
ran amlabel to label 29 slots and then amcheck test which did not find problems.
Only thing I had not done was restart Amanda server
Hello Brian,
Thanks again. I just ran amdump test and looks like there is some issue which I
am not able to understand why it's happening. Here is ther email from Amanda
Admin.
These dumps were to tape TEST-1.
The next 6 tapes Amanda expects to use are: 6 new tapes.
The next 6 new tapes alread
I have made some changed to amanda.conf. First I have changed disk size to
10GB, then number of Vtapes/slots = 29 and also added runtapes = 6
My amanda.conf
dumpcycle 7
runspercycle 7
tapecycle 29
runtapes 6
dumpuser "amanda"
tpchanger "chg-disk"# a virtual tape chang
Thanks for the advise.
I understand you have asked me some questions and that is actually making me
think of more points to be considered while sizing and make correct decisions.
Some of the points that you have mentioned I did not really think of them when
I started. Thanks for pointing them o
Firstly, thanks for the response!
1. You have 50 gig under backup/amanda control, but how much data
are you currently backing up per week ?
Currently not doing any backups through Amanda. I am trying to understand this
whole theory of numbers involved in configuration.
I want to start backing
Hi,
Using Amanda on Solaris 10 "2.5.2p1,REV=2008.05.21" and amanda client on a
solaris 8 which I beleive has same version of Amanda.
I am not sure what settings for tapecycle dumpcycle should be used for
efficient usage of Vtapes. I'd like advise in setting those parameters in
amanda.conf
Her
cat chg-zd-mtx.20101118170102.debug
chg-zd-mtx: debug 1 pid 14462 ruid 1066 euid 1066: start at Thu Nov 18 17:01:02
2010
17:01:03 Using config file /opt/csw/etc/amanda/changer.conf
17:01:03 Arg info:
$# = 1
$0 = "/opt/csw/libexec/chg-zd-mtx"
$1 = "-info"
17:01:03 Runnin
Okay guys, I am not sure what's going wrong that you can't read my posts here.
What I am doing is pretty straightforward, going to backupcentral.com and
Amanda forums and writing my posts. I am using codes button available on forum
tools to highlight the configuration part. I am not emailing my
-rwxr-xr-x 1 amanda sys
0 May 20 2010 .amandahosts
Su - amanda
mkdir fullbackup
cd fullback
ls -al
-rw-r--r-- 1 amanda sys 7911 Nov 18 15:07 amanda.conf
-rw-r--r-- 1 amanda root1663 May 26 13:33 amanda.conf_old
-rw-r--r-- 1 amanda sys 55 Nov 1
I wonder if one can edit their posts , I could not find option to do so. so
adding info below,
Root user can run that command , however the resultdoes not seem accurate,
bash-3.00# /opt/csw/libexec/chg-zd-mtx -info
1 10 1
bash-3.00# /opt/csw/sbin/mtx -f /dev/scsi/changer/c2t6d0 status
Storag
Hi,
I am trying to configure amanda on Solaris10/sparc and running into some
issues. amanda package was installed through CSW/blastwave.
Below is what I see when amanda user tries to run amcheck.
opt/csw/sbin/amcheck fullbackup
Amanda Tape Server Host Check
-
Holdin
33 matches
Mail list logo
