Re: Got no header and data from server / Can't locate object method

2010-12-15 Thread Toomas Aas

K, 15 dets  2010 kirjutas Jean-Louis Martineau :


Toomas Aas wrote:



$AMANDA_COMPONENTS = " client amrecover ndmp";
That's the problem, it looks like the server code is installed but  
it is not in that line.
I don't know how the FreeBSD port collection works, but it is not  
compiled correctly.


Looks like this has already been fixed in the FreeBSD ports collection  
on December 3rd. I had built my new Amanda before that, so I missed  
out on that update.


Quoting the cvsweb:

- Amanda/Constants.pm is installed by amanda-client, and it includes
  constat variable as of client components only.  When amanda-server
  installed, Constants.pm should include also server components.
- To work around it, use pkg-install/pkg-deinstall script to tweak
  this variable by inplace updating.

Reported by:Christian Gusenbauer 

--
Toomas Aas



Re: Got no header and data from server / Can't locate object method

2010-12-15 Thread Jean-Louis Martineau

Toomas Aas wrote:

Hello Jean-Louis!

What's the output of: grep -i AMANDA_COMPONENTS 
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Constants.pm


$AMANDA_COMPONENTS = " client amrecover ndmp";
That's the problem, it looks like the server code is installed but it is 
not in that line.
I don't know how the FreeBSD port collection works, but it is not 
compiled correctly.


Jean-Louis



Re: Got no header and data from server / Can't locate object method

2010-12-15 Thread Toomas Aas

Hello Jean-Louis!

What's the output of: grep -i AMANDA_COMPONENTS  
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Constants.pm


$AMANDA_COMPONENTS = " client amrecover ndmp";



Add the same 'use Amanda::XFerServer;' in  
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Taper/Scribe.pm




Thanks a lot, looks like this helped. I started an amflush, and it  
seems to be running successfully. It's flushing the 4th DLE out of 12  
as I type this.


--
Toomas Aas



[Amanda-users] amanda.conf config help

2010-12-15 Thread upengan78
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 /export {  4.5GB
  comp-tar
  include "./def"
}  -1 


client.domain.com /export/./ghi /export { 1.2GB
  comp-tar
  include "./ghi"
}   2


client.domain.com /export/./jkl /export {   1GB
  comp-tar
  include "./jkl"
}  -1


#client.domain.com /export/./mno /export {   23GB
#  comp-tar
#  include "./mno"
#}   2


client.domain.com /export/./pqr /export {  14GB
  comp-tar
  include "./pqr"
}   2

client.domain.com /export/./stu /export {  162 MB
  comp-tar
  include "./stu"
}   -1



Monthlyfull ~ total size about 90GB


client.domain.com /export/./vwx /export { 3.3 GB
  comp-tar
  include "./vwx"
}  -1


client.domain.com /export/./yz /export {   1.0GB
  comp-tar
  include "./yz"
}   -1

client.domain.com /export/OTHER/./a-m /export/OTHER {9GB
  comp-tar
  include "./[a-m]*"
}   -1

client.domain.com /export/OTHER/./n-z /export/OTHER {   9GB
  comp-tar
  include "./[n-z]*"
}   2

client.domain.com /export/OTHER/./_rest_ /export/OTHER {  9GB
  comp-tar
 exclude append "./[a-z]*"
}   2


client.domain.com /export/./jack /export { 2.3GB
  comp-tar
  include "./jack"
}   2


client.domain.com /export/./users /export { 24 GB
  comp-tar
  include "./users"
}   -1


client.domain.com /export/./egg /export {8GB
  comp-tar
  include "./egg"
}   -1


client.domain.com /export/./apple /export {21GB
  comp-tar
  include "./apple"
}   2


client.domain.com /export/./vls /export {14GB
  comp-tar
  include "./vls"
}   -1


Apart from this,

Total holding space from hd1 and hd2 is = 17 GB + 41 GB = 58GB. May be I should 
try to use  flush-threshhold-* options if there is nothing else that can be 
adjusted in my case.

+--
|This was sent by upendra.gan...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--




[Amanda-users] amanda.conf config help

2010-12-15 Thread upengan78
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 /export {  4.5GB
  comp-tar
  include "./def"
}  -1 


pluto.ece.iit.edu /export/./ghi /export { 1.2GB
  comp-tar
  include "./ghi"
}   2


pluto.ece.iit.edu /export/./jkl /export {   1GB
  comp-tar
  include "./jkl"
}  -1


#pluto.ece.iit.edu /export/./mno /export {   23GB
#  comp-tar
#  include "./mno"
#}   2


pluto.ece.iit.edu /export/./pqr /export {  14GB
  comp-tar
  include "./pqr"
}   2

