Backup exec reports empty library

classic Classic list List threaded Threaded
9 messages Options
Reply | Threaded
Open this post in threaded view
|

Backup exec reports empty library

tomse
Hello.

I've tried setting mhVTL up on 2 linux dists, Ubuntu and CentOS, both latest versions.

My problem is that backup exec 12 reports the library slots to be empty. Though I can see both tape drive and library.

The setup.

1. Windows 2003 server with Backup Exec 12 and iSCSI initiator
2. Linux box (Ubuntu/CentOS) stgt and mhVTL

Install and config has been done through mhvtl-gui with a few minor tweaks, like start up script copied to /etc/init.d.
copied tgt conf file with proper name so stgt is properly configured at boot time (it seems there's a bug in mhvtl-gui, or just the lack of feature, well that isn't important atm).

on the linux box everything seems to work when using mt / tar / mtx.. basically I can load/unload a tape, dump to /dev/nst0 using tar, restore the dumped contents (very simple test).

mtx -f /dev/sg8 inventory
returns nothing

mtx -f /dev/sg8 status
returns a fully configured library
(sample line below)
Storage Element 1: Full  :VolumeTag=H00001L2

Tape size is 400000M
Drive configured LTO2 (I also tried with LTO6 and LTO6 tapes)



cheers
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

Mark Harvey
Administrator
Is it possible to post the /etc/mhvtl/device.conf and /etc/mhvtl/library_contents.* files so I can review the configuration.

Many thanks.

On Thu, Sep 25, 2014 at 12:02 AM, tomse [via mhVTL - A Linux Virtual Tape Library] <[hidden email]> wrote:
Hello.

I've tried setting mhVTL up on 2 linux dists, Ubuntu and CentOS, both latest versions.

My problem is that backup exec 12 reports the library slots to be empty. Though I can see both tape drive and library.

The setup.

1. Windows 2003 server with Backup Exec 12 and iSCSI initiator
2. Linux box (Ubuntu/CentOS) stgt and mhVTL

Install and config has been done through mhvtl-gui with a few minor tweaks, like start up script copied to /etc/init.d.
copied tgt conf file with proper name so stgt is properly configured at boot time (it seems there's a bug in mhvtl-gui, or just the lack of feature, well that isn't important atm).

on the linux box everything seems to work when using mt / tar / mtx.. basically I can load/unload a tape, dump to /dev/nst0 using tar, restore the dumped contents (very simple test).

mtx -f /dev/sg8 inventory
returns nothing

mtx -f /dev/sg8 status
returns a fully configured library
(sample line below)
Storage Element 1: Full  :VolumeTag=H00001L2

Tape size is 400000M
Drive configured LTO2 (I also tried with LTO6 and LTO6 tapes)



cheers



If you reply to this email, your message will be added to the discussion below:
http://mhvtl-a-linux-virtual-tape-library.966029.n3.nabble.com/Backup-exec-reports-empty-library-tp4025868.html
To start a new topic under mhVTL - A Linux Virtual Tape Library, email [hidden email]
To unsubscribe from mhVTL - A Linux Virtual Tape Library, click here.
NAML

Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

tomse
Of course.
I'll post it monday :-)
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

tomse
Please see attached files, and disregard the extensions ;-)

device.txt

mhvtl.txt

targets.txt

The tapes, or should I say directories exist in /opt/mhvtl
if I let the Linux box do a backup to a tape, I can see data inside the chosen "tape" being added.

Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

BriGuy
I've encoutered same situation.
Can any one give some help?
Thks!

[root@RHEL4FB ~]# more /etc/mhvtl/mhvtl.conf

# Home directory for config file(s)
MHVTL_CONFIG_PATH=/etc/mhvtl

# Default media capacity (500 M)
CAPACITY=10240

# Set default verbosity [0|1|2|3]
VERBOSE=1

# Set kernel module debuging [0|1]
VTL_DEBUG=0
[root@RHEL4FB ~]# more /etc/mhvtl/device.conf          

VERSION: 5

# VPD page format:
# <page #> <Length> <x> <x+1>... <x+n>
# NAA format is an 8 hex byte value seperated by ':'
# Note: NAA is part of inquiry VPD 0x83
#
# Each 'record' is separated by one (or more) blank lines.
# Each 'record' starts at column 1
# Serial num max len is 10.
# Compression: factor X enabled 0|1
#     Where X is zlib compression factor        1 = Fastest compression
#                                               9 = Best compression
#     enabled 0 == off, 1 == on
#
# fifo: /var/tmp/mhvtl
# If enabled, data must be read from fifo, otherwise daemon will block
# trying to write.
# e.g. cat /var/tmp/mhvtl (in another terminal)

