No data found on restoring from backups taken from Windows host - Seeking help

[Dinesh Vashisht]

Hi,



While restoring backups taken from Windows host, receiving following error 
'part 1/UNKNOWN ' and there is no data:



[amandabackup@pciambkup restore]$ amfetchdump DailySet21 pcivmm1.itrnetwork.com 
"C:/Scripts" 20170119010002

1 volume(s) needed for restoration

The following volumes are needed: DailySet21-08



Press enter when ready





Reading label 'DailySet21-08' filenum 1

split dumpfile: date 20170119010002 host pcivmm1.itrnetwork.com disk 
"C:/Scripts" part 1/UNKNOWN lev 1 comp N program pkzip 1 kb

[amandabackup@pciambkup restore]$



Can someone help to identify cause & resolving this issue?



There is only one entry in the disklist file:



pcivmm1.itrnetwork.com  C:/Scripts   zwc-compress










CONFIDENTIAL NOTICE: All information, data and attachments contained in this 
message are confidential and are the property of the sender. If you are not the 
intended recipient and have received this email in error delete it immediately 
and destroy all copies. Any redistribution, communication or actions taken on 
information contained in this message is strictly prohibited.

RE: Unable to make tape rotation work in Amanda - Seeking Help

[Dinesh Vashisht]

Tape rotation issue is solved by changing taperscan algorithm to oldest.

I am validating restores now.

-Original Message-
From: Stefan G. Weichinger [mailto:s...@amanda.org]
Sent: 18 January 2017 20:08
To: Dinesh Vashisht; li...@xunil.at
Cc: amanda-users@amanda.org
Subject: Re: Unable to make tape rotation work in Amanda - Seeking Help

Am 2017-01-18 um 12:24 schrieb Dinesh Vashisht:
> [amandabackup@pciambkup DailySet19]$ *amcheck DailySet19*

> Searching for label 'DailySet19-01':found in slot 1: volume 'DailySet19-01'
> all slots have been loaded
>
> Taper scan algorithm did not find an acceptable volume.
> (expecting volume 'DailySet19-01' or a new volume)

Hm, that looks strange, yes.
I don't see the error, although I assume it will be something small ...
Maybe someone else here spots it ... ?

One thing I think of:

try changing the taperscan algorithm (just remove that line and let amanda use 
the default)

And 2nd (not related, I think): why don't you have any holdingdisk defined?  A 
holdingdisk is crucial for many of amanda's features.

CONFIDENTIAL NOTICE:  All information, data and attachments contained in this 
message are confidential and are the property of the sender.  If you are not 
the intended recipient and have received this email in error delete it 
immediately and destroy all copies.  Any redistribution, communication or 
actions taken on information contained in this message is strictly prohibited.

Re: Unable to make tape rotation work in Amanda - Seeking Help

[Stefan G. Weichinger]

Am 2017-01-18 um 12:24 schrieb Dinesh Vashisht:
> [amandabackup@pciambkup DailySet19]$ *amcheck DailySet19*

> Searching for label 'DailySet19-01':found in slot 1: volume 'DailySet19-01'
> all slots have been loaded
> 
> Taper scan algorithm did not find an acceptable volume.
> (expecting volume 'DailySet19-01' or a new volume)

Hm, that looks strange, yes.
I don't see the error, although I assume it will be something small ...
Maybe someone else here spots it ... ?

One thing I think of:

try changing the taperscan algorithm (just remove that line and let
amanda use the default)

And 2nd (not related, I think): why don't you have any holdingdisk
defined?  A holdingdisk is crucial for many of amanda's features.

RE: Unable to make tape rotation work in Amanda - Seeking Help

[Dinesh Vashisht]

After changing the retention-tapes to 11 in amanda.conf, still there is an 
error Taper error: "No acceptable volumes found" and cannot backup data.



Following are details of amcheck & amreport commands:



[amandabackup@pciambkup DailySet19]$ amcheck DailySet19

Amanda Tape Server Host Check

-

Searching for label 'DailySet19-01':found in slot 1: volume 'DailySet19-01'

all slots have been loaded

Taper scan algorithm did not find an acceptable volume.

(expecting volume 'DailySet19-01' or a new volume)

ERROR: No acceptable volumes found

Server check took 0.533 seconds

Amanda Backup Client Hosts Check



Client check: 1 host checked in 0.202 seconds.  0 problems found.

(brought to you by Amanda 3.4.1)



You have new mail in /var/spool/mail/root

[amandabackup@pciambkup DailySet19]$





amandabackup@pciambkup DailySet19]$ amreport DailySet19

Hostname: pciambkup

Org : DailySet19

Config  : DailySet19

Date: January 18, 2017



*** A TAPE ERROR OCCURRED: [No acceptable volumes found].

No dumps are left in the holding disk.

The next tape Amanda expects to use is: DailySet19-01.





FAILURE DUMP SUMMARY:

  pcivmm1.itrnetwork.com "C:/Scripts" lev 1  FAILED [can't do degraded dump 
without holding disk]





STATISTICS:

  Total   Full  Incr.   Level:#

        

Estimate Time (hrs:min) 0:00

Run Time (hrs:min)  0:00

Dump Time (hrs:min) 0:00   0:00   0:00

Output Size (meg)0.00.00.0

Original Size (meg)  0.00.00.0

Avg Compressed Size (%)  -- -- --

DLEs Dumped0  0  0

Avg Dump Rate (k/s)  -- -- --



Tape Time (hrs:min) 0:00   0:00   0:00

Tape Size (meg)  0.00.00.0

Tape Used (%)0.00.00.0

DLEs Taped 0  0  0

Parts Taped0  0  0

Avg Tp Write Rate (k/s)  -- -- --





NOTES:

  planner: Last full dump of pcivmm1.itrnetwork.com:"C:/Scripts" on tape 
DailySet19-01 overwritten on this run.

  driver: Taper error: "No acceptable volumes found"

  taper: all slots have been loaded





DUMP SUMMARY:

  DUMPER STATS   
TAPER STATS

HOSTNAME   DISK L ORIG-GB  OUT-GB  COMP%  MMM:SS   KB/s 
MMM:SS   KB/s

- -- -- 
-

pcivmm1.itrnetwork.com "C:/Scripts"  FAILED



(brought to you by Amanda version 3.4.1)

[amandabackup@pciambkup DailySet19]$ amcheck DailySet19

Amanda Tape Server Host Check

-

Searching for label 'DailySet19-01':found in slot 1: volume 'DailySet19-01'

all slots have been loaded

Taper scan algorithm did not find an acceptable volume.

(expecting volume 'DailySet19-01' or a new volume)

ERROR: No acceptable volumes found

Server check took 0.533 seconds

Amanda Backup Client Hosts Check



Client check: 1 host checked in 0.202 seconds.  0 problems found.

(brought to you by Amanda 3.4.1)



You have new mail in /var/spool/mail/root

[amandabackup@pciambkup DailySet19]$





What could be the other reason of backup failure?











-Original Message-
From: Stefan G. Weichinger [mailto:s...@amanda.org]
Sent: 18 January 2017 16:34
To: Dinesh Vashisht
Cc: amanda-users@amanda.org
Subject: Re: Unable to make tape rotation work in Amanda - Seeking Help





I think you should reduce retention-tapes to 11.



tapecycle 12 -> retention-tapes 11


CONFIDENTIAL NOTICE: All information, data and attachments contained in this 
message are confidential and are the property of the sender. If you are not the 
intended recipient and have received this email in error delete it immediately 
and destroy all copies. Any redistribution, communication or actions taken on 
information contained in this message is strictly prohibited.

Re: Unable to make tape rotation work in Amanda - Seeking Help

[Stefan G. Weichinger]

I think you should reduce retention-tapes to 11.

tapecycle 12 -> retention-tapes 11

RE: Unable to make tape rotation work in Amanda - Seeking Help

[Dinesh Vashisht]

# amtape DailySet19 inventory



[amandabackup@pciambkup root]$ amtape DailySet19 inventory

slot 1: label DailySet19-01 [retention-tapes]

slot 2: label DailySet19-02 [retention-tapes]

slot 3: label DailySet19-03 [retention-tapes]

slot 4: label DailySet19-04 [retention-tapes]

slot 5: label DailySet19-05 [retention-tapes]

slot 6: label DailySet19-06 [retention-tapes]

slot 7: label DailySet19-07 [retention-tapes]

slot 8: label DailySet19-08 [retention-tapes]

slot 9: label DailySet19-09 [retention-tapes]

slot 10: label DailySet19-10 [retention-tapes]

slot 11: label DailySet19-11 [retention-tapes]

slot 12: label DailySet19-12 (current) [retention-tapes]

[amandabackup@pciambkup root]$



# amadmin DailySet19 tape



amandabackup@pciambkup root]$ amadmin DailySet19 tape

The next Amanda should go onto 1 new tape.

[amandabackup@pciambkup root]$



and show the tapelist file



[amandabackup@pciambkup DailySet19]$ cat tapelist

20170118041059 DailySet19-12 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118041025 DailySet19-11 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118041008 DailySet19-10 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040956 DailySet19-09 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040945 DailySet19-08 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040935 DailySet19-07 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040920 DailySet19-06 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040910 DailySet19-05 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040858 DailySet19-04 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040845 DailySet19-03 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040821 DailySet19-02 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

20170118040231 DailySet19-01 reuse BLOCKSIZE:32 POOL:DailySet19 
STORAGE:DailySet19 CONFIG:DailySet19

[amandabackup@pciambkup DailySet19]$



why did you rename the config?



I didn't rename the config, instead created new config for testing purposes





-Original Message-
From: Stefan G. Weichinger [mailto:s...@amanda.org]
Sent: 18 January 2017 15:41
To: Dinesh Vashisht; li...@xunil.at
Cc: amanda-users@amanda.org
Subject: Re: Unable to make tape rotation work in Amanda - Seeking Help



Am 2017-01-18 um 10:24 schrieb Dinesh Vashisht:



> *amadmin DailySet1 inventory ?*

>

> --

>

> It's not a valid command, instead:



that should have been:



# amtape DailySet19 inventory



and please



# amadmin DailySet19 tape



and show the tapelist file



why did you rename the config?








CONFIDENTIAL NOTICE: All information, data and attachments contained in this 
message are confidential and are the property of the sender. If you are not the 
intended recipient and have received this email in error delete it immediately 
and destroy all copies. Any redistribution, communication or actions taken on 
information contained in this message is strictly prohibited.

Re: Unable to make tape rotation work in Amanda - Seeking Help

[Stefan G. Weichinger]

Am 2017-01-18 um 10:24 schrieb Dinesh Vashisht:


*amadmin DailySet1 inventory ?*

--

It's not a valid command, instead:


that should have been:

# amtape DailySet19 inventory

and please

# amadmin DailySet19 tape

and show the tapelist file

why did you rename the config?

RE: Unable to make tape rotation work in Amanda - Seeking Help

[Dinesh Vashisht]

I tried this option labelstr "DailySet1-[0-9][0-9]*" creating another DLE.



Still getting same error while running 'amcheck DailySet19' and tape rotation 
is not working:



amandabackup@pciambkup DailySet19]$ amcheck DailySet19

Amanda Tape Server Host Check

-

slot 12: volume 'DailySet19-12' is still active and cannot be overwritten

slot 1: volume 'DailySet19-01' is still active and cannot be overwritten

slot 2: volume 'DailySet19-02' is still active and cannot be overwritten

slot 3: volume 'DailySet19-03' is still active and cannot be overwritten

slot 4: volume 'DailySet19-04' is still active and cannot be overwritten

slot 5: volume 'DailySet19-05' is still active and cannot be overwritten

slot 6: volume 'DailySet19-06' is still active and cannot be overwritten

slot 7: volume 'DailySet19-07' is still active and cannot be overwritten

slot 8: volume 'DailySet19-08' is still active and cannot be overwritten

slot 9: volume 'DailySet19-09' is still active and cannot be overwritten

slot 10: volume 'DailySet19-10' is still active and cannot be overwritten

slot 11: volume 'DailySet19-11' is still active and cannot be overwritten

all slots have been loaded

Taper scan algorithm did not find an acceptable volume.

(expecting a new volume)

ERROR: No acceptable volumes found

Server check took 0.591 seconds

Amanda Backup Client Hosts Check



Client check: 1 host checked in 0.265 seconds.  0 problems found.

(brought to you by Amanda 3.4.1)



[amandabackup@pciambkup DailySet19]$



Attached is the new amanda.conf file.







-Original Message-
From: Stefan G. Weichinger [mailto:s...@amanda.org]
Sent: 17 January 2017 23:33
To: Dinesh Vashisht; amanda-users@amanda.org
Subject: Re: Unable to make tape rotation work in Amanda - Seeking Help



I assume the problem is here:



labelstr "DailySet1"



That should be something like:



labelstr "DailySet1-[0-9][0-9]*" "



otherwise every tape has the same label.


CONFIDENTIAL NOTICE: All information, data and attachments contained in this 
message are confidential and are the property of the sender. If you are not the 
intended recipient and have received this email in error delete it immediately 
and destroy all copies. Any redistribution, communication or actions taken on 
information contained in this message is strictly prohibited.


amanda.rar
Description: amanda.rar

RE: Unable to make tape rotation work in Amanda - Seeking Help

[Dinesh Vashisht]

What does "amcheck DailySet1" say?

--

[amandabackup@pciambkup amanda]$ amcheck DailySet1

Amanda Tape Server Host Check

-

slot 12: volume 'DailySet1-12' is still active and cannot be overwritten

slot 1: volume 'DailySet1-1' is still active and cannot be overwritten

slot 2: volume 'DailySet1-2' is still active and cannot be overwritten

slot 3: volume 'DailySet1-3' is still active and cannot be overwritten

slot 4: volume 'DailySet1-4' is still active and cannot be overwritten

slot 5: volume 'DailySet1-5' is still active and cannot be overwritten

slot 6: volume 'DailySet1-6' is still active and cannot be overwritten

slot 7: volume 'DailySet1-7' is still active and cannot be overwritten

slot 8: volume 'DailySet1-8' is still active and cannot be overwritten

slot 9: volume 'DailySet1-9' is still active and cannot be overwritten

slot 10: volume 'DailySet1-10' is still active and cannot be overwritten

slot 11: volume 'DailySet1-11' is still active and cannot be overwritten

all slots have been loaded

Taper scan algorithm did not find an acceptable volume.

(expecting a new volume)

ERROR: No acceptable volumes found

Server check took 0.319 seconds

Amanda Backup Client Hosts Check



Client check: 1 host checked in 0.133 seconds.  0 problems found.

(brought to you by Amanda 3.4.1)



[amandabackup@pciambkup amanda]$

-

And show the content of /data1/amanda/vtape/DailySet1.



[amandabackup@pciambkup DailySet1]$ pwd

/data1/amanda/vtape/DailySet1

[amandabackup@pciambkup DailySet1]$ ll

total 4

lrwxrwxrwx 1 amandabackup disk6 Jan 18 03:27 data -> slot12

drwx-- 2 amandabackup disk   78 Jan 18 03:25 slot1

drwx-- 2 amandabackup disk   79 Jan 18 03:26 slot10

drwx-- 2 amandabackup disk   79 Jan 18 03:27 slot11

drwx-- 2 amandabackup disk   79 Jan 18 03:27 slot12

drwx-- 2 amandabackup disk   78 Jan 18 03:25 slot2

drwx-- 2 amandabackup disk   78 Jan 18 03:25 slot3

drwx-- 2 amandabackup disk   78 Jan 18 03:25 slot4

drwx-- 2 amandabackup disk   78 Jan 18 03:26 slot5

drwx-- 2 amandabackup disk   78 Jan 18 03:26 slot6

drwx-- 2 amandabackup disk   78 Jan 18 03:26 slot7

drwx-- 2 amandabackup disk   78 Jan 18 03:26 slot8

drwx-- 2 amandabackup disk   78 Jan 18 03:26 slot9

-rw--- 1 amandabackup disk 1081 Jan 18 03:27 state

[amandabackup@pciambkup DailySet1]$

---

Did you create slots/tapes there and label them?

---

It's done by the ' amserverconfig' command itself.

---

amadmin DailySet1 inventory ?

--

It's not a valid command, instead:



amandabackup@pciambkup DailySet1]$ amadmin DailySet1 info



Current info for pcivmm1.itrnetwork.com C:/Scripts:

  Stats: dump rates (kps), Full:   11.8,  -1.0,  -1.0

Incremental:1.0,   1.0,   1.0

  compressed size, Full:  57.0%,-100.0%,-100.0%

Incremental: 100.0%,100.0%,100.0%

  Dumps: lev datestmp  tape file   origK   compK secs

  0  20170118  DailySet1-1  1 228 130 11

  1  20170118  DailySet1-12 1 1 1 4

[amandabackup@pciambkup DailySet1]$



--











-Original Message-
From: Stefan G. Weichinger [mailto:s...@amanda.org]
Sent: 17 January 2017 23:25
To: Dinesh Vashisht
Subject: Re: Unable to make tape rotation work in Amanda - Seeking Help



Am 2017-01-17 um 17:22 schrieb Dinesh Vashisht:



> amserverconfig DailySet1 --template harddisk --tapedev

> /data1/amanda/vtape/DailySet1 --mailto root@localhost --dumpcycle

> 1week --runspercycle 5 --tapecycle 12 --runtapes 1

>

>

>

> Every time to make backup happen, I have to create New DLE  (& vTape

> set) and at the end it gives a message: driver: Taper error: "No

> acceptable volumes found".

>

> It is difficult to modify the cron job each time since there are many

> backups running.



What does "amcheck DailySet1" say?

And show the content of /data1/amanda/vtape/DailySet1.

Did you create slots/tapes there and label them?



amadmin DailySet1 inventory ?




CONFIDENTIAL NOTICE: All information, data and attachments contained in this 
message are confidential and are the property of the se

Re: Unable to make tape rotation work in Amanda - Seeking Help

[Stefan G. Weichinger]

I assume the problem is here:

labelstr "DailySet1"

That should be something like:

labelstr "DailySet1-[0-9][0-9]*" "

otherwise every tape has the same label.

Re: Request for help: 'amdump' creates empty backup

[Stefan G. Weichinger]

Am 2016-12-11 um 21:13 schrieb Thomas Fischer:

> So, the question is: what am I doing wrong in my second, live CD/USB setup? I 
> cannot see any obvious problems, so I am open for suggestions!
> 
> Looking forward to your help!

Thomas, thanks for your *book* about your tests ;-)

Some issue that might be related or not: pls use FQDNs for your DLEs,
not "localhost".

And I'd suggest trying

record yes
(or removing "record no" as "yes" is default)

in your dumptype(s)

Request for help: 'amdump' creates empty backup

[Thomas Fischer]

tname: amandausb
Org : LIM
Config  : usb
Date: December 11, 2016

These dumps were to tape User_amanda_Backup_01.
The next tape Amanda expects to use is: 1 new tape.
The next new tape already labelled is: User_amanda_Backup_02.


STATISTICS:
  Total   Full  Incr.   Level:#
        
Estimate Time (hrs:min) 0:00
Run Time (hrs:min)  0:00
Dump Time (hrs:min) 0:00   0:00   0:00
Output Size (meg)0.00.00.0
Original Size (meg)  0.00.00.0
Avg Compressed Size (%)100.0  100.0--
DLEs Dumped1  1  0
Avg Dump Rate (k/s)714.3  714.3--

Tape Time (hrs:min) 0:00   0:00   0:00
Tape Size (meg)  0.00.00.0
Tape Used (%)  Amanda Tape Server Host Check
-
Holding disk /backup/holding: 1007616 KB disk space available, using 495616 KB
slot 1: volume 'User_amanda_Backup_01' is still active and cannot be overwritten
slot 2: volume 'User_amanda_Backup_02'
Will write to volume 'User_amanda_Backup_02' in slot 2.
NOTE: skipping tape-writable test
Server check took 0.158 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 2.029 seconds.  0 problems found.

(brought to you by Amanda 3.3.9)
  0.00.00.0
DLEs Taped 1  1  0
Parts Taped1  1  0
Avg Tp Write Rate (k/s)100.0  100.0--

USAGE BY TAPE:
  Label   Time Size  %  DLEs Parts
  User_amanda_Backup_01   0:00  10K0.0 1 1



NOTES:
  planner: Adding new disk localhost:/windows/documents.
  taper: Slot 1 with label User_amanda_Backup_01 is usable
  taper: tape User_amanda_Backup_01 kb 10 fm 1 [OK]


