Re: [Bacula-users] LTO media type mixup
Am 02.03.2012 03:02, schrieb mark.berg...@uphs.upenn.edu: = I have replaced the previous LTO-1 drive by an LTO-2 one. = [...] When I mounted the current backup tape in the new = drive, Bacula [...] refused to use it. The only difference was that = it had media type LTO-1 and Bacula requested LTO-2. Did you make any change to the bacula configuration, specifically the Media Type definition in bacula-sd.conf? Indeed, I commented out the device section LTO-1 in bacula-sd.conf and uncommented the LTO-2 section instead, effectively changing both Name and Media Type from LTO-1 to LTO-2, and adapted bacula-dir.conf accordingly. I guess that was my mistake. = - If I connect two LTO drives of different levels to the = same Bacula server, is there a way to use the same tape = alternatingly in both drives as supported by the = hardware? (*without* losing the data on it, that is) Yes. Don't change the Media Type string in bacula-sd.conf. In our environment, we've migrated from LTO-2 = LTO-3 = LTO-4. The current library can read LTO-2 tapes, and can write to LTO-3 (as per the LTO standard). Our bacula-sd.conf definition for Media Type still has LTO-2, and that's written to all the tapes, including the LTO-3 and LTO-4 tapes, when they are labeled. Makes sense. In that case, wouldn't it be better if the default bacula-sd.conf distributed with Bacula would just say Media Type = LTO for all the LTO devices? That would reduce the temptation to change that field when changing drives. Another question: Is there a way to fix the mix-up I've created? update volume doesn't let me change the media type. Can I just run the MySQL query update Media set MediaType = 'LTO-2' where MediaType = 'LTO-1' or is there more to it? Thanks, Tilman -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
On Mon, Mar 05, 2012 at 11:00:06AM +0100, Tilman Schmidt wrote: Makes sense. In that case, wouldn't it be better if the default bacula-sd.conf distributed with Bacula would just say Media Type = LTO for all the LTO devices? That would reduce the temptation to change that field when changing drives. Well, 'Media Type' is misleading. It is more a 'Media Group'. every medium in the same group can be requested on every SD that support that 'Media Group'. It doesn't actually have anything to do with the mediums capabilities/size. Another question: Is there a way to fix the mix-up I've created? update volume doesn't let me change the media type. Can I just run the MySQL query update Media set MediaType = 'LTO-2' where MediaType = 'LTO-1' or is there more to it? Should work and worked elsewhere. Regards, Adrian -- LiHAS - Adrian Reyer - Hessenwiesenstraße 10 - D-70565 Stuttgart Fon: +49 (7 11) 78 28 50 90 - Fax: +49 (7 11) 78 28 50 91 Mail: li...@lihas.de - Web: http://lihas.de Linux, Netzwerke, Consulting Support - USt-ID: DE 227 816 626 Stuttgart -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
On 05/03/12 14:17, Adrian Reyer wrote: On Mon, Mar 05, 2012 at 11:00:06AM +0100, Tilman Schmidt wrote: Makes sense. In that case, wouldn't it be better if the default bacula-sd.conf distributed with Bacula would just say Media Type = LTO for all the LTO devices? That would reduce the temptation to change that field when changing drives. Well, 'Media Type' is misleading. It is more a 'Media Group'. every medium in the same group can be requested on every SD that support that 'Media Group'. It doesn't actually have anything to do with the mediums capabilities/size. Correct. To add confusion, any given bacula drive can only support one media type. The only way around this problem is to define extra drives for each media type supported (ie, LTO5, LTO4 and (read-only) LTO3). I don't know how well this solution will work in terms of concurrency, I'm about to try it as I've been told to reuse ~200 LTO4 tapes from another project. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
Am 05.03.2012 15:43, schrieb Alan Brown: On 05/03/12 14:17, Adrian Reyer wrote: Well, 'Media Type' is misleading. It is more a 'Media Group'. every medium in the same group can be requested on every SD that support that 'Media Group'. It doesn't actually have anything to do with the mediums capabilities/size. To add confusion, any given bacula drive can only support one media type. The only way around this problem is to define extra drives for each media type supported (ie, LTO5, LTO4 and (read-only) LTO3). What's wrong with just defining a single media type LTO covering all generations in use? -- Tilman Schmidt Phoenix Software GmbH Bonn, Germany -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
On Mon, Mar 5, 2012 at 10:44 AM, Tilman Schmidt t.schm...@phoenixsoftware.de wrote: Am 05.03.2012 15:43, schrieb Alan Brown: On 05/03/12 14:17, Adrian Reyer wrote: Well, 'Media Type' is misleading. It is more a 'Media Group'. every medium in the same group can be requested on every SD that support that 'Media Group'. It doesn't actually have anything to do with the mediums capabilities/size. To add confusion, any given bacula drive can only support one media type. The only way around this problem is to define extra drives for each media type supported (ie, LTO5, LTO4 and (read-only) LTO3). What's wrong with just defining a single media type LTO covering all generations in use? The problem is that you may want to separate your volumes so bacula does not want to try to write to an LTO2 tape on an LTO5 drive. Remember that with LTO drives you can read 2 generations back but only write 1 generation back. John -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
In the message dated: Mon, 05 Mar 2012 11:05:28 EST,
The pithy ruminations from John Drescher on
Re: [Bacula-users] LTO media type mixup were:
= On Mon, Mar 5, 2012 at 10:44 AM, Tilman Schmidt
= t.schm...@phoenixsoftware.de wrote:
= Am 05.03.2012 15:43, schrieb Alan Brown:
= On 05/03/12 14:17, Adrian Reyer wrote:
=
= Well, 'Media Type' is misleading. It is more a 'Media Group'. every
= medium in the same group can be requested on every SD that support that
= 'Media Group'. It doesn't actually have anything to do with the mediums
= capabilities/size.
Good explanation. I'd strongly support changing the name of the directive in
the configuration file to something like Media Group.
=
= To add confusion, any given bacula drive can only support one media type.
=
Yeah I guess it would make sense if Media Group was a list of supported
strings, not a single value.
In this model, sites with multiple devices (tape libraries, disk storage
arrays, etc) could use multiple media types, with each physical device being
assigned a list of media types (in a Media Group) that the device can use.
Furthermore, the device definition in bacula-sd.conf could list properties for
each media type. For example:
Device {
Name = lto5-changer
Media Group = LTO3, LTO4, LTO5
Media Options {
LTO3 = ReadOnly
LTO4 = ReadWrite
LTO5 = ReadWrite
}
}
Device {
Name = lto4-changer
Media Group = LTO2, LTO3, LTO4
Media Options {
LTO2 = ReadOnly
LTO3 = ReadWrite
LTO4 = ReadWrite
}
}
Device {
Name = File
Media Group = localNAS, remoteNAS_for_DR
Media Options {
localNAS = ReadWrite
remoteNAS_for_DR = ReadOnly
}
}
= The only way around this problem is to define extra drives for each
= media type supported (ie, LTO5, LTO4 and (read-only) LTO3).
=
= What's wrong with just defining a single media type LTO covering all
= generations in use?
=
=
= The problem is that you may want to separate your volumes so bacula
= does not want to try to write to an LTO2 tape on an LTO5 drive.
= Remember that with LTO drives you can read 2 generations back but only
= write 1 generation back.
When we moved to an LTO4 library, our solution to that issue was to update
the volume status on all the LTO-2 media to Read-Only (in the bacula
database, but this could have been done with the physical read-only tab
on each tape). Obviously, this would be a problem if we wanted to use
both the LTO3 and LTO4 libraries.
Thanks,
Mark
=
=
= John
=
=
--
= Try before you buy = See our experts in action!
= The most comprehensive online learning library for Microsoft developers
= is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
= Metro Style Apps, more. Free future releases when you subscribe now!
= http://p.sf.net/sfu/learndevnow-dev2
= ___
= Bacula-users mailing list
= Bacula-users@lists.sourceforge.net
= https://lists.sourceforge.net/lists/listinfo/bacula-users
=
--
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
On 05/03/12 18:11, mark.berg...@uphs.upenn.edu wrote: Yeah I guess it would make sense if Media Group was a list of supported strings, not a single value. I asked for this a few years ago. It never happened. -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] LTO media type mixup
On a Bacula server running openSUSE 11.4 and Bacula 5.0.2 I have replaced the previous LTO-1 drive by an LTO-2 one. The LTO-2 drive can read and write LTO-1 tapes, and so I naively assumed I should be able to continue using my old tapes without further ado. Not so. When I mounted the current backup tape in the new drive, Bacula insisted: Cannot find any appendable volumes. Please use the label command to create a new Volume for: Storage: LTO-2 (/dev/nst0) Pool: Daily Media type: LTO-2 The mounted tape was in pool Daily and state Append, but still Bacula refused to use it. The only difference was that it had media type LTO-1 and Bacula requested LTO-2. I then purged and relabeled it, losing all the backups on it. Purging alone did not help, but after relabeling, Bacula listed it as media type LTO-2 (even though it is of course still an LTO-1 tape) and willingly wrote the waiting backup to it. - Am I right to assume that it was the difference in the media type which caused Bacula to refuse that tape? - What is the rationale behind that behaviour? - What would happen if I tried to restore with the LTO-2 drive one of my old backups written with the LTO-1 drive? Would Bacula refuse that too? - If I connect two LTO drives of different levels to the same Bacula server, is there a way to use the same tape alternatingly in both drives as supported by the hardware? (*without* losing the data on it, that is) Thanks, Tilman -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] LTO media type mixup
In the message dated: Fri, 02 Mar 2012 02:08:27 +0100, The pithy ruminations from Tilman Schmidt on [Bacula-users] LTO media type mixup were: = On a Bacula server running openSUSE 11.4 and Bacula 5.0.2 = I have replaced the previous LTO-1 drive by an LTO-2 one. = The LTO-2 drive can read and write LTO-1 tapes, and so I = naively assumed I should be able to continue using my old = tapes without further ado. Sounds good so far. = = Not so. When I mounted the current backup tape in the new = drive, Bacula insisted: = = Cannot find any appendable volumes. = Please use the label command to create a new Volume for: = Storage: LTO-2 (/dev/nst0) = Pool: Daily = Media type: LTO-2 = = The mounted tape was in pool Daily and state Append, but = still Bacula refused to use it. The only difference was that = it had media type LTO-1 and Bacula requested LTO-2. Did you make any change to the bacula configuration, specifically the Media Type definition in bacula-sd.conf? = = I then purged and relabeled it, losing all the backups on = it. Purging alone did not help, but after relabeling, Bacula = listed it as media type LTO-2 (even though it is of course = still an LTO-1 tape) and willingly wrote the waiting backup = to it. = = - Am I right to assume that it was the difference in the = media type which caused Bacula to refuse that tape? It seems like that is correct. = = - What is the rationale behind that behaviour? As far as I know, the Media Type definition in bacula-sd.conf is not connected to the hardware in any way. In other words, the Media Type defines different categories, but the tape library doesn't report the media type to bacula. Bacula uses compares the required Media Type definition (from bacula-sd.conf) to the string written to the media when it was labeled. = = - What would happen if I tried to restore with the LTO-2 = drive one of my old backups written with the LTO-1 drive? = Would Bacula refuse that too? = = - If I connect two LTO drives of different levels to the = same Bacula server, is there a way to use the same tape = alternatingly in both drives as supported by the = hardware? (*without* losing the data on it, that is) = Yes. Don't change the Media Type string in bacula-sd.conf. In our environment, we've migrated from LTO-2 = LTO-3 = LTO-4. The current library can read LTO-2 tapes, and can write to LTO-3 (as per the LTO standard). Our bacula-sd.conf definition for Media Type still has LTO-2, and that's written to all the tapes, including the LTO-3 and LTO-4 tapes, when they are labeled. We ignore the Media Type data and use the tape numbers to help keep track of the different types of media. For example, all LTO-3 tapes have barcode labels with media ID numbers in the range 003000-003999. Mark = Thanks, = Tilman = = -- = Virtualization Cloud Management Using Capacity Planning = Cloud computing makes use of virtualization - but cloud computing = also focuses on allowing computing to be delivered as a service. = http://www.accelacomm.com/jaw/sfnl/114/51521223/ = ___ = Bacula-users mailing list = Bacula-users@lists.sourceforge.net = https://lists.sourceforge.net/lists/listinfo/bacula-users = -- Virtualization Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
