To me it looks as this is in issue with either that specific tape drive or tape path to that device from affected system.  This is usually when you get CRC errors.

Definitely there is no problem with tape drives or control path, as it happens on 2 separate Quantum libraries and drives . Also under other backup software ( Netbackup, backupexec)  on the same libraries there is no problem. The problem shows only when labeling new tapes for first time in Networker . Subsequent labeling goes with no problem as well as backups and other library /drives operations.

jarek,

This is an odd.  Normally this message means that there is an issue with the hardware.  However, as you pointed out, the drives are working for other processes.

Just out of couriosity, have you run an inquire on the NetWorker server?  Also, it would help to have the daemon.raw file from the NetWorker server showing from the mount to the error.

If you need help rendering the daemon.raw file to gather that information, let me know.

Mark

jaroslawnowicki wrote: Definitely there is no problem with tape drives or control path, as it happens on 2 separate Quantum libraries and drives . Also under other backup software ( Netbackup, backupexec)  on the same libraries there is no problem. The problem shows only when labeling new tapes for first time in Netbackup . Subsequent labeling goes with no problem as well as backups and other library /drives operations.

I'm a bit confused now - are you saying that very same library is used by two different products?  You are also now mentioning problems with NetBackup... can you explain this a bit?  If using two products with same library, unless it is partitioned and unless both products are configured correctly, you may get collisions and also one to get tape from other...

Hi Hrvoje,

I made mistake in spelling - problems are only with Networker

To be clear about environment:

Installation A

Quantum I500 , 2 FC HP LTO4, Networker 7.6.2 ( fresh installation) on Windows 2008/2008 R2 ( we made several reinstallations)  - problems with inital labeling form the begining.

All firmwares and drivers up to date.

Installation B

Quantum I500 partitioned:

     - first partition : 6 FC HP LTO4 drives , Netbackup 7.1 - no problems with labeling the same tapes as used in installation A

     - second partition : 1 FC HP LTO4 drive, Networker 7.6.2 ( upgraded form 7.6.1 ) , Windows 2003 - on initial installation there were no problems with initial labeling; as problems appeared on installation A, we made tests here and problem is the same ( we didn't add new tapes for a long time so we noticed it just now ) ; the only change was LTO4 firmware upgrade in meantime and upgrade to 7.6.2.

Maybe there is some kind of problem with Networker and newest HP  LTO4 firmware in such situation ?

Rgrds,

jarek

Mark_Bellows wrote: jarek, This is an odd.  Normally this message means that there is an issue with the hardware.  However, as you pointed out, the drives are working for other processes. Just out of couriosity, have you run an inquire on the NetWorker server?  Also, it would help to have the daemon.raw file from the NetWorker server showing from the mount to the error. If you need help rendering the daemon.raw file to gather that information, let me know. Mark

Hi Mark,

This is odd to me as well. We lost a few days trying to figure it out on that new installation.

What do you mean by running an inquire on Networker server ?

If you could provide me with info how to render daemon.raw file (as I am a bit new to Networker,) I would make another test and present logged results.

Rgrds,

jarek

jaroslawnowicki wrote: Installation A Quantum I500 , 2 FC HP LTO4, Networker 7.6.2 ( fresh installation) on Windows 2008/2008 R2 ( we made several reinstallations)  - problems with inital labeling form the begining. All firmwares and drivers up to date. Installation B Quantum I500 partitioned:      - first partition : 6 FC HP LTO4 drives , Netbackup 7.1 - no problems with labeling the same tapes as used in installation A      - second partition : 1 FC HP LTO4 drive, Networker 7.6.2 ( upgraded form 7.6.1 ) , Windows 2003 - on initial installation there were no problems with initial labeling; as problems appeared on installation A, we made tests here and problem is the same ( we didn't add new tapes for a long time so we noticed it just now ) ; the only change was LTO4 firmware upgrade in meantime and upgrade to 7.6.2.

You most likely have one robotic... leading both software to use same control port to access robotic.  On NW backup server, do nsrjb -V.  This will give you, among other things, contol port (something like scsidev@X.Y.Z).  Then do following: sjirdtag X.Y.Z  This will give you inventory of library as defined (partitioned) and presented to system where robotics is.  Then you can try to move media which is giving you a problem: sjimm X.Y.Z slot drive .  Also, check if you are using library driver on system where robotics for NW is presented; rule of thumb is you should not use it as communication is being done over SJI interface which usually should not require any additional drivers.

Hrvoje is correct - there is going to be a conflict with the robitc control and use of tapes.

If you need to have one library used by both applications, I would suggest partitioning the library so that half of the slots and drives are used by NBU and half are used by NW.  There may be contention for the robotic arm to load and unload tapes.  The hardware vendor can advise you best on how to deal with portion of the configuration.

The command to use within NetWorker to configure the library as a shared device is jbconfig.  It would be best for you to read through the command in the command reference guide.  Below is an EXAMPLE of the command usage:

Example 1)

# jbconfig

1) Configure an AlphaStor Library.

2) Configure an Autodetected SCSI Jukebox.

3) Configure an Autodetected NDMP SCSI Jukebox.

4) Configure a SJI Jukebox.

