Backup Central

I’d really appreciate it if someone can just go over what I’m doing below, so I don’t miss out anything silly.

I’m using Amanda version 2.6.0p1, and finally cannot effectively make full backups each night anymore, so I’m looking into using Amanda the ‘classic’ way and to set up another config for monthly full backups.

If I recall correctly, then something like this should work for the monthly backup runs. I simply made a copy of my daily config and am just modifying the existing files, e.g. amanda.conf:

dumpcycle 0 to make full backups on each run
runspercycle 1 not really sure about this because dumpcycle is 0??
tapecycle 12 tapes one tape for each month of the year, but will actually use 15 in the set up tapes for the odd amflush, if necessary

index yes to generate the catalogue for use by amrecover
record no apparently: “This is normally enabled for daily backups and turned off for periodic archival runs.” (Amanda wiki)

infofile "/etc/amanda/monthly/curinfo"
logdir "/etc/amanda/monthly"
indexdir "/etc/amanda/monthly/index"

Other than that, because I made a copy of the daily config, I’ve cleaned out the copied config folder’s index and log files, and tapelist file.

Does that look sensible?

Thanks.

Johan

Anyone?

Thanks.

Johan

From: owner-amanda-users < at > amanda.org [mailto:owner-amanda-users < at > amanda.org] On Behalf Of Johan Booysen
Sent: 15 March 2011 12:25
To: amanda-users < at > amanda.org
Subject: monthly archive config



I’d really appreciate it if someone can just go over what I’m doing below, so I don’t miss out anything silly.

I’m using Amanda version 2.6.0p1, and finally cannot effectively make full backups each night anymore, so I’m looking into using Amanda the ‘classic’ way and to set up another config for monthly full backups.

If I recall correctly, then something like this should work for the monthly backup runs. I simply made a copy of my daily config and am just modifying the existing files, e.g. amanda.conf:

dumpcycle 0 to make full backups on each run
runspercycle 1 not really sure about this because dumpcycle is 0??
tapecycle 12 tapes one tape for each month of the year, but will actually use 15 in the set up tapes for the odd amflush, if necessary

index yes to generate the catalogue for use by amrecover
record no apparently: “This is normally enabled for daily backups and turned off for periodic archival runs.” (Amanda wiki)

infofile "/etc/amanda/monthly/curinfo"
logdir "/etc/amanda/monthly"
indexdir "/etc/amanda/monthly/index"

Other than that, because I made a copy of the daily config, I’ve cleaned out the copied config folder’s index and log files, and tapelist file.

Does that look sensible?

Thanks.

Johan

On Friday, I tried a full monthly backup using the config as mentioned in the email below.

The backup seems to have run successfully, and I received the amanda email showing that all disklist entries had a level 0 backup done, but amrecover doesn’t seem able to restore from tape, e.g.

amrecover> setdisk /matrix/data1
200 Disk set to /matrix/data1.
No index records for disk for specified date
If date correct, notify system administrator

-sh-3.2$ less client/monthly/amrecover.20110328144524.debug
1301319924.401732: amrecover: pid 5380 ruid 0 euid 0: start at Mon Mar 28 14:45:24 2011
1301319924.402305: amrecover: pid 5380 ruid 0 euid 0: rename at Mon Mar 28 14:45:24 2011
1301319924.402376: amrecover: security_getdriver(name=bsdtcp) returns 0x1531e0
1301319924.402417: amrecover: security_handleinit(handle=0x838a058, driver=0x1531e0 (BSDTCP))
1301319924.402755: amrecover: security_streaminit(stream=0x838d878, driver=0x1531e0 (BSDTCP))
1301319924.403683: amrecover: connect_port: Skip port 700: owned by epp.
1301319924.404249: amrecover: connect_port: Skip port 701: owned by lmp.
1301319924.404823: amrecover: connect_port: Skip port 702: owned by iris-beep.
1301319924.408278: amrecover: connect_port: Try port 703: available - Success
1301319924.408388: amrecover: connected to 127.0.0.1.10080
1301319924.408403: amrecover: our side is 0.0.0.0.703
1301319924.408417: amrecover: try_socksize: send buffer size is 65536
1301319924.408431: amrecover: try_socksize: receive buffer size is 65536
1301319929.464602: amrecover: security_streaminit(stream=0x83958b0, driver=0x1531e0 (BSDTCP))
1301319929.464640: amrecover: security_close(handle=0x838a058, driver=0x1531e0 (BSDTCP))
1301319929.464656: amrecover: security_stream_close(0x838d878)
1301319947.583494: amrecover: user command: 'sethost npt01'
1301319949.698629: amrecover: user command: 'listdisk'
1301319959.814081: amrecover: user command: 'setdisk /matrix/data1'
1301320116.448051: amrecover: user command: 'exit'
1301320116.448440: amrecover: security_stream_close(0x83958b0)
1301320116.448492: amrecover: pid 5380 finish time Mon Mar 28 14:48:36 2011

