I apologize — that was too flippant of me.
I actually still HAVE client nodes running 2.6, I think.
But I wouldn’t newly install 2.6 on a server, especially one with such nice
new tapes as LTO5 and
LTO6 tape drives. I am only just now moving into the modern world of LTO5
tapes.
I envy you that. :)
Anyway, I hope we can get you running better.
Deb
On Feb 3, 2015, at 4:42 PM, Debra S Baddorf <[email protected]> wrote:
> Ahhh. Well, Windows 3.0 is a stable release too, but I’m not using it
> anymore. ;)
> But I’ll let others say whether amanda 2.6.1 is effectively *that* ancient.
>
> Deb
>
>
> On Feb 3, 2015, at 4:27 PM, <[email protected]>
> <[email protected]> wrote:
>
>> Hi Debra,
>>
>> OEL or RHEL count the same, it's not a big deal to build a package on them.
>> The question for me in that case is that 2.6.1p2 stated as stable release
>> and doesn't matter that it is old it should work.
>>
>> Kind Regards,
>> Dmitry Lozitskiy
>>
>> -----Original Message-----
>> From: Debra S Baddorf [mailto:[email protected]]
>> Sent: Wednesday, February 04, 2015 10:54 AM
>> To: [email protected]
>> Cc: Debra S Baddorf; AMANDA users
>> Subject: Re: amanda 2.6.1p2-8 issue
>>
>> I don't know anything about ORACLE Linux 6, but from a
>> Scientific packaging of RedHat Linux (versions 5 and 6) I quite easily
>> build my own fresh versions of Amanda from
>> http://www.amanda.org/download.php
>> all of the time.
>> You need C compilers, and perl, and a few other things, but it couldn't hurt
>> to try it in a /tmp area.
>>
>> Deb Baddorf
>> Fermilab
>>
>>>
>>> On 02/03/2015 03:47 PM, [email protected] wrote:
>>>> Hi Jean-Louis,
>>>>
>>>> There is only Amanda 2.6.1p1 is available in public repository for
>>>> Oracle Linux 6.
>>>> Are you suggesting to build a fresh version of Amanda from there:
>>>> http://www.amanda.org/download.php?
>>>>
>>>> I thought it was a space issue after migration and I replaced LTO5
>>>> tapedrive and LTO-4 tapes that we used with Amanda 2.5 to LTO-6
>>>> tapedrive and LTO-6 tapes.
>>>> Usually 800GB was enough, but now I use 2.5TB tapes and still have
>>>> the same issues, I doubt that it is a space issue as I calculated all
>>>> space required for backup manually and even if count that there are
>>>> all Leve 0 backups they require less than 1 TB space.
>>>>
>>>> I attached amdump trace and backup log from the last Amanda run. May
>>>> be you can say something looking at them?
>>>>
>>>> Kind Regards,
>>>> Dmitry Lozitskiy
>>>>
>>>>
>>>> -----Original Message-----
>>>> From: Jean-Louis Martineau [mailto:[email protected]]
>>>> Sent: Wednesday, February 04, 2015 9:38 AM
>>>> To: [email protected]; [email protected]
>>>> Subject: Re: amanda 2.6.1p2-8 issue
>>>>
>>>> Why upgrade to an old version? You should upgrade again.
>>>>
>>>> It's hard to say something because you didn't posted enough information.
>>>> I will guess is that amanda need more tape space to do the backup
>>>> according to your configuration, you should increase runtapes.
>>>>
>>>> Jean-Louis
>>>>
>>>> On 02/03/2015 03:07 PM, [email protected] wrote:
>>>>> Hello,
>>>>>
>>>>> I just recently migrated amanda software from version 2.5.0p2:
>>>>>
>>>>> # uname -a
>>>>>
>>>>> Linux asp-al-backup 2.6.18-128.2.1.4.25.el5xen #1 SMP Tue Mar 23
>>>>> 12:43:27 EDT 2010 i686 i686 i386 GNU/Linux
>>>>>
>>>>> # rpm -qa | grep amanda
>>>>>
>>>>> amanda-server-2.5.0p2-8.el5
>>>>>
>>>>> amanda-client-2.5.0p2-8.el5
>>>>>
>>>>> amanda-2.5.0p2-9.el5
>>>>>
>>>>> to a 2.6.1p1 version:
>>>>>
>>>>> # uname -a
>>>>>
>>>>> Linux asp-al-backup 3.8.13-55.1.5.el6uek.x86_64 #2 SMP Wed Jan 28
>>>>> 17:03:28 PST 2015 x86_64 x86_64 x86_64 GNU/Linux
>>>>>
>>>>> # rpm -qa | grep amanda
>>>>>
>>>>> amanda-server-2.6.1p2-8.el6.x86_64
>>>>>
>>>>> amanda-client-2.6.1p2-8.el6.x86_64
>>>>>
>>>>> amanda-2.6.1p2-8.el6.x86_64
>>>>>
>>>>> Before the upgrade my backups were running smoothly without a fail,
>>>>> but after the upgrade I'm facinig partially backups every amanda run.
>>>>>
>>>>> The error it finishes with:
>>>>>
>>>>> Hostname: asp-al-backup
>>>>>
>>>>> Org : PMKRS Daily
>>>>>
>>>>> Config : DailySet1
>>>>>
>>>>> Date : February 3, 2015
>>>>>
>>>>> These dumps were to tape DailySet1-03.
>>>>>
>>>>> *** A TAPE ERROR OCCURRED: [runtapes volumes already written].
>>>>>
>>>>> There are 76826M of dumps left in the holding disk.
>>>>>
>>>>> Run amflush to flush them to tape.
>>>>>
>>>>> The next tape Amanda expects to use is: 1 new tape.
>>>>>
>>>>> FAILURE DUMP SUMMARY:
>>>>>
>>>>> alfresco /apps/alfresco/backups lev 0 FAILED "runtapes volumes
>>>>> already written"
>>>>>
>>>>> alfresco /apps/alfresco/backups lev 0 FAILED [too many taper
>>>>> retries]
>>>>>
>>>>> asp-al-backup /backup lev 1 FAILED [out of holding
>>>>> space in degraded mode]
>>>>>
>>>>> alfresco /apps/alfresco/backups lev 0: partial taper: No space
>>>>> left on device
>>>>>
>>>>> Does anyone have a clue what these messages are talking about.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Dmitry.
>>>>>
>>>>>
>>>>> Disclaimer: Asparona is part of the Deloitte group of companies.
>>>>> Deloitte refers to the New Zealand member firm of Deloitte Touche
>>>>> Tohmatsu
>>>> Limited.
>>>>> The information contained in this document is confidential to the
>>>>> addressee(s) and may be legally privileged. Any view or opinions
>>>>> expressed are those of the author and may not be those of the
>>>>> organisation to which the author belongs. No guarantee or
>>>>> representation is made that this communication is free of errors,
>>>>> viruses or interference. If you have received this e-mail message in
>>>>> error
>>>> please delete it and notify me.
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Disclaimer: Asparona is part of the Deloitte group of companies. Deloitte
>> refers to the New Zealand member firm of Deloitte Touche Tohmatsu Limited.
>>
>> The information contained in this document is confidential to the
>> addressee(s) and may be legally privileged. Any view or opinions expressed
>> are those of the author and may not be those of the organisation to which
>> the author belongs. No guarantee or representation is made that this
>> communication is free of errors, viruses or interference. If you have
>> received this e-mail message in error please delete it and notify me.
>