Library: 10 CHANNEL: 00 TARGET: 00 LUN: 00
 Vendor identification: IBM
 Product identification: 03584L22
 Product revision level: 4.02
 Unit serial number: XYZZY_A
 NAA: 10:22:33:44:ab:00:00:00
 Home directory: /opt/tapes
 PERSIST: False
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 11 CHANNEL: 00 TARGET: 01 LUN: 00
 Library ID: 10 Slot: 01
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Unit serial number: XYZZY_A1
 Product revision level: A3K6
 NAA: 10:22:33:44:ab:00:01:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 12 CHANNEL: 00 TARGET: 01 LUN: 01
 Library ID: 10 Slot: 02
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: A3K6
 Unit serial number: XYZZY_A2
 NAA: 10:22:33:44:ab:00:02:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 13 CHANNEL: 00 TARGET: 01 LUN: 02
 Library ID: 10 Slot: 03
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: A3K6
 Unit serial number: XYZZY_A3
 NAA: 10:22:33:44:ab:00:03:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Drive: 14 CHANNEL: 00 TARGET: 01 LUN: 03
 Library ID: 10 Slot: 04
 Vendor identification: IBM
 Product identification: ULT3580-TD5
 Product revision level: A3K6
 Unit serial number: XYZZY_A4
 NAA: 10:22:33:44:ab:00:04:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
 fifo: /var/tmp/mhvtl

Library: 30 CHANNEL: 00 TARGET: 08 LUN: 00
 Vendor identification: STK
 Product identification: L80
 Unit serial number: XYZZY_B
 NAA: 30:22:33:44:ab:00:08:00
 Home directory: /opt/tapes
 PERSIST: False
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 31 CHANNEL: 00 TARGET: 09 LUN: 00
 Library ID: 30 Slot: 01
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B1
 NAA: 30:22:33:44:ab:00:09:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 32 CHANNEL: 00 TARGET: 10 LUN: 00
 Library ID: 30 Slot: 02
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B2
 NAA: 30:22:33:44:ab:00:10:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 33 CHANNEL: 00 TARGET: 11 LUN: 00
 Library ID: 30 Slot: 03
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B3
 NAA: 30:22:33:44:ab:00:11:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

Drive: 34 CHANNEL: 00 TARGET: 12 LUN: 00
 Library ID: 30 Slot: 04
 Vendor identification: STK
 Product identification: T10000B
 Unit serial number: XYZZY_B4
 NAA: 30:22:33:44:ab:00:12:00
 Compression: factor 1 enabled 1
 Compression type: lzo
 Backoff: 400
# fifo: /var/tmp/mhvtl

[root@RHEL4FB ~]#   more /etc/scst.conf
# Header Info
setup_id 0x1234
# Changer Devices
HANDLER dev_changer {
  DEVICE 4:0:0:0
  DEVICE 4:0:8:0
}
# Tape device
HANDLER dev_tape {
  DEVICE 4:0:1:0
  DEVICE 4:0:1:1
  DEVICE 4:0:1:2
  DEVICE 4:0:1:3
  DEVICE 4:0:9:0
  DEVICE 4:0:10:0
  DEVICE 4:0:11:0
  DEVICE 4:0:12:0
}
# Qlogic Devices
TARGET_DRIVER qla2x00t {
    TARGET 21:00:00:24:ff:06:37:16 {
          LUN 0 4:0:0:0
          LUN 1 4:0:1:0
          LUN 2 4:0:1:1
          LUN 3 4:0:1:2
          LUN 4 4:0:1:3
          LUN 5 4:0:8:0
          LUN 6 4:0:9:0
          LUN 7 4:0:10:0
          LUN 8 4:0:11:0
          LUN 9 4:0:12:0
            enabled 1
  }
}
TARGET_DRIVER iscsi {  
        enabled 1  
 
        TARGET iqn.2015-04.com.inspur:mhvtl {
        enabled 1  
                rel_tgt_id 5  
                cpu_mask 1  
          LUN 0 4:0:0:0
          LUN 1 4:0:1:0
          LUN 2 4:0:1:1
          LUN 3 4:0:1:2
          LUN 4 4:0:1:3
  }
}
[root@RHEL4FB ~]#  ^C
[root@RHEL4FB ~]# more /etc/mhvtl/library_contents.10

Drive 1:
Drive 2:
Drive 3:
Drive 4:

Picker 1:

MAP 1:
MAP 2:
MAP 3:
MAP 4:

# Slot 1 - ?, no gaps
# Slot N: [barcode]
# [barcode]
# a barcode is comprised of three fields: [Leading] [identifier] [Trailing]
# Leading "CLN" -- cleaning tape
# Leading "W" -- WORM tape
# Leading "NOBAR" -- will appear to have no barcode
# If the barcode is at least 8 character long, then the last two characters are
 Trailing