-sh-3.2$ amadmin monthly find npt01 /matrix/data1
date host disk lv tape or file file part status
2011-03-25 20:05:26 npt01 /matrix/data1 0 monthly-3 328 1/1 OK

-sh-3.2$ cat /etc/amanda/monthly/log.20110325200526.0 | grep data1
DISK planner npt01 /matrix/data1
INFO planner Adding new disk npt01:/matrix/data1.
SUCCESS dumper npt01 /matrix/data1 20110325200526 0 [sec 113.520 kb 331365 kps 2919.0 orig-kb 1719510]
SUCCESS chunker npt01 /matrix/data1 20110325200526 0 [sec 113.870 kb 326362 kps 2866.4]
STATS driver estimate npt01 /matrix/data1 20110325200526 0 [sec 839 nkb 1719542 ckb 859808 kps 1024]
PART taper monthly-3 328 npt01 /matrix/data1 20110325200526 1/1 0 [sec 6.126424 kb 326361 kps 53271.143702]
DONE taper npt01 /matrix/data1 20110325200526 1 0 [sec 6.126424 kb 326361 kps 53271.143702]

-sh-3.2$ ls -l /etc/amanda/monthly/index/npt01/_matrix_data1
total 124
-rw------- 1 amandabackup disk 119158 Mar 26 08:44 20110325200526_0.gz

It looks like using amrestore will work, although it’s still running at the moment:

-sh-3.2$ amrestore tape:/dev/nst0 npt01 /matrix/data1 2011-03-25
…
…
…
amrestore: 210: skipping split dumpfile: date 20110325200526 host npt01 disk /matrix/data part 119/151 lev 0 comp .gz program /bin/tar crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d
amrestore: 211: skipping split dumpfile: date 20110325200526 host npt01 disk /matrix/data part 120/151 lev 0 comp .gz program /bin/tar crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d

Can anyone please help me understand why this would be?

Thanks.

From: owner-amanda-users < at > amanda.org [mailto:owner-amanda-users < at > amanda.org] On Behalf Of Johan Booysen
Sent: 15 March 2011 12:25
To: amanda-users < at > amanda.org
Subject: monthly archive config



I’d really appreciate it if someone can just go over what I’m doing below, so I don’t miss out anything silly.

I’m using Amanda version 2.6.0p1, and finally cannot effectively make full backups each night anymore, so I’m looking into using Amanda the ‘classic’ way and to set up another config for monthly full backups.

If I recall correctly, then something like this should work for the monthly backup runs. I simply made a copy of my daily config and am just modifying the existing files, e.g. amanda.conf:

dumpcycle 0 to make full backups on each run
runspercycle 1 not really sure about this because dumpcycle is 0??
tapecycle 12 tapes one tape for each month of the year, but will actually use 15 in the set up tapes for the odd amflush, if necessary

index yes to generate the catalogue for use by amrecover
record no apparently: “This is normally enabled for daily backups and turned off for periodic archival runs.” (Amanda wiki)

infofile "/etc/amanda/monthly/curinfo"
logdir "/etc/amanda/monthly"
indexdir "/etc/amanda/monthly/index"

Other than that, because I made a copy of the daily config, I’ve cleaned out the copied config folder’s index and log files, and tapelist file.

Does that look sensible?

Thanks.

Johan

On Mon, Mar 28, 2011 at 04:24:57PM +0100, Johan Booysen wrote:
On Friday, I tried a full monthly backup using the config as mentioned
in the email below.

The backup seems to have run successfully, and I received the amanda
email showing that all disklist entries had a level 0 backup done, but
amrecover doesn't seem able to restore from tape, e.g.


amrecover> setdisk /matrix/data1

