Re: [Bacula-users] Mixed Drives
In the message dated: Fri, 23 Jan 2009 22:47:41 +0100, The pithy ruminations from Jesper Krogh on Re: [Bacula-users] Mixed Drives were: = Alan Brown wrote: = On Wed, 21 Jan 2009, Ryan Novosielski wrote: = = Media type is completely arbitrary. If you want the new drive to be able = to share media with the old drive, you should use the same media type. Yes. When we replaced our LTO-2 changer with LTO-3 (keeping the LTO-2 media), I simply added the new LTO-3 tapes to pools with the LTO-2 media type. [SNIP!] = This is something I raised at least 2-3 years ago. There's been no = apparent interest in solving the issue and likely won't be until one of = the developers encounters the problem. I'd like to see that supported, but it's not critical...and there are probably a huge number of vendor-specific corner cases. = = Supported media lists would have to cover r/w and ro support: = = LTO drives are r/w compatible with the previous generation, but read only = with the one before that. = = ie: LTO4 can R/W LTO3 tapes, but only read LTO2 and can't read LTO1 at all. = = (As far as I can tell these are _minimum_ specs for LTO. It's perfectly = possible to exceed them and produce a LTO4 drive which can write LTO2 and = read LTO1, but as far as I know no manufacturer has done that yet. That's my understanding too. AIT is a different story, with a well-defined compatability spec. That's the advantage when the hardware is made by just one company. = = Sure about that?, the marketing material I've seen shows only read-only = capabillity one-generation back and write capabillity one generation, if = the tape was un-used before (never written before). Nope. I've had no problem reading and re-writing LTO-2 media in LTO-3 drives. Of course, this is a small sample set for anyone to use as the basis for a purchase or for defining rules in software. Mark = = = -- = Jesper = The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
= This is something I raised at least 2-3 years ago. There's been no = apparent interest in solving the issue and likely won't be until one of = the developers encounters the problem. I'd like to see that supported, but it's not critical...and there are probably a huge number of vendor-specific corner cases. What I like about what I specified in my earlier e-mail is that the user determines which compatibility they want. If they only want to read a previous gen tape, even though the drive could write to it, they can specify that. That would prevent having to code some nasty stuff to cover all the corner cases. Robert LeBlanc College of Life Sciences Computer Support Brigham Young University (801) 422-1882 lebl...@byu.edu -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
On Wed, 21 Jan 2009, Ryan Novosielski wrote: Media type is completely arbitrary. If you want the new drive to be able to share media with the old drive, you should use the same media type. If not, you should have them be different. It would be best if you could make a supported media type list, to allow for backward compatible drives, but that's not possible at present. This is something I raised at least 2-3 years ago. There's been no apparent interest in solving the issue and likely won't be until one of the developers encounters the problem. Supported media lists would have to cover r/w and ro support: LTO drives are r/w compatible with the previous generation, but read only with the one before that. ie: LTO4 can R/W LTO3 tapes, but only read LTO2 and can't read LTO1 at all. (As far as I can tell these are _minimum_ specs for LTO. It's perfectly possible to exceed them and produce a LTO4 drive which can write LTO2 and read LTO1, but as far as I know no manufacturer has done that yet. -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
Hi, 23.01.2009 15:03, Alan Brown wrote: On Wed, 21 Jan 2009, Ryan Novosielski wrote: Media type is completely arbitrary. If you want the new drive to be able to share media with the old drive, you should use the same media type. If not, you should have them be different. It would be best if you could make a supported media type list, to allow for backward compatible drives, but that's not possible at present. This is something I raised at least 2-3 years ago. There's been no apparent interest in solving the issue and likely won't be until one of the developers encounters the problem. Possible... of course, a patch or even a detailed description how to implement this would be appreciated, I'm sure (and I know there already is some detail available but can't find the thread(s) at the moment :-) Supported media lists would have to cover r/w and ro support: LTO drives are r/w compatible with the previous generation, but read only with the one before that. ie: LTO4 can R/W LTO3 tapes, but only read LTO2 and can't read LTO1 at all. (As far as I can tell these are _minimum_ specs for LTO. It's perfectly possible to exceed them and produce a LTO4 drive which can write LTO2 and read LTO1, but as far as I know no manufacturer has done that yet. I don't know any such drive either... Anyway, personally, I'd like to see Alans suggestions implemented, but neither I nor any of my customers has a setup where that would be needed... the original poster might think about how they could support development here :-) Arno -- Arno Lehmann IT-Service Lehmann Sandstr. 6, 49080 Osnabrück www.its-lehmann.de -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Arno Lehmann wrote: Hi, 23.01.2009 15:03, Alan Brown wrote: On Wed, 21 Jan 2009, Ryan Novosielski wrote: Media type is completely arbitrary. If you want the new drive to be able to share media with the old drive, you should use the same media type. If not, you should have them be different. It would be best if you could make a supported media type list, to allow for backward compatible drives, but that's not possible at present. This is something I raised at least 2-3 years ago. There's been no apparent interest in solving the issue and likely won't be until one of the developers encounters the problem. Possible... of course, a patch or even a detailed description how to implement this would be appreciated, I'm sure (and I know there already is some detail available but can't find the thread(s) at the moment :-) Supported media lists would have to cover r/w and ro support: LTO drives are r/w compatible with the previous generation, but read only with the one before that. ie: LTO4 can R/W LTO3 tapes, but only read LTO2 and can't read LTO1 at all. (As far as I can tell these are _minimum_ specs for LTO. It's perfectly possible to exceed them and produce a LTO4 drive which can write LTO2 and read LTO1, but as far as I know no manufacturer has done that yet. I don't know any such drive either... Anyway, personally, I'd like to see Alans suggestions implemented, but neither I nor any of my customers has a setup where that would be needed... the original poster might think about how they could support development here :-) I would appreciate this as it saves us some money. I have DDS4, DAT72, and DLT8000 drives. I can use DDS3, DDS4, DAT72, and DLT-IV tapes -- and the price difference I recall being significant, at least where we are allowed to buy from (public institution). There are times where I'm limited to using one drive where I could be using another, but it's no showstopper. - -- _ _ _ _ ___ _ _ _ |Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II |$| |__| | | |__/ | \| _| |novos...@umdnj.edu - 973/972.0922 (2-0922) \__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEUEARECAAYFAkl6M88ACgkQmb+gadEcsb6n3ACfZnYQmI6AkCoi8jpM25Xx+EzG kgkAmMdOMY58mgCGWvA2mvZDj2lmph0= =J9O8 -END PGP SIGNATURE- begin:vcard fn:Ryan Novosielski n:Novosielski;Ryan org:UMDNJ;IST/AST adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103 email;internet:novos...@umdnj.edu title:Systems Programmer II tel;work:(973) 972-0922 tel;fax:(973) 972-7412 tel;pager:(866) 20-UMDNJ x-mozilla-html:FALSE version:2.1 end:vcard -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
Alan Brown wrote: On Wed, 21 Jan 2009, Ryan Novosielski wrote: Media type is completely arbitrary. If you want the new drive to be able to share media with the old drive, you should use the same media type. If not, you should have them be different. It would be best if you could make a supported media type list, to allow for backward compatible drives, but that's not possible at present. This is something I raised at least 2-3 years ago. There's been no apparent interest in solving the issue and likely won't be until one of the developers encounters the problem. Supported media lists would have to cover r/w and ro support: LTO drives are r/w compatible with the previous generation, but read only with the one before that. ie: LTO4 can R/W LTO3 tapes, but only read LTO2 and can't read LTO1 at all. (As far as I can tell these are _minimum_ specs for LTO. It's perfectly possible to exceed them and produce a LTO4 drive which can write LTO2 and read LTO1, but as far as I know no manufacturer has done that yet. Sure about that?, the marketing material I've seen shows only read-only capabillity one-generation back and write capabillity one generation, if the tape was un-used before (never written before). -- Jesper -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
Anyway, personally, I'd like to see Alans suggestions implemented, but neither I nor any of my customers has a setup where that would be needed... the original poster might think about how they could support development here :-) Believe me, I'd love to support the development of Bacula especially in this area. Unfortunately, we have a serious shortage of man power in my area to dedicate to coding. I would be willing to help with testing to a point as we only have the one library and it is used for production, it would have to be sandboxed to certain tapes for testing purposes. An overall idea that I've had is when a job is run, it finds the pool to put/get the data and knows the SD, the DIR queries the SD to find the supported media for the devices then selects a drive that matches the media from the volume. This would remove the Media directive from the SD directive in the Director config. To extend this to support backwards compatibility, the media directive could be split into media-write, media-read directives which could either support multiple directives or a delimited list of media the drive supports. This list would be fed back to the director when the DIR queries the SD for devices to choose an appropriate device. When we have time and resources we will look into coding it, but don't hold your breath on that being anytime soon. Robert LeBlanc College of Life Sciences Computer Support Brigham Young University (801) 422-1882 lebl...@byu.edu -- This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
[Bacula-users] Mixed Drives
We just added a new LTO4 drive to our Neo8000 with two existing LTO3
drives. I thought I would just have to add the drive into the device
section of the SD with a new Media Label and things would be set to go.
Well, the director wants to know what media type the SD is. I've created
a second SD block in the dir pointing to the same SD with a different
name and Media type. Doing a stat storage on both result in the same
info.
Can someone please help me to make sure I'm not shooting myself in the
foot. I was able to label a tape using the LTO3 SD directive with the
LTO4 device, but it did show up as LTO3 media despite what the device
setting is. Relabeling the tape with the second directive did label the
tape as LTO4.
Bacula-sd.conf:
Autochanger {
Name = Neo8000
Device = Drive-0
Device = Drive-1
Device = Drive-2
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Changer Device = /dev/tape/neo8000
}
Device {
Name = Drive-0 #
Drive Index = 0
Media Type = LTO3
Archive Device = /dev/tape/drive0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Device {
Name = Drive-1 #
Drive Index = 1
Media Type = LTO3
Archive Device = /dev/tape/drive1
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# # If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Device {
Name = Drive-2 #
Drive Index = 2
Media Type = LTO4
Archive Device = /dev/tape/drive2
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# # If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Bacula-dir.conf
Storage {
Name = Neo8000
Address = 192.168.3.18 # N.B. Use a fully qualified name here
SDPort = 9103
Password = mysecretpassword
Media Type = LTO3 # must be same as MediaType in
Storage daemon
Device = Neo8000
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 2
}
Storage {
Name = Neo8000-LTO4
Address = 192.168.3.18 # N.B. Use a fully qualified name here
SDPort = 9103
Password = mysecretpassword
Media Type = LTO4 # must be same as MediaType in
Storage daemon
Device = Neo8000
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 2
}
Robert LeBlanc
College of Life Sciences Computer Support
Brigham Young University
(801) 422-1882
lebl...@byu.edu
--
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
Re: [Bacula-users] Mixed Drives
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert LeBlanc wrote:
We just added a new LTO4 drive to our Neo8000 with two existing LTO3
drives. I thought I would just have to add the drive into the device
section of the SD with a new Media Label and things would be set to go.
Well, the director wants to know what media type the SD is. I’ve created
a second SD block in the dir pointing to the same SD with a different
name and Media type. Doing a stat storage on both result in the same info.
Can someone please help me to make sure I’m not shooting myself in the
foot. I was able to label a tape using the LTO3 SD directive with the
LTO4 device, but it did show up as LTO3 media despite what the device
setting is. Relabeling the tape with the second directive did label the
tape as LTO4.
Bacula-sd.conf:
Autochanger {
Name = Neo8000
Device = Drive-0
Device = Drive-1
Device = Drive-2
Changer Command = /etc/bacula/scripts/mtx-changer %c %o %S %a %d
Changer Device = /dev/tape/neo8000
}
Device {
Name = Drive-0 #
Drive Index = 0
Media Type = LTO3
Archive Device = /dev/tape/drive0
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Device {
Name = Drive-1 #
Drive Index = 1
Media Type = LTO3
Archive Device = /dev/tape/drive1
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# # If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Device {
Name = Drive-2 #
Drive Index = 2
Media Type = LTO4
Archive Device = /dev/tape/drive2
AutomaticMount = yes; # when device opened, read it
AlwaysOpen = yes;
RemovableMedia = yes;
RandomAccess = no;
AutoChanger = yes
Spool Directory = /backup/spool
Maximum Network Buffer Size = 65536
# Enable the Alert command only if you have the mtx package loaded
# Alert Command = sh -c 'tapeinfo -f %c |grep TapeAlert|cat'
# # If you have smartctl, enable this, it has more info than tapeinfo
Alert Command = sh -c 'smartctl -H -l error %c'
}
Bacula-dir.conf
Storage {
Name = Neo8000
Address = 192.168.3.18 # N.B. Use a fully qualified name here
SDPort = 9103
Password = mysecretpassword
Media Type = LTO3 # must be same as MediaType in
Storage daemon
Device = Neo8000
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 2
}
Storage {
Name = Neo8000-LTO4
Address = 192.168.3.18 # N.B. Use a fully qualified name here
SDPort = 9103
Password = mysecretpassword
Media Type = LTO4 # must be same as MediaType in
Storage daemon
Device = Neo8000
Autochanger = yes # enable for autochanger device
Maximum Concurrent Jobs = 2
}
Media type is completely arbitrary. If you want the new drive to be able
to share media with the old drive, you should use the same media type.
If not, you should have them be different. It would be best if you could
make a supported media type list, to allow for backward compatible
drives, but that's not possible at present.
- --
_ _ _ _ ___ _ _ _
|Y#| | | |\/| | \ |\ | | |Ryan Novosielski - Systems Programmer II
|$| |__| | | |__/ | \| _| |novos...@umdnj.edu - 973/972.0922 (2-0922)
\__/ Univ. of Med. and Dent.|IST/AST - NJMS Medical Science Bldg - C630
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkl3hOYACgkQmb+gadEcsb7bAgCgv68ZhhlECIMoUJ0T56F4qEAk
dYYAn1zOP7x6oIMervvL3+tYBz8kg2FH
=EM0h
-END PGP SIGNATURE-
begin:vcard
fn:Ryan Novosielski
n:Novosielski;Ryan
org:UMDNJ;IST/AST
adr;dom:MSB C630;;185 South Orange Avenue;Newark;NJ;07103
email;internet:novos...@umdnj.edu
title:Systems Programmer II
tel;work:(973) 972-0922
tel;fax:(973) 972-7412
tel;pager:(866) 20-UMDNJ
x-mozilla-html:FALSE
version:2.1
end:vcard
Re: [Bacula-users] Mixed drives in Autochanger
On Jan 16, 2008 11:08 AM, Robert LeBlanc [EMAIL PROTECTED] wrote: We have a Neo8000 with 2 LTO-3 drives. We are looking into the possibility of adding 2 LTO-4 drives to it. Can Bacula handle two different types of drives in the same autochanger? I don't need the LTO-4 drives to read the LTO-3 tapes or anything. I believe others on this list have reported this working. Make the drives have different media types in the device definition. John - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse012070mrt/direct/01/ ___ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