DUMP SUMMARY:
  DUMPER STATS   TAPER 
STATS
HOSTNAME DISK   L ORIG-KB  OUT-KB  COMP%  MMM:SS   KB/s MMM:SS  
 KB/s
- -- -- 
-
localhost/windows/documents 0  10  10 --0:00  682.7   0:00  
100.0

(brought to you by Amanda version 3.3.9)
$ amcheck usb
Amanda Tape Server Host Check
-
Holding disk /backup/holding: 1007616 KB disk space available, using 495616 KB
slot 1: volume 'User_amanda_Backup_01' is still active and cannot be overwritten
slot 2: volume 'User_amanda_Backup_02'
Will write to volume 'User_amanda_Backup_02' in slot 2.
NOTE: skipping tape-writable test
Server check took 0.158 seconds

Amanda Backup Client Hosts Check
----
Client check: 1 host checked in 2.029 seconds.  0 problems found.

(brought to you by Amanda 3.3.9)
---8<---8<---8<---

As can be seen in the output, 'Output Size (meg)' and 'Original Size (meg)', 
despite having data in the directory to be backup'ed:

---8<---8<---8<---
$ ls -l /windows/documents
total 8256
-rw-r--r-- 1 root root  30 Dec 11 18:34 date.txt
-rw-r--r-- 1 root root   53103 Dec 11 18:34 dmesg.txt
-rw-r--r-- 1 root root   11487 Dec 11 18:34 ps-ax.txt
-rw-r--r-- 1 root root 8388608 Dec 11 18:34 rand.bin
---8<---8<---8<---

So, the question is: what am I doing wrong in my second, live CD/USB setup? I 
cannot see any obvious problems, so I am open for suggestions!

Looking forward to your help!

Bye,
Thomas

Re: Newbie help

[Jon LaBadie]

On Tue, Dec 01, 2015 at 10:28:27PM +, Debra S Baddorf wrote:
> I agree with Alan’s comment.   You shouldn’t need   - - notaper.   (But you 
> CAN use it
> if you want - see below).
> Some comments below.
> Deb Baddorf
> 
> > On Dec 1, 2015, at 3:18 PM, Chris Lewis  wrote:
> > 
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA1
> > 
> > Hi,
> > 
> > Running Amanda 3.3.3 on Ubuntu 14.04, with a simple LT04 tape drive.
> > 
...
> > 
> > localhost /fisher2 lev 0  FAILED [Skipping: new disk can't be dumped
> > in degraded mode]
> 
> So then, why is it trying to use “degraded mode”,   if the holding disk is 
> big enough
> to fit all of the data?   Check this parameter:
> 
> reserve 02 # percent
> # This means save only 2% of the holding disk space for degraded
> # mode backups. 
> 
> I think the default may be 30%.   Or at least,  the value mine was initially 
> set for
> was 30%.If your new disk takes up more than 70% of the holding disk, 
> there would
> not be 30% left,  and THAT could be why it is complaining.
>  But you don’t care,  so get rid of that default (or original)  value, 
> and set it to a value
> that YOU want. Mine is the 2% I’ve shown above.
> 
> Once you get that value low enough,  you certainly  CAN  use  - - notaper
> to force the backup to sit on the holding disk until you are ready to back up 
> the rest of
> the set.If you like.
> 
> See if this fixes it.  So I guess this was just one comment.

The default is actually 100%, i.e. only incrementals allowed in
degraded mode.  Degraded mode is no tape available.  I suspect
the OP's amanda.conf hasn't even set the 'reserve' value.

  reserve int

Default: 100. The part of holding-disk space that should be reserved
for incremental backups if no tape is available, expressed as a
percentage of the available holding-disk space (0-100). By default,
when there is no tape to write to, degraded mode (incremental) backups
will be performed to the holding disk. If full backups should also be
allowed in this case, the amount of holding disk space reserved for
incrementals should be lowered.

jl
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: Newbie help

[Jon LaBadie]

