Tape mount time too long

[Jeff_Li]

Hi All,

Did someone have experince the connection time & tape mount time over 5 ~ 10 mins ? The tape library is LTO4 HP MSL6000 with 6 drive. Only one job is running at that moment. Media server is Windows 2008 64bit Ent. Master server is Windows 2003 and NBU 6.5.5 is running.
Appreciated to your response.

8/25/2010 3:04:16 PM - connecting
8/25/2010 3:04:24 PM - connected; connect time: 00:00:08
8/25/2010 3:10:48 PM - mounting EPN882
8/25/2010 3:14:38 PM - mounted; mount time: 00:03:50
8/25/2010 3:14:40 PM - positioning EPN882 to file 16
8/25/2010 3:16:04 PM - positioned EPN882; position time: 00:01:24
8/25/2010 3:16:04 PM - begin writing
8/25/2010 3:19:43 PM - end writing; write time: 00:03:39


8/25/2010 2:04:06 PM - connecting
8/25/2010 2:04:13 PM - connected; connect time: 00:00:07
8/25/2010 2:10:38 PM - mounting EPN882
8/25/2010 2:25:20 PM - mounted; mount time: 00:14:42
8/25/2010 2:25:22 PM - positioning EPN882 to file 15
8/25/2010 2:26:43 PM - positioned EPN882; position time: 00:01:21
8/25/2010 2:26:43 PM - begin writing
8/25/2010 2:30:24 PM - end writing; write time: 00:03:41

[Marianne]

Test tape mounts using robtest.

http://seer.entsupport.symantec.com/docs/274063.htm

Also: add VERBOSE to vm.conf (..\Veritas\volmgr\vm.conf) on server that has robotic control. Stop/start NBU services after adding VERBOSE. All robotic operations will be logged in Event Viewer Application log.

[J_H_Is_gone]

If you are ejecting or injecting tapes when you start the job.
It waits for that to complete before it will actually mount your tape.

[Jeff_Li]

Hi Marianne,

Where should I put ? Just put at the end is fine ? Here is the content of vm.conf

MM_SERVER_NAME = nbu1
MEDIA_ID_BARCODE_CHARS = 0 8 1:2:3:4:5:6
VERBOSE <- Put here ?

Thanks !
Jeff

[Jeff_Li]

Hi All,

Nothing doing that moment.
Ususally, all job completed within 5 mins but only 1 job taken over 20 ~ 30mins.
This happen suddenly.
Many thanks !

Jeff

[Marianne]

It will be fine there.
VERBOSE can be anywhere in vm.conf, as long as it's a line on its own.

[Jeff_Li]

Hi,

I just found some message about "starting tldcd"

Thanks !

[Andy_Welburn]

Where? When?

Can you post a fuller extract of the log?

tldcd is the tape library control daemon.

[Jeff_Li]

Hi,

In fact, same problem not happen again yet. Here just an application informational event for your reference. Thanks !

The description for Event ID ( 0 ) in Source ( NetBackup TLD Control Daemon ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: starting tldcd.

[Marianne]

You are viewing the Event log on the backup server itself?