Bacula-users

Re: [Bacula-users] Can't access tape device after upgrade from v2.4.4-1 to 5.0.2-1

2010-07-19 10:10:53
Subject: Re: [Bacula-users] Can't access tape device after upgrade from v2.4.4-1 to 5.0.2-1
From: Rory Campbell-Lange <rory AT campbell-lange DOT net>
To: Dan Langille <dan AT langille DOT org>
Date: Mon, 19 Jul 2010 15:06:51 +0100
Hi Dan

Thanks for your email.

On 19/07/10, Dan Langille (dan AT langille DOT org) wrote:
> On 7/19/2010 4:21 AM, Rory Campbell-Lange wrote:
> Oh.... your tapes should still be usable after the upgrade.  I think
> you need to concentrate on that problem first. Ignore all others.
> 
> >Is the best thing to do to:
> 
> Your objective is missing from this post.  What are you trying to
> accomplish?  What is your goal?

My objective, foolishly ommitted from my email, is to start from scratch
after the upgrade. I have now managed to do so by using the brute force
method to relabel the tapes as the catalogues from my tests failed to
follow from 2.4.4 to 5.0.2.

(For reference, I note how I did that here:

1. Stop the bacula SD daemons
    (note that only bacula-sd needs to be stopped)

2. Use the "brute force" approach to "clear" the tape 

    mtx -f /dev/sg4 load <tape_no>
    mt -f /dev/nst0 rewind
    mt -f /dev/nst0 weof
    mtx -f /dev/sg4 unload <tape_no>

3. label

    bconsole
    label
    ... follow instructions ...
)

-- 
Rory Campbell-Lange
rory AT campbell-lange DOT net

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users