# Trailing "S3" - SDLT600
# Trailing "X4" - AIT-4
# Trailing "L1" - LTO 1, "L2" - LTO 2, "L3" - LTO 3, "L4" - LTO 4, "L5" - LTO 5
# Trailing "LT" - LTO 3 WORM, "LU" -  LTO 4 WORM, "LV" - LTO 5 WORM
# Trailing "L6" - LTO 6, "LW" - LTO 6 WORM
# Trailing "TA" - T10000+
# Trailing "TZ" - 9840A, "TY" - 9840B, "TX" - 9840C, "TW" - 9840D
# Trailing "TV" - 9940A, "TU" - 9940B
# Trailing "JA" - 3592+
# Trailing "JB" - 3592E05+
# Trailing "JW" - WORM 3592+
# Trailing "JX" - WORM 3592E05+
# Trailing "D7" - DLT7000 media (DLT IV)
#
Slot 1: E01001L5
Slot 2: E01002L5
Slot 3: E01003L5
Slot 4: E01004L5
Slot 5: E01005L5
Slot 6: E01006L5
Slot 7: E01007L5
Slot 8: E01008L5
Slot 9: E01009L5
Slot 10: E01010L5
Slot 11: E01011L5
Slot 12: E01012L5
Slot 13: E01013L5
Slot 14: E01014L5
Slot 15: E01015L5
Slot 16: E01016L5
Slot 17: E01017L5
Slot 18: E01018L5
Slot 19: E01019L5
Slot 20: E01020L5
Slot 21:
Slot 22: CLN101L5
Slot 23: CLN102L5
Slot 24:
Slot 25:
Slot 26:
Slot 27:
Slot 28:
Slot 29:
Slot 30: F01030L5
Slot 31: F01031L5
Slot 32: F01032L5
Slot 33: F01033L5
Slot 34: F01034L5
Slot 35: F01035L5
Slot 36: F01036L5
Slot 37: F01037L5
Slot 38: F01038L5
Slot 39: F01039L5
[root@RHEL4FB ~]#  
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

Mark Harvey
Administrator
I notice several fifo: /.... are uncommented. Do you have something reading from these fifo pipes ?

The fifo is of limited size and will block updates from the vtl code waiting on updates..

Simply running "cat /var/tmp/mhvtl" will suffice (command will not return, until the pipe is closed - i.e. the vtl is shutdown)

Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

BriGuy
Thanks a lot.
Seems very bizarre.The STK vtl works just fine.But seems robot of 3854 cannot work rightly,so I cannot see any tape in slot.
Here is the content:
[root@RHEL4FB ~]#  cat /var/tmp/mhvtl
Mon Apr 13 08:43:58 2015 - 11: - Initialising v2
Mon Apr 13 08:43:58 2015 - 12: - Initialising v2
Mon Apr 13 08:43:58 2015 - 13: - Initialising v2
Mon Apr 13 08:43:58 2015 - 14: - Initialising v2
Mon Apr 13 08:43:58 2015 - 10: - Initialising v2
Mon Apr 13 08:43:59 2015 - 10: - Robot Inventory
Mon Apr 13 08:44:02 2015 - 11: - Idle
Mon Apr 13 08:44:02 2015 - 12: - Idle
Mon Apr 13 08:44:02 2015 - 13: - Idle
Mon Apr 13 08:44:02 2015 - 14: - Idle
Mon Apr 13 08:44:11 2015 - 10: - Idle
Mon Apr 13 09:29:56 2015 - 10: - Moving E01001L5 from Storage slot 1 to drive 1
Mon Apr 13 09:29:57 2015 - 11: - Loading NULL media
Mon Apr 13 09:29:58 2015 - 11: - Loaded
Mon Apr 13 09:30:08 2015 - 10: - Idle
Mon Apr 13 09:31:58 2015 - 11: - Reading
Mon Apr 13 09:31:58 2015 - 11: - Load failed
Mon Apr 13 09:32:03 2015 - 11: - Loaded
Mon Apr 13 09:32:37 2015 - 11: - Load failed
Mon Apr 13 09:32:42 2015 - 11: - Loaded
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

Mark Harvey
Administrator
BriGuy wrote
Thanks a lot.
Seems very bizarre.The STK vtl works just fine.But seems robot of 3854 cannot work rightly,so I cannot see any tape in slot.
OK, this 'bizarre' behaviour can be explained simply enough :)

The mhVTL is a 'pet' project used to assist myself in my paid day-to-day job. Feature development often stops once NetBackup is happy - rather than follow thru to match the given standard.

Some of the 'emulations' (or personalizations) are more complete than others - depending on available documentation (and interest) at the development point in time.

Mostly, NetBackup has been working fine for many years, and many of the bug fixes since have been due to bug reports from other backup applications or an attempt to fix op code xx to more accurately match the standards.
Regards from Australia
Mark Harvey
Reply | Threaded
Open this post in threaded view
|

Re: Backup exec reports empty library

BriGuy
Hi,Harvey
Thanks anyway.
Since you have opened source generously,wish some day some one can provide more function.
Thank you a lot for giving us a VTL to use.