On Wed, Dec 02, 2015 at 08:35:26PM -0500, Chris Lewis wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> On 12/02/2015 01:36 PM, Jon LaBadie wrote:
> | On Tue, Dec 01, 2015 at 10:28:27PM +, Debra S Baddorf wrote:
> |> I agree with Alan’s comment.   You shouldn’t need   - - notaper.
> |> (But you CAN use it
> 
> Thanks all, I think I understand now.  It's a bit more subtle than
> understanding Amanda config (which I don't yet!)
> 
> The filesystem to be backed up consists of 9 directories, where almost
> every file is hard-linked into the other 8 directories.
> 
> [It's daily backups and incrementals, where if the file is unchanged,
> it's hard-linked to the other identical copies.]
> 
> While df and du both show the backup to be 990Gb, a naive view (not
> taking into account hard links) shows it at over 7Tb.  The Amanda size
> estimator shows 7Tb (via amstatus), not 990Gb, hence, it's way too big
> for my 1.5Tb holding area.  Web searches on the subject seem to
> indicate that the Amanda backups _will_ preserve hard links (hence
> only backing up 990Gb), so if I let the backup run, it would have
> worked (but shoe-shined unacceptably).  On a faster drive, the
> shoe-shine wouldn't have mattered, but it would have bleated about not
> having enough tapes (even tho it wouldn't use them).
> 

What "estimate" type are you using for your new DLE?

  estimate [ client | calcsize | server ]+

Default: client.  Determine the way Amanda estimates the size of each DLE
before beginning a backup.  This is a list of acceptable estimate methods,
and Amanda applies the first method supported by the application.
The methods are:

  client

Use the same program as the dumping program.  This is the most accurate
method to do estimates, but it can take a long time.

  calcsize

Use a faster program to do estimates, but the result is less accurate.

  server

Use only statistics from the previous few runs to give an estimate.
This very quick, but the result is not accurate if ...

Note the client type estimate will use tar, using the backup options but
dumping to /dev/null, to make the estimate.  As you note the standard tar
options deal with hard links so the estimate should match the actual size.

jl
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: Newbie help

[Chris Lewis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/02/2015 01:36 PM, Jon LaBadie wrote:
| On Tue, Dec 01, 2015 at 10:28:27PM +, Debra S Baddorf wrote:
|> I agree with Alan’s comment.   You shouldn’t need   - - notaper.
|> (But you CAN use it

Thanks all, I think I understand now.  It's a bit more subtle than
understanding Amanda config (which I don't yet!)

The filesystem to be backed up consists of 9 directories, where almost
every file is hard-linked into the other 8 directories.

[It's daily backups and incrementals, where if the file is unchanged,
it's hard-linked to the other identical copies.]

While df and du both show the backup to be 990Gb, a naive view (not
taking into account hard links) shows it at over 7Tb.  The Amanda size
estimator shows 7Tb (via amstatus), not 990Gb, hence, it's way too big
for my 1.5Tb holding area.  Web searches on the subject seem to
indicate that the Amanda backups _will_ preserve hard links (hence
only backing up 990Gb), so if I let the backup run, it would have
worked (but shoe-shined unacceptably).  On a faster drive, the
shoe-shine wouldn't have mattered, but it would have bleated about not
having enough tapes (even tho it wouldn't use them).

To get around this, I tar'd it to a file (result just over 1TB), which
Amanda was perfectly willing to copy to holding area (albeit not
necessary in this case), and then stream to the drive.  Annoying -
extra steps and extra tar wrapping - would be nice if the estimator
got it right.

I've not dived into the Amanda planner/estimator code, is it possible
for it to take into account hard links?

[If it required coding, potentially it's simple: by making the
assumption that every target of a hard link is going to be backed up
in the same run, so you could divide every file's size by it's link
count.  Otherwise, you have to do the accounting that du/tar/rsync does.
]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWX5xeAAoJENy2YTBCU1ml9aQH/iawzDbRdj4b25lHaCbMJUfw
VIdij1M7omAg/zewEIQVnPG8fM5hEjSTnISLPfQIsDVGDxHpLmR6m3h8OmfSDi93
hnX5vod3kI+kEr+OaF8nGQPDwzIlKEWgdCOyQQ+fT+FDEs70bRuXBy0boBYgXB3V
HRCKx23r4rH4J9iKBZ7AaQWqkjDHnwzfZvPxzIvAA6MGTNPRSXms4A00Vk6oMAZC
1K/+v0taPssuJlDOAP1Qp7FlrJto6hdc4ZbwrLsyqDjsSpowBq4t5ioz7obOiOCf
P1p3sRcQS9SQTyGoLDyA2RXIJaVgnsVaRPle4FxziY9xTSNCJyF7ATkr+jR1MYM=
=SJ4S
-END PGP SIGNATURE-

Newbie help

[Chris Lewis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi,

Running Amanda 3.3.3 on Ubuntu 14.04, with a simple LT04 tape drive.

I've found myself elected as the "tape backup-er" for three different
(and not network connected machines).  The tape drive is on one of the
three (on my machine).

I've made up an amanda profile for each of the three.

Backups are done by replicating the desired data to a large portable
raid array (10Tb), the raid is brought over to my place, I mount it,
and back it up.  Each of the machines has its own 'profile', and own
set of tapes and label convention.  Works fine.

I just got a 4Tb single drive brought over to be dumped under one of
the profiles.  I've mounted it as a new disklist entry under the
corresponding profile.

If I try to dump directly, the drive can't keep up and the tape
shoe-shines.  So, I try to do a "amdump --no-taper " so the
4Tb drive gets dumped onto my holding area (which is 50% larger than
the contents of the drive), to flush it later from the faster holding
area.  This runs for a while and estimates the amount to dump (much
less than the holding area), and then it fails and bleats:

localhost /fisher2 lev 0  FAILED [Skipping: new disk can't be dumped
in degraded mode]

[running amcheck against it is perfectly happy.]

By this I interpret to mean that it simply won't use the taper for
brand new disklist entries.  Right?

Is there a way to trick it?  Like, unmount the disk leaving the
directory, doing a "amdump", then remounting and doing a "amdump
- --no-taper"?  Seems kind of ugly, and I can't see why you can't
"--no-taper" a brand new full dump.

Or do I have to copy the 4Tb drive somewhere faster for this?  Ugh.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWXg6zAAoJENy2YTBCU1mlpkoH/0eEN1AyxdRXiaUy2RcxM6eJ
1bglg/wDZtlv/ftCl+onWKQhuOJmls68l+SUsUBqSeqK5caV2iYQdXa0NHbVj/P9
VrQD9cNT0M/vEZNNk50IYvAlgs4qmg3NqccLyCVNpTszx6uMF411ssGre3Oqqg/P
IhsWz56SiXOqsVuW2WFeCYQ45qdz4mTG3dXGyiiowFuFM4c/3FG9iuayohSVg/w5
0P3DjX0tf6aDJBwcSDZQDZyN1aKRzopU9l0tBO5w7fuRzegValjshso5UCj76so9
xKSwZcj7lroh44QAny9iFNt54CCz2aD43lLB0TkCEUiDo+qMLEmDMZk7Psedemg=
=AYF2
-END PGP SIGNATURE-

Re: Newbie help

[Debra S Baddorf]

I agree with Alan’s comment.   You shouldn’t need   - - notaper.   (But you CAN 
use it
if you want - see below).
Some comments below.
Deb Baddorf

> On Dec 1, 2015, at 3:18 PM, Chris Lewis  wrote:
> 
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hi,
> 
> Running Amanda 3.3.3 on Ubuntu 14.04, with a simple LT04 tape drive.
> 
> I've found myself elected as the "tape backup-er" for three different
> (and not network connected machines).  The tape drive is on one of the
> three (on my machine).
> 
> I've made up an amanda profile for each of the three.
> 
> Backups are done by replicating the desired data to a large portable
> raid array (10Tb), the raid is brought over to my place, I mount it,
> and back it up.  Each of the machines has its own 'profile', and own
> set of tapes and label convention.  Works fine.
> 
> I just got a 4Tb single drive brought over to be dumped under one of
> the profiles.  I've mounted it as a new disklist entry under the
> corresponding profile.
> 
> If I try to dump directly, the drive can't keep up and the tape
> shoe-shines.  So, I try to do a "amdump --no-taper " so the
> 4Tb drive gets dumped onto my holding area (which is 50% larger than
> the contents of the drive), to flush it later from the faster holding
> area.  This runs for a while and estimates the amount to dump (much
> less than the holding area), and then it fails and bleats:
> 
> localhost /fisher2 lev 0  FAILED [Skipping: new disk can't be dumped
> in degraded mode]

So then, why is it trying to use “degraded mode”,   if the holding disk is big 
enough
to fit all of the data?   Check this parameter:

reserve 02 # percent
# This means save only 2% of the holding disk space for degraded
# mode backups. 

I think the default may be 30%.   Or at least,  the value mine was initially 
set for
was 30%.If your new disk takes up more than 70% of the holding disk, there 
would
not be 30% left,  and THAT could be why it is complaining.
 But you don’t care,  so get rid of that default (or original)  value, and 
set it to a value
that YOU want. Mine is the 2% I’ve shown above.

Once you get that value low enough,  you certainly  CAN  use  - - notaper
to force the backup to sit on the holding disk until you are ready to back up 
the rest of
the set.If you like.

See if this fixes it.  So I guess this was just one comment.
Deb Baddorf

> 
> [running amcheck against it is perfectly happy.]
> 
> By this I interpret to mean that it simply won't use the taper for
> brand new disklist entries.  Right?
> 
> Is there a way to trick it?  Like, unmount the disk leaving the
> directory, doing a "amdump", then remounting and doing a "amdump
> - --no-taper"?  Seems kind of ugly, and I can't see why you can't
> "--no-taper" a brand new full dump.
> 
> Or do I have to copy the 4Tb drive somewhere faster for this?  Ugh.
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v2.0.22 (GNU/Linux)
> 
> iQEcBAEBAgAGBQJWXg6zAAoJENy2YTBCU1mlpkoH/0eEN1AyxdRXiaUy2RcxM6eJ
> 1bglg/wDZtlv/ftCl+onWKQhuOJmls68l+SUsUBqSeqK5caV2iYQdXa0NHbVj/P9
> VrQD9cNT0M/vEZNNk50IYvAlgs4qmg3NqccLyCVNpTszx6uMF411ssGre3Oqqg/P
> IhsWz56SiXOqsVuW2WFeCYQ45qdz4mTG3dXGyiiowFuFM4c/3FG9iuayohSVg/w5
> 0P3DjX0tf6aDJBwcSDZQDZyN1aKRzopU9l0tBO5w7fuRzegValjshso5UCj76so9
> xKSwZcj7lroh44QAny9iFNt54CCz2aD43lLB0TkCEUiDo+qMLEmDMZk7Psedemg=
> =AYF2
> -END PGP SIGNATURE-

Re: Newbie help

[Alan Hodgson]

On Tuesday, December 01, 2015 04:18:44 PM you wrote:
> If I try to dump directly, the drive can't keep up and the tape
> shoe-shines.  So, I try to do a "amdump --no-taper " so the
> 4Tb drive gets dumped onto my holding area (which is 50% larger than
> the contents of the drive), to flush it later from the faster holding
> area.

Amanda should always use the holding disk if it's available and big enough and 
not otherwise disabled. You don't need to do a no-taper dump to use the 
holding disk.


signature.asc
Description: This is a digitally signed message part.

Re: Newbie help

[Chris Lewis]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

On 12/01/2015 04:44 PM, Alan Hodgson wrote:
| On Tuesday, December 01, 2015 04:18:44 PM you wrote:
|> If I try to dump directly, the drive can't keep up and the tape
|> shoe-shines.  So, I try to do a "amdump --no-taper " so
|> the 4Tb drive gets dumped onto my holding area (which is 50%
|> larger than the contents of the drive), to flush it later from
|> the faster holding area.
|
| Amanda should always use the holding disk if it's available and big
| enough and not otherwise disabled. You don't need to do a no-taper
| dump to use the holding disk.

You'd think, but, it doesn't seem to want to do it.

Oh, I think I know what's going on.  df shows the disk is at 900Gb,
the holding area 1.5Gb, but the amanda estimator thinks it's 7.5 Tb
(using tar backups).  Hard links.

Maybe this one I have to do with a filesys dump instead of tar.
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)

iQEcBAEBAgAGBQJWXhqeAAoJENy2YTBCU1mlgikIAKUoHD/0KVm7/PHKkjvAGNwn
wUDf9BpFDkLqkA1v62fzZq4BhQ0mTZGu5LTGUSArupo1isWa+jrFRXuHTJk8bmfR
keyGJJOcZxm2I+3In70P2eVLaJ4cedOJaa082vILGJg5jRSedl0E/kzvh3XVkBG/
5blkM8nh9I7/DtXixZ2XcNtqVumiL6wckPCfbeZNxyuNqEFTmv09YfFgcixB7+eR
WcssNsefsv/FXs94trpmb6sBU5xhIhC8l7N/BoFN6tUuiB3Qon3mMr9idH5DAqhb
ubiy1DmBc7nqOBtG2vxtIhJobSL2y1+98oc2CpSoinrPSPMiu/khdnRwDznvuHY=
=zKjN
-END PGP SIGNATURE-

RE: Losing it, need help with amrecover

[Joi L. Ellis]

It sounds like your new empty client is trying to talk to itself instead of 
your amanda server.  You run amrecover on the client, not the server, and the 
client needs to know who the server is.  Also, the server needs to know who the 
client host is, and who the user is running amrecover.

> > > gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote AMRECOVER
> > > Version 3.3.1. Contacting server on localhost ...
> > > NAK: execute access to "/usr/lib/amanda/amindexd" denied

This means the client successfully reached the server, but the server didn't 
want to allow this client to talk to the index service.  It doesn't mean the 
amindexd binary isn't installed on your client--it shouldn't be there on the 
client anyway.  My amanda version is newer than yours and the error message is 
clearer:

NAK: user root from cesonia.pavlovmedia.corp is not allowed to execute the 
service amindexd: Please add the line "cesonia.pavlovmedia.corp root amindexd 
amidxtaped" to /var/backups/.amandahosts on the server

As soon as I fix .amandahosts on the server, I can run amrecover as root on the 
client.  Mine server's .amandahost contains, in part:

cesonia.pavlovmedia.corprootamdump amindexd amidxtaped
cesonia.pavlovmedia.corpbackup  amdump amindexd amidxtaped

(Many sample Amanda configurations I've seen only list amdump in here, not
all three... which is fine for doing backups but then you can't restore.)

Your new empty client needs to have the amanda-client package installed on it, 
not the amanda-server package.  You then need to configure the 
amanda-client.conf file on the new empty client to contain the info needed to 
identify your amanda backup server, the index server, etc.  

On my clients the minimal setup is:

conf"DailySet1"
index_server"Macropus.pavlovmedia.corp"
tape_server "Macropus.pavlovmedia.corp"
auth"bsd"

Macropus is my amanda server.  

If this new empty client is using a new hostname or IP from the dead host, you 
need to update the server's .amandahosts file to identify the name of the new 
empty client or its IP, and the name of the account running Amanda on that 
client (backup in my case because mine are Ubuntu.)

To summarize:
On the amanda server:
  * tweak .amandahosts to allow the new empty client to connect to amandad.

On the new empty client:
  * edit amanda-client.conf to point it at the amanda server
  * if this client is running a firewall, configure it to allow amanda, 
including if-conntrack-amanda if that module is provided for your kernel.

You want to run amrecover as user root, otherwise you won't have the privs 
necessary to restore most of the files under /.  I almost always do this from 
/, because I want to recover just a few files and want them written to the same 
place.  If you don't want to do this, just make a temporary directory in /tmp, 
cd there, and then run amrecover.  The recovered files will be placed in the 
temporary directory and its then up to you to move them where they belong.


> -Original Message-
> From: owner-amanda-us...@amanda.org [mailto:owner-amanda-us...@amanda.org]
> On Behalf Of Gene Heskett
> Sent: Tuesday, October 6, 2015 10:36 AM
> To: amanda-users@amanda.org
> Subject: Re: Losing it, need help with amrecover
> 
> On Tuesday 06 October 2015 09:54:41 Jean-Louis Martineau wrote:
> 
> > On 06/10/15 09:20 AM, Gene Heskett wrote:
> > > Greetings all;
> > >
> > > I have been following the recomendations spit out by amcheck as I am
> > > needing to restore a machine after the machine in that spot failed.
> > >
> > > I am now down to this error, and apparently something in the
> > > installer did setup the amanda-client correctly.
> > >
> > > gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote AMRECOVER
> > > Version 3.3.1. Contacting server on localhost ...
> > > NAK: execute access to "/usr/lib/amanda/amindexd" denied
> >
> > Is it contacting the correct server??? localhost
> >
> > > What are the correct user:group and access rights to this file?
> > >
> > > Better question yet, why does it not exist?
> > >
> > > Because on that machine, with 3.3.1 amanda-client and amanda-common
> > > freshly installed, that file is not there.
> >
> > Because you need amanda-server
> 
> Its now installed on the client (GO704.coyote.den) I am trying to recover.
> 
> > But maybe you need to add '-s coyote -t coyote' to the amrecover
> > command line if 'coyote' is the amanda server.
> 
> > Or you can put them in amanda-client.conf
> 
> On which machine?
> 
> Humm:  Might be a step in the right direction.
> 
> root@GO704:/li

Re: Losing it, need help with amrecover

[Gene Heskett]

On Wednesday 07 October 2015 18:39:27 Joi L. Ellis wrote:

> It sounds like your new empty client is trying to talk to itself
> instead of your amanda server.  You run amrecover on the client, not
> the server, and the client needs to know who the server is.  Also, the
> server needs to know who the client host is, and who the user is
> running amrecover.
>
> > > > gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote AMRECOVER
> > > > Version 3.3.1. Contacting server on localhost ...
> > > > NAK: execute access to "/usr/lib/amanda/amindexd" denied
>
> This means the client successfully reached the server, but the server
> didn't want to allow this client to talk to the index service.  It
> doesn't mean the amindexd binary isn't installed on your client--it
> shouldn't be there on the client anyway.  My amanda version is newer
> than yours and the error message is clearer:
>
> NAK: user root from cesonia.pavlovmedia.corp is not allowed to execute
> the service amindexd: Please add the line "cesonia.pavlovmedia.corp
> root amindexd amidxtaped" to /var/backups/.amandahosts on the server
>
> As soon as I fix .amandahosts on the server, I can run amrecover as
> root on the client.  Mine server's .amandahost contains, in part:
>
> cesonia.pavlovmedia.corprootamdump amindexd amidxtaped
> cesonia.pavlovmedia.corpbackup  amdump amindexd amidxtaped
>
> (Many sample Amanda configurations I've seen only list amdump in here,
> not all three... which is fine for doing backups but then you can't
> restore.)
>
> Your new empty client needs to have the amanda-client package
> installed on it, not the amanda-server package.  You then need to
> configure the amanda-client.conf file on the new empty client to
> contain the info needed to identify your amanda backup server, the
> index server, etc.
>
> On my clients the minimal setup is:
>
>   conf"DailySet1"
>   index_server"Macropus.pavlovmedia.corp"
>   tape_server "Macropus.pavlovmedia.corp"
>   auth"bsd"
>
> Macropus is my amanda server.
>
> If this new empty client is using a new hostname or IP from the dead
> host, you need to update the server's .amandahosts file to identify
> the name of the new empty client or its IP, and the name of the
> account running Amanda on that client (backup in my case because mine
> are Ubuntu.)
>
> To summarize:
> On the amanda server:
>   * tweak .amandahosts to allow the new empty client to connect to
> amandad.
>
> On the new empty client:
>   * edit amanda-client.conf to point it at the amanda server
>   * if this client is running a firewall, configure it to allow
> amanda, including if-conntrack-amanda if that module is provided for
> your kernel.
>
> You want to run amrecover as user root, otherwise you won't have the
> privs necessary to restore most of the files under /.  I almost always
> do this from /, because I want to recover just a few files and want
> them written to the same place.  If you don't want to do this, just
> make a temporary directory in /tmp, cd there, and then run amrecover. 
> The recovered files will be placed in the temporary directory and its
> then up to you to move them where they belong.
>
> > -Original Message-
> > From: owner-amanda-us...@amanda.org
> > [mailto:owner-amanda-us...@amanda.org] On Behalf Of Gene Heskett
> > Sent: Tuesday, October 6, 2015 10:36 AM
> > To: amanda-users@amanda.org
> > Subject: Re: Losing it, need help with amrecover
> >
> > On Tuesday 06 October 2015 09:54:41 Jean-Louis Martineau wrote:
> > > On 06/10/15 09:20 AM, Gene Heskett wrote:
> > > > Greetings all;
> > > >
> > > > I have been following the recomendations spit out by amcheck as
> > > > I am needing to restore a machine after the machine in that spot
> > > > failed.
> > > >
> > > > I am now down to this error, and apparently something in the
> > > > installer did setup the amanda-client correctly.
> > > >
> > > > gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote AMRECOVER
> > > > Version 3.3.1. Contacting server on localhost ...
> > > > NAK: execute access to "/usr/lib/amanda/amindexd" denied
> > >
> > > Is it contacting the correct server??? localhost
> > >
> > > > What are the correct user:group and access rights to this file?
> > > >
> > > > Better question yet, why does it not exist?
> > > >
> > > > Because on that machine, with 3.3.1 amanda-client and
> > >

RE: Losing it, need help with amrecover

[Joi L. Ellis]

[snip]

> 
> Which is sort of what I did Joi.
> 
> amrecover bothers me because that is no apparent way to strip the leading
> part of the path from what you want to recover, and from the messages it
> presents, if you don't just give up and use a scratch directory, then move
> what it recovers, I am sure not about to let it destroy everything in my
> home dir just to recover the linuxcnc subdir.  It may be capable of doing
> that, but the "are you sure" messages just warn that the /home/gene
> directory will be nuked.
> 

What backup method is your DLE using?  Gnutar strips the leading / off 
automatically when you extract from a tarball, so it won't just overwrite your 
real stuff automatically.  The only way it will overwrite original anything is 
if you're sitting in / when you run amrecover.  

You don't have to recover a whole tree of stuff to test, just select one 
unimportant file, and see where it writes it.

If you tell amrecover you only want the linuxcnc directory, that is all it will 
extract, it won't touch anything else.

It doesn't delete the target directory and then restore into it, if that's what 
you're thinking... it will just overwrite the current file(s) in that target 
with what you extract from the backup, if the paths are exact matches.

> Thanks Joi.
> 
> Cheers, Gene Heskett
> --
> "There are four boxes to be used in defense of liberty:
>  soap, ballot, jury, and ammo. Please use in that order."
> -Ed Howdershelt (Author)
> Genes Web page 

Re: Losing it, need help with amrecover

[Jon LaBadie]

On Thu, Oct 08, 2015 at 12:04:34AM +, Joi L. Ellis wrote:
> 
> 
> [snip]
> 
> > 
> > Which is sort of what I did Joi.
> > 
> > amrecover bothers me because that is no apparent way to strip the leading
> > part of the path from what you want to recover, and from the messages it
> > presents, if you don't just give up and use a scratch directory, then move
> > what it recovers, I am sure not about to let it destroy everything in my
> > home dir just to recover the linuxcnc subdir.  It may be capable of doing
> > that, but the "are you sure" messages just warn that the /home/gene
> > directory will be nuked.
> > 
> 
> What backup method is your DLE using?  Gnutar strips the leading / off
> automatically when you extract from a tarball, so it won't just overwrite
> your real stuff automatically.  The only way it will overwrite original
> anything is if you're sitting in / when you run amrecover.  
> 
Joi,
In this case "/" is the "root" of the DLE, not the file system.  Gene's
DLE is of /home.  So if he were to recover his home directory "gene"
while sitting in the file system root, I think it would make "/gene"
as a new directory rather than overwriting "/home/gene".

jl
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (703) 935-6720 (C)

Re: Losing it, need help with amrecover

[Gene Heskett]

On Wednesday 07 October 2015 20:04:34 Joi L. Ellis wrote:

> [snip]
>
> > Which is sort of what I did Joi.
> >
> > amrecover bothers me because that is no apparent way to strip the
> > leading part of the path from what you want to recover, and from the
> > messages it presents, if you don't just give up and use a scratch
> > directory, then move what it recovers, I am sure not about to let it
> > destroy everything in my home dir just to recover the linuxcnc
> > subdir.  It may be capable of doing that, but the "are you sure"
> > messages just warn that the /home/gene directory will be nuked.
>
> What backup method is your DLE using?  Gnutar strips the leading / off
> automatically when you extract from a tarball, so it won't just
> overwrite your real stuff automatically.  The only way it will
> overwrite original anything is if you're sitting in / when you run
> amrecover.
>
> You don't have to recover a whole tree of stuff to test, just select
> one unimportant file, and see where it writes it.
>
> If you tell amrecover you only want the linuxcnc directory, that is
> all it will extract, it won't touch anything else.
>
> It doesn't delete the target directory and then restore into it, if
> that's what you're thinking... it will just overwrite the current
> file(s) in that target with what you extract from the backup, if the
> paths are exact matches.
>
The are you sure messages says otherwise. I thought I was doing good when 
I extracted the contents of the linuxcnc directory while locally cd'd 
to /home/gene/linuxcnc (which I had to create) but when the extraction 
was finished, I had a sybdir tree of

/home/gene/linuxcnc/gene/linuxcnc/*

So I just mv'd them to where they belonged, nuking empty dirs as they 
emptied out.

So it all worked out.  This was with deb of what I believe is 3.3.1p1 on 
the clients, 3 of them, and a locally built 3.3.7p1 on this server.  The 
last several times I tried to build a 4.something was a disaster, so I 
got out of the "canary in the coal mine" business when my comments about 
the failures were ignored.

I don't mind bleeding a little when the bleeding is stopped by the next 
tarball download & build.  But that hasn't happened for about 2 years 
now.

Thanks Joi.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Losing it, need help with amrecover

[Gene Heskett]

On Tuesday 06 October 2015 09:54:41 Jean-Louis Martineau wrote:

> On 06/10/15 09:20 AM, Gene Heskett wrote:
> > Greetings all;
> >
> > I have been following the recomendations spit out by amcheck as I am
> > needing to restore a machine after the machine in that spot failed.
> >
> > I am now down to this error, and apparently something in the
> > installer did setup the amanda-client correctly.
> >
> > gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote
> > AMRECOVER Version 3.3.1. Contacting server on localhost ...
> > NAK: execute access to "/usr/lib/amanda/amindexd" denied
>
> Is it contacting the correct server??? localhost
>
> > What are the correct user:group and access rights to this file?
> >
> > Better question yet, why does it not exist?
> >
> > Because on that machine, with 3.3.1 amanda-client and amanda-common
> > freshly installed, that file is not there.
>
> Because you need amanda-server

Its now installed on the client (GO704.coyote.den) I am trying to 
recover.

> But maybe you need to add '-s coyote -t coyote' to the amrecover
> command line if 'coyote' is the amanda server.

> Or you can put them in amanda-client.conf

On which machine?

Humm:  Might be a step in the right direction.

root@GO704:/lib/firmware/hm2# su amanda -c "amrecover -C Daily -s 
coyote -t coyote"
No passwd entry for user 'amanda'

At least on that machine.

Next?

I also tried by using backup as the user since that is in passwd here:

root@GO704:/lib/firmware/hm2# su backup -c "amrecover -C Daily -s 
coyote -t coyote"
X11 connection rejected because of wrong authentication.
sh: 1: amrecover: not found

I also tried running it on this machine to write on that one from here, 
but there isn't an obvious way to change the / that an lpwd displays.  
Obviously extracting to there "/" would destroy this machine.

Thanks Jean-Louis.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page 

Re: Losing it, need help with amrecover

[Jean-Louis Martineau]

On 06/10/15 09:20 AM, Gene Heskett wrote:

Greetings all;

I have been following the recomendations spit out by amcheck as I am
needing to restore a machine after the machine in that spot failed.

I am now down to this error, and apparently something in the installer
did setup the amanda-client correctly.

gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote
AMRECOVER Version 3.3.1. Contacting server on localhost ...
NAK: execute access to "/usr/lib/amanda/amindexd" denied

Is it contacting the correct server??? localhost



What are the correct user:group and access rights to this file?

Better question yet, why does it not exist?

Because on that machine, with 3.3.1 amanda-client and amanda-common
freshly installed, that file is not there.


Because you need amanda-server

But maybe you need to add '-s coyote -t coyote' to the amrecover command 
line if 'coyote' is the amanda server.

Or you can put them in amanda-client.conf

Jean-Louis

Losing it, need help with amrecover

[Gene Heskett]

Greetings all;

I have been following the recomendations spit out by amcheck as I am 
needing to restore a machine after the machine in that spot failed.

I am now down to this error, and apparently something in the installer 
did setup the amanda-client correctly.

gene@GO704:/etc$ sudo  amrecover -C Daily -h coyote
AMRECOVER Version 3.3.1. Contacting server on localhost ...
NAK: execute access to "/usr/lib/amanda/amindexd" denied

What are the correct user:group and access rights to this file?

Better question yet, why does it not exist?

Because on that machine, with 3.3.1 amanda-client and amanda-common 
freshly installed, that file is not there.

Slowly running out of hair folks.

Thanks for any help.

Cheers, Gene Heskett
-- 
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>

I need help!

[Alexander Geronymakis]

  Thank you all so much for your lightning-fast responses, your 
examples and comments have helped me a great deal and I have been able 
to move own  with my configuration.I have also done my homework and I 
think I wont bother you anymore with such trivial questions.

Fwd: I need help!

[Alexander Geronymakis]

 Original-Nachricht 
Betreff:I need help!
Datum:  Wed, 31 Jul 2013 18:39:46 +0200
Von:Alexander Geronymakis a.geronyma...@portunity.de
An: amanda-users-requ...@amanda.org



Hi,
I'm new to IT , I' m currently doing my internship in a firm in
germany.I was recently asked to make a research on backup software and
we all agreed on trying amanda community version as a best solution.So
after I had succesfully  installed and tested the server, I'm currently
having troubles setting up the clients.More specific ,I have 4 virtual
machines running debian6-64bit  under a centOS host, 3 as clients and
one as server.My question is how to setup exactly the dumptype  in the
disklist configuration file.I mean what are the options/choices/format?
amcheck is giving me errors for it and I could't find any helpful infos
on the internet.Moreover, is amcheck supposed only to run on the
server?because ,no matter how I tried on the clients I always get the
same error: amcheck: command not found . I have double-checked
dependencies,various procedures etc. and everything seems to be in
order.The version I installed is the latest stable release 3.3.4. I know
my questions might sound very noob to you,but hey, I'm new to this.I
would be sooo happy if somenone could help me figure that out.

Fwd: I need help!

[Alexander Geronymakis]

 Original-Nachricht 
Betreff:I need help!
Datum:  Thu, 01 Aug 2013 13:47:30 +0200
Von:Alexander Geronymakis a.geronyma...@portunity.de
An: amanda-users-requ...@amanda.org



 Thank you so much for the quick response,now my only obstacle left ,is
how to set the dumptype up.I've already tried to figure that out with
the man pages,but I ended up being even more confused.All I need is a
list of some sort that will show me exactly the options and formats to
configure the dumptype in the disklist and perhaps also in the amanda.conf . my 
current settings are
`simple-gnutar-global' which of course is wrong.I need to set the server to 
communicate with the clients through
ssh and not use compression for the meantime .A good example of an actual 
disklist configuration would also
do the trick for me.

Re: I need help!

[Markus Iturriaga Woelfel]

Alexander - You need to define your dumptypes in your amanda.conf file (or 
another file included in that). You can then refer to them in your disklist. 
Your best source for information should be the amanda.conf manual page. This is 
also where you can learn about the other features of the amanda.conf file such 
as inheritance. 

You may only need one dump type for a very basic setup or you may want to set 
up something more complex. You may also want to look at the manual page for 
amgtar, amanda's interface with tar. Here is an example from our amanda 
configuration:

First I set up the options for amgtar:

define application-tool app_amgtar {
plugin amgtar
property ATIME-PRESERVE NO
property ONE-FILE-SYSTEM NO
property SPARSE YES
property ACLS YES
property SELINUX NO
property XATTRS YES
property CHECK-DEVICE NO
property append IGNORE : value .* out of time_t range
property append NORMAL : file changed as we read it
property append NORMAL : Exiting with failure status due to previous 
errors
}

This tells amgtar what flags to use for tar and what kind of messages to ignore 
or consider normal. I have a few other application-tool definitions as well.

Next, I have a global dump type template that sets options I want to include in 
all my other dump types:

define dumptype global {
index yes
strategy standard
ssh_keys /etc/amanda/eecs/ssh-key
}

Since I use SSH as the transport mechanism for Amanda, I want to define the key 
to use in all dumptypes.

I can then inherit this in a specific dump type:

define dumptype amgtar-nolvm {
global
auth ssh
comment Backup using amgtar with best server-side compression
compress server custom
server_custom_compress /usr/bin/pigz
program APPLICATION
application app_amgtar
}

As you can see, I include the global definition, tell it to use a custom 
compress program (pigz, a multi-threaded version of gzip which gives me a nice 
speed boost on this 8-core server). I then tell it that I want to use the 
application tool app_amgtar (which I defined earlier) as the backup program. 

I now have a dumptype I can use in my disk list, for example:

#Host DiskDumptype  
  Spindle Network
abzu.eecs.utk.edu /etcamgtar-nolvm  
  2   main

My example may be more or less complex than what you need in your setup. I hope 
that gets you started.

Grüße nach Deutschland,

Markus
On Aug 1, 2013, at 6:38 AM, Alexander Geronymakis a.geronyma...@portunity.de 
wrote:

 
 
 
  Original-Nachricht 
 Betreff:  I need help!
 Datum:Wed, 31 Jul 2013 18:39:46 +0200
 Von:  Alexander Geronymakis a.geronyma...@portunity.de
 An:   amanda-users-requ...@amanda.org
 
 Hi,
 I'm new to IT , I' m currently doing my internship in a firm in 
 germany.I was recently asked to make a research on backup software and 
 we all agreed on trying amanda community version as a best solution.So 
 after I had succesfully  installed and tested the server, I'm currently 
 having troubles setting up the clients.More specific ,I have 4 virtual 
 machines running debian6-64bit  under a centOS host, 3 as clients and 
 one as server.My question is how to setup exactly the dumptype  in the 
 disklist configuration file.I mean what are the options/choices/format? 
 amcheck is giving me errors for it and I could't find any helpful infos 
 on the internet.Moreover, is amcheck supposed only to run on the 
 server?because ,no matter how I tried on the clients I always get the 
 same error: amcheck: command not found . I have double-checked 
 dependencies,various procedures etc. and everything seems to be in 
 order.The version I installed is the latest stable release 3.3.4. I know 
 my questions might sound very noob to you,but hey, I'm new to this.I 
 would be sooo happy if somenone could help me figure that out.
 
 
 

---
Markus A. Iturriaga Woelfel, IT Administrator
Department of Electrical Engineering and Computer Science
University of Tennessee
Min H. Kao Building, Suite 424 / 1520 Middle Drive
Knoxville, TN 37996-2250
mitur...@eecs.utk.edu / (865) 974-3837
http://twitter.com/UTKEECSIT

Re: I need help!

[Debra S Baddorf]

Great examples here for you.  I'll make some comments about the parts we DON'T 
use,  in case you don't need them either.

On Aug 1, 2013, at 9:03 AM, Markus Iturriaga Woelfel mitur...@eecs.utk.edu
 wrote:

 Alexander - You need to define your dumptypes in your amanda.conf file (or 
 another file included in that). You can then refer to them in your 
 disklist. Your best source for information should be the amanda.conf manual 
 page. This is also where you can learn about the other features of the 
 amanda.conf file such as inheritance. 
 
 You may only need one dump type for a very basic setup or you may want to set 
 up something more complex. You may also want to look at the manual page for 
 amgtar, amanda's interface with tar. Here is an example from our amanda 
 configuration:
 
 First I set up the options for amgtar:
 
 define application-tool app_amgtar {
plugin amgtar
property ATIME-PRESERVE NO
property ONE-FILE-SYSTEM NO
property SPARSE YES
property ACLS YES
property SELINUX NO
property XATTRS YES
property CHECK-DEVICE NO
property append IGNORE : value .* out of time_t range
property append NORMAL : file changed as we read it
property append NORMAL : Exiting with failure status due to previous 
 errors
 }
 

You may not need amgtar at all,  if regular tar is sufficient for you.
I use amgtar only in SOME cases,  and I only bother with the last three lines, 
so that
I get less printed in my error outputs.



 This tells amgtar what flags to use for tar and what kind of messages to 
 ignore or consider normal. I have a few other application-tool definitions 
 as well.
 
 Next, I have a global dump type template that sets options I want to include 
 in all my other dump types:
 
 define dumptype global {
index yes
strategy standard
ssh_keys /etc/amanda/eecs/ssh-key
 }
 
 Since I use SSH as the transport mechanism for Amanda, I want to define the 
 key to use in all dumptypes.
 
 I can then inherit this in a specific dump type:
 
 define dumptype amgtar-nolvm {
global
auth ssh
comment Backup using amgtar with best server-side compression
compress server custom
server_custom_compress /usr/bin/pigz
program APPLICATION
application app_amgtar
 }

You might be able to drop the last two lines and just use
  program GNUTAR
if gnu tar works for you.   It's easier to start with just plain tar, perhaps.
I personally change global into something that tells me it isn't a keyword:
I use   MYglobalor something like that,  to indicate that it's a name.


 
 As you can see, I include the global definition, tell it to use a custom 
 compress program (pigz, a multi-threaded version of gzip which gives me a 
 nice speed boost on this 8-core server). I then tell it that I want to use 
 the application tool app_amgtar (which I defined earlier) as the backup 
 program. 
 
 I now have a dumptype I can use in my disk list, for example:
 
 #Host DiskDumptype
 Spindle Network
 abzu.eecs.utk.edu /etcamgtar-nolvm
 2   main


The last two bits might not be necessary either -- I don't use them.   Just
hostname  diskdumptype
myhost.where.ok  /etc MYtar

for example.

Deb Baddorf



 
 My example may be more or less complex than what you need in your setup. I 
 hope that gets you started.
 
 Grüße nach Deutschland,
 
 Markus
 On Aug 1, 2013, at 6:38 AM, Alexander Geronymakis 
 a.geronyma...@portunity.de wrote:
 
 
 
 
  Original-Nachricht 
 Betreff: I need help!
 Datum:   Wed, 31 Jul 2013 18:39:46 +0200
 Von: Alexander Geronymakis a.geronyma...@portunity.de
 An:  amanda-users-requ...@amanda.org
 
 Hi,
 I'm new to IT , I' m currently doing my internship in a firm in 
 germany.I was recently asked to make a research on backup software and 
 we all agreed on trying amanda community version as a best solution.So 
 after I had succesfully  installed and tested the server, I'm currently 
 having troubles setting up the clients.More specific ,I have 4 virtual 
 machines running debian6-64bit  under a centOS host, 3 as clients and 
 one as server.My question is how to setup exactly the dumptype  in the 
 disklist configuration file.I mean what are the options/choices/format? 
 amcheck is giving me errors for it and I could't find any helpful infos 
 on the internet.Moreover, is amcheck supposed only to run on the 
 server?because ,no matter how I tried on the clients I always get the 
 same error: amcheck: command not found . I have double-checked 
 dependencies,various procedures etc. and everything seems to be in 
 order.The version I installed is the latest stable release 3.3.4. I know 
 my questions might sound very noob to you,but hey, I'm new to this.I 
 would be sooo happy if somenone could help me figure that out.
 
 
 
 
 ---
 Markus A. Iturriaga Woelfel

[Amanda-users] Help with a custom LVM snapshot script

[neal lawson]

here is what i have so far, but i welcome any suggestions or help..

https://github.com/neallawson/Amanda-LVM-snapshot

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

Re: [Amanda-users] Help with a custom LVM snapshot script

[Jon LaBadie]

On Fri, Feb 08, 2013 at 11:30:45AM -0800, neal lawson wrote:
 here is what i have so far, but i welcome any suggestions or help..
 
 https://github.com/neallawson/Amanda-LVM-snapshot
 
Glad to see someone working on this important piece.

I question if ruby is a good choice of languages as none of
the rest of the amanda code uses it.  Users would have an
additional requirement of installing ruby support and the
code maintainers would have to be conversant in another
language.

jl
-- 
Jon H. LaBadie j...@jgcomp.com
 11226 South Shore Rd.  (703) 787-0688 (H)
 Reston, VA  20190  (609) 477-8330 (C)

[Amanda-users] Help with a custom LVM snapshot script

[neal lawson]

i chose ruby since its a stable modern language i know, and most linux 
distributions already ship with 1.8.7

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

[Amanda-users] Help with a custom LVM snapshot script

[neal lawson]

i chose ruby since its a stable modern language i know, and most linux 
distributions already ship with 1.8.7, further more Amanda should be agnostic 
to the language that the helper scripts use. If Amanda requires i use perl, it 
might be time to find another backup solution.

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

Re: [Amanda-users] Help with a custom LVM snapshot script

[Markus Iturriaga Woelfel]

On Feb 8, 2013, at 5:21 PM, neal lawson amanda-for...@backupcentral.com wrote:

 i chose ruby since its a stable modern language i know, and most linux 
 distributions already ship with 1.8.7, further more Amanda should be agnostic 
 to the language that the helper scripts use. If Amanda requires i use perl, 
 it might be time to find another backup solution.



Amanda is certainly agnostic as far as helper scripts/Applications are 
concerned. The only advantage to using Perl would be that you can use the 
included Amanda API, avoiding re-coding some functions and having an easier 
interaction with the rest of the amanda system. If that's not an issue, then 
Ruby should do fine. 

 Markus Iturriaga Woelfel, it seems the repo you referenced no longer exists, 
 Markus Iturriaga Woelfel


https://github.com/marxarelli/amlvm-snapshot still works for me. 

I'm all for a ground-up rewrite of the LVM script though. I don't know if I can 
contribute much in Ruby, but I'd be interested in seeing design decisions 
discussed. I don't know if this is the right forum - depends on the Amanda.org 
folks, I guess. I wrote the snapshot scripts we use for BackupPC (which we also 
use for backups) in Perl, so I have some experience writing scripts that 
interact with LVM. I can't promise they're elegant though. I've never made them 
publicly available mostly because they are hacks, but they do work. :)

Markus

---
Markus A. Iturriaga Woelfel, IT Administrator
Department of Electrical Engineering and Computer Science
University of Tennessee
Min H. Kao Building, Suite 424 / 1520 Middle Drive
Knoxville, TN 37996-2250
mitur...@eecs.utk.edu / (865) 974-3837
http://twitter.com/UTKEECSIT

Re: [Amanda-users] Help with a custom LVM snapshot script

[Bob Vickers]

On Thu, 31 Jan 2013, Stefan G. Weichinger wrote:


I would also like to see improved scripts, I have the issue at one
client that the LVM-snapshots aren't correctly removed sometimes ...
that leads to non-working backups and dozens of lurking snapshots ...



I had a lot of problems with LVM snapshots that would not go away, so I 
wrote a script deleteLV that repeatedly waits a little while then tries 
again. This has worked fine, though i have a suspicion that SuSE fixed the 
bug I was working round at exactly the same time as I installed my script!


The script deleteLV is appended to this message in case anyone finds it 
useful.


Bob Vickers

#! /bin/bash

# Delete an LVM logical volume (typically used for a snapshot that won't go
# away). See 
# https://bugzilla.novell.com/show_bug.cgi?id=642296

# Author: Bob Vickers, Royal Holloway University of london

set -o nounset
export PATH=/sbin:/usr/sbin:/bin:/usr/bin

usage=\
 deleteLV  [-n maxTries] [-t timetowait] LVdevice...
-n max number of tries (default 10)
-t time to wait after sync (default 10 seconds)

#
#   Parse the command options
declare -i maxtries=10 delay=10
ERRFLAG=OK
OPTIND=1
while getopts n:t: OPTION
do
case $OPTION in
n)  maxtries=$OPTARG;;
t)  delay=$OPTARG;;
\?) ERRFLAG=BAD;;
esac
done
shift `expr $OPTIND - 1`
#
# Exit with a usage message if the syntax is wrong.
#
if [ $ERRFLAG != OK -o $# -eq 0 ]
then
echo 21 $0: usage:
echo 21 $usage
exit 1
fi

declare -i ntries

for lv in $@
do
if lvs $lv /dev/null
then
# We have a valid LVM logical volume, so repeatedly try to delete it.
ntries=0
while (( $ntries  $maxtries ))
do
ntries=$(( $ntries + 1 ))
echo 2 $0: Removing $lv attempt $ntries
udevadm settle
sync
sleep $delay
lvremove -f $lv  break
done
if lvs $lv /dev/null 2/dev/null
then
echo 2  $0: FAILED to remove $lv after $ntries attempts
else
echo 2  $0: Successfully removed $lv after $ntries attempt(s)
fi
else
 echo 2  $0: $lv is not an LVM logical volume
fi
done

Re: [Amanda-users] Help with a custom LVM snapshot script

[Stefan G. Weichinger]

Am 2013-02-01 10:56, schrieb Bob Vickers:
 On Thu, 31 Jan 2013, Stefan G. Weichinger wrote:

 I would also like to see improved scripts, I have the issue at one
 client that the LVM-snapshots aren't correctly removed sometimes ...
 that leads to non-working backups and dozens of lurking snapshots ...

 
 I had a lot of problems with LVM snapshots that would not go away, so I
 wrote a script deleteLV that repeatedly waits a little while then tries
 again. This has worked fine, though i have a suspicion that SuSE fixed
 the bug I was working round at exactly the same time as I installed my
 script!
 
 The script deleteLV is appended to this message in case anyone finds it
 useful.

Thanks for sharing, Bob!

I saw these issues with Gentoo Linux as well, so it might not be
Suse-specific. The server in question has recently been upgraded to a
more recent kernel and newer lvm2-userspace tools, I haven't seen the
non-deleted LV-snapshots since then.

I will take a look at your script and how I could fit it into my scheme,
at first glance I think I have to figure out how to select the snapshot
as it changes name every day. But that shouldn't be that hard ;-)

Thanks, Stefan

Re: [Amanda-users] Help with a custom LVM snapshot script

[Stefan G. Weichinger]

Am 28.01.2013 17:48, schrieb Markus Iturriaga Woelfel:

 I would, however, be interested in seeing an
 effort to rewrite this from the ground up as there are certainly a
 lot of things that could be improved/fixed.

I would also like to see improved scripts, I have the issue at one
client that the LVM-snapshots aren't correctly removed sometimes ...
that leads to non-working backups and dozens of lurking snapshots ...

Stefan

Re: [Amanda-users] Help with a custom LVM snapshot script

[Jean-Louis Martineau]

On 01/26/2013 01:33 PM, neal lawson wrote:

I've been working on a custom LVM snapshot script, I have the bulk of the 
script working, but i'm not sure how to message amanand to change the backup 
location to the snapshot location. and thoughts would be helpful.

The script must print the directory property on stdout:
PROPERTY directory /path/to/mount-point


(FYI: i did try the existing scripts that can be found on the internet, but 
they seem to be abandoned, and longer functional).

I would prefer if you can enhance that script instead of writing a new one.

Jean-Louis

[Amanda-users] Help with a custom LVM snapshot script

[neal lawson]

Markus Iturriaga Woelfel, it seems the repo you referenced no longer exists, 
Markus Iturriaga Woelfel

Jean-Louis Martineau, the current scripts seem to be a bit of a disaster, and i 
did try to fix them, currently i do have a ruby based script that is 99% there 
i'm just missing the last bit to get amgtar to backup the new location.

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

[Amanda-users] Help with a custom LVM snapshot script

[neal lawson]

so the correct link to the repo is https://github.com/marxarelli/amlvm-snapshot 
 the one posted had a trailing ., there are sever versions of this on github, 
this project seems to be abandoned as it was last updated over 2 years go

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

Re: [Amanda-users] Help with a custom LVM snapshot script

[Markus Iturriaga Woelfel]

On Jan 28, 2013, at 11:23 AM, neal lawson amanda-for...@backupcentral.com 
wrote:

 so the correct link to the repo is 
 https://github.com/marxarelli/amlvm-snapshot  the one posted had a trailing 
 ., there are sever versions of this on github, this project seems to be 
 abandoned as it was last updated over 2 years go


Sorry, I think that was me ending a sentence out of sheer automatism. We 
patched the script to work with CentOS/RedHat 6, our main Linux distribution, 
and it works fine if what you're backing up is the entire logical volume. If 
you're only backing up a subdirectory, there may be problems. I would, however, 
be interested in seeing an effort to rewrite this from the ground up as there 
are certainly a lot of things that could be improved/fixed. We also wound up 
also creating our own amanda RPMs since the ones distributed by ZManda place 
files in /usr/local which conflicts with the way we manage our systems. 
However, it all seems to work together well. I back up 103 DLEs using the 
amlvm-snapshot script.

Markus
---
Markus A. Iturriaga Woelfel, IT Administrator
Department of Electrical Engineering and Computer Science
University of Tennessee
Min H. Kao Building, Suite 424 / 1520 Middle Drive
Knoxville, TN 37996-2250
mitur...@eecs.utk.edu / (865) 974-3837
http://twitter.com/UTKEECSIT

Re: [Amanda-users] Help in installing Amanda Client in FreeBSD 8.0/9.0

[Olivier Nicole]

Jose,

 Im new to Amanda. I have installed Amanda Server on a CentOS but on
 trying to install it on the FreeBSD clients I have I am experiencing
 hitches. Any help you can accord will be highly appreciated.

I am not sure what are your problem sin installing amanda client on
FreeBSD.

Go to /usr/ports/misc/amanda-client
make
make install

That should do it.

Else you ned to be specific on the type of propblems you are facing.

Best regards,

Olivier

Re: help with moving client between servers

[Brian Cuttler]

Amanda users,

I recalled the magic.

I had multiple DLE defined in the disklist, one with the 'correct'
dumptype and the rest not. I thought I could invoke # amcheck on
the single DLE to verify the config, this is NOT the case, the other
DLE for the same host with different/competing dumptypes causing
the problem.

When I commented out the other DLE and corrected amanda.conf auto
to be bsd (not bsdtcp) # amcheck ran correctly.

I will not update the DLE in the disklist, remove comment field and
update dumptype.

thank you,

Brian


On Fri, Jun 29, 2012 at 09:53:47AM -0400, Brian Cuttler wrote:
 
 Amanda Users,
 
 I've been successfully backing up amanda client on Suse with
 amanda server on Suse, but want to migrate the client to another
 amanda server that is a newer version.
 
 I have (attempted) to follow the article
 
 http://forums.zmands.com/archive/index.php/t-423.html
 which is an article that gives the error I am receiving.
 
 I am clearly missing something obvious, and I'm asking you 
 to look over what I did and tell me what dumb thing I'm doing.
 
 Thanks in advance,  Brian
 
 
 Client is: amanda 2.5.2.1-46 on openSUSE 10.3 (X86-64)
 
 New Server is: Amanda 3.3.0 on openSUSE 12.1 (x86_64)
 
 I've configured a DLE this way, please don't put too much emphisis
 on the dumptype's name, that is easilly fixed.
 
 From disklist
 radha  /usr12/andaman/usr1 user-tar-bsdtcp
 
 
 From amanda.conf
 define dumptype user-tar-bsdtcp {
 root-tar
 index
 comment user partitions dumped with tar
 auth bsdtcp
 compress client fast
 priority medium
 }
 
 And updated /etc/xinetd.d/amanda on the Client to read
 
 # default: off
 # description: Amanda backup client
 #
 service amanda 
 {
 socket_type = stream
 protocol= tcp
 wait= no
 user= amanda
 group   = disk
 server  = /usr/lib/amanda/amandad -auth=bsdtcp
 #   disable = yes
 disable = no
 }
 
 I think I've hit every possible combination of bsd and bsdtcp
 on both the client and server end, remembering to restart xinetd on
 the client each time, but it continues to fail.
 
 Amanda Backup Client Hosts Check
 
 WARNING: radha: selfcheck request failed: tcpm_recv_token: invalid size: 
 chown(/tmp/amanda/amandad/amandad.20120629095135.debug, 110, 110) failed. 
 Operation not permitted
 Client check: 1 host checked in 0.095 seconds.  1 problem found.
 
 (brought to you by Amanda 3.3.0)
 
 
 ---
Brian R Cuttler brian.cutt...@wadsworth.org
Computer Systems Support(v) 518 486-1697
Wadsworth Center(f) 518 473-6384
NYS Department of HealthHelp Desk 518 473-0773
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

Recovery Help Request

[Greg Copeland]

I have a client who needs to recover a file. I'm using amrecover. I add
the file needed for recovery. I then type, extract. I then get the
following.

Extracting files using tape drive tape:/dev/nst0 on host
backup.chapal.com.
Load tape weekly-00 now
Continue [?/Y/n/s/d]? Y
amrecover - amidxtaped closed the connection
amrecover - can't talk to tape server: (null)
amrecover Write failed: Broken pipe

Syslogs show:
Apr 13 12:06:42 backup amidxtaped[8523]: TypeError in method 'debug',
argument 1 of type 'char *'

I'm rather pressed for time on this so any solutions would be most
appreciated. Even if I need to use a different recovery tool
(amrestore).

Help,

-- 
Greg Copeland g...@copelandconsulting.net
Copeland Computer Consulting

Re: Recovery Help Request

[Marcus Pless]

Have you tried amfetchdump? In the near-worst case scenario
you can use the log file to help you locate the file on tape,
extract the file to disk using dd, and then manually process
things.


On 04/13/2012 10:30:55 AM, Greg Copeland wrote:
I have a client who needs to recover a file. I'm using amrecover. I  
add

the file needed for recovery. I then type, extract. I then get the
following.

Extracting files using tape drive tape:/dev/nst0 on host
backup.chapal.com.
Load tape weekly-00 now
Continue [?/Y/n/s/d]? Y
amrecover - amidxtaped closed the connection
amrecover - can't talk to tape server: (null)
amrecover Write failed: Broken pipe

Syslogs show:
Apr 13 12:06:42 backup amidxtaped[8523]: TypeError in method 'debug',
argument 1 of type 'char *'

I'm rather pressed for time on this so any solutions would be most
appreciated. Even if I need to use a different recovery tool
(amrestore).

Help,

--
Greg Copeland g...@copelandconsulting.net
Copeland Computer Consulting

Re: Recovery Help Request

[Steven Backus]

A quick google came up with two solutions:

http://forums.zmanda.com/showthread.php?3691-amrecover-segmentation-fault
http://www.mail-archive.com/amanda-users@amanda.org/msg46079.html

I'll offer my own, upgrade to the latest version (3.3.1) and see if
that helps.

Steve
-- 
Steven J. BackusComputer Specialist
University of Utah  E-Mail:  steven.bac...@utah.edu
Genetic EpidemiologyAlternate:  bac...@math.utah.edu
391 Chipeta Way -- Suite D  Office:  801.587.9308
Salt Lake City, UT 84108-1266   http://www.math.utah.edu/~backus

Re: Recovery Help Request

[Greg Copeland]

On Fri, 2012-04-13 at 12:01 -0600, Steven Backus wrote:

 A quick google came up with two solutions:
 
 http://forums.zmanda.com/showthread.php?3691-amrecover-segmentation-fault
 http://www.mail-archive.com/amanda-users@amanda.org/msg46079.html
 
 I'll offer my own, upgrade to the latest version (3.3.1) and see if
 that helps.
 
 Steve


Thanks. I'll check those out.

FYI, this is Amanda 3.3.1.


-- 
Greg Copeland g...@copelandconsulting.net
Copeland Computer Consulting

Re: Recovery Help Request

[Greg Copeland]

On Fri, 2012-04-13 at 11:19 -0700, Marcus Pless wrote:

 I don't know if it's documented online but here's something like
 what I've done in the past (config name was SGVA):
 


Thanks. I'm currently trying the proposed patch, which is to simply
comment out those debugging lines. So far, so good. It does appear to be
trying to recover the desired file. Fingers crossed.

If that fails, I'm sure I'll quickly be paying close attention to your
wonderful reply. I made sure to include the the mailing list such that
it can benefit others down the road.

Again, thanks everyone so much for your rapid replies.

If I get stuck, I'm sure I'll be back.

Regards,


 
 To determine where on a tape a certain dumpfile is:
  Look in ~amanda/logs/SGVA/log.[date].[N] where date is the  
 date that the
  tape was written, and N is a serial number, for the  
 amdump/amflush
  performed that day. N is usually 0.
 
  grep taper ~amanda/logs/SGVA/log.20060316.0 | less -N
 
  Once you find the filesystem you look for, the number will be  
 one
  greater than the filenumber on the tape. If you fsf to the  
 index
  minus two, you should be okay. I like using two for the extra
  insurance.
 
  Be careful when restoring from a multiple tape set. The  
 numbers will
  be far off. A second tape is used when you see something like  
 this:
 
  307 START taper datestamp 20060316 label SGVA0024 tape 1
 
  You will have to account for the index number (307), and the  
 INFO line
  that follows it. Only SUCCESS lines indicate a file written to  
 tape.
 
 
 To manually extract a file from an amanda tape:
  1) insert the tape
  2) fast forward to the position on the tape desired
 $ mt -f /dev/nst0 fsf 13
  3) extract the file
 $ dd if=/dev/nst0 bs=32k skip=1 of=restored.file
 
  The format will either be a native dump format, or in a tar  
 format.
  It will possibly be gzipped.
 
  additional notes
  Following the above procedures I was able to manually extract  
 the
  necessary files from tape.  However, I was unable to read them  
 using
  tar or restore.  The recovered dump files also weren't  
 compressed or
  gzip'd.  I used 'file' for the name of the output file with  
 'dd'.
 
  [mpless@sgva-serv1 58]# file file
  file: AMANDA  dump file, DATE 20060422 hostname.ucsd.edu /var/s
 
  So, it's an AMANDA dump file.  What that means is that I still  
 needed
  to use 'amrestore file' to convert (extract?) the file I  
 pulled from
  the tape into something I could work with.  This produced a  
 file named
  'hostname.ucsd.edu._var_spool_mail.20060422.2' which I was  
 able to
  process using tar.
 
  [mpless@sgva-serv1 58]# file  
 hostname.ucsd.edu._var_spool_mail.20060422.2
  hostname.ucsd.edu._var_spool_mail.20060422.2: GNU tar archive
 
 
 Things can get more complicated depending on the version of
 amanda you're using, if you're splitting files, spanning tapes,
 etc. More complicated in that the entries in the log file may
 not line up quite as nicely, but they can still be used to get
 close, if you have a lot of disk list entries. My daily backups
 are usually 500+ disk list entries, so I need to get close on
 the tape to do this manually.
 
 The 'bs' argument to 'dd' needs to match whatever blocksize
 amanda used when it wrote the tape; I think the default for
 amanda is 32k. If you're not sure where you are on the tape you
 can do something like
 
 dd if=/dev/nst0 bs=32k count=1
 
 to see the amanda header, which will include the name of the
 host and filesystem. Compare this to the entries in the log
 file to see if you're getting close. If that's not it you can
 then do something like
 
 dd if=/dev/nst0 bs=32k fsf=1
 
 to get to the start of the next file on tape, and then check the
 amanda header using the above dd command. You can follow this in
 the amanda log file so you'll know when you're getting close.
 
 If you're at the beginning of the file on tape (you haven't
 read the amanda header you can use
 
 dd if=/dev/nst0 bs=32k skip=1 of=restored.file
 
 to extract that file, minus the amanda header. If you just read the
 amanda header and that's the file you want you can use
 
 dd if=/dev/nst0 bs=32k of=restored.file
 
 (don't do the skip=1)
 
 
 This is actually a lot easier than it sounds, once you're gone
 through it a time or two. If nothing else it's a good experience
 for when things have really hit the fan and you need to manually
 recover your amanda logs from tape to bootstrap your way back up.
 
 Good luck!
 
 --Marcus
 
 
 
 On 04/13/2012 11:02:33 AM, Greg Copeland wrote:
  On Fri, 2012-04-13 at 10:48 -0700, Marcus Pless wrote:
  
   Have you tried amfetchdump? In the near-worst case scenario
   you can use the log file to help you

Re: Recovery Help Request [RESOLVED]

[Greg Copeland]

Just a quick follow up. I wanted to share the file in question was
successfully recovered without further problems. The trick is to comment
out all of the debugging statements in the index server (amidxtaped). 

Change these lines: 
debug(CTL  $chopped);

Into these lines:
#debug(CTL  $chopped);

Reference, as suggested by Steven Backus:
http://forums.zmanda.com/showthread.php?3691-amrecover-segmentation-fault

This is definitely a bug in the latest amanda stable. To clarify, I am
running Amanda version 3.3.1, compiled from source on CentOS 6.2.

Is it presumptuous to assume this will make its way to the developers as
a bug report?

Thanks again.


Sincerely,

-- 
Greg Copeland g...@copelandconsulting.net
Copeland Computer Consulting

Re: Need help with new architecture for NAS/NFS setup

[Leon Meßner]

On Thu, Nov 03, 2011 at 11:53:46AM -0400, Brendon Martino wrote:
 Thus, it was proposed that I mount some NFS space from another system (a
 NAS, for all intents and purposes, though it has a WORM architecture and
 is only used for archiving data with retention periods that delete old
 archives). So now I have 1TB of space mounted under /nfsbackup. How do I
 implement my architecture to only keep about a week (or even a day) of
 backups in the holding disk (locally on the system) but use the nfs
 storage space for archiving the rest of the old backups? The idea is
 that we keep 30 to 60 days worth of old backups on the NAS, but only the
 last day or few days locally on the backup server.
 
 How do I do that? Is it possible? What would be the general idea/layout?
 What directives would I need to change? Would I need to use multiple
 DailySets?? I'm totally stumped. Any advice would be greatly appreciated.

Did you actually try yo setup a holdingdisk with a capacity of
7+something days of vtapes and putting your tapes on NFS ? You would
need to configure your holdingspace to flush after said time of course.
Or can't a holdingdisk have more than one tape worth of data?

cheers,
Leon

Need help with new architecture for NAS/NFS setup

[Brendon Martino]

I'm having trouble figuring out what type of new architecture to go with
for an NFS share dir on a NAS.

I'm running Amanda version 2.6.0p2-14 on Fedora 10. My current
architecture for Amanda is as follows:

I'm running a set called DailySet1. My holding disk/vtapes are:
/amanda/day0x/data/  where x is 1-8. So I have 8 vtapes in my holding
disk. Here's my changer.conf:
multieject 0
gravity 0
needeject 0
ejectdelay 0
statefile /var/lib/amanda/DailySet1/changer-status
firstslot 1
lastslot 8
slot 1file:/amanda/day01
slot 2file:/amanda/day02
slot 3file:/amanda/day03
slot 4file:/amanda/day04
slot 5file:/amanda/day05
slot 6file:/amanda/day06
slot 7file:/amanda/day07
slot 8file:/amanda/day08

If I do a dump each night, I get a backup for each client in my disklist
per day. That gives me about a week's worth of backups. Here's some info
from the amanda.conf file:

dumpcycle 7 days# the number of days in the normal dump cycle
runspercycle 0  # the number of amdump runs in dumpcycle days
tapecycle 8 tapes   # the number of tapes in rotation
runtapes 1  # number of tapes to be used in a single run of
amdump
tpchanger chg-multi   # the tape-changer glue script
changerfile /etc/amanda/DailySet1/changer.conf


This works fine, however, it only does a week of backups. If I wanted to
do a month of backups, I would have to multiply my current system X 4.
So I would need a tapecycle of 30 (or so). My dumpcycle would remain 7
since I still want to do full dumps weekly. But in this case, I would
need to expand my array of vtapes from /amanda/day01/ to /amanda/day30/.
This is not possible since my holding disk area (the size of the
system's usable hard disk space) is not big enough for all of those
vtapes (and the data they would end up having in them) as it only has
about 100 GB free and my backups are about 50GB per week.

Thus, it was proposed that I mount some NFS space from another system (a
NAS, for all intents and purposes, though it has a WORM architecture and
is only used for archiving data with retention periods that delete old
archives). So now I have 1TB of space mounted under /nfsbackup. How do I
implement my architecture to only keep about a week (or even a day) of
backups in the holding disk (locally on the system) but use the nfs
storage space for archiving the rest of the old backups? The idea is
that we keep 30 to 60 days worth of old backups on the NAS, but only the
last day or few days locally on the backup server.

How do I do that? Is it possible? What would be the general idea/layout?
What directives would I need to change? Would I need to use multiple
DailySets?? I'm totally stumped. Any advice would be greatly appreciated.

Thanks
-Brendon Martino

Re: Need help with new architecture for NAS/NFS setup

[Charles Curley]

On Thu, 3 Nov 2011 11:53:46 -0400
Brendon Martino brendon.mart...@hds.com wrote:

 I'm having trouble figuring out what type of new architecture to go
 with for an NFS share dir on a NAS.

I'm inclined to think you can't, short of a messy script that plays
with symlinks and rsync. I wouldn't touch that with a ten meter pole.

I do a backup of similar size to a USB external hard drive, which I then
rsync to another external hard drive. The second I swap out weekly and
is my off-site backup. See:

http://www.charlescurley.com/blog/articles/off_site_backups_for_amanda/index.html
http://www.charlescurley.com/blog/articles/backing_up_amanda_metadata/index.html




-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

re: Need help with new architecture for NAS/NFS setup

[Olivier]

Hi Brendon,

 I'm having trouble figuring out what type of new architecture to go with
 for an NFS share dir on a NAS.

You could run two dumps in parallel, one with tapecycle of 7 onj your local 
disk and one with tape cycle of 30 or 60 on your NAS.

Best regards,

Olivier

 I'm running Amanda version 2.6.0p2-14 on Fedora 10. My current
 architecture for Amanda is as follows:
 
 I'm running a set called DailySet1. My holding disk/vtapes are:
 /amanda/day0x/data/  where x is 1-8. So I have 8 vtapes in my holding
 disk. Here's my changer.conf:
 multieject 0
 gravity 0
 needeject 0
 ejectdelay 0
 statefile /var/lib/amanda/DailySet1/changer-status
 firstslot 1
 lastslot 8
 slot 1file:/amanda/day01
 slot 2file:/amanda/day02
 slot 3file:/amanda/day03
 slot 4file:/amanda/day04
 slot 5file:/amanda/day05
 slot 6file:/amanda/day06
 slot 7file:/amanda/day07
 slot 8file:/amanda/day08
 
 If I do a dump each night, I get a backup for each client in my disklist
 per day. That gives me about a week's worth of backups. Here's some info
 from the amanda.conf file:
 
 dumpcycle 7 days# the number of days in the normal dump cycle
 runspercycle 0  # the number of amdump runs in dumpcycle days
 tapecycle 8 tapes   # the number of tapes in rotation
 runtapes 1  # number of tapes to be used in a single run of
 amdump
 tpchanger chg-multi   # the tape-changer glue script
 changerfile /etc/amanda/DailySet1/changer.conf
 
 
 This works fine, however, it only does a week of backups. If I wanted to
 do a month of backups, I would have to multiply my current system X 4.
 So I would need a tapecycle of 30 (or so). My dumpcycle would remain 7
 since I still want to do full dumps weekly. But in this case, I would
 need to expand my array of vtapes from /amanda/day01/ to /amanda/day30/.
 This is not possible since my holding disk area (the size of the
 system's usable hard disk space) is not big enough for all of those
 vtapes (and the data they would end up having in them) as it only has
 about 100 GB free and my backups are about 50GB per week.
 
 Thus, it was proposed that I mount some NFS space from another system (a
 NAS, for all intents and purposes, though it has a WORM architecture and
 is only used for archiving data with retention periods that delete old
 archives). So now I have 1TB of space mounted under /nfsbackup. How do I
 implement my architecture to only keep about a week (or even a day) of
 backups in the holding disk (locally on the system) but use the nfs
 storage space for archiving the rest of the old backups? The idea is
 that we keep 30 to 60 days worth of old backups on the NAS, but only the
 last day or few days locally on the backup server.
 
 How do I do that? Is it possible? What would be the general idea/layout?
 What directives would I need to change? Would I need to use multiple
 DailySets?? I'm totally stumped. Any advice would be greatly 
appreciated.
 
 Thanks
 -Brendon Martino

Re: Need help with new architecture for NAS/NFS setup

[John Hein]

Brendon Martino wrote at 11:53 -0400 on Nov  3, 2011:
  I'm running Amanda version 2.6.0p2-14 on Fedora 10. My current
  architecture for Amanda is as follows:
.
.
   How do I
  implement my architecture to only keep about a week (or even a day) of
  backups in the holding disk (locally on the system) but use the nfs
  storage space for archiving the rest of the old backups? The idea is
  that we keep 30 to 60 days worth of old backups on the NAS, but only the
  last day or few days locally on the backup server.
  
  How do I do that? Is it possible? What would be the general idea/layout?
  What directives would I need to change? Would I need to use multiple
  DailySets?? I'm totally stumped. Any advice would be greatly appreciated.

In addition to other suggestions on this thread, there's also amvault.
But not with amanda-2.6.

[Amanda-users] amanda.conf config help

[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 absolute total time-out.
# The default is 5 minutes per filesystem.
#dtimeout 1800# number 

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

[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
 }
 
 define dumptype comp-tar {
 program GNUTAR
 compress fast
 index yes
 record yes  # Important! avoid interfering with production runs
 #   tape_splitsize 1

[Amanda-users] amanda.conf config help

[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.
+--

[Amanda-users] amanda.conf config help

[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

[upengan78]

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 correct spindles in 
DLEs.

And yes, split_diskbuffer is correct. I am using it now which I think I ignored 
completely earlier. 

Currently, I have scheduled 2 amanda configurations in cron for amcheck/amdump. 
These jobs are going fine. One is weeklyfullbackup(daily incremental(5 days) 
and other monthlyfull ( daily incremental ) . I am thinking about buying 
another storage in order to accomodate additional DLEs that I have enabled. 
300G is not enough. And, yes virtual tapes option looks cost effective as well..

I will write more ..

Thanks!

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

[Amanda-users] amanda.conf config help

[upengan78]

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 got below email when I ran the 
dump. May be using multiple DLEs is my only option rather than one here.

Here is the Amanda email I got. I don't understand what it is trying to tell me 
to do.


These dumps were to tapes TEST-1, TEST-2.
The next 6 tapes Amanda expects to use are: 6 new tapes.
The next 6 new tapes already labelled are: TEST-3, TEST-4, TEST-5, TEST-6, 
TEST-7, TEST-8
STRANGE DUMP SUMMARY:
  TEST.domain.com /bk/location lev 0  STRANGE (see below)



STATISTICS:
  Total   Full  Incr.
      
Estimate Time (hrs:min) 0:29
Run Time (hrs:min)  2:07
Dump Time (hrs:min) 1:38   1:38   0:00
Output Size (meg)16131.316131.30.0
Original Size (meg)  31043.731043.70.0
Avg Compressed Size (%) 52.0   52.0--
Filesystems Dumped 1  1  0
Avg Dump Rate (k/s)   2795.5 2795.5--

Tape Time (hrs:min) 1:38   1:38   0:00
Tape Size (meg)  16131.316131.30.0
Tape Used (%)  157.5  157.50.0
Filesystems Taped  1  1  0
Parts Taped   33 33  0
Avg Tp Write Rate (k/s)   2795.9 2795.9--

USAGE BY TAPE:
  Label   Time Size  %NbNc
  TEST-1 1:1210485088k  100.0 120
  TEST-2 0:27 6556954k   62.5 013

STRANGE DUMP DETAILS:
  /-- TEST.domain.com /bk/location lev 0 STRANGE
  sendbackup: start [TEST.domain.com:/bk/location level 0]
  sendbackup: info BACKUP=/opt/csw/bin/gtar
  sendbackup: info RECOVER_CMD=/opt/csw/bin/gzip -dc |/opt/csw/bin/gtar -xpGf - 
...
  sendbackup: info COMPRESS_SUFFIX=.gz
  sendbackup: info end
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/filenames.log: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.out: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.out.BAK: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sim: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sp: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sp.cache: 
File removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.st0: File 
removed before we read it
  ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/tclIndex: File 
removed before we read it
  | Total bytes written: 32551710720 (31GiB, 5.3MiB/s)
  sendbackup: size 31788780
  sendbackup: end
  \

NOTES:
  planner: Incremental of TEST.domain.com:/bk/location bumped to level 2.
  planner: TEST.domain.com /bk/location 20101202160419 0 
/opt/csw/libexec/amanda/runtar exited with status 1: see 
/tmp/amanda/client/test/sendsize.20101202160241.debug
  taper: Will request retry of failed split part.
  taper: tape TEST-1 kb 9961472 fm 20 [OK]
  taper: tape TEST-2 kb 6556954 fm 13 [OK]
  big estimate: TEST.domain.com /bk/location 0
  est: 20791072kout 16518426k


DUMP SUMMARY:
DUMPER STATSTAPER STATS
HOSTNAME DISKL  ORIG-kB   OUT-kB  COMP%  MMM:SS   KB/s 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 
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
labelstr TEST-.*
#label_new_tapes TEST-%%
autolabel TEST-%%
tapetype DVD_SIZED_DISK
logdir /opt/csw/etc/amanda/test
infofile /opt/csw/etc/amanda/test/curinfo
indexdir /opt/csw/etc/amanda/test/index
tapelist /opt/csw/etc/amanda/test/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 

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

[Jon LaBadie]

On Fri, Dec 03, 2010 at 09:55:14AM -0500, upengan78 wrote:
 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 got below email when I ran the 
 dump. May be using multiple DLEs is my only option rather than one here.
 

Congratulations on a successful amdump!

 Here is the Amanda email I got. I don't understand what it is trying to tell 
 me to do.
 
 
 These dumps were to tapes TEST-1, TEST-2.
 The next 6 tapes Amanda expects to use are: 6 new tapes.
 The next 6 new tapes already labelled are: TEST-3, TEST-4, TEST-5, TEST-6, 
 TEST-7, TEST-8

OK, you allow amanda to use up to six tapes, but it only needed two.

 STRANGE DUMP SUMMARY:
   TEST.domain.com /bk/location lev 0  STRANGE (see below)

Lots of strange messages are quite normal, particularly when
dumping an active/live file system.

 
 STATISTICS:
   Total   Full  Incr.
       
 Estimate Time (hrs:min) 0:29
 Run Time (hrs:min)  2:07
 Dump Time (hrs:min) 1:38   1:38   0:00
 Output Size (meg)16131.316131.30.0
 Original Size (meg)  31043.731043.70.0
 Avg Compressed Size (%) 52.0   52.0--

fairly compressible data.

 Filesystems Dumped 1  1  0
 Avg Dump Rate (k/s)   2795.5 2795.5--
 
 Tape Time (hrs:min) 1:38   1:38   0:00
 Tape Size (meg)  16131.316131.30.0
 Tape Used (%)  157.5  157.50.0
 Filesystems Taped  1  1  0
 Parts Taped   33 33  0

Hmm, a 16.1GB dump written in taped in 33 parts.  Sounds
like your splits are about 0.5GB.  I wouldn't leave it that
low unless you are really concerned with maximizing each
vtape's filling.

 Avg Tp Write Rate (k/s)   2795.9 2795.9--
 
 USAGE BY TAPE:
   Label   Time Size  %NbNc
   TEST-1 1:1210485088k  100.0 120
   TEST-2 0:27 6556954k   62.5 013
 

Hmm, 20 parts successfully taped on the first (TEST-1) vtape.
So you must be sizing them at about 10GB.

 STRANGE DUMP DETAILS:
   /-- TEST.domain.com /bk/location lev 0 STRANGE
   sendbackup: start [TEST.domain.com:/bk/location level 0]
   sendbackup: info BACKUP=/opt/csw/bin/gtar
   sendbackup: info RECOVER_CMD=/opt/csw/bin/gzip -dc |/opt/csw/bin/gtar -xpGf 
 - ...
   sendbackup: info COMPRESS_SUFFIX=.gz
   sendbackup: info end
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/filenames.log: File 
 removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.out: File 
 removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.out.BAK: 
 File removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sim: File 
 removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sp: File 
 removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.sp.cache: 
 File removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/no_name.st0: File 
 removed before we read it
   ? /opt/csw/bin/gtar: ./fall2010/ece429/albert/cpu32/sue/tclIndex: File 
 removed before we read it
   | Total bytes written: 32551710720 (31GiB, 5.3MiB/s)
   sendbackup: size 31788780
   sendbackup: end
   \

These are strange, not failed.  I.e., tar noted something but
continued to run.  Gtar makes a list of files it will backup up
then copies them.  If during the interval between noting a file
to back up and the actual backup, some{one|thing} removes the
file, the above strange messages are produced.  I'm not
concerned about missing backups of things that were just removed,
they were probably some type of temporary file.

Strange messages are also generaged about files that change while
being backed up (eg. log files) and the backup of these may be
inaccurate.  Gtar does not backup network sockets nor (I think)
device files.  But it generates unexpected, thus strange mesgs.

 
 NOTES:
   planner: Incremental of TEST.domain.com:/bk/location bumped to level 2.
   planner: TEST.domain.com /bk/location 20101202160419 0 
 /opt/csw/libexec/amanda/runtar exited with status 1: see 
 /tmp/amanda/client/test/sendsize.20101202160241.debug
   taper: Will request retry of failed split part.
   taper: tape TEST-1 kb 9961472 fm 20 [OK]

While attempting to put part 21 on the vtape, the end of the
tape was reached.  Thus an error.  But from the line below,
it successfully was sent to the next vtape.

   taper: tape TEST-2 kb 6556954 fm 13 [OK]
   big estimate: 

[Amanda-users] amanda.conf config help

[upengan78]

#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 amdump summary : 
  taper: Will request retry of failed split part.
  taper: tape TEST-1 kb 9845830 fm 15 [OK]
  taper: tape TEST-2 kb 6661060 fm 7 [OK]

But now that I read your reply, I think it just doesn't mean a lot as long as I 
see OK below that particular message. Here is full DUMP summary :
These dumps were to tapes TEST-1, TEST-2.
The next 6 tapes Amanda expects to use are: 6 new tapes.
The next 6 new tapes already labelled are: TEST-3, TEST-4, TEST-5, TEST-6, 
TEST-7, TEST-8


STATISTICS:
  Total   Full  Incr.
      
Estimate Time (hrs:min) 0:10
Run Time (hrs:min)  1:51
Dump Time (hrs:min) 1:38   1:38   0:00
Output Size (meg)16120.016120.00.0
Original Size (meg)  30661.630661.60.0
Avg Compressed Size (%) 52.6   52.6--
Filesystems Dumped 9  9  0
Avg Dump Rate (k/s)   2809.3 2809.3--

Tape Time (hrs:min) 0:17   0:17   0:00
Tape Size (meg)  16120.016120.00.0
Tape Used (%)  157.4  157.40.0
Filesystems Taped  9  9  0
Parts Taped   22 22  0
Avg Tp Write Rate (k/s)  16506.916506.9--

USAGE BY TAPE:
  Label   Time Size  %NbNc
  TEST-1 0:1010485219k  100.0 815
  TEST-2 0:07 6661060k   63.5 2 7

NOTES:
  planner: Adding new disk TEST.domain.com:/bk/location/./apple2007.
  planner: Adding new disk TEST.domain.com:/bk/location/./apple2008.
  planner: Adding new disk TEST.domain.com:/bk/location/./apple2009.
  planner: Adding new disk TEST.domain.com:/bk/location/./apple2010.
  planner: Adding new disk TEST.domain.com:/bk/location/./pear2008.
  planner: Adding new disk TEST.domain.com:/bk/location/./pear2009.
  planner: Adding new disk TEST.domain.com:/bk/location/./pear2010.
  planner: Adding new disk TEST.domain.com:/bk/location/./other.
  planner: Adding new disk TEST.domain.com:/bk/location/./_rest_.
  taper: Will request retry of failed split part.
  taper: tape TEST-1 kb 9845830 fm 15 [OK]
  taper: tape TEST-2 kb 6661060 fm 7 [OK]
  big estimate: TEST.domain.com /bk/location/./apple2007 0
  est: 244128kout 119306k
  big estimate: TEST.domain.com /bk/location/./apple2009 0
  est: 834272kout 521751k
  big estimate: TEST.domain.com /bk/location/./apple2010 0
  est: 3646880kout 2857940k


DUMP SUMMARY:
   DUMPER STATS   TAPER STATS
HOSTNAME DISKL ORIG-kB  OUT-kB  COMP%  MMM:SS   KB/s MMM:SSKB/s
-- - --
TEST.domain.co -u/./_rest_ 0 2981200 2155287   72.37:25 4838.8   2:05 
17242.3
TEST.domain.co -./apple2007 0  488140  119306   24.41:40 1188.0   0:06 
19884.3
TEST.domain.co -./apple2008 0 6484400 3803120   58.7   28:08 2253.5   4:23 
14460.5
TEST.domain.co -./apple2009 0 1668440  521751   31.33:17 2642.9   0:29 
17991.4
TEST.domain.co -./apple2010 0 7308970 2857940   39.1   22:30 2117.1   2:46 
17216.5
TEST.domain.co -tu/./other 0 5833440 3828839   65.6   18:01 3542.5   3:44 
17093.0
TEST.domain.co -pear2008 0   88010   46283   52.60:23 2040.3   0:02 23141.5
TEST.domain.co -pear2009 0 4127930 1932585   46.89:16 3475.2   1:53 17102.5
TEST.domain.co -pear2010 0 2416990 1241776   51.47:15 2853.0   1:12 17246.9

(brought to you by Amanda version 3.1.1)


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 tape_splitsize = 1Gb although I do have fallback_splitsize = 512MB . Do you 
mean I should grow this value to a higher value or you said that about 
tape_splitsize value?

Other than this, your explanation was really informative and thanks again for 
that.

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

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

[Brian Cuttler]

 Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] amanda.conf config help

[upengan78]

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 portion from amanda.conf

holdingdisk hd1 {
directory /random/amandahold/test
}

define dumptype comp-tar {
program GNUTAR
compress fast
index yes
record yes  # Important! avoid interfering with production runs
   tape_splitsize 1 Gb
   #fallback_splitsize 512 MB
   fallback_splitsize 2048 MB
   splitdisk_buffer /random/amandahold/test
}

define tapetype DVD_SIZED_DISK {
filemark 1 KB
length 10240 MB
}

I should have mentioned, Amanda server has 16GB of memory, you still recommend 
splitdisk_buffer?

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

[Amanda-users] amanda.conf config help

[upengan78]

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 GB 
memory on amanda client.

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

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

[Thomas Marko]

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:

# split_diskbuffer - (optional) When dumping a split dump  in  PORT-WRITE
# mode (usually meaning no holding disk), buffer the split
# chunks to a file in the directory specified by this
option.
# Default: [none]

Cheers,
Thomas

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

[Jon LaBadie]

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 is expected
 amcheck: errors processing config file

spelling error split_diskbuffer != splitdisk_buffer 

 
 Relevant portion from amanda.conf
 
 holdingdisk hd1 {
 directory /random/amandahold/test
 }
 
 define dumptype comp-tar {
 program GNUTAR
 compress fast
 index yes
 record yes  # Important! avoid interfering with production runs
tape_splitsize 1 Gb
#fallback_splitsize 512 MB
fallback_splitsize 2048 MB
splitdisk_buffer /random/amandahold/test
 }
 
 define tapetype DVD_SIZED_DISK {
 filemark 1 KB
 length 10240 MB
 }
 
 I should have mentioned, Amanda server has 16GB of memory, you still 
 recommend splitdisk_buffer?
 
 +--
 |This was sent by upendra.gan...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
 
 End of included message 

-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

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

[Jon LaBadie]

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 tape_splitsize = 1Gb although I do have fallback_splitsize = 
 512MB . Do you mean I should grow this value to a higher value or you said 
 that about tape_splitsize value?
 

At the time I wrote that I saw you had backed up and taped
16GB of data and they were taped in 33 parts.  16GB / 33
is about 0.5GB/part.

Your amdump run used the fallback_splitsize because you
had not specified a split_diskbuffer.  If one had been
specified, data would move from holding disk to the
split_diskbuffer creating parts of tape_splitsize.
If a part failed, such as at the end of a tape, then
the part would be retried on the next tape (if available).

Without a split_diskbuffer the parts have to be created
in memory.  In this situation the parts are sized to the
fallback_splitsize rather than tape_splitsize.  Typically
this is smaller than tape_splitsize to avoid using too much
memory.  As you had no split_diskbuffer, the fallback_splitsize
(0.5GB) was used as the part size.

-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

[Amanda-users] amanda.conf config help

[upengan78]

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
slot 1: read label `TEST-1', date `20101124'
cannot overwrite active tape TEST-1
slot 2: read label `TEST-2', date `X'
NOTE: skipping tape-writable test
Tape TEST-2 label ok
Server check took 0.815 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.536 seconds, 0 problems found

(brought to you by Amanda 2.5.2p1)


@ 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 A1999E90
gpg: Good signature from Blastwave Software (Blastwave.org Inc.) 
softw...@blastwave.org
package   installed catalog
CSWamanda 2.5.2p1,REV=2008.05.21SAME

Is openCSW for opensolaris or something, ofcourse I will google it now :)

Also, I am going to try using splitsize parameter and try again now. (5GB)

Thanks

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

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

[Jon LaBadie]

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 A1999E90
 gpg: Good signature from Blastwave Software (Blastwave.org Inc.) 
 softw...@blastwave.org
 package   installed catalog
 CSWamanda 2.5.2p1,REV=2008.05.21SAME
 
 Is openCSW for opensolaris or something, ofcourse I will google it now :)

I don't know the details, but there was a disagreement among
the owner of the blastwave name and some (all?) of the developers
who maintained the packages.  This eventually caused a fork of
the catalog with the new one being called openCSW.

It seemed to me that openCSW is now more complete and better
maintained than blastwave.  I switched earlier this year.
I think packages from the two sites are supposed to be
?interchangeable? (i.e. you should be able to pick and
choose from either site).  I've not encountered any
problems caused by my switching sites, but if I were
switching a production system I'd make sure all pkgs
were from the same site.

jl
-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

[Amanda-users] amanda.conf config help

[upengan78]

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
slot 1: read label `TEST-1', date `20101124'
cannot overwrite active tape TEST-1
slot 2: read label `TEST-2', date `X'
NOTE: skipping tape-writable test
Tape TEST-2 label ok
Server check took 0.815 seconds

Amanda Backup Client Hosts Check

Client check: 1 host checked in 0.536 seconds, 0 problems found

(brought to you by Amanda 2.5.2p1)


@ 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 A1999E90
gpg: Good signature from Blastwave Software (Blastwave.org Inc.) 
softw...@blastwave.org
package   installed catalog
CSWamanda 2.5.2p1,REV=2008.05.21SAME

Is openCSW for opensolaris or something, ofcourse I will google it now :)

Also, I am going to try using splitsize parameter and try again now. (5GB)

Thanks

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

[Amanda-users] amanda.conf config help

[upengan78]

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 think things have changed a lot 
between amanda version as far as parameters are concerned? so this dicussion is 
always helping me. 

I will try amanda 3.1.1 and let you know how that works. Thanks much!

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

[Amanda-users] amanda.conf config help

[upengan78]

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
tapedev file:/random/amanda/vtapes/test/slots
changerfile /opt/csw/etc/amanda/test/changerfile
labelstr TEST-.*
#label_new_tapes TEST-%%
#autolabel TEST-%%
tapetype DVD_SIZED_DISK
logdir /opt/csw/etc/amanda/test
infofile /opt/csw/etc/amanda/test/curinfo
indexdir /opt/csw/etc/amanda/test/index
tapelist /opt/csw/etc/amanda/test/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 /another drive/amanda/amandahold/test
}

define dumptype comp-tar {
program GNUTAR
compress fast
index yes
record yes  # Important! avoid interfering with production runs
}

define tapetype DVD_SIZED_DISK {
filemark 1 KB
length 10240 MB
}

I am still confused about spanning because 
http://wiki.zmanda.com/index.php/How_To:Split_Dumps_Across_Tapes mentions that 
spanning is automatically enabled in Vtapes. Now is that for specific version 
that means or all versions and is there any command to verify if it is enabled 
or not? Copying the relevent portion from wiki below.

Disk Backups (Vtapes)

For vtapes, spanning is automatically enabled, as the VFS device supports LEOM. 
You can add a part_size if you'd like to split dumps into smaller parts; 
otherwise, Amanda will just fill each vtape with a single part before moving on 
to the next vtape.

Thanks for continuing to help guys. Appreciate it and it is wonderful to see 
how much deep knowledge people have about backups and sharing it happily. And, 
I do understand there has to be offsite storage as I know pipes can burst and 
it has happened before. These things I plan to consider once I am confortable 
with setup. :)

Can anyone advise on spanning ?  how to do it in Vtapes?

Thanks

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

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

[Brian Cuttler]

Nothing strickes me as wrong with your new config but...

I'm sorry, I can't actually comment on spanning, never
configured it on any of my amanda servers.

Just for the sake of argument I'm going to include an
extract of my disklist file.

Originally we backed up a 1Tbyte drive, this was impractical,
as much for wall clock time as for any other reason.

Because we are no longer backing up the 'partition' we can't
use dump, the DLE specifies tar. I broke the partition into
two main pieces, with planning and a little luck the directories
that being with letters [A-Q] will contain about the same amount
of data as the directories beginning R to Z.

Because _users_ have access on this file system to create new
directories at will I also included a DLE that would pick up
any directories or files beginning with lower-case letters.
These I allow to backup all at once since there currently
aren't any. ie, avoid missing them by oversight.

trel   /Users   comp-user-tar
#trel   /treluser-tar
trel   /trelAQ /trel   {
comp-server-user-tar
include ./[A-Q]*
}

trel   /trelRZ /trel   {
comp-server-user-tar
include ./[R-Z]*
}

trel   /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
 
 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
 labelstr TEST-.*
 #label_new_tapes TEST-%%
 #autolabel TEST-%%
 tapetype DVD_SIZED_DISK
 logdir /opt/csw/etc/amanda/test
 infofile /opt/csw/etc/amanda/test/curinfo
 indexdir /opt/csw/etc/amanda/test/index
 tapelist /opt/csw/etc/amanda/test/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 /another drive/amanda/amandahold/test
 }
 
 define dumptype comp-tar {
 program GNUTAR
 compress fast
 index yes
 record yes  # Important! avoid interfering with production runs
 }
 
 define tapetype DVD_SIZED_DISK {
 filemark 1 KB
 length 10240 MB
 }
 
 I am still confused about spanning because 
 http://wiki.zmanda.com/index.php/How_To:Split_Dumps_Across_Tapes mentions 
 that spanning is automatically enabled in Vtapes. Now is that for specific 
 version that means or all versions and is there any command to verify if it 
 is enabled or not? Copying the relevent portion from wiki below.
 
 Disk Backups (Vtapes)
 
 For vtapes, spanning is automatically enabled, as the VFS device supports 
 LEOM. You can add a part_size if you'd like to split dumps into smaller 
 parts; otherwise, Amanda will just fill each vtape with a single part before 
 moving on to the next vtape.
 
 Thanks for continuing to help guys. Appreciate it and it is wonderful to see 
 how much deep knowledge people have about backups and sharing it happily. 
 And, I do understand there has to be offsite storage as I know pipes can 
 burst and it has happened before. These things I plan to consider once I am 
 confortable with setup. :)
 
 Can anyone advise on spanning ?  how to do it in Vtapes?
 
 Thanks
 
 +--
 |This was sent by upendra.gan...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] amanda.conf config help

[upengan78]

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 already labelled are: TEST-2, TEST-3, TEST-4, TEST-5, 
TEST-6, TEST-7.

FAILURE AND STRANGE DUMP SUMMARY:
  TEST.domain.com  bk/location  lev 0  FAILED [dump larger than available tape 
space, 30927955 KB, incremental dump also larger than tape]
  planner: FATAL cannot fit anything on tape, bailing out


STATISTICS:
  Total   Full  Incr.
      
Estimate Time (hrs:min)0:00
Run Time (hrs:min) 1:28
Dump Time (hrs:min)0:00   0:00   0:00
Output Size (meg)   0.00.00.0
Original Size (meg) 0.00.00.0
Avg Compressed Size (%) -- -- -- 
Filesystems Dumped0  0  0
Avg Dump Rate (k/s) -- -- -- 

Tape Time (hrs:min)0:00   0:00   0:00
Tape Size (meg) 0.00.00.0
Tape Used (%)   0.00.00.0
Filesystems Taped 0  0  0

Chunks Taped  0  0  0
Avg Tp Write Rate (k/s) -- -- -- 

USAGE BY TAPE:
  Label Time  Size  %NbNc
  TEST-1   0:000k0.0 0 0


NOTES:
  planner: disk TEST.domain.com:bk/location, full dump (30927955KB) will be 
larger than available tape space, you could define a splitsize
  driver: WARNING: got empty schedule from planner
  taper: tape TEST-1 kb 0 fm 0 [OK]


DUMP SUMMARY:
   DUMPER STATS   TAPER STATS 
HOSTNAME DISKL ORIG-kB  OUT-kB  COMP%  MMM:SS   KB/s MMM:SS   KB/s
-- - -
TEST.domain.com bk/location 0 FAILED 



Here is the amdump.1

amdump: start at Wed Nov 24 11:46:40 CST 2010
amdump: datestamp 20101124
amdump: starttime 20101124114640
driver: pid 9565 executable /opt/csw/libexec/driver version 2.5.2p1
planner: pid 9564 executable /opt/csw/libexec/planner version 2.5.2p1
planner: build: VERSION=Amanda-2.5.2p1
planner:BUILT_DATE=Wed May 21 15:37:10 EDT 2008
planner:BUILT_MACH=SunOS ra 5.8 Generic_117350-53 sun4u sparc 
SUNW,Sun-Blade-1000
planner:CC=cc
planner:CONFIGURE_COMMAND='./configure' '--prefix=/opt/csw' 
'--infodir=/opt/csw/share/info' '--mandir=/opt/csw/share/man' 
'--with-dumperdir=/opt/csw/lib/amanda/dumper' '--with-index-server=localhost' 
'--with-gnutar=/opt/csw/bin/gtar' '--with-maxtapeblocksize=512' 
'--with-user=amanda' '--with-group=sys' '--with-amandahosts' 
'--disable-libtool' '--disable-shared' '--disable-static'
planner: paths: bindir=/opt/csw/bin sbindir=/opt/csw/sbin
planner:libexecdir=/opt/csw/libexec mandir=/opt/csw/share/man
planner:AMANDA_TMPDIR=/tmp/amanda AMANDA_DBGDIR=/tmp/amanda
planner:CONFIG_DIR=/opt/csw/etc/amanda DEV_PREFIX=/dev/dsk/
planner:RDEV_PREFIX=/dev/rdsk/ DUMP=/usr/sbin/ufsdump
planner:RESTORE=/usr/sbin/ufsrestore VDUMP=UNDEF VRESTORE=UNDEF
planner:XFSDUMP=UNDEF XFSRESTORE=UNDEF VXDUMP=UNDEF VXRESTORE=UNDEF
planner:SAMBA_CLIENT=UNDEF GNUTAR=/opt/csw/bin/gtar
planner:COMPRESS_PATH=/opt/csw/bin/gzip
planner:UNCOMPRESS_PATH=/opt/csw/bin/gzip
planner:LPRCMD=/opt/csw/bin/lpr MAILER=/usr/bin/mailx
planner:listed_incr_dir=/opt/csw/var/amanda/gnutar-lists
planner: defs:  DEFAULT_SERVER=localhost DEFAULT_CONFIG=DailySet1
planner:DEFAULT_TAPE_SERVER=localhost HAVE_MMAP NEED_STRSTR
planner:HAVE_SYSVSHM LOCKING=POSIX_FCNTL SETPGRP_VOID DEBUG_CODE
planner:AMANDA_DEBUG_DAYS=4 BSD_SECURITY RSH_SECURITY USE_AMANDAHOSTS
planner:CLIENT_LOGIN=amanda FORCE_USERID HAVE_GZIP
planner:COMPRESS_SUFFIX=.gz COMPRESS_FAST_OPT=--fast
planner:COMPRESS_BEST_OPT=--best UNCOMPRESS_OPT=-dc
READING CONF FILES...
planner: timestamp 20101124
planner: time 0.033: startup took 0.033 secs

SENDING FLUSHES...
ENDFLUSH

SETTING UP FOR ESTIMATES...
planner: time 0.033: setting up estimates for TEST.domain.com:bk/location
driver: tape size 10485760
driver: adding holding disk 0 dir /amandaservername/amanda/amandahold/test size 
3881997 chunksize 1048576
TEST.domain.com:bk/location overdue 14931 days for level 0
setup_estimate: TEST.domain.com:bk/location: command 0, options: none
last_level 0 next_level0 -14931 level_days 0getting estimates 0 (-2) 1 (-2) 
-1 (-2)
planner: time 0.037: setting up estimates took 0.004 secs

GETTING ESTIMATES...
reserving 3881997 out of 3881997 for degraded-mode dumps
driver: send-cmd time 0.102 to taper: START-TAPER 20101124

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

[Brian Cuttler]

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 tapes Amanda expects to use are: 6 new tapes.
 The next 6 new tapes already labelled are: TEST-2, TEST-3, TEST-4, TEST-5, 
 TEST-6, TEST-7.
 
 FAILURE AND STRANGE DUMP SUMMARY:
   TEST.domain.com  bk/location  lev 0  FAILED [dump larger than available 
 tape space, 30927955 KB, incremental dump also larger than tape]
   planner: FATAL cannot fit anything on tape, bailing out

When you increased the size of your vtapes did you also alter
the length of the tapes in your tapedev definition ?

amanda seems to think that vtape_length * 6  estimated_dump_size



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] amanda.conf config help

[upengan78]

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 processes again. However, I 
wonder if that plays any role here. I am trying amdump again will keep posted.

Good day.

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

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

[Jon LaBadie]

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
 tpchanger chg-disk# a virtual tape changer
 tapedev file:/random/amanda/vtapes/test/slots
 changerfile /opt/csw/etc/amanda/test/changerfile
 labelstr TEST-.*
 #label_new_tapes TEST-%%
 #autolabel TEST-%%
 tapetype DVD_SIZED_DISK
 logdir /opt/csw/etc/amanda/test
 infofile /opt/csw/etc/amanda/test/curinfo
 indexdir /opt/csw/etc/amanda/test/index
 tapelist /opt/csw/etc/amanda/test/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 /another drive/amanda/amandahold/test
 }
 
 define dumptype comp-tar {
 program GNUTAR
 compress fast
 index yes
 record yes  # Important! avoid interfering with production runs
 }
 
 define tapetype DVD_SIZED_DISK {
 filemark 1 KB
 length 10240 MB
 }
 
 I am still confused about spanning because 
 http://wiki.zmanda.com/index.php/How_To:Split_Dumps_Across_Tapes mentions 
 that spanning is automatically enabled in Vtapes. Now is that for specific 
 version that means or all versions and is there any command to verify if it 
 is enabled or not? Copying the relevent portion from wiki below.
 
 Disk Backups (Vtapes)
 
 For vtapes, spanning is automatically enabled, as the VFS device supports 
 LEOM. You can add a part_size if you'd like to split dumps into smaller 
 parts; otherwise, Amanda will just fill each vtape with a single part before 
 moving on to the next vtape.
 
From the same document:

  In Amanda earlier than Amanda-3.2, this was done with some dumptype 
parameters.
   For these versions, see How To:Split Dumps Across Tapes (Amanda-3.1 and 
earlier).

You said you are using amanda version 2.5.x.  Clearly that is earlier than 3.2.

-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

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

[Jon LaBadie]

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  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

[Amanda-users] amanda.conf config help

[upengan78]

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 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 with.

Current settings in Amanda.conf are,


dumpcycle 7
runspercycle 7
tapecycle 20 
dumpuser amanda
tpchanger chg-disk# a virtual tape changer
tapedev file:/export/amanda/vtapes/test/slots
changerfile /opt/csw/etc/amanda/test/changerfile
labelstr TEST-.*
#label_new_tapes TEST-%%
#autolabel TEST-%%
tapetype DVD_SIZED_DISK
logdir /opt/csw/etc/amanda/test
infofile /opt/csw/etc/amanda/test/curinfo
indexdir /opt/csw/etc/amanda/test/index
tapelist /opt/csw/etc/amanda/test/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/amanda/amandahold/test
}

define dumptype comp-tar {
program GNUTAR
compress fast
index yes
record yes  # Important! avoid interfering with production runs
}  

define tapetype DVD_SIZED_DISK {
filemark 4 KB
length 4482 MB
}

I'd like to retain backup for a month if that's possible by doing some 
modifications in amanda.conf and adding more tapes of modifying tape size or 
so..

Please advise..

Thanks

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

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

[Brian Cuttler]

Upengan,

You have 50 gig under backup/amanda control, but how much data
are you currently backing up per week ?

With current settings, tapecycle and dumpcycle you will have
between 2 and 3 full dumps per partition on tape at any one
time, 2.x X 50 Gig  80 Gig so you are already short on (vtape) space.

I believe that vtape size is an upper bound, unused space on
the vtape is actually free space on the disk, so you can actually
oversubscribe the 300 gig pool by some percentage (depending on
numerous factors that we currently do NOT have a handle on).

With 4 Gig tapes... how large are your DLEs ? 4 Gig is relatively
small, are you using tape spanning or are all of the DLE's small ?

With 4-gig tapes and 50 gig under backup you must use 12 tapes
for a complete dump of the system, with a pool of 20 tapes you
can not have two complete dump cycles... 

It seems that either I'm badly misunderstanding your config or
you are badly underconfiguring your tape pool.

There is probably more stuff we could address in your email
but I want to make sure I've understood this much before digging
elsewhere.

Brian


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.
 
 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 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 
 with.
 
 Current settings in Amanda.conf are,
 
 
 dumpcycle 7
 runspercycle 7
 tapecycle 20 
 dumpuser amanda
 tpchanger chg-disk# a virtual tape changer
 tapedev file:/export/amanda/vtapes/test/slots
 changerfile /opt/csw/etc/amanda/test/changerfile
 labelstr TEST-.*
 #label_new_tapes TEST-%%
 #autolabel TEST-%%
 tapetype DVD_SIZED_DISK
 logdir /opt/csw/etc/amanda/test
 infofile /opt/csw/etc/amanda/test/curinfo
 indexdir /opt/csw/etc/amanda/test/index
 tapelist /opt/csw/etc/amanda/test/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/amanda/amandahold/test
 }
 
 define dumptype comp-tar {
 program GNUTAR
 compress fast
 index yes
 record yes  # Important! avoid interfering with production runs
 }  
 
 define tapetype DVD_SIZED_DISK {
 filemark 4 KB
 length 4482 MB
 }
 
 I'd like to retain backup for a month if that's possible by doing some 
 modifications in amanda.conf and adding more tapes of modifying tape size or 
 so..
 
 Please advise..
 
 Thanks
 
 +--
 |This was sent by upendra.gan...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] amanda.conf config help

[upengan78]

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 up a 50G partition with a Full backup on Monday and 
incrementals on each day till next week's Monday. So I think for 7 days I will 
have to backup 50G + 200M x 6 days = 50.6G . Let's say 55G a week. 

My original configuration is with little idea.
dumpcycle 7
runspercycle 7
tapecycle 20
I though above would yield me 7 Days of backup including 1 Full and 6 
incrementals in 1 dumpcycle and all 20 tapes will be used. I don't know if I am 
right.


2. With current settings, tapecycle and dumpcycle you will have 
between 2 and 3 full dumps per partition on tape at any one 
time, 2.x X 50 Gig  80 Gig so you are already short on (vtape) space. 

Correct I think I also think I am short of Vtapes. I wonder if I should add 
more 4.xx G size tapes or redo Vtapes of 40G size each to utilize whole 300GB 
of disk space.

3. I believe that vtape size is an upper bound, unused space on 
the vtape is actually free space on the disk, so you can actually 
oversubscribe the 300 gig pool by some percentage (depending on 
numerous factors that we currently do NOT have a handle on). 

I am not sure I understand what oversubscribe actually is but I wonder if I 
really need it. could you tell me what it will actually do in my case?

4. With 4 Gig tapes... how large are your DLEs ? 4 Gig is relatively 
small, are you using tape spanning or are all of the DLE's small ? 

I don't believe Tape spanning is configured. I just used Vtapes document from 
Amanda wiki and so used 4GB dvd size as it is  mentioned there. that's why I am 
here now to tweak it. DLEs in my disklist are as below,

amandaclient.domain.com   /backup/location comp-tar

5. With 4-gig tapes and 50 gig under backup you must use 12 tapes 
for a complete dump of the system, with a pool of 20 tapes you 
can not have two complete dump cycles... 

Okay. that makes sense.

6. It seems that either I'm badly misunderstanding your config or 
you are badly underconfiguring your tape pool. 

Yes, I can provide you whatever is required. I know even 300G may not very 
large but then I'd like to have best possible that I can make use of it as of 
now. Thanks for helping me out!

Thanks

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

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

[Charles Curley]

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
 understand this whole theory of numbers involved in configuration. I
 want to start backing up a 50G partition with a Full backup on Monday
 and incrementals on each day till next week's Monday. So I think for
 7 days I will have to backup 50G + 200M x 6 days = 50.6G . Let's say
 55G a week.

If you have a dump cycle of 7, and expect 50 G per, then you need 50 x
3 G, or 150 G, plus some spare.

 
 My original configuration is with little idea.
 dumpcycle 7
 runspercycle 7
 tapecycle 20
 I though above would yield me 7 Days of backup including 1 Full and 6
 incrementals in 1 dumpcycle and all 20 tapes will be used. I don't
 know if I am right.

You need 3 x dump cycle tapes plus some spares, so I'd bump that up to
25, a nice integer factor of 150.

The reason you need three times dump cycle is that Amanda spreads out
level 0 (full) backups across the dump cycle, and this ensures that you
always have at least the most recent level 0 backup for any DLE.



 
 
 2. With current settings, tapecycle and dumpcycle you will have 
 between 2 and 3 full dumps per partition on tape at any one 
 time, 2.x X 50 Gig  80 Gig so you are already short on (vtape)
 space. 
 
 Correct I think I also think I am short of Vtapes. I wonder if I
 should add more 4.xx G size tapes or redo Vtapes of 40G size each to
 utilize whole 300GB of disk space.

I use tapes of 10 G and find that a convenient size. I also set
runtapes to 2, but be warned that that introduces a new and potentially
messy factor into your tape requirements calculation.

I also set tape_splitsize to 900 mb, which splits up large dumps into
smaller chunks. 11of them will barely fit onto a 10 G vtape, so I get
maximum use of each one.


 
 3. I believe that vtape size is an upper bound, unused space on 
 the vtape is actually free space on the disk, so you can actually 
 oversubscribe the 300 gig pool by some percentage (depending on 
 numerous factors that we currently do NOT have a handle on). 

Correct, and I have not looked into the calculation.

 
 I am not sure I understand what oversubscribe actually is but I
 wonder if I really need it. could you tell me what it will actually
 do in my case?

Let's say you have 25 4 G tapes, for a theoretical supply of 100 G, so
you give Amanda a partition of 100 G. But you notice that the runs tend
to under-use each tape, by an average of 10%. So you are actually using
90 G. You could (in theory) add two more tapes to that partition.

I recommend against it; I prefer to play with the tape size and
tape_splitsize to make things better emulate tapes.


 
 4. With 4 Gig tapes... how large are your DLEs ? 4 Gig is relatively 
 small, are you using tape spanning or are all of the DLE's small ? 
 
 I don't believe Tape spanning is configured. I just used Vtapes
 document from Amanda wiki and so used 4GB dvd size as it is
 mentioned there.

Are you planning to back up vtapes to DVD? If not, I'd say, don't worry
about the 4 G size and pick something that suits your data set.




-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

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

[Brian Cuttler]

 (mirrored) ?

Do you need to think in terms of off-site storage for
disaster recovery ?

Are you worried about data recovery if you lose the vtape
pool as well as files/drives in your data pool ?


 Thanks
 
 +--
 |This was sent by upendra.gan...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

[Amanda-users] amanda.conf config help

[upengan78]

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 out.

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 looking at amdump o/p in previous email I think I must 
mention 'runtape' 

Now back to the questions.

@Charles
* Are you planning to back up vtapes to DVD? If not, I'd say, don't worry 
about the 4 G size and pick something that suits your data set.

No I am not planning on that. I think I better make tapesize larger like 40G or 
so

@Brian
*You talk in terms of 'new data' each day, do you touch existing 
files ?

It will be modification of exsiting files as well as addition of directories 
and more files and may involve removal of directories/files.


*How many DLEs, disklist entries, will you have, what are their
relative sizes ? 

Only 1 entry for a amanda-network client server. Size is about 50G and grows by 
100M-200M a day or data size sometimes stays as it is for 2-3 days.

*Did you plan on using the VTape pool for anything else ?
No but I think I did not mention that actual filesystem size of RAID5 storage 
mounted is 300G and I only created 20 tapes of 4.x G size on it. I don't plan 
to use the remaining space for anything else.

*How large are your DLEs ? Are they actually all small enough to expect level 0 
dumps to fit on 4 gig volumes ?

I have only 1 DLE in disklist and DUMP 0 will be of about 50G therefore won't 
fit on a single 4GB volume(vtape) however Ithought Amanda will span it 
automatically for Virtual tapes.

*Ah - how many DVD do you typically write per day now ? 
*Is that all level 0 or a mix of 0 and non-0 dumps ? 

No I don't write DVDs actually, it is just named DVD as per the wiki example. I 
have tried taking manual dumps using amdump and they fail as in my earlier 
email :( . Once it is confirmed amdump works manually I will let Amanda do this 
automatically.

*Are you manually intermixing the levels now to even out dump 
times across your week ? 

No I don't plan on doing that. I am only trying to do amdump for testing if a 
Backup job works or no.


*What is the structure of your vtape pool ? 

It is a directory with 1 slot and 20 vtaps. This directory resides on a sotrage 
mount which itself is RAID5 configured.

size of /blah is 300GB

lrwxrwxrwx   1 amanda   sys   50 Nov 23 12:32 data - 
/blah/amanda/vtapes/test/slots/slot2
-rw---   1 amanda   sys   15 Nov 23 13:13 info
drwxr-xr-x   2 amanda   sys  512 Nov 23 11:07 slot1
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot10
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot11
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot12
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot13
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot14
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot15
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot16
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot17
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot18
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot19
drwxr-xr-x   2 amanda   sys  512 Nov 23 13:13 slot2
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot20
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot3
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot4
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot5
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot6
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot7
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot8
drwxr-xr-x   2 amanda   sys  512 Nov 23 10:27 slot9

cat tapelist

0 TEST-20 reuse
0 TEST-19 reuse
0 TEST-18 reuse
0 TEST-17 reuse
0 TEST-16 reuse
0 TEST-15 reuse
0 TEST-14 reuse
0 TEST-13 reuse
0 TEST-12 reuse
0 TEST-11 reuse
0 TEST-10 reuse
0 TEST-9 reuse
0 TEST-8 reuse
0 TEST-7 reuse
0 TEST-6 reuse
0 TEST-5 reuse
0 TEST-4 reuse
0 TEST-3 reuse
0 TEST-2 reuse
0 TEST-1 reuse

*Do you need to think in terms of off-site storage for 
disaster recovery ?

No I don't think I will be doing that. Don't want any redundancy for now 
because there is already RAID5 on DAS.

*Are you worried about data recovery if you lose the vtape 
Nope, Mount is RAID 5 so don't think it will be a big problem
pool as well as files/drives in your data pool ?

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

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

[Chris Hoogendyk]

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 about 50G and grows by 
100M-200M a day or data size sometimes stays as it is for 2-3 days.


Just a comment that this isn't making good use of Amanda. You will get a full backup of 50G, and 
then incrementals of 100M-200M on all the other days of the dump cycle. Making your vtapes all one 
size then wastes a lot of space, not to mention that the load is virtually all on one day of the 
cycle when the full backup is done.


You should break up the 50G into multiple pieces. Suppose there are, say, 10 directories in there, 
and that stays the same. Make each of those directories a disklist entry. Then Amanda's planner will 
decide when to do a full of each directory in such a way as to smooth out the load and the usage of 
space in the vtapes over the span of the dump cycle. If it works out well, and you have a 7 day dump 
cycle, then you should end up getting about 7G+/- every day after it gets started. Since each dle 
has to have a full backup before it can do incrementals, you could add one dle each day to your 
disklist to get a smoother start. Otherwise, the first time you run it, it will want to do a full of 
everything anyway.


Since you are not going to be using the space for anything else, make your vtapes about 10G. Give 
yourself, say, 21 of those. You will have some space left. If you set up a holding disk, then Amanda 
can run multiple dle's in parallel. Ideally, your holding disk should be somewhere else, but you 
could use the remaining 90G or so if you don't have anything else. I like to have a separate drive 
for a holding disk so that I'm not in competition for i/o bandwidth with anything that I might be 
backing up, or in your case with the vtapes.


That's just an example of how to go about it. It would give you a typecycle with 3 weeks of backup 
with 3 full dump cycles of 7 days.


--
---

Chris Hoogendyk

-
   O__   Systems Administrator
  c/ /'_ --- Biology  Geology Departments
 (*) \(*) -- 140 Morrill Science Center
~~ - University of Massachusetts, Amherst

hoogen...@bio.umass.edu

---

Erdös 4

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

[Brian Cuttler]

...@gmail.com via Backup Central.
 |Forward SPAM to ab...@backupcentral.com.
 +--
 
 
---
   Brian R Cuttler brian.cutt...@wadsworth.org
   Computer Systems Support(v) 518 486-1697
   Wadsworth Center(f) 518 473-6384
   NYS Department of HealthHelp Desk 518 473-0773



IMPORTANT NOTICE: This e-mail and any attachments may contain
confidential or sensitive information which is, or may be, legally
privileged or otherwise protected by law from further disclosure.  It
is intended only for the addressee.  If you received this in error or
from someone who was not authorized to send it to you, please do not
distribute, copy or use it or any attachments.  Please notify the
sender immediately by reply e-mail and delete this from your
system. Thank you for your cooperation.

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

[Charles Curley]

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 looking at amdump o/p in previous
 email I think I must mention 'runtape' 

You don't have to use it, but you will find you get more efficient use
of your storage space if you do. If all your DLEs are the same size,
you won't need it because Amanda will even out the level 0 backups
across the dump cycle, and then all the dumps will be of similar size.

But that's a rare situation. More often there are one or two huge DLEs
and the rest are small. Then you have to accommodate the occasional
huge dump without wasting much space the rest of the time. Tape
spanning lets you accommodate the huge DLEs by spreading them across
multiple tapes. The rest of the time you use fewer tapes.

-- 

Charles Curley  /\ASCII Ribbon Campaign
Looking for fine software   \ /Respect for open standards
and/or writing?  X No HTML/RTF in email
http://www.charlescurley.com/ \No M$ Word docs in email

Key fingerprint = CE5C 6645 A45A 64E4 94C0  809C FFF6 4C48 4ECD DFDB

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

[Jon LaBadie]

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 job for her.
OTOH, your environment is simple enough (one host, one DLE,
50GB data) that self-management is not unreasonable.

Amanda's design addressed a problem that can be seen even
in your scheme; a monster dump once a week, tiny incrementals
the other days.  Amanda tries to balance the amount of data
dumped each day by spreading the level 0 dumps out over the
entire dumpcycle.  So each day some DLEs get incrementals
and a few others get full dumps.  Obviously with only one
DLE, it is difficult to spread the fulls out.

Sizing your vtapes is a concern.  Make them large enough to
hold a full dump and you waste lots of space on incremental
days.  To deal with this, choose a relatively small size
and tell Amanda that she can use multiple tapes if needed
(i.e. set runtapes to an appropriate number).  You will also
have to allow tape spanning, otherwise the media has to be
big enough to hold the entire DLE.  Spanning is not default.

You can create multiple DLEs from your current single DLE.
This is done using include and exclude directives.  For
example, you could have /var, /home, /usr/share, /usr ex-
cluding /usr/share, /opt, etc. Then a final DLE that starts
at / and is a catch-all which excludes the directories in
the other DLEs.

You asked what someone meant by oversubscribing your vtapes.
It means your vtapes are sized to use more than one per dump
and recognizing that, on average, the last one each day is
only half full.  My setup has 2300GB of space for vtapes
and I've created 100 x 25GB tapes, i.e. 2500GB if all are
full.  But because of those partially full tapes I actually
have 270GB of free space, only about 85% full.  I could
push it and add another 5 or 10 vtapes :)).

Jon
-- 
Jon H. LaBadie  j...@jgcomp.com
 JG Computing
 12027 Creekbend Drive  (703) 787-0884
 Reston, VA  20194  (703) 787-0922 (fax)

script help?

[Gene Heskett]

Greetings all;

My catchup script seems to be working with 2 exceptions, first being that I 
am not getting any emails from it, so I installed dnsmasq to see if that 
fixes that.

2nd, each pass through my catchup script loop elicits an error warning from 
the main script:

./flush.sh: line 173: [: !=: unary operator expected

from that script:
# or are we running as flush.sh

if [ $0 == ./flush.sh ] || [ $0 == ${MYDIR}/flush.sh ] || [ $0 == 
flush.sh ]; then
# we don't want amflush to disconnect or ask questions
if [ `/bin/ls /dumps` !=  ] ; then  ---line 173
echo Backup script running amflush -bf $CONFIGNAME  |tee -
a  $LOG

An error I don't recall having seen before.  Needs a translation to English 
for me, please. ;-)

-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
A pencil with no point needs no eraser.

Re: script help?

[John Hein]

Gene Heskett wrote at 12:04 -0400 on Jul 21, 2010:
  Greetings all;
  
  My catchup script seems to be working with 2 exceptions, first being that I 
  am not getting any emails from it, so I installed dnsmasq to see if that 
  fixes that.
  
  2nd, each pass through my catchup script loop elicits an error warning from 
  the main script:
  
  ./flush.sh: line 173: [: !=: unary operator expected
  
  from that script:
  # or are we running as flush.sh
  
  if [ $0 == ./flush.sh ] || [ $0 == ${MYDIR}/flush.sh ] || [ $0 == 
  flush.sh ]; then

== is a bash-ism.  Get in the habit of using = for posix compliance.
You'll thank yourself when you might have to run a script on a system
that doesn't use bash for sh(1) (bsd's, solaris).

Always put quotes around vars ($foo, $0, etc.) since vars
can contain strings with spaces confusing test(1) (aka [).

You don't need quotes around literals that you have written
(./flush.sh in your case above).  So in '[ $0 == ./flush.sh ]',
you have your quoting backwards (with respect to defensive script
writing).


  # we don't want amflush to disconnect or ask questions
  if [ `/bin/ls /dumps` !=  ] ; then  ---line 173
  echo Backup script running amflush -bf $CONFIGNAME  |tee -
  a  $LOG

Same deal (use quotes) for back-tick expressions (`cmd` or $(cmd)).
And that's your problem.  Looks like `ls /dumps` is providing empty
output.

example:

if [ `echo 1 2` = 1 ]; then echo y; else echo n; fi
[: 1: unexpected operator

 or

bash -c 'if [ `echo -n` !=  ]; then echo y; else echo n; fi'
bash: [: !=: unary operator expected


if [ `echo 1 2` = 1 ]; then echo y; else echo n; fi
n

Re: script help?

[Gene Heskett]

On Wednesday, July 21, 2010 01:10:50 pm John Hein did opine:

 Gene Heskett wrote at 12:04 -0400 on Jul 21, 2010:
   Greetings all;
   
   My catchup script seems to be working with 2 exceptions, first being
   that I am not getting any emails from it, so I installed dnsmasq to
   see if that fixes that.
   
   2nd, each pass through my catchup script loop elicits an error
   warning from the main script:
   
   ./flush.sh: line 173: [: !=: unary operator expected
   
   from that script:
   # or are we running as flush.sh
   
   if [ $0 == ./flush.sh ] || [ $0 == ${MYDIR}/flush.sh ] || [ $0 ==
   flush.sh ]; then
 
 == is a bash-ism.  Get in the habit of using = for posix compliance.
 You'll thank yourself when you might have to run a script on a system
 that doesn't use bash for sh(1) (bsd's, solaris).
 
 Always put quotes around vars ($foo, $0, etc.) since vars
 can contain strings with spaces confusing test(1) (aka [).
 
 You don't need quotes around literals that you have written
 (./flush.sh in your case above).  So in '[ $0 == ./flush.sh ]',
 you have your quoting backwards (with respect to defensive script
 writing).
 
   # we don't want amflush to disconnect or ask questions
   if [ `/bin/ls /dumps` !=  ] ; then 
   ---line 173
   
   echo Backup script running amflush -bf $CONFIGNAME 
   |tee -
   
   a  $LOG
 
 Same deal (use quotes) for back-tick expressions (`cmd` or $(cmd)).
 And that's your problem.  Looks like `ls /dumps` is providing empty
 output.
 
And that is all I care about, is whether or not its a null\r return.  If 
its an empty return, then there is no need to do the flush operation.

I'll give the  a shot for grins, thanks.  And I'll reread the bash docs 
too.

 example:
 
 if [ `echo 1 2` = 1 ]; then echo y; else echo n; fi
 [: 1: unexpected operator
 
  or
 
 bash -c 'if [ `echo -n` !=  ]; then echo y; else echo n; fi'
 bash: [: !=: unary operator expected
 
 
 if [ `echo 1 2` = 1 ]; then echo y; else echo n; fi
 n


-- 
Cheers, Gene
There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order.
-Ed Howdershelt (Author)
When asked by an anthropologist what the Indians called America before
the white men came, an Indian said simply Ours.
-- Vine Deloria, Jr.

plea for help: chio + chg-robot

[Dustin J. Mitchell]

A user on IRC asked me about support for chio, the FreeBSD equivalent
to mtx.  I know Amanda has chg-chio, but for some reason this wasn't
working well.

This particular user didn't hang around long enough to get things
working, but it did remind me that chg-robot doesn't support chio,
since I don't have a FreeBSD box with a changer attached.  The old
chg-chio script will continue to work as well as it ever has, but
chg-robot is a lot smarter about remembering where tapes are and
finding them quickly, so it'd be great to have support for FreeBSD as
well.

So: I'm looking for someone who knows a bit about chio and a bit of
Perl to put this particular piece of support together.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

Re: plea for help: chio + chg-robot

[Aaron J. Grier]

On Mon, Dec 14, 2009 at 11:20:03AM -0600, Dustin J. Mitchell wrote:
 A user on IRC asked me about support for chio, the FreeBSD equivalent
 to mtx.  I know Amanda has chg-chio, but for some reason this wasn't
 working well.
 
 This particular user didn't hang around long enough to get things
 working, but it did remind me that chg-robot doesn't support chio,
 since I don't have a FreeBSD box with a changer attached.  The old
 chg-chio script will continue to work as well as it ever has, but
 chg-robot is a lot smarter about remembering where tapes are and
 finding them quickly, so it'd be great to have support for FreeBSD as
 well.
 
 So: I'm looking for someone who knows a bit about chio and a bit of
 Perl to put this particular piece of support together.

I've worked on chg-chio a bit under NetBSD to drive my adic scalar 448
DLT changer.  it has a barcode scanner, but I've never bothered to
configure it since amanda's normal access pattern is sequential.  it
sounds like chg-robot would be an improvement.

it doesn't look like chio has diverged much between NetBSD and FreeBSD,
so I expect if I get it working under NetBSD it should work under
FreeBSD as well.

is the chg-robot script something I could use with 2.5.2p1, or do I need
to fire up subversion?  :)

-- 
  Aaron J. Grier | Not your ordinary poofy goof. | agr...@poofygoof.com

Re: plea for help: chio + chg-robot

[Dustin J. Mitchell]

On Mon, Dec 14, 2009 at 3:13 PM, Aaron J. Grier agr...@poofygoof.com wrote:
 I've worked on chg-chio a bit under NetBSD to drive my adic scalar 448
 DLT changer.  it has a barcode scanner, but I've never bothered to
 configure it since amanda's normal access pattern is sequential.  it
 sounds like chg-robot would be an improvement.

Quite, I'm sure.  I didn't realize chg-chio didn't support barcodes at all.

 it doesn't look like chio has diverged much between NetBSD and FreeBSD,
 so I expect if I get it working under NetBSD it should work under
 FreeBSD as well.

Cool!

 is the chg-robot script something I could use with 2.5.2p1, or do I need
 to fire up subversion?  :)

It needs the latest code - there are some tweaks to the new Changer
API that didn't make it into 2.6.1.

You'll see that there's an Amanda::Changer::robot::Interface subclass
that wraps 'mtx'.  I separated this out so that I would have the
option of implementing a direct-to-SCSI interface, but it turns out
this isn't such a great idea.  However, the abstraction should make it
easy to add in support for chio in parallel to that for mtx.

I don't know if it's any help, but both Subversion and Git are
options.  The git repo is at github.com/zmanda/amanda, and mirrors the
Sourceforge Subversion repository.

Dustin

-- 
Open Source Storage Engineer
http://www.zmanda.com

I accidentally ran chown and need help

[Matt Burkhardt]

I'm trying to set up a backup for a client machine running 8.10 Ubuntu
using an Ubuntu 8.04 server running 2.6.1b1 - but the version on the
client machine is an earlier one.

Anyway, I fat fingered something and changed the ownerships on all the
files in /usr/libexec/amanda and I'm now getting an error message that
says 

Amanda Backup Client Hosts Check

ERROR: 192.168.1.102: [/usr/libexec/amanda/runtar is not SUID root]
Client check: 1 host checked in 0.091 seconds.  1 problem found.

Right now, I have that set to root:disk - I basically copied the same
permissions from the /usr/libexec on the server.  Here's the directory
with the owners/groups

 ls -lh /usr/libexec/amanda
total 988K
-rwxr-xr-x 1 root root  29K 2008-07-30 19:29 amandad
-rw-r--r-- 1 root root  957 2008-07-30 19:28 amanda-sh-lib.sh
-rw-r--r-- 1 root root  135 2008-07-30 19:29 amcat.awk
-rwxr-xr-x 1 root root 6.6K 2008-07-30 19:29 amcleanupdisk
-rwxr-xr-x 1 root root  19K 2008-07-30 19:29 amidxtaped
-rwxr-xr-x 1 root root  43K 2008-07-30 19:29 amindexd
-rwxr-xr-x 1 root root 7.2K 2008-07-30 19:29 amlogroll
-rw-r--r-- 1 root root  18K 2008-07-30 19:29 amplot.awk
-rw-r--r-- 1 root root 3.3K 2008-07-30 19:29 amplot.g
-rw-r--r-- 1 root root 3.3K 2008-07-30 19:29 amplot.gp
-rwxr-xr-x 1 root root  11K 2008-07-30 19:29 amtrmidx
-rwxr-xr-x 1 root root 9.9K 2008-07-30 19:29 amtrmlog
drwxr-xr-x 2 root root 4.0K 2008-08-02 10:18 application
-rwxr-xr-- 1 root disk  15K 2008-07-30 19:29 calcsize
-rwxr-xr-x 1 root root  12K 2008-07-30 19:29 chg-chio
-rwxr-xr-x 1 root root 9.7K 2008-07-30 19:29 chg-chs
-rwxr-xr-x 1 root root 7.9K 2008-07-30 19:29 chg-disk
-rwxr-xr-x 1 root root 7.3K 2008-07-30 19:29 chg-iomega
-rwxr-xr-x 1 root root 5.1K 2008-07-30 19:29 chg-juke
-rw-r--r-- 1 root root 4.4K 2008-07-30 19:29 chg-lib.sh
-rwxr-xr-x 1 root root 6.8K 2008-07-30 19:29 chg-manual
-rwxr-xr-x 1 root root  14K 2008-07-30 19:29 chg-mcutil
-rwxr-xr-x 1 root root 4.8K 2008-07-30 19:29 chg-mtx
-rwxr-xr-x 1 root root  12K 2008-07-30 19:29 chg-multi
-rwxr-xr-x 1 root root 1.7K 2008-07-30 19:29 chg-null
-rwxr-xr-x 1 root root 4.0K 2008-07-30 19:29 chg-rait
-rwxr-xr-x 1 root root 6.8K 2008-07-30 19:29 chg-rth
-rwxr-xr-x 1 root root 196K 2008-07-30 19:29 chg-scsi
-rwxr-xr-x 1 root root  40K 2008-07-30 19:29 chg-zd-mtx
-rwxr-xr-x 1 root root  22K 2008-07-30 19:29 chunker
-rwxr-xr-x 1 root root  71K 2008-07-30 19:29 driver
-rwxr-xr-x 1 root disk  39K 2008-07-30 19:29 dumper
-rwxr-xr-- 1 root disk 6.8K 2008-07-30 19:29 killpgrp
-rwxr-xr-x 1 root root 5.8K 2008-07-30 19:29 noop
-rwxr-xr-x 1 root root 5.1K 2008-07-30 19:28 patch-system
-rwxr-xr-x 1 root disk  60K 2008-07-30 19:29 planner
-rwxr-xr-- 1 root disk 4.9K 2008-07-30 19:29 rundump
-rwxr-xr-- 1 root disk 7.8K 2008-07-30 19:29 runtar
-rwxr-xr-x 1 root root  27K 2008-07-30 19:29 selfcheck
-rwxr-xr-x 1 root root  48K 2008-07-30 19:29 sendbackup
-rwxr-xr-x 1 root root  51K 2008-07-30 19:29 sendsize
-rwxr-xr-x 1 root root  49K 2008-07-30 19:29 taper
-rwxr-xr-x 1 root root 4.1K 2008-07-30 19:29 versionsuffix

Thanks!


Matt Burkhardt, MSTM
President
Impari Systems, Inc.
502 Fairview Avenue
Frederick, MD  21701
[EMAIL PROTECTED]
www.imparisystems.com
(301) 682-7901

Re: I accidentally ran chown and need help

[Chad Kotil]

Here are my permissions. Notice all the files owned by root have the  
setUID permission set.


[EMAIL PROTECTED] amanda]$ ls -alrth
total 1.5M
-rw-r--r-- 1 amandabackup disk  956 Jun 25 18:11 amanda-sh-lib.sh
-rwxr-xr-x 1 amandabackup disk  48K Jun 25 18:11 amandad
drwxr-xr-x 3 root root 4.0K Jun 25 18:11 ..
-rwsr-x--- 1 root disk 9.9K Jun 25 18:11 rundump
-rwxr-xr-x 1 amandabackup disk  11K Jun 25 18:11 noop
-rwsr-x--- 1 root disk  13K Jun 25 18:11 killpgrp
-rwsr-x--- 1 root disk  29K Jun 25 18:11 calcsize
-rwxr-xr-x 1 amandabackup disk 8.6K Jun 25 18:11 versionsuffix
-rwxr-xr-x 1 amandabackup disk  73K Jun 25 18:11 sendsize
-rwxr-xr-x 1 amandabackup disk  77K Jun 25 18:11 sendbackup
-rwxr-xr-x 1 amandabackup disk  43K Jun 25 18:11 selfcheck
-rwsr-x--- 1 root disk  14K Jun 25 18:11 runtar
-rwxr-xr-x 1 amandabackup disk 5.1K Jun 25 18:11 patch-system
drwxr-xr-x 2 root root 4.0K Jun 25 18:11 application
-rwxr-xr-x 1 amandabackup disk 107K Jun 25 18:11 driver
-rwxr-xr-x 1 amandabackup disk  21K Jun 25 18:11 amtrmlog
-rwxr-xr-x 1 amandabackup disk  25K Jun 25 18:11 amtrmidx
-rwxr-xr-x 1 amandabackup disk  14K Jun 25 18:11 amlogroll
-rwxr-xr-x 1 amandabackup disk  84K Jun 25 18:11 amindexd
-rwxr-xr-x 1 amandabackup disk 132K Jun 25 18:11 taper
-rwsr-x--- 1 root disk 103K Jun 25 18:11 planner
-rwsr-x--- 1 root disk  65K Jun 25 18:11 dumper
-rwxr-xr-x 1 amandabackup disk  39K Jun 25 18:11 chunker
-rwxr-xr-x 1 amandabackup disk  16K Jun 25 18:11 amcleanupdisk
-rwxr-xr-x 1 amandabackup disk 267K Jun 25 18:11 chg-scsi
-rwxr-xr-x 1 amandabackup disk 6.8K Jun 25 18:11 chg-rth
-rwxr-xr-x 1 amandabackup disk 4.0K Jun 25 18:11 chg-rait
-rwxr-xr-x 1 amandabackup disk 1.7K Jun 25 18:11 chg-null
-rwxr-xr-x 1 amandabackup disk  12K Jun 25 18:11 chg-multi
-rwxr-xr-x 1 amandabackup disk 4.8K Jun 25 18:11 chg-mtx
-rwxr-xr-x 1 amandabackup disk  14K Jun 25 18:11 chg-mcutil
-rwxr-xr-x 1 amandabackup disk 6.8K Jun 25 18:11 chg-manual
-rw-r--r-- 1 amandabackup disk 4.0K Jun 25 18:11 chg-lib.sh
-rwxr-xr-x 1 amandabackup disk 5.1K Jun 25 18:11 chg-juke
-rwxr-xr-x 1 amandabackup disk 7.3K Jun 25 18:11 chg-iomega
-rwxr-xr-x 1 amandabackup disk 7.9K Jun 25 18:11 chg-disk
-rwxr-xr-x 1 amandabackup disk 9.7K Jun 25 18:11 chg-chs
-rwxr-xr-x 1 amandabackup disk  12K Jun 25 18:11 chg-chio
-rwxr-xr-x 1 amandabackup disk  32K Jun 25 18:11 amidxtaped
-rw-r--r-- 1 amandabackup disk 3.3K Jun 25 18:11 amplot.gp
-rw-r--r-- 1 amandabackup disk 3.3K Jun 25 18:11 amplot.g
-rw-r--r-- 1 amandabackup disk  18K Jun 25 18:11 amplot.awk
-rw-r--r-- 1 amandabackup disk  135 Jun 25 18:11 amcat.awk
drwxr-xr-x 3 root root 4.0K Jun 25 18:11 .
-rwxr-xr-x 1 amandabackup disk  40K Nov 19 16:14 chg-zd-mtx


On Dec 3, 2008, at 2:13 PM, Matt Burkhardt wrote:

I'm trying to set up a backup for a client machine running 8.10  
Ubuntu using an Ubuntu 8.04 server running 2.6.1b1 - but the version  
on the client machine is an earlier one.


Anyway, I fat fingered something and changed the ownerships on all  
the files in /usr/libexec/amanda and I'm now getting an error  
message that says


Amanda Backup Client Hosts Check

ERROR: 192.168.1.102: [/usr/libexec/amanda/runtar is not SUID root]
Client check: 1 host checked in 0.091 seconds.  1 problem found.

Right now, I have that set to root:disk - I basically copied the  
same permissions from the /usr/libexec on the server.  Here's the  
directory with the owners/groups


ls -lh /usr/libexec/amanda
total 988K
-rwxr-xr-x 1 root root  29K 2008-07-30 19:29 amandad
-rw-r--r-- 1 root root  957 2008-07-30 19:28 amanda-sh-lib.sh
-rw-r--r-- 1 root root  135 2008-07-30 19:29 amcat.awk
-rwxr-xr-x 1 root root 6.6K 2008-07-30 19:29 amcleanupdisk
-rwxr-xr-x 1 root root  19K 2008-07-30 19:29 amidxtaped
-rwxr-xr-x 1 root root  43K 2008-07-30 19:29 amindexd
-rwxr-xr-x 1 root root 7.2K 2008-07-30 19:29 amlogroll
-rw-r--r-- 1 root root  18K 2008-07-30 19:29 amplot.awk
-rw-r--r-- 1 root root 3.3K 2008-07-30 19:29 amplot.g
-rw-r--r-- 1 root root 3.3K 2008-07-30 19:29 amplot.gp
-rwxr-xr-x 1 root root  11K 2008-07-30 19:29 amtrmidx
-rwxr-xr-x 1 root root 9.9K 2008-07-30 19:29 amtrmlog
drwxr-xr-x 2 root root 4.0K 2008-08-02 10:18 application
-rwxr-xr-- 1 root disk  15K 2008-07-30 19:29 calcsize
-rwxr-xr-x 1 root root  12K 2008-07-30 19:29 chg-chio
-rwxr-xr-x 1 root root 9.7K 2008-07-30 19:29 chg-chs
-rwxr-xr-x 1 root root 7.9K 2008-07-30 19:29 chg-disk
-rwxr-xr-x 1 root root 7.3K 2008-07-30 19:29 chg-iomega
-rwxr-xr-x 1 root root 5.1K 2008-07-30 19:29 chg-juke
-rw-r--r-- 1 root root 4.4K 2008-07-30 19:29 chg-lib.sh
-rwxr-xr-x 1 root root 6.8K 2008-07-30 19:29 chg-manual
-rwxr-xr-x 1 root root  14K 2008-07-30 19:29 chg-mcutil
-rwxr-xr-x 1 root root 4.8K 2008-07-30 19:29 chg-mtx
-rwxr-xr-x 1 root root  12K 2008-07-30 19:29 chg-multi
-rwxr-xr-x 1 root root 1.7K 2008-07-30 19:29 chg-null
-rwxr-xr-x 1 root root 4.0K 2008-07-30 19:29 chg-rait