5) Configure a STL Silo.

What kind of Jukebox are you configuring? [1] 2

These are the SCSI Jukeboxes currently attached to your system:

1) scsidev@0.6.0: EXB-210

2) scsidev@3.0.0: ADIC

Which one do you want to install? 1

Installing an ’EXB-210’ jukebox - scsidev@0.6.0

What name do you want to assign to this jukebox device?

Engineering

Turn NetWorker auto-cleaning on (yes/no) [yes]? yes

The following drives have been detected in this autochanger:

1> 8mm @ 1.1.0 ==> \\.\Tape0

2> 8mm @ 1.2.0 ==> \\.\Tape1 These are all the drives that

this auto changer possesses.

Do you want to change the model(s) or configure them as

shared or NDMP drives? (yes / no) [no] yes

Is (any path of) any drive intended for NDMP use? (yes / no)

[no] yes

Is any drive going to have more than one path defined? (yes

/ no) [no] yes

You will be prompted for multiple paths for each drive.

Pressing on a null default advances to the next

drive.

Please enter the device path information in one of the following

formats:

\\.\Tape0 --for local path or

host:device-path --for remote node or

host:drive-letter:directory path --for Windows disk file

Drive 1, element 82, system name = \\.\Tape0,

local bus / target / lun value = 1/1/0,

model 8mm

Device path 1 ? [\\.\Tape0]

Enter NDMP user name for host ’happy’? [] user1

Enter NDMP password (characters will not be echoed):

Device path 2 ? [] helium:/dev/rmt/1cbn

Enter NDMP user name for host ’helium’? [] user3

Enter NDMP password (characters will not be echoed):

Device path 3 ? []

Drive 2, element 83, system name = \\.\Tape1,

local bus / target / lun value = 1/2/0,

model 8mm

Device path 1 ? [\\.\Tape1]

Enter NDMP user name for host ’ableix.emc.com’? []

Device path 2 ? []

Only model 8mm drives have been detected.

Are all drives in this jukebox of the same model? (yes /

no) [yes] yes

A Dedicated Storage Node can backup only local data to its

devices. Should helium be configured as a Dedicated Storage Node?

(yes / no) [no] no

Jukebox has been added successfully

The following configuration options have been set:

> Jukebox description to the control port and model.

> Autochanger control port to the port at which we found it.

> NetWorker managed tape autocleaning on.

> At least one drive was defined with multiple paths. All

such drives are defined with a hardware identification as

well as a path value to avoid confusion by uniquely identifying

the drive. The hardware identification for all drives

which have one is always ’autochanger_name - Drive #’ where

"autochanger_name" is the name you gave to the autochanger

that was just defined, and the # symbol is the drive numer.

> Barcode reading to on.

> Volume labels that match the barcodes.

> Slot intended to hold cleaning cartridge to 1. Please

ensure that a cleaning cartridge is in that slot

> Number of times we will use a new cleaning cartridge to

12.

> Cleaning interval for the tape drives to 6 months.

You can review and change the characteristics of the

autochanger and its associated devices using NetWorker Management

Console.

Would you like to configure another jukebox? (yes/no) [no] no

====================================================================

Also, since you are new to NetWorker, I strongly recommend downloading and reviewing the admin guide, the disaster recovery guide and, as I mentioned, the command reference guide.

I do not have current NetBackup experience (it has been 4 years since I was an NBU admin), but I there used to a command to partition a library in the NBU command guide. The command in NBU 5.x was:

The bpsturep command modifies an existing NetBackup storage unit by replacing
selected storage-unit or storage-unit-group attributes in the NetBackup catalog. The
command line must include a label for the storage unit or a group name for the storage
unit group. The label or group name is the only storage-unit attribute that bpsturep
cannot modify.

I cannot venture any further with NBU than that - I am sure you understand!

One last note:

Learn and understand the following commands:

mminfo

scanner

These commands are very useful for reporting on savesets and restoring data from savesets that are no longer browseable - or even outside of the retention period.

Good luck and let us know if there is anything else we can do to help you!

Mark

Jarek,

The inquire program lists SCSI devices available. The inquire program returns INQUIRY data either for the named SCSI device (with the -a option), or for all SCSI devices attached to the system. In addition to the standard SCSI inquiry data, inquire now returns serial number information obtained from the Vital Product Data (VPD) pages supported by the devices that are being queried. There may be any- where from zero to eight different identifiers for each device, depending on which of the VPD pages that particular device supports.

You can find specific information and command options in the Command reference guide for the version of NetWorker you have.  You can locate the manuals at support.emc.com.

To render a daemon.raw file, navigate to the install path of NetWorker and into the Legato\nsr\logs folder.  Locate the daemon.raw file and copy it.  Next paste it into a folder – it can be the logs folder or you can create another one.  Rename the file to a name like the daemon_todays_date.raw.

Open the command prompt.  CD to the folder the copied daemon.raw file is in.  Run the following command:

nsr_render_log daemon_todays_date.raw  >>saemon_todays_date.log

When the command is finished, you will have a file that is human readable.  Open it up and look for the time frame listed in the error message.

I hope that helps!

Mark Bellows