200 Disk set to /matrix/data1.

No index records for disk for specified date

If date correct, notify system administrator


In amrecover, did you set the date to one where dumps were made?

In amanda.conf, do you have the index parameter set to yes?

In your config directory, do you have index dirs and files
for the DLE?

--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

Post the server/montly/amindexd.*.debug file

Johan Booysen wrote:

On Friday, I tried a full monthly backup using the config as mentioned
in the email below.



The backup seems to have run successfully, and I received the amanda
email showing that all disklist entries had a level 0 backup done, but
amrecover doesn’t seem able to restore from tape, e.g.



amrecover> setdisk /matrix/data1

200 Disk set to /matrix/data1.

*No index records for disk for specified date*

If date correct, notify system administrator



*-sh-3.2$ less client/monthly/amrecover.20110328144524.debug*

1301319924.401732: amrecover: pid 5380 ruid 0 euid 0: start at Mon Mar
28 14:45:24 2011

1301319924.402305: amrecover: pid 5380 ruid 0 euid 0: rename at Mon
Mar 28 14:45:24 2011

1301319924.402376: amrecover: security_getdriver(name=bsdtcp) returns
0x1531e0

1301319924.402417: amrecover: security_handleinit(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319924.402755: amrecover: security_streaminit(stream=0x838d878,
driver=0x1531e0 (BSDTCP))

1301319924.403683: amrecover: connect_port: Skip port 700: owned by epp.

1301319924.404249: amrecover: connect_port: Skip port 701: owned by lmp.

1301319924.404823: amrecover: connect_port: Skip port 702: owned by
iris-beep.

1301319924.408278: amrecover: connect_port: Try port 703: available -
Success

1301319924.408388: amrecover: connected to 127.0.0.1.10080

1301319924.408403: amrecover: our side is 0.0.0.0.703

1301319924.408417: amrecover: try_socksize: send buffer size is 65536

1301319924.408431: amrecover: try_socksize: receive buffer size is 65536

1301319929.464602: amrecover: security_streaminit(stream=0x83958b0,
driver=0x1531e0 (BSDTCP))

1301319929.464640: amrecover: security_close(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319929.464656: amrecover: security_stream_close(0x838d878)

1301319947.583494: amrecover: user command: 'sethost npt01'

1301319949.698629: amrecover: user command: 'listdisk'

1301319959.814081: amrecover: user command: 'setdisk /matrix/data1'

1301320116.448051: amrecover: user command: 'exit'

1301320116.448440: amrecover: security_stream_close(0x83958b0)

1301320116.448492: amrecover: pid 5380 finish time Mon Mar 28 14:48:36
2011



*-sh-3.2$ amadmin monthly find npt01 /matrix/data1*

date host disk lv tape or
file file part status

2011-03-25 20:05:26 npt01 /matrix/data1 0
monthly-3 328 1/1 OK



*-sh-3.2$ cat /etc/amanda/monthly/log.20110325200526.0 | grep data1*

DISK planner npt01 /matrix/data1

INFO planner Adding new disk npt01:/matrix/data1.

SUCCESS dumper npt01 /matrix/data1 20110325200526 0 [sec 113.520 kb
331365 kps 2919.0 orig-kb 1719510]

SUCCESS chunker npt01 /matrix/data1 20110325200526 0 [sec 113.870 kb
326362 kps 2866.4]

STATS driver estimate npt01 /matrix/data1 20110325200526 0 [sec 839
nkb 1719542 ckb 859808 kps 1024]

PART taper monthly-3 328 npt01 /matrix/data1 20110325200526 1/1 0 [sec
6.126424 kb 326361 kps 53271.143702]

DONE taper npt01 /matrix/data1 20110325200526 1 0 [sec 6.126424 kb
326361 kps 53271.143702]



*-sh-3.2$ ls -l /etc/amanda/monthly/index/npt01/_matrix_data1*

total 124

-rw------- 1 amandabackup disk 119158 Mar 26 08:44 20110325200526_0.gz



It looks like using amrestore will work, although it’s still running
at the moment:



*-sh-3.2$ amrestore tape:/dev/nst0 npt01 /matrix/data1 2011-03-25*

…

…

…

amrestore: 210: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 119/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d

amrestore: 211: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 120/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d



Can anyone please help me understand why this would be?



Thanks.



*From:* owner-amanda-users < at > amanda.org
[mailto:owner-amanda-users < at > amanda.org] *On Behalf Of *Johan Booysen
*Sent:* 15 March 2011 12:25
*To:* amanda-users < at > amanda.org
*Subject:* monthly archive config



I’d really appreciate it if someone can just go over what I’m doing
below, so I don’t miss out anything silly.



I’m using Amanda version 2.6.0p1, and finally cannot effectively make
full backups each night anymore, so I’m looking into using Amanda the
‘classic’ way and to set up another config for monthly full backups.



If I recall correctly, then something like this should work for the
monthly backup runs. I simply made a copy of my daily config and am
just modifying the existing files, e.g. amanda.conf:



dumpcycle 0 to make full backups on each run

runspercycle 1 not really sure about this because
dumpcycle is 0??

tapecycle 12 tapes one tape for each month of the year, but
will actually use 15 in the set up tapes for the odd amflush, if necessary



index yes to generate the catalogue for
use by amrecover

record no apparently: “This is normally
enabled for daily backups and turned off for periodic archival runs.”
(Amanda wiki)



infofile "/etc/amanda/monthly/curinfo"

logdir "/etc/amanda/monthly"

indexdir "/etc/amanda/monthly/index"



Other than that, because I made a copy of the daily config, I’ve
cleaned out the copied config folder’s index and log files, and
tapelist file.



Does that look sensible?



Thanks.



Johan

-----Original Message-----
From: owner-amanda-users < at > amanda.org
[mailto:owner-amanda-users < at > amanda.org] On Behalf Of Jon LaBadie
Sent: 28 March 2011 17:05
To: amanda-users < at > amanda.org
Subject: Re: monthly archive config

On Mon, Mar 28, 2011 at 04:24:57PM +0100, Johan Booysen wrote:
On Friday, I tried a full monthly backup using the config as mentioned
in the email below.

The backup seems to have run successfully, and I received the amanda
email showing that all disklist entries had a level 0 backup done, but
amrecover doesn't seem able to restore from tape, e.g.


amrecover> setdisk /matrix/data1

200 Disk set to /matrix/data1.

No index records for disk for specified date

If date correct, notify system administrator


In amrecover, did you set the date to one where dumps were made?

Yes, I used 'setdate 2011-03-25', but it usually defaults to the date of
the last backup made, I believe.

In amanda.conf, do you have the index parameter set to yes?

Yes. I have it defined in the dumptype I'm using as follows (this works
for me in my daily backup config, of which the monthly one is a copy,
but with the logdir and indexdir set to /etc/amanda/monthly):

define dumptype comp-tar {
program "GNUTAR"
tape_splitsize 1Gb
compress fast
index yes
record no
exclude list "/etc/amanda/exclude-list"
encrypt server
server_encrypt "/usr/sbin/amgpgcrypt"
server_decrypt_option "-d"
}

In your config directory, do you have index dirs and files for the
DLE?

I believe so. Do you mean these?

-sh-3.2$ ls -l index/npt01/_matrix_data1/
total 124
-rw------- 1 amandabackup disk 119158 Mar 26 08:44 20110325200526_0.gz

Thanks.

--
Jon H. LaBadie jon < at > jgcomp.com
JG Computing
12027 Creekbend Drive (703) 787-0884
Reston, VA 20194 (703) 787-0922 (fax)

Contents of /var/log/amanda/server/monthly/amindexd.20110329093735.debug below. Note that the stuff still on holding disk is where the daily backup also ran on Friday, but I haven't flushed that to tape yet. My understanding is that setting 'record' to 'no' would prevent the daily and monthly backups from "interfering" with each other, by the way.

1301387855.928632: amindexd: pid 14759 ruid 500 euid 500: start at Tue Mar 29 09:37:35 2011
1301387855.928681: amindexd: version 2.6.0p1
1301387855.928807: amindexd: < 220 amanda AMANDA index server (2.6.0p1) ready.
1301387860.934757: amindexd: > FEATURES ffffffff9ffeffffffff00
1301387860.934810: amindexd: < 200 FEATURES ffffffff9ffeffffffff00
1301387860.934983: amindexd: > DATE 2011-03-29
1301387860.935015: amindexd: < 200 Working date set to 2011-03-29.
1301387860.935186: amindexd: > SCNF monthly
1301387860.942518: amindexd: pid 14759 ruid 500 euid 500: rename at Tue Mar 29 09:37:40 2011
1301387860.956174: amindexd: < 200 Config set to monthly.
1301387875.038901: amindexd: > DATE 2011-03-25
1301387875.038938: amindexd: < 200 Working date set to 2011-03-25.
1301387878.250434: amindexd: > LISTHOST
1301387878.250463: amindexd: < 200- List hosts for config monthly
1301387878.250542: amindexd: < 201- npt01
1301387878.250605: amindexd: < 200 List hosts for config monthly
1301387880.541498: amindexd: > HOST npt01
1301387880.545923: amindexd: < 200 Dump host set to npt01.
1301387882.965546: amindexd: > LISTDISK
1301387882.965575: amindexd: < 200- List of disk for host npt01
1301387882.965818: amindexd: < 201- /matrix/data1
1301387882.966207: amindexd: < 200 List of disk for host npt01
1301387893.469388: amindexd: > DISK /matrix/data1
1301387893.474612: amindexd: append_to_tapelist(tapelist=(nil), label='/data2/holdingdisk/20110325220002/npt01._matrix_data1.1', file=0, partnum=-1, isafile=1)
1301387893.474633: amindexd: - 2011-03-25-22-00-02 1 /data2/holdingdisk/20110325220002/npt01._matrix_data1.1 0 -1 -1
1301387893.474667: amindexd: append_to_tapelist(tapelist=(nil), label='monthly-3', file=328, partnum=-1, isafile=0)
1301387893.474681: amindexd: - 2011-03-25-20-05-26 0 monthly-3 328 -1 -1
1301387893.474726: amindexd: < 200 Disk set to /matrix/data1.
1301387893.474878: amindexd: > OISD /
1301387893.477263: amindexd: < 599 index not found
1301387927.350191: amindexd: > QUIT
1301387927.350361: amindexd: < 200 Good bye.
1301387927.351092: amindexd: pid 14759 finish time Tue Mar 29 09:38:47 2011

Thanks.

-----Original Message-----
From: Jean-Louis Martineau [mailto:martineau < at > zmanda.com]
Sent: 28 March 2011 17:09
To: Johan Booysen
Cc: amanda-users < at > amanda.org
Subject: Re: monthly archive config

Post the server/montly/amindexd.*.debug file

Johan Booysen wrote:

On Friday, I tried a full monthly backup using the config as mentioned
in the email below.



The backup seems to have run successfully, and I received the amanda
email showing that all disklist entries had a level 0 backup done, but
amrecover doesn’t seem able to restore from tape, e.g.



amrecover> setdisk /matrix/data1

200 Disk set to /matrix/data1.

*No index records for disk for specified date*

If date correct, notify system administrator



*-sh-3.2$ less client/monthly/amrecover.20110328144524.debug*

1301319924.401732: amrecover: pid 5380 ruid 0 euid 0: start at Mon Mar
28 14:45:24 2011

1301319924.402305: amrecover: pid 5380 ruid 0 euid 0: rename at Mon
Mar 28 14:45:24 2011

1301319924.402376: amrecover: security_getdriver(name=bsdtcp) returns
0x1531e0

1301319924.402417: amrecover: security_handleinit(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319924.402755: amrecover: security_streaminit(stream=0x838d878,
driver=0x1531e0 (BSDTCP))

1301319924.403683: amrecover: connect_port: Skip port 700: owned by epp.

1301319924.404249: amrecover: connect_port: Skip port 701: owned by lmp.

1301319924.404823: amrecover: connect_port: Skip port 702: owned by
iris-beep.

1301319924.408278: amrecover: connect_port: Try port 703: available -
Success

1301319924.408388: amrecover: connected to 127.0.0.1.10080

1301319924.408403: amrecover: our side is 0.0.0.0.703

1301319924.408417: amrecover: try_socksize: send buffer size is 65536

1301319924.408431: amrecover: try_socksize: receive buffer size is 65536

1301319929.464602: amrecover: security_streaminit(stream=0x83958b0,
driver=0x1531e0 (BSDTCP))

1301319929.464640: amrecover: security_close(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319929.464656: amrecover: security_stream_close(0x838d878)

1301319947.583494: amrecover: user command: 'sethost npt01'

1301319949.698629: amrecover: user command: 'listdisk'

1301319959.814081: amrecover: user command: 'setdisk /matrix/data1'

1301320116.448051: amrecover: user command: 'exit'

1301320116.448440: amrecover: security_stream_close(0x83958b0)

1301320116.448492: amrecover: pid 5380 finish time Mon Mar 28 14:48:36
2011



*-sh-3.2$ amadmin monthly find npt01 /matrix/data1*

date host disk lv tape or
file file part status

2011-03-25 20:05:26 npt01 /matrix/data1 0
monthly-3 328 1/1 OK



*-sh-3.2$ cat /etc/amanda/monthly/log.20110325200526.0 | grep data1*

DISK planner npt01 /matrix/data1

INFO planner Adding new disk npt01:/matrix/data1.

SUCCESS dumper npt01 /matrix/data1 20110325200526 0 [sec 113.520 kb
331365 kps 2919.0 orig-kb 1719510]

SUCCESS chunker npt01 /matrix/data1 20110325200526 0 [sec 113.870 kb
326362 kps 2866.4]

STATS driver estimate npt01 /matrix/data1 20110325200526 0 [sec 839
nkb 1719542 ckb 859808 kps 1024]

PART taper monthly-3 328 npt01 /matrix/data1 20110325200526 1/1 0 [sec
6.126424 kb 326361 kps 53271.143702]

DONE taper npt01 /matrix/data1 20110325200526 1 0 [sec 6.126424 kb
326361 kps 53271.143702]



*-sh-3.2$ ls -l /etc/amanda/monthly/index/npt01/_matrix_data1*

total 124

-rw------- 1 amandabackup disk 119158 Mar 26 08:44 20110325200526_0.gz



It looks like using amrestore will work, although it’s still running
at the moment:



*-sh-3.2$ amrestore tape:/dev/nst0 npt01 /matrix/data1 2011-03-25*

…

…

…

amrestore: 210: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 119/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d

amrestore: 211: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 120/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d



Can anyone please help me understand why this would be?



Thanks.



*From:* owner-amanda-users < at > amanda.org
[mailto:owner-amanda-users < at > amanda.org] *On Behalf Of *Johan Booysen
*Sent:* 15 March 2011 12:25
*To:* amanda-users < at > amanda.org
*Subject:* monthly archive config



I’d really appreciate it if someone can just go over what I’m doing
below, so I don’t miss out anything silly.



I’m using Amanda version 2.6.0p1, and finally cannot effectively make
full backups each night anymore, so I’m looking into using Amanda the
‘classic’ way and to set up another config for monthly full backups.



If I recall correctly, then something like this should work for the
monthly backup runs. I simply made a copy of my daily config and am
just modifying the existing files, e.g. amanda.conf:



dumpcycle 0 to make full backups on each run

runspercycle 1 not really sure about this because
dumpcycle is 0??

tapecycle 12 tapes one tape for each month of the year, but
will actually use 15 in the set up tapes for the odd amflush, if necessary



index yes to generate the catalogue for
use by amrecover

record no apparently: “This is normally
enabled for daily backups and turned off for periodic archival runs.”
(Amanda wiki)



infofile "/etc/amanda/monthly/curinfo"

logdir "/etc/amanda/monthly"

indexdir "/etc/amanda/monthly/index"



Other than that, because I made a copy of the daily config, I’ve
cleaned out the copied config folder’s index and log files, and
tapelist file.



Does that look sensible?



Thanks.



Johan

Is there any chance a dodgy (brand-new) tape could have caused all of this?

I've just tried backing up a small subset of data, using another new tape, and can quite happily restore from it.

Thanks.

Johan

-----Original Message-----
From: owner-amanda-users < at > amanda.org [mailto:owner-amanda-users < at > amanda.org] On Behalf Of Johan Booysen
Sent: 29 March 2011 09:57
To: amanda-users < at > amanda.org
Subject: RE: monthly archive config

Contents of /var/log/amanda/server/monthly/amindexd.20110329093735.debug below. Note that the stuff still on holding disk is where the daily backup also ran on Friday, but I haven't flushed that to tape yet. My understanding is that setting 'record' to 'no' would prevent the daily and monthly backups from "interfering" with each other, by the way.

1301387855.928632: amindexd: pid 14759 ruid 500 euid 500: start at Tue Mar 29 09:37:35 2011
1301387855.928681: amindexd: version 2.6.0p1
1301387855.928807: amindexd: < 220 amanda AMANDA index server (2.6.0p1) ready.
1301387860.934757: amindexd: > FEATURES ffffffff9ffeffffffff00
1301387860.934810: amindexd: < 200 FEATURES ffffffff9ffeffffffff00
1301387860.934983: amindexd: > DATE 2011-03-29
1301387860.935015: amindexd: < 200 Working date set to 2011-03-29.
1301387860.935186: amindexd: > SCNF monthly
1301387860.942518: amindexd: pid 14759 ruid 500 euid 500: rename at Tue Mar 29 09:37:40 2011
1301387860.956174: amindexd: < 200 Config set to monthly.
1301387875.038901: amindexd: > DATE 2011-03-25
1301387875.038938: amindexd: < 200 Working date set to 2011-03-25.
1301387878.250434: amindexd: > LISTHOST
1301387878.250463: amindexd: < 200- List hosts for config monthly
1301387878.250542: amindexd: < 201- npt01
1301387878.250605: amindexd: < 200 List hosts for config monthly
1301387880.541498: amindexd: > HOST npt01
1301387880.545923: amindexd: < 200 Dump host set to npt01.
1301387882.965546: amindexd: > LISTDISK
1301387882.965575: amindexd: < 200- List of disk for host npt01
1301387882.965818: amindexd: < 201- /matrix/data1
1301387882.966207: amindexd: < 200 List of disk for host npt01
1301387893.469388: amindexd: > DISK /matrix/data1
1301387893.474612: amindexd: append_to_tapelist(tapelist=(nil), label='/data2/holdingdisk/20110325220002/npt01._matrix_data1.1', file=0, partnum=-1, isafile=1)
1301387893.474633: amindexd: - 2011-03-25-22-00-02 1 /data2/holdingdisk/20110325220002/npt01._matrix_data1.1 0 -1 -1
1301387893.474667: amindexd: append_to_tapelist(tapelist=(nil), label='monthly-3', file=328, partnum=-1, isafile=0)
1301387893.474681: amindexd: - 2011-03-25-20-05-26 0 monthly-3 328 -1 -1
1301387893.474726: amindexd: < 200 Disk set to /matrix/data1.
1301387893.474878: amindexd: > OISD /
1301387893.477263: amindexd: < 599 index not found
1301387927.350191: amindexd: > QUIT
1301387927.350361: amindexd: < 200 Good bye.
1301387927.351092: amindexd: pid 14759 finish time Tue Mar 29 09:38:47 2011

Thanks.

-----Original Message-----
From: Jean-Louis Martineau [mailto:martineau < at > zmanda.com]
Sent: 28 March 2011 17:09
To: Johan Booysen
Cc: amanda-users < at > amanda.org
Subject: Re: monthly archive config

Post the server/montly/amindexd.*.debug file

Johan Booysen wrote:

On Friday, I tried a full monthly backup using the config as mentioned
in the email below.



The backup seems to have run successfully, and I received the amanda
email showing that all disklist entries had a level 0 backup done, but
amrecover doesn’t seem able to restore from tape, e.g.



amrecover> setdisk /matrix/data1

200 Disk set to /matrix/data1.

*No index records for disk for specified date*

If date correct, notify system administrator



*-sh-3.2$ less client/monthly/amrecover.20110328144524.debug*

1301319924.401732: amrecover: pid 5380 ruid 0 euid 0: start at Mon Mar
28 14:45:24 2011

1301319924.402305: amrecover: pid 5380 ruid 0 euid 0: rename at Mon
Mar 28 14:45:24 2011

1301319924.402376: amrecover: security_getdriver(name=bsdtcp) returns
0x1531e0

1301319924.402417: amrecover: security_handleinit(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319924.402755: amrecover: security_streaminit(stream=0x838d878,
driver=0x1531e0 (BSDTCP))

1301319924.403683: amrecover: connect_port: Skip port 700: owned by epp.

1301319924.404249: amrecover: connect_port: Skip port 701: owned by lmp.

1301319924.404823: amrecover: connect_port: Skip port 702: owned by
iris-beep.

1301319924.408278: amrecover: connect_port: Try port 703: available -
Success

1301319924.408388: amrecover: connected to 127.0.0.1.10080

1301319924.408403: amrecover: our side is 0.0.0.0.703

1301319924.408417: amrecover: try_socksize: send buffer size is 65536

1301319924.408431: amrecover: try_socksize: receive buffer size is 65536

1301319929.464602: amrecover: security_streaminit(stream=0x83958b0,
driver=0x1531e0 (BSDTCP))

1301319929.464640: amrecover: security_close(handle=0x838a058,
driver=0x1531e0 (BSDTCP))

1301319929.464656: amrecover: security_stream_close(0x838d878)

1301319947.583494: amrecover: user command: 'sethost npt01'

1301319949.698629: amrecover: user command: 'listdisk'

1301319959.814081: amrecover: user command: 'setdisk /matrix/data1'

1301320116.448051: amrecover: user command: 'exit'

1301320116.448440: amrecover: security_stream_close(0x83958b0)

1301320116.448492: amrecover: pid 5380 finish time Mon Mar 28 14:48:36
2011



*-sh-3.2$ amadmin monthly find npt01 /matrix/data1*

date host disk lv tape or
file file part status

2011-03-25 20:05:26 npt01 /matrix/data1 0
monthly-3 328 1/1 OK



*-sh-3.2$ cat /etc/amanda/monthly/log.20110325200526.0 | grep data1*

DISK planner npt01 /matrix/data1

INFO planner Adding new disk npt01:/matrix/data1.

SUCCESS dumper npt01 /matrix/data1 20110325200526 0 [sec 113.520 kb
331365 kps 2919.0 orig-kb 1719510]

SUCCESS chunker npt01 /matrix/data1 20110325200526 0 [sec 113.870 kb
326362 kps 2866.4]

STATS driver estimate npt01 /matrix/data1 20110325200526 0 [sec 839
nkb 1719542 ckb 859808 kps 1024]

PART taper monthly-3 328 npt01 /matrix/data1 20110325200526 1/1 0 [sec
6.126424 kb 326361 kps 53271.143702]

DONE taper npt01 /matrix/data1 20110325200526 1 0 [sec 6.126424 kb
326361 kps 53271.143702]



*-sh-3.2$ ls -l /etc/amanda/monthly/index/npt01/_matrix_data1*

total 124

-rw------- 1 amandabackup disk 119158 Mar 26 08:44 20110325200526_0.gz



It looks like using amrestore will work, although it’s still running
at the moment:



*-sh-3.2$ amrestore tape:/dev/nst0 npt01 /matrix/data1 2011-03-25*

…

…

…

amrestore: 210: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 119/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d

amrestore: 211: skipping split dumpfile: date 20110325200526 host
npt01 disk /matrix/data part 120/151 lev 0 comp .gz program /bin/tar
crypt enc server_encrypt /usr/sbin/amgpgcrypt server_decrypt_option -d



Can anyone please help me understand why this would be?



Thanks.



*From:* owner-amanda-users < at > amanda.org
[mailto:owner-amanda-users < at > amanda.org] *On Behalf Of *Johan Booysen
*Sent:* 15 March 2011 12:25
*To:* amanda-users < at > amanda.org
*Subject:* monthly archive config



I’d really appreciate it if someone can just go over what I’m doing
below, so I don’t miss out anything silly.



I’m using Amanda version 2.6.0p1, and finally cannot effectively make
full backups each night anymore, so I’m looking into using Amanda the
‘classic’ way and to set up another config for monthly full backups.



If I recall correctly, then something like this should work for the
monthly backup runs. I simply made a copy of my daily config and am
just modifying the existing files, e.g. amanda.conf:



dumpcycle 0 to make full backups on each run

runspercycle 1 not really sure about this because
dumpcycle is 0??

tapecycle 12 tapes one tape for each month of the year, but
will actually use 15 in the set up tapes for the odd amflush, if necessary



index yes to generate the catalogue for
use by amrecover

record no apparently: “This is normally
enabled for daily backups and turned off for periodic archival runs.”
(Amanda wiki)



infofile "/etc/amanda/monthly/curinfo"

logdir "/etc/amanda/monthly"

indexdir "/etc/amanda/monthly/index"



Other than that, because I made a copy of the daily config, I’ve
cleaned out the copied config folder’s index and log files, and
tapelist file.



Does that look sensible?



Thanks.



Johan