ome changes in disklist I think this option is not working.
> > That is strange. Is anyone using successfully this option? What
> > version of amanda are you using in the server? Anyone can check the
> > code?
>
> I haven't used this option myself, but from the amanda.co
cessfully this option? What
> version of amanda are you using in the server? Anyone can check the
> code?
I haven't used this option myself, but from the amanda.conf man page
entry for it the first question to ask is whether you are indeed using
ssh authentication in this particular dumptype?
In
Hi,
I am using the latest amanda 3.5.1 in Debian stretch and I want to do
backup of other Linux systems, in this case CentOS. The amandad
daemon in Debian packages is located in /usr/lib/amanda/amandad but in
CentOS rpms is located in /usr/lib64/amanda/amandad.
To workaround this I am using a
Ok, thanks for the tip:
[root@ulysses ~]# su amandabackup -c '/usr/sbin/amtape Mensuel-LTO7 verify'
GOOD : Drive 0 is device tape:/dev/nst1
GOOD : Drive 1 is device tape:/dev/nst0
property "TAPE-DEVICE" "0=tape:/dev/nst1" "1=tape:/dev/nst0"
Best regards, Luc.
On 2018-01-15 08:10 AM,
Luc,
The assignment of 'Data Transfer Element 0' to '/dev/nst1' and 'Data
Transfer Element 1' to '/dev/nst0' is done by the kernel.
You can use the 'amtape CONF verify' command to check if you correctly
configured amanda.
Jean-Louis
On 13/01/18 06:40 PM, Luc Lalonde wrote:
Hello Folks,
Hello Folks,
I’m getting a strange result when I do an ‘amcheck’:
slot 3: Tape device /dev/nst1 is not ready or is empty
slot 4:Slot 4, label '000279L7', mismatch barcode between changer '000280L7'
and tapelist file '000279L7'
ERROR: Slot 4, label '000279L7', mismatch barcode between changer
Nathan,
Thanks for the patch, I committed it
Jean-Louis
On 27/11/17 02:38 AM, Nathan Stratton Treadway wrote:
> The attached patch against amanda.conf.5.xml tries to fill in some
> specific details on the operation of the vault-storage parameter, and
> also fixes a couple typos in ot
The attached patch against amanda.conf.5.xml tries to fill in some
specific details on the operation of the vault-storage parameter, and
also fixes a couple typos in other parts of the page.
(The patch is against the git master branch version of the file, though
I believe the changes should apply
On 01/08/15 03:35 AM, Jon LaBadie wrote:
When replying to Gene H's thread I quoted the
amanda.conf(5) manpage
estimate [ client | calcsize | server ]+
I thought I knew the meaning of the + at the
end of parameter specifications -- the final
term can be repeated. But now I'm not certain
On Tue, Aug 04, 2015 at 12:27:08PM -0400, Jean-Louis Martineau wrote:
On 01/08/15 03:35 AM, Jon LaBadie wrote:
When replying to Gene H's thread I quoted the
amanda.conf(5) manpage
estimate [ client | calcsize | server ]+
I thought I knew the meaning of the + at the
end of parameter
When replying to Gene H's thread I quoted the
amanda.conf(5) manpage
estimate [ client | calcsize | server ]+
I thought I knew the meaning of the + at the
end of parameter specifications -- the final
term can be repeated. But now I'm not certain.
In a spec like:
property [append] string
to be dumped?
-M
On Thu, Jan 9, 2014 at 1:58 PM, Jean-Louis Martineau martin...@zmanda.com
wrote:
On 01/09/2014 01:47 PM, Michael Stauffer wrote:
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf:
The documentation says: If multiple configurations are run from
. Then with amdump, I can specify the individual
DLE's to be dumped?
-M
On Thu, Jan 9, 2014 at 1:58 PM, Jean-Louis Martineau martin...@zmanda.com
wrote:
On 01/09/2014 01:47 PM, Michael Stauffer wrote:
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf
. Then with amdump, I can specify the
individual DLE's to be dumped?
-M
On Thu, Jan 9, 2014 at 1:58 PM, Jean-Louis Martineau
martin...@zmanda.comwrote:
On 01/09/2014 01:47 PM, Michael Stauffer wrote:
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf:
The documentation says
/2014 01:47 PM, Michael Stauffer wrote:
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf:
The documentation says: If multiple configurations are run from the same tape
server host, it is helpful to set their labels to different strings (for
example, DAILY[0-9][0-9]* vs
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf:
The documentation says: If multiple configurations are run from the same
tape server host, it is helpful to set their labels to different strings
(for example, DAILY[0-9][0-9]* vs. ARCHIVE[0-9][0-9]*) to avoid
overwriting
On 01/09/2014 01:47 PM, Michael Stauffer wrote:
Hi,
I'm setting up amanda 3.3.4.
Regarding 'labelstr' in amanda.conf:
The documentation says: If multiple configurations are run from the
same tape server host, it is helpful to set their labels to different
strings (for example, DAILY[0-9][0
op 09-01-14 19:47, Michael Stauffer schreef:
Does this mean that if I have multiple configurations in order to
break up a large 30TB data set into managable chunks, each
configuration will have to have a particular set of tapes assigned to
it? That seems very awkward if so.
Why would you make
CC: SYSLOG
Jean-Louis,
I added the unreserved-tcp-port line to my amanda.conf because
we where running short on UPD ports, too many concurrent dumps
when we had --tcp-portrange and --udp-portrange configured.
This did not create an issue between client-server on the same
or close networks
- 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
.
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
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
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
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
to you by Amanda version 3.1.1)
Here is the amanda.conf
dumpcycle 7
runspercycle 7
tapecycle 29
runtapes 6
dumpuser amanda
tpchanger chg-disk# a virtual tape changer
tapedev file:/random/amanda/vtapes/test/slots
changerfile /opt/csw/etc/amanda/test/changerfile
MMM:SS
KB/s
-- ---
-
TEST.ece.ii /bk/location 0 31788780 16518426 52.0 98:29 2795.5 98:28
2795.9
(brought to you by Amanda version 3.1.1)
Here is the amanda.conf
dumpcycle 7
runspercycle 7
tapecycle 29
#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
dispite the multiple DLEs the wall clock time is not shorter
than the dumptime, check use of inparallel and maxdump and
you should be able to get some concurrency, not that running
into the work day is an issue with this config, but its good
to practice and now about it later.
On Fri, Dec 03,
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
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
Hi!
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
I think you mean the split_diskbuffer parameter:
See example amanda.conf
On Fri, Dec 03, 2010 at 04:29:59PM -0500, upengan78 wrote:
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
On Fri, Dec 03, 2010 at 04:04:16PM -0500, upengan78 wrote:
Now I am thinking about, removing runtapes option completely, and add
splitdisk_buffer option to the holding disk, I am confused about one thing,
why you mentioned that looks like your splits are about 0.5GB. I have
actually set
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
On Mon, Nov 29, 2010 at 10:08:04AM -0500, upengan78 wrote:
@ Jon,
It doesn't show me 3.1.1 version available in CSW which I am using here. See
below,
/opt/csw/bin/pkgutil -c amanda
Checking catalog integrity with gpg.
gpg: Signature made Sun Oct 17 21:35:22 2010 CDT using DSA key ID
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 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
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 changer
/trelaz /trel {
user-tar
include ./[a-z]*
}
On Wed, Nov 24, 2010 at 11:37:31AM -0500, upengan78 wrote:
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
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
On Wed, Nov 24, 2010 at 02:22:52PM -0500, upengan78 wrote:
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
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
On Wed, Nov 24, 2010 at 11:37:31AM -0500, upengan78 wrote:
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
On Tue, Nov 23, 2010 at 10:27:15AM -0500, upengan78 wrote:
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.
OpenCSW shows amanda version 3.1.1. Why are you using
such an old version?
Jon
--
Jon H. LaBadie
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
Here
parameters in
amanda.conf
Here is the situation,
Data to be backed up is around 50G and grows by about 100-200MB each day.
I have 20 Vtapes and each tape is 4G size on the server. I do have total
300G available on server disk but I just decided to start with 80G to start
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
On Tue, 23 Nov 2010 12:35:10 -0500
upengan78 amanda-fo...@backupcentral.com wrote:
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
On Tue, Nov 23, 2010 at 12:35:10PM -0500, upengan78 wrote:
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
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
On 11/23/10 2:34 PM, upengan78 wrote:
snip
One thing I am confused about and want to confirm do I really need to use
spanning in Virtual tapes ?
snip
*How many DLEs, disklist entries, will you have, what are their
relative sizes ?
Only 1 entry for a amanda-network client server. Size is
Upendra,
On Tue, Nov 23, 2010 at 02:34:17PM -0500, upengan78 wrote:
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
On Tue, 23 Nov 2010 14:34:17 -0500
upengan78 amanda-fo...@backupcentral.com wrote:
One thing I am confused about and want to confirm do I really need to
use spanning in Virtual tapes ?
This document here mentions that one doesn't need to configure
'runtapes' variable with vtapes but
On Tue, Nov 23, 2010 at 02:34:17PM -0500, upengan78 wrote:
Thanks for the advise.
While Amanda can be used for your needs, it may not be
an optimal choice. Amanda is a backup manager, she makes
choices about what and how to backup your DLEs. But you
are trying to do most or all of Amanda's
I have an /etc/amanda/foo/amanda.conf which starts with:
define holdingdisk external_holding {
directory /media/amanda_holdingdisk
}
...and amcheck complains:
amandabac...@backupserver:/etc/amanda/foo$ amcheck foo
/etc/amanda/foo/amanda.conf, line 2: DUMPTYPE, INTERFACE, TAPETYPE
On Monday 29 March 2010, Craig Constantine wrote:
I have an /etc/amanda/foo/amanda.conf which starts with:
define holdingdisk external_holding {
directory /media/amanda_holdingdisk
}
...and amcheck complains:
amandabac...@backupserver:/etc/amanda/foo$ amcheck foo
/etc/amanda/foo/amanda.conf
On Monday 29 March 2010, Craig Constantine wrote:
I don't think it needs the 'define' above, here is mine that has been
in continuous use for several years now:
Thanks!
Yeah, it's a mistake in the man page (which says define holdingdisk
name )
-c
I appreciate the reply, but it should be
On Mon, Mar 29, 2010 at 9:38 AM, Craig Constantine cr...@blkbx.com wrote:
...line 2 is the define holdingdisk . . . line. Isn't this how I define a
holdingdisk?
Until 3.1, you had to just use
holdingdisk foo {
...
}
In 3.1, you can define as many holding disks as you want, and then use
looking a the newest manpages. The 2.6.1 manpages
are correct for that version:
http://wiki.zmanda.com/man/2.6.1/amanda.conf.5.html#id538874
Dustin
--
Open Source Storage Engineer
http://www.zmanda.com
I have an /etc/amanda/foo/amanda.conf which starts with:
define holdingdisk external_holding { directory
/media/amanda_holdingdisk }
...it seems it should be just
holdingdisk name {
that works with amcheck, etal. (I've emailed jds@ about the error in the
man page for amanda.conf .)
-c
I suspect you're looking a the newest manpages. The 2.6.1 manpages
are correct for that version:
http://wiki.zmanda.com/man/2.6.1/amanda.conf.5.html#id538874
yeup. I got zinged by the recent release of 3.1, combined with my older
bookmark to the current manpages... doh :)
On Mon, Mar 29, 2010 at 12:34 PM, Craig Constantine cr...@blkbx.com wrote:
that works with amcheck, etal. (I've emailed jds@ about the error in the man
page for amanda.conf .)
I'm sure he'll be amused! He's moved on to bigger and better things
(well, smaller and better .. embedded systems
On Monday 29 March 2010, Dustin J. Mitchell wrote:
On Mon, Mar 29, 2010 at 9:38 AM, Craig Constantine cr...@blkbx.com wrote:
...line 2 is the define holdingdisk . . . line. Isn't this how I
define a holdingdisk?
Until 3.1, you had to just use
holdingdisk foo {
...
}
In 3.1, you can define
Dustin,
Updated amanda.conf with
device_property BLOCK_SIZE 2 mbytes
Tried to relabel a labeled but never used tape, priviously
Curie46, labeled with the default device_property (default
as in I hadn't specified anything).
I have to overwrite the tape header, there is a level below
the amanda
Dustin,
Ivan at my site nailed it.
Mar 8 12:59:37 curie scsi: [ID 107833 kern.warning] WARNING:
/p...@3,0/pci1022,7...@9/pci1000,1...@1/f...@0,0/t...@w500110a0008b3fda,0 (st0):
Mar 8 12:59:37 curie Cannot alloc contig buf for I/O for 2097152 blk size
setting the block_size to 1 meg took.
of amanda.conf on the system with the fiber
connection, left the faster scsi connected server alone.
I found that # amcheck was unable to find any valid tapes
in the existing tape pool.
amcheck -t curie
Amanda Tape Server Host Check
-
slot 13:Found an empty or non-amanda tape.
slot
.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf!
The relevant amindexd.*.debug on the server then looks like this:
amindexd: debug 1 pid 28092 ruid 34 euid
file /etc/amanda/amindexd/amanda.conf!
The relevant amindexd.*.debug on the server then looks like this:
amindexd: debug 1 pid 28092 ruid 34 euid 34: start at Fri Apr 3 17:31:45
2009
amindexd: version 2.5.2p1
could not open conf file /etc/amanda/amindexd/amanda.conf: No such file
Version 2.5.2p1. Contacting server on srv ...
220 srv AMANDA index server (2.5.2p1) ready.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf
. Contacting server on srv ...
220 srv AMANDA index server (2.5.2p1) ready.
[...]
But running it on the client does not:
$ amrecover -C myconf -s srv -t srv
AMRECOVER Version 2.4.4p3. Contacting server on srv ...
501 Could not read config file /etc/amanda/amindexd/amanda.conf!
The relevant amindexd
Since I've been this deep (holds hand above head) in trying to get encryption to
work, I've been reading and re-reading documentation and man pages. I noticed a
small typo in the amanda.conf page for the section detailing encryption in
dumptypes. Basically, for encrypt client it says to look
and man
pages. I noticed a small typo in the amanda.conf page for the section
detailing encryption in dumptypes. Basically, for encrypt client it says
to look at dumptype server-encrypt-fast in example/amanda.conf and for
encrypt server it says to look at dumptype client-encrypt-nocomp in
example
I'm new to Amanda and after several days of reading the docs. I'm still
unclear as to when is it necessary to restart Amanda. In particular, is it
necessary for me to restart amanda after making changes to the
amanda.conffile on the tapehost? If so, what is the proper way to
restart amanda?
--Gil
Gil Vidals wrote:
I'm new to Amanda and after several days of reading the docs. I'm
still unclear as to when is it necessary to restart Amanda. In
particular, is it necessary for me to restart amanda after making
changes to the amanda.conf file on the tapehost? If so, what is the
proper way
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf incorrectly...
I'd thought this would allow me to push my log files (log.YYMMDD
and amdump.N) into a subdirectory, but its not, I am finding
* Brian Cuttler [EMAIL PROTECTED] [20071108 11:12]:
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf incorrectly...
I'd thought this would allow me to push my log files (log.YYMMDD
On Thu, Nov 08, 2007 at 11:15:19AM -0500, Jean-Francois Malouin wrote:
* Brian Cuttler [EMAIL PROTECTED] [20071108 11:12]:
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf
Brian Cuttler wrote:
Hello amanda users,
This isn't an issue of great import, I'm just trying to avoid
clutter in the config directory.
I must be using logdir in amanda.conf incorrectly...
I'd thought this would allow me to push my log files (log.YYMMDD
and amdump.N) into a subdirectory
Hello list
Please let me ask a question about an Amanda2.4.X version.
A question is asked about the item called dumpcycle in an
amanda.conf configuration file.
Is a full backup performed at intervals of that value, as for the
value set up by the this dumpcycle item?
For example, if it sets
On Tue, Aug 14, 2007 at 11:17:02AM +0900, d_boy wrote:
Hello list
Please let me ask a question about an Amanda2.4.X version.
A question is asked about the item called dumpcycle in an
amanda.conf configuration file.
Is a full backup performed at intervals of that value, as for the
value
Hi,
amanda 2.5.1 doesn't support old syntax/obsoletes options.
Use holdingdisk and logdir instead.
Jean-Louis
Chan, Victor wrote:
To all,
I’ve changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn’t work anymore.
diskdir “var/tmp
On Thu, 14 Sep 2006, Frank Smith wrote:
Chan, Victor wrote:
To all,
I've changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn't work anymore.
What version were you using?
diskdir var/tmp:
I don't see that in my 2.4.5 or my
To all,
Ive changed up to Amanda 2.5.1. For some reason,
these three parameters that used to work in Amanda.conf didnt work
anymore.
diskdir var/tmp:
disksize 25000 MB
logfile /usr/adm/Amanda/test/log
When I ran amcheck it tells me on those lines that
/usr/local/etc
Chan, Victor wrote:
To all,
I've changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn't work anymore.
What version were you using?
diskdir var/tmp:
I don't see that in my 2.4.5 or my 2.5 configs. I vaguely recall
On Thu, Sep 14, 2006 at 05:18:46PM -0600, Chan, Victor wrote:
To all,
I've changed up to Amanda 2.5.1. For some reason, these three
parameters that used to work in Amanda.conf didn't work anymore.
diskdir var/tmp:
No '/' at start of /var/tmp
No '' at end of string
Did you
I am looking at using the includefile feature in the amanda configuration
file.
I am running 2.4.5P1.
1) Is the includefile available in 2.4.5P1.
2) What would happen if I have the same configuration parameters in both the
include file and the amanda.conf file? Which one would have
file and the amanda.conf file? Which one would have
precedence? Does order matter?
That last one read takes precedence, Robert, so AIUI, it would be in the
order of amanda.conf, then the individual include/exclude in that
dumptype, or if files are named in the dumptype, then whatever
the same configuration parameters in both the
include file and the amanda.conf file? Which one would have precedence? Does
order matter?
In one of my older setups I broke lots of common things out of amanda.conf
to be read in with includefile. Things like dumptypes, tapetypes,
templates
Hi all, I want to specify estimate server in my dumptype definition in
my amanda.conf file; however, amanda doesn't seem to like it:
/etc/amanda/DailySet1/amanda.conf, line 68: dump type parameter
expected
/etc/amanda/DailySet1/amanda.conf, line 68: end of line expected
Here's the section
On Mon, Jul 03, 2006 at 02:30:57PM -0400, Byarlay, Wayne A. wrote:
Hi all, I want to specify estimate server in my dumptype definition in
my amanda.conf file; however, amanda doesn't seem to like it:
/etc/amanda/DailySet1/amanda.conf, line 68: dump type parameter
expected
/etc/amanda
Joe wrote:
I finally got it out in interactive mode. To be honest, I think
everything you have said here should be in the docs. As far as
I can tell, there is no method explained on how to extract a
single file if you cannot use amrecover as in the case of a
missing amanda.conf.
You read
Joe Konecny wrote:
# amrestore -p /dev/nst0 servername '/disk/list/entry$' |
gtar -xpvf - ./path/to/amanda.conf
# Note that the disklistentry is a pattern, not a string
# use restore instead of gtar if you make backups with dump
...
R4P17# amrestore -p /dev/nsa0 no.such.host
Can someone help me out on how to restore
amanda.conf from tape? I can't see any way to do it.
[EMAIL PROTECTED] wrote:
Can someone help me out on how to restore
amanda.conf from tape? I can't see any way to do it.
Basically: on the amanda server
$ cd /tmp
$ mkdir restore-tmp; cd restore-tmp
# we restore in a safe place so that we don't overwrite
# anyting useful
$ su
On Tue, Nov 15, 2005 at 08:52:24AM -0700, [EMAIL PROTECTED] wrote:
Can someone help me out on how to restore
amanda.conf from tape? I can't see any way to do it.
Sure it is possible, that is a reason I use amanda.
You can recover without having amanda.
Do you have printed reports showing
Anyone has a sample workingamanda.conf file?
I downloadedthe binary from SUN freeware, but do not know how to configure Amanda.
please help.
thanks.
Yahoo! FareChase - Search multiple travel sites in one click.
On Monday 24 October 2005 18:25, Tuan Quan wrote:
Anyone has a sample working amanda.conf file?
I downloaded the binary from SUN freeware, but do not know how to
configure Amanda.
please help.
thanks.
The man pages are available at amanda.org in case the Sun download didn't
include them
directory.
If I do it anywhere else, I get the exact same error as amtape does:
bash-2.05$ pwd
/export/home/amanda
bash-2.05$ /usr/local/libexec/chg-zd-mtx -reset
none changerfile must be specified in amanda.conf
bash-2.05$ set | grep PATH
LD_LIBRARY_PATH=:/usr/local/lib
MANPATH
Hi has anyone got a GFS(Grand Father Son rotation setup for amanda.conf
file. As I going to use this commonly used backup cycle for dumpcycle,
runspercycle and tapecycle of 24.
4 daily, 4/5 for weekly and 12 monthly two for error/amflush and 1 for
tape cleaning.
Cheers Chuck
--
Unix/ Linux
Hi,
I have a StorEdge L7 on an E220R running Solaris9.
I have configured Solaris9 with sgen and mtx and chg-zd-mtx
mtx is working
chg-zd-mtx is also working
The relevant entries in amanda.conf are:
changerdev /dev/scsi/changer/c2t1d0
tpchanger chg-zd-mtx # the tape-changer glue script
tapedev
1 - 100 of 194 matches
Mail list logo
