Forum Discussion

Remco's avatar
Remco
Level 2
15 years ago

Drive scan host is not active

Hello world,

I've got a question and I want to see if you might be able to help me.
IHAC that is seeing some strange behaviour that I cannot immidately explain. Let me elaborate, his primary backups are running to a VTL. At a later stage this vtl is being drained to real tape. During these duplication jobs we're seeing the following issues.

9/20/2009 7:43:19 PM - begin Duplicate
9/20/2009 7:43:22 PM - requesting resource srv-bumedia02-rtl
9/20/2009 7:43:22 PM - requesting resource 700237
9/20/2009 7:43:22 PM - reserving resource 700237
9/20/2009 7:43:22 PM - reserving resource 700132
9/20/2009 7:43:26 PM - awaiting resource srv-bumedia02-rtl
  Reason: Drive scan host is not active., Media Server: srv-bumedia02,
  Robot Number: 0, Robot Type: ACS, Media ID: N/A, Drive Name: N/A,
  Volume Pool: Offsite, Storage Unit: srv-bumedia02-rtl, Drive Scan Host: N/A
9/20/2009 10:21:00 PM - awaiting resource srv-bumedia02-rtl
  Reason: Drives are in use., Media Server: not_selected,
  Robot Number: 0, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,
  Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
9/20/2009 10:21:13 PM - awaiting resource srv-bumedia02-rtl
  Reason: Drive scan host is not active., Media Server: srv-bumedia02,
  Robot Number: 0, Robot Type: ACS, Media ID: N/A, Drive Name: N/A,
  Volume Pool: Offsite, Storage Unit: srv-bumedia02-rtl, Drive Scan Host: N/A
...
...
9/21/2009 8:25:35 AM - awaiting resource srv-bumedia02-rtl
  Reason: Drive scan host is not active., Media Server: srv-bumedia02,
  Robot Number: 0, Robot Type: ACS, Media ID: N/A, Drive Name: N/A,
  Volume Pool: Offsite, Storage Unit: srv-bumedia02-rtl, Drive Scan Host: N/A
9/21/2009 8:26:11 AM - awaiting resource srv-bumedia02-rtl
  Reason: Drives are in use., Media Server: not_selected,
  Robot Number: 0, Robot Type: NONE, Media ID: N/A, Drive Name: N/A,
  Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A
9/21/2009 8:26:18 AM - awaiting resource srv-bumedia02-rtl
  Reason: Drive scan host is not active., Media Server: srv-bumedia02,
  Robot Number: 0, Robot Type: ACS, Media ID: N/A, Drive Name: N/A,
  Volume Pool: Offsite, Storage Unit: srv-bumedia02-rtl, Drive Scan Host: N/A
9/21/2009 8:26:23 AM - reserved resource 700237
9/21/2009 8:26:23 AM - reserved resource 700132
9/21/2009 8:26:23 AM - granted resource 700098
9/21/2009 8:26:23 AM - granted resource LTO4_04_FC01
9/21/2009 8:26:23 AM - granted resource srv-bumedia02-rtl


Basic question, what exactly is causing these messages. Has the mediaserver lost its connection to the robot?

Any input is highly appreciated,
Thanks in advance,
Remco

  • Hello All,

    Issue is solved, it turned out that customer also was running sanmanager (qlogic) on one of the mediaserver. This brings its own portmapper and disables/kills the sunrpc (libattach) portmapper. After restarting these services, all problems disappeared.

    Thanks for thinking with me!

    remco

4 Replies

  • What is the status of these duplication jobs? 

    Have you looked at the media server to check that all the services/daemons are running?  You may also want to check your nbrb log  (resource broker) on the master to see more detail and possible cause.
  • If you use SSO, I bet they are assigned and in use by a diffrent  media server. I see a lot of "Drives are in use" messages. " Drive scan host is not active" means the drive(s) are  active on a diffrent media server.


  • run: vmdareq -D <drive name>

    This will show you the list of media servers who share the drive and you will see which one is the SCAN_HOST if the media server who owns the control of the drive is down or cannot see the drive you need to fix it on that specific media server or move the drive to a different media server so it can be the new SCAN_HOST or drive controler.

    You can use: vmdareq -release -D <drivename> to release the drive from that SCAN_HOST
    and: vmdareq -reserve -D <drive name> -H <media server> to move the drive to a different media server.
    so you can register the drive:
    vmdareq -register -D <drive name> -H <media server> -S scan_ability

    hope this helps.
    regards.

  • Hello All,

    Issue is solved, it turned out that customer also was running sanmanager (qlogic) on one of the mediaserver. This brings its own portmapper and disables/kills the sunrpc (libattach) portmapper. After restarting these services, all problems disappeared.

    Thanks for thinking with me!

    remco