Re: amvault and label problem as of 3.4.5
On 20/11/17 10:54 AM, Winston Sorfleet wrote:
Thanks Nathan... I have tried the command line without any -o options:
|/usr/sbin/amvault --latest-fulls --dest-storage "HP G2 Robot" vtl
|
Now the response is "FATAL amvault no 'tape-device' property
specified" which doesn't make sense to me, since the storage
definition includes a tapedev string.
|/define changer "HP G2" {//
//tpchanger "chg-robot:/dev/LTOchanger"//
//property "tape-device" "0=tape:/dev/nst0"//
//property "use-slots" "1-7"//
//property "load-poll" "13s poll 5s"//
//device-property "LEOM" "TRUE" //
//}/
...
define storage "HP G2 Robot" {||
||tapedev "HP G2"||
||tapetype "LTO2"||
||tapepool "$r"||
||tpchanger "chg-robot:/dev/LTOchanger"||
||labelstr "Vault-[1-7]"||
||autolabel "Vault-%" any||
||}|
|Try with:
define storage "HP G2 Robot" {||
||tapetype "LTO2"||
||tapepool "$r"||
||tpchanger "HP G2"||
||labelstr "Vault-[1-7]"||
||autolabel "Vault-%" any||
||}
|
Nevertheless, if I manually specify a tapedev in the amvault command line
|/usr/sbin/amvault -otapedev='HP G2' --latest-fulls --dest-storage
"HP G2 Robot" vtl
|
/Now/ I see the robot cycling through tapes to no avail (progress?),
finally going through the cleaning slot, but... well here is the logfile:|
|
|INFO amvault amvault pid 20654
START amvault date 20171120102558
STATS amvault hostname flamen
INFO amvault vaulting
DISK amvault flamen.romanus.ca
/
DISK amvault flamen.romanus.ca
/home
DISK amvault pomerium.romanus.ca
/
DISK amvault forum.romanus.ca
/
INFO taper Slot 5 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 6 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 7 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 8 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper error from mtx: Unloading drive 0 into Storage Element
8...Cleaning Cartridge Installed and Ejected
FATAL amvault error from mtx: Unloading drive 0 into Storage
Element 8...Cleaning Cartridge Installed and Ejected
FINISH driver fake driver finish
FINISH amvault date 20171120102558 time 226
INFO amvault pid-done 20654
FATAL amvault Taper::Scan did not quit at
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Taper/Scan.pm line
347 during global destruction.
|
Obvious oddities:
1. "|device in error: Can't open tape device HP G2: No such file or
directory"?|
2. "|driver fake driver finish"? |
|
|Configuration files and log in
https://drive.google.com/open?id=0B_vw5EcgO15lXzJwQVk3UXpkTUE
||
||
On 2017-11-18 08:44 PM, Nathan Stratton Treadway wrote:
On Sat, Nov 18, 2017 at 18:20:14 -0500, Winston Sorfleet wrote:
As of 3.4.5 --dst-changer is deprecated, so I have to use a storage
template from amanda.conf. I have defined a storage template as follows:
|define storage "HP G2 Robot" {
tapedev "HP G2"
tapetype "LTO2"
#tpchanger "chg-robot:/dev/LTOchanger"
#autolabel "Vault-%"
labelstr "Vault-[1-7]"
}
|
Now the monthly cron line /I thought/ should be:
|/usr/sbin/amvault -q -otapetype="LTO2" -otapecycle=5
-olabelstr="Vault-[1-7]" -otapedev="HP G2" --latest-fulls
--dest-storage "HP G2 Robot" vtl|
However, this gives me an error message:
|argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
errors processing config file
|
I haven't looked at your full config yet, but a few quick notes:
* The underlying cause of this particular error message from the -o
option is that Amanda is explicitly looking a String object for the
template value. You should be able to work around that quirk
with nested quotes, something like
amvault ... '-olabelstr="Vault-[1-7]"' ...
* That aside, though, it really should sufficient to define the labelstr
in the storage definition itself; you shouldn't need to specify the
labelstr on the command line at all. If that's not working it's
probably worth further investigation to figure out why. (In fact,
with the use of a 'policy' on the HP storage, you shouldn't need any of
the "-o" options on the amvault line, I believe.)
* The Wiki page
http://wiki.zmanda.com/index.php/How_To:Copy_Data_from_Volume_to_Volume
might have some useful hints.
Nathan
-
Re: amvault and label problem as of 3.4.5
Thanks Nathan... I have tried the command line without any -o options:
|/usr/sbin/amvault --latest-fulls --dest-storage "HP G2 Robot" vtl
|
Now the response is "FATAL amvault no 'tape-device' property specified"
which doesn't make sense to me, since the storage definition includes a
tapedev string.
|/define changer "HP G2" {//
// tpchanger "chg-robot:/dev/LTOchanger"//
// property "tape-device" "0=tape:/dev/nst0"//
// property "use-slots" "1-7"//
// property "load-poll" "13s poll 5s"//
// device-property "LEOM" "TRUE" //
//}/
...
define storage "HP G2 Robot" {||
|| tapedev "HP G2"||
|| tapetype "LTO2"||
|| tapepool "$r"||
|| tpchanger "chg-robot:/dev/LTOchanger"||
|| labelstr "Vault-[1-7]"||
|| autolabel "Vault-%" any||
||}|
Nevertheless, if I manually specify a tapedev in the amvault command line
|/usr/sbin/amvault -otapedev='HP G2' --latest-fulls --dest-storage
"HP G2 Robot" vtl
|
/Now/ I see the robot cycling through tapes to no avail (progress?),
finally going through the cleaning slot, but... well here is the logfile:|
|
|INFO amvault amvault pid 20654
START amvault date 20171120102558
STATS amvault hostname flamen
INFO amvault vaulting
DISK amvault flamen.romanus.ca /
DISK amvault flamen.romanus.ca /home
DISK amvault pomerium.romanus.ca /
DISK amvault forum.romanus.ca /
INFO taper Slot 5 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 6 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 7 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper Slot 8 is a device in error: Can't open tape device HP
G2: No such file or directory, autolabel disabled
INFO taper error from mtx: Unloading drive 0 into Storage Element
8...Cleaning Cartridge Installed and Ejected
FATAL amvault error from mtx: Unloading drive 0 into Storage Element
8...Cleaning Cartridge Installed and Ejected
FINISH driver fake driver finish
FINISH amvault date 20171120102558 time 226
INFO amvault pid-done 20654
FATAL amvault Taper::Scan did not quit at
/usr/lib/x86_64-linux-gnu/amanda/perl/Amanda/Taper/Scan.pm line 347
during global destruction.
|
Obvious oddities:
1. "|device in error: Can't open tape device HP G2: No such file or
directory"?|
2. "|driver fake driver finish"? |
|
|Configuration files and log in
https://drive.google.com/open?id=0B_vw5EcgO15lXzJwQVk3UXpkTUE
||
||
On 2017-11-18 08:44 PM, Nathan Stratton Treadway wrote:
> On Sat, Nov 18, 2017 at 18:20:14 -0500, Winston Sorfleet wrote:
>> As of 3.4.5 --dst-changer is deprecated, so I have to use a storage
>> template from amanda.conf. I have defined a storage template as follows:
>>
>> |define storage "HP G2 Robot" {
>> tapedev "HP G2"
>> tapetype "LTO2"
>> #tpchanger "chg-robot:/dev/LTOchanger"
>> #autolabel "Vault-%"
>> labelstr "Vault-[1-7]"
>> }
>> |
>>
>> Now the monthly cron line /I thought/ should be:
>>
>> |/usr/sbin/amvault -q -otapetype="LTO2" -otapecycle=5
>> -olabelstr="Vault-[1-7]" -otapedev="HP G2" --latest-fulls
>> --dest-storage "HP G2 Robot" vtl|
>>
>> However, this gives me an error message:
>>
>> |argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
>> argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
>> errors processing config file
>> |
> I haven't looked at your full config yet, but a few quick notes:
>
> * The underlying cause of this particular error message from the -o
> option is that Amanda is explicitly looking a String object for the
> template value. You should be able to work around that quirk
> with nested quotes, something like
>
> amvault ... '-olabelstr="Vault-[1-7]"' ...
>
> * That aside, though, it really should sufficient to define the labelstr
> in the storage definition itself; you shouldn't need to specify the
> labelstr on the command line at all. If that's not working it's
> probably worth further investigation to figure out why. (In fact,
> with the use of a 'policy' on the HP storage, you shouldn't need any of
> the "-o" options on the amvault line, I believe.)
>
> * The Wiki page
> http://wiki.zmanda.com/index.php/How_To:Copy_Data_from_Volume_to_Volume
> might have some useful hints.
>
> Nathan
>
>
>
> Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
> Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
> GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
> Key fin
Re: amvault and label problem as of 3.4.5
On Sat, Nov 18, 2017 at 18:20:14 -0500, Winston Sorfleet wrote:
> As of 3.4.5 --dst-changer is deprecated, so I have to use a storage
> template from amanda.conf. I have defined a storage template as follows:
>
> |define storage "HP G2 Robot" {
> tapedev "HP G2"
> tapetype "LTO2"
> #tpchanger "chg-robot:/dev/LTOchanger"
> #autolabel "Vault-%"
> labelstr "Vault-[1-7]"
> }
> |
>
> Now the monthly cron line /I thought/ should be:
>
> |/usr/sbin/amvault -q -otapetype="LTO2" -otapecycle=5
> -olabelstr="Vault-[1-7]" -otapedev="HP G2" --latest-fulls
> --dest-storage "HP G2 Robot" vtl|
>
> However, this gives me an error message:
>
> |argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
> argument 'Vault-[1-7]': labelstr template or MATCH_AUTOLABEL expected
> errors processing config file
> |
I haven't looked at your full config yet, but a few quick notes:
* The underlying cause of this particular error message from the -o
option is that Amanda is explicitly looking a String object for the
template value. You should be able to work around that quirk
with nested quotes, something like
amvault ... '-olabelstr="Vault-[1-7]"' ...
* That aside, though, it really should sufficient to define the labelstr
in the storage definition itself; you shouldn't need to specify the
labelstr on the command line at all. If that's not working it's
probably worth further investigation to figure out why. (In fact,
with the use of a 'policy' on the HP storage, you shouldn't need any of
the "-o" options on the amvault line, I believe.)
* The Wiki page
http://wiki.zmanda.com/index.php/How_To:Copy_Data_from_Volume_to_Volume
might have some useful hints.
Nathan
Nathan Stratton Treadway - [email protected] - Mid-Atlantic region
Ray Ontko & Co. - Software consulting services - http://www.ontko.com/
GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt ID: 1023D/ECFB6239
Key fingerprint = 6AD8 485E 20B9 5C71 231C 0C32 15F3 ADCD ECFB 6239