pluto.ece.iit.edu /export/./stu /export {  162 MB
  comp-tar
  include "./stu"
}   -1



Monthlyfull ~ total size about 90GB


pluto.ece.iit.edu /export/./vwx /export { 3.3 GB
  comp-tar
  include "./vwx"
}  -1


pluto.ece.iit.edu /export/./yz /export {   1.0GB
  comp-tar
  include "./yz"
}   -1

pluto.ece.iit.edu /export/OTHER/./a-m /export/OTHER {9GB
  comp-tar
  include "./[a-m]*"
}   -1

pluto.ece.iit.edu /export/OTHER/./n-z /export/OTHER {   9GB
  comp-tar
  include "./[n-z]*"
}   2

pluto.ece.iit.edu /export/OTHER/./_rest_ /export/OTHER {  9GB
  comp-tar
 exclude append "./[a-z]*"
}   2


pluto.ece.iit.edu /export/./jack /export { 2.3GB
  comp-tar
  include "./jack"
}   2


pluto.ece.iit.edu /export/./users /export { 24 GB
  comp-tar
  include "./users"
}   -1


pluto.ece.iit.edu /export/./egg /export {8GB
  comp-tar
  include "./egg"
}   -1


pluto.ece.iit.edu /export/./apple /export {21GB
  comp-tar
  include "./apple"
}   2


pluto.ece.iit.edu /export/./vls /export {14GB
  comp-tar
  include "./vls"
}   -1


Apart from this,

Total holding space from hd1 and hd2 is = 17 GB + 41 GB = 58GB. May be I should 
try to use  flush-threshhold-* options if there is nothing else that can be 
adjusted in my case.

+--
|This was sent by upendra.gan...@gmail.com via Backup Central.
|Forward SPAM to ab...@backupcentral.com.
+--




Re: [Amanda-users] amanda.conf config help

2010-12-15 Thread Brian Cuttler
Upendra,

I don't recall how large your holding area is or if you end up
with multiple DLE in holding waiting for tape or not.

I've had good success with "taperalgo" and selecting the "largestfit"
option. This seems to fill my (non-spanning physical) tapes pretty
close to 100%.

If you have lots of work area and can delay your dumps until there
are mulipul DLE in the work area so the taper algorithms have more
choices there are paramters for that as well.

I believe (unless they have been removed in the last itteration)
that these relatively new parameters will help you get where you
want to go.

Note this is one of several examples in the amanda.conf file.
There are several examples to look at.

# You want to fill tapes completely even in the case of failed dumps, and
# don't care if some dumps are left on the holding disk after a run:
# flush-threshold-dumped100 # (or more)
# flush-threshold-scheduled 100 # (or more)
# taperflush100
# autoflush yes



On Wed, Dec 15, 2010 at 01:34:31PM -0500, upengan78 wrote:
> 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 discussion 
> here.
> 
> I am doing below cron jobs currently (no manual amdumps)
> #Amcheck
> 59 19 * * 1-5 su - amanda -c "/opt/csw/sbin/amcheck -a weeklyfull"
> 5 20 * * * su - amanda -c "/opt/csw/sbin/amcheck -a monthlyfull"
> #amdump
> 01 00 * * 1-5 su - amanda -c "/opt/csw/sbin/amdump weeklyfull"
> 15 01 * * * su - amanda -c "/opt/csw/sbin/amdump monthlyfull"
> 
> weeklyfull- amanda.conf
> inparallel 4
> maxdumps 4
> dumpcycle 7
> runspercycle 5
> tapecycle 9
> runtapes 3
> dumpuser "amanda"
> tpchanger "chg-disk"# a virtual tape changer
> tapedev "file:/bk/location/amanda/vtapes/weeklyfull/slots"
> changerfile "/opt/csw/etc/amanda/weeklyfull/changerfile"
> labelstr "WF-.*"
> #label_new_tapes "PLUTO-%%"
> autolabel "WF-%%"
> tapetype DVD_SIZED_DISK
> logdir "/opt/csw/etc/amanda/weeklyfull"
> infofile "/opt/csw/etc/amanda/weeklyfull/curinfo"
> indexdir "/opt/csw/etc/amanda/weeklyfull/index"
> tapelist "/opt/csw/etc/amanda/weeklyfull/tapelist"
> #etimeout 600 # number of seconds per filesystem for estimates.
> etimeout 3600 # number of seconds per filesystem for estimates.
> #etimeout -600   # total number of seconds for estimates.
> # a positive number will be multiplied by the number of filesystems on
> # each host; a negative number will be taken as an absolute total time-out.
> # The default is 5 minutes per filesystem.
> #dtimeout 1800# number of idle seconds before a dump is aborted.
> dtimeout 3600# number of idle seconds before a dump is aborted.
> ctimeout 30  # maximum number of seconds that amcheck waits
>  # for each client host
> 
> 
> holdingdisk hd1 {
> directory "/random/amandahold/hold"
> }
> 
> holdingdisk hd2 {
> directory "/random1/amanda/holdingdisk2"
> }
> 
> define dumptype comp-tar {
> program "GNUTAR"
> compress fast
> index yes
> record yes  # Important! avoid interfering with production runs
> #  tape_splitsize 1 Gb
> tape_splitsize 1024 mbytes
> #  fallback_splitsize 512 MB 
> fallback_splitsize 4096 MB 
> split_diskbuffer "/random/buffer"
> }  
> 
> define tapetype DVD_SIZED_DISK {
> filemark 1 KB
> length 10240 MB
> }
> 
> 
> 
> 
> 
> inparallel 5
> maxdumps 5
> dumpcycle 30 days
> runspercycle 30 
> tapecycle 20 
> runtapes 9 
> dumpuser "amanda"
> tpchanger "chg-disk"# a virtual tape changer
> tapedev "file:/bk/location/amanda/vtapes/monthlyfull/slots"
> changerfile "/opt/csw/etc/amanda/monthlyfull/changerfile"
> labelstr "MF-.*"
> #label_new_tapes "PLUTO-%%"
> autolabel "MF-%%"
> tapetype DVD_SIZED_DISK
> logdir "/opt/csw/etc/amanda/monthlyfull"
> infofile "/opt/csw/etc/amanda/monthlyfull/curinfo"
> indexdir "/opt/csw/etc/amanda/monthlyfull/index"
> tapelist "/opt/csw/etc/amanda/monthlyfull/tapelist"
> #etimeout 600 # number of seconds per filesystem for estimates.
> etimeout 3600 # number of seconds per filesystem for estimates.
> #etimeout -600   # total number of seconds for estimates.
> # a positive number will be multiplied by the number of filesystems on
> # each host; a negative number will be taken as an absolute total time-out.
> # The default is 5 minutes per filesystem.
> #dtimeout 1800# number of idle seconds before a dump is aborted.
> dtimeout 3600# number of idle seconds before a dump is aborted.
> ctimeout 30  # maximum number of seconds that amcheck waits
>  # for each client host
> 
> 
> holdingdisk hd1 {
> directory "/random/amandahold/hold"
> }
> 
> holdingdisk hd2 {
> directory "/random1/amanda/holdingdisk2"

[Amanda-users] amanda.conf config help

2010-12-15 Thread upengan78
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 discussion here.

I am doing below cron jobs currently (no manual amdumps)
#Amcheck
59 19 * * 1-5 su - amanda -c "/opt/csw/sbin/amcheck -a weeklyfull"
5 20 * * * su - amanda -c "/opt/csw/sbin/amcheck -a monthlyfull"
#amdump
01 00 * * 1-5 su - amanda -c "/opt/csw/sbin/amdump weeklyfull"
15 01 * * * su - amanda -c "/opt/csw/sbin/amdump monthlyfull"

weeklyfull- amanda.conf
inparallel 4
maxdumps 4
dumpcycle 7
runspercycle 5
tapecycle 9
runtapes 3
dumpuser "amanda"
tpchanger "chg-disk"# a virtual tape changer
tapedev "file:/bk/location/amanda/vtapes/weeklyfull/slots"
changerfile "/opt/csw/etc/amanda/weeklyfull/changerfile"
labelstr "WF-.*"
#label_new_tapes "PLUTO-%%"
autolabel "WF-%%"
tapetype DVD_SIZED_DISK
logdir "/opt/csw/etc/amanda/weeklyfull"
infofile "/opt/csw/etc/amanda/weeklyfull/curinfo"
indexdir "/opt/csw/etc/amanda/weeklyfull/index"
tapelist "/opt/csw/etc/amanda/weeklyfull/tapelist"
#etimeout 600 # number of seconds per filesystem for estimates.
etimeout 3600 # number of seconds per filesystem for estimates.
#etimeout -600   # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
#dtimeout 1800# number of idle seconds before a dump is aborted.
dtimeout 3600# number of idle seconds before a dump is aborted.
ctimeout 30  # maximum number of seconds that amcheck waits
 # for each client host


holdingdisk hd1 {
directory "/random/amandahold/hold"
}

holdingdisk hd2 {
directory "/random1/amanda/holdingdisk2"
}

define dumptype comp-tar {
program "GNUTAR"
compress fast
index yes
record yes  # Important! avoid interfering with production runs
#  tape_splitsize 1 Gb
tape_splitsize 1024 mbytes
#  fallback_splitsize 512 MB 
fallback_splitsize 4096 MB 
split_diskbuffer "/random/buffer"
}  

define tapetype DVD_SIZED_DISK {
filemark 1 KB
length 10240 MB
}





inparallel 5
maxdumps 5
dumpcycle 30 days
runspercycle 30 
tapecycle 20 
runtapes 9 
dumpuser "amanda"
tpchanger "chg-disk"# a virtual tape changer
tapedev "file:/bk/location/amanda/vtapes/monthlyfull/slots"
changerfile "/opt/csw/etc/amanda/monthlyfull/changerfile"
labelstr "MF-.*"
#label_new_tapes "PLUTO-%%"
autolabel "MF-%%"
tapetype DVD_SIZED_DISK
logdir "/opt/csw/etc/amanda/monthlyfull"
infofile "/opt/csw/etc/amanda/monthlyfull/curinfo"
indexdir "/opt/csw/etc/amanda/monthlyfull/index"
tapelist "/opt/csw/etc/amanda/monthlyfull/tapelist"
#etimeout 600 # number of seconds per filesystem for estimates.
etimeout 3600 # number of seconds per filesystem for estimates.
#etimeout -600   # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolute total time-out.
# The default is 5 minutes per filesystem.
#dtimeout 1800# number of idle seconds before a dump is aborted.
dtimeout 3600# number of idle seconds before a dump is aborted.
ctimeout 30  # maximum number of seconds that amcheck waits
 # for each client host


holdingdisk hd1 {
directory "/random/amandahold/hold"
}

holdingdisk hd2 {
directory "/random1/amanda/holdingdisk2"
}

define dumptype comp-tar {
program "GNUTAR"
compress fast
index yes
record yes  # Important! avoid interfering with production runs
#   tape_splitsize 1 Gb
tape_splitsize 1024 mbytes
#fallback_splitsize 512 MB 
   fallback_splitsize 4096 MB 
   split_diskbuffer "/random/buffer"
}  

define tapetype DVD_SIZED_DISK {
filemark 1 KB
length 10240 MB
}


monthlyfull amanda.conf

inparallel 5
maxdumps 5
dumpcycle 30 days
runspercycle 30 
tapecycle 20 
runtapes 9 
dumpuser "amanda"
tpchanger "chg-disk"# a virtual tape changer
tapedev "file:/bk/location/amanda/vtapes/monthlyfull/slots"
changerfile "/opt/csw/etc/amanda/monthlyfull/changerfile"
labelstr "MF-.*"
#label_new_tapes "PLUTO-%%"
autolabel "MF-%%"
tapetype DVD_SIZED_DISK
logdir "/opt/csw/etc/amanda/monthlyfull"
infofile "/opt/csw/etc/amanda/monthlyfull/curinfo"
indexdir "/opt/csw/etc/amanda/monthlyfull/index"
tapelist "/opt/csw/etc/amanda/monthlyfull/tapelist"
#etimeout 600 # number of seconds per filesystem for estimates.
etimeout 3600 # number of seconds per filesystem for estimates.
#etimeout -600   # total number of seconds for estimates.
# a positive number will be multiplied by the number of filesystems on
# each host; a negative number will be taken as an absolut

Re: Got no header and data from server / Can't locate object method

2010-12-15 Thread Toomas Aas

T, 14 dets  2010 kirjutas Jean-Louis Martineau :


Try this one line patch, you can patch the installed Clerk.pm file


Thanks Jean-Louis, after applying this patch I could run amrecover
successfully. However, the other problem remains in that when I run  
amdump or amflush, taper fails with this message:


  taper: FATAL Can't locate object method "new" via package  
"Amanda::Xfer::Dest::Taper::Splitter" (perhaps you forgot to load  
"Amanda::Xfer::Dest::Taper::Splitter"?) at  
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Taper/Scribe.pm line 706.


Maybe you have an idea about that one too?

--
Toomas Aas



Re: Got no header and data from server / Can't locate object method

2010-12-15 Thread Jean-Louis Martineau
What's the output of: grep -i AMANDA_COMPONENTS 
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Constants.pm


Add the same 'use Amanda::XFerServer;' in 
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Taper/Scribe.pm


Jean-Louis

Toomas Aas wrote:

T, 14 dets  2010 kirjutas Jean-Louis Martineau :


Try this one line patch, you can patch the installed Clerk.pm file


Thanks Jean-Louis, after applying this patch I could run amrecover
successfully. However, the other problem remains in that when I run 
amdump or amflush, taper fails with this message:


  taper: FATAL Can't locate object method "new" via package 
"Amanda::Xfer::Dest::Taper::Splitter" (perhaps you forgot to load 
"Amanda::Xfer::Dest::Taper::Splitter"?) at 
/usr/local/lib/perl5/site_perl/5.12.2/Amanda/Taper/Scribe.pm line 706.


Maybe you have an idea about that one too?