Author: Kathryn Hemness <kfhemness AT ucdavis DOT edu>
Date: Wed, 9 Apr 2008 15:25:28 -0700 (PDT)
Hi Dan and NetBackup advisors, I realize this subject is from a very old thread (Tue, 15 Aug 2006) but the situation from 2006 most closely resembles my current problem. I've been upgrading my RHEL3
Author: mjohnson at entertainmentpartners.com (Matthew Johnson)
Date: Tue, 5 Dec 2006 10:57:17 -0800
Hello all, I am having problems with the make_scsi_dev command as well. I have read every thing out there and some are great ideas, however when I run it on a particular system it crashed the system,
Near as I can tell, make_scsi_dev determines which drives are connected to the system and creates symlinks to those corresponding devices. When you load your 'st' module, you get something like this:
In 5.1 MP1+ placing ENABLE_AUTO_PATH_CORRECTION in the vm.conf file should also help. Additionally, it creates files in /dev/sg/ that point to any SCSI device (disks, tape, controllers, etc. This app
We've got a few media servers running NetBackup 5.1 MP5 under Linux (RedHat AS4) and we're having no end of problems with FC attached tape drive device mappings. I see when NB starts it runs make_scs
If your environment is SSO I will give you 2 tips. Wait for the completion of all backups and then run make_scsi_dev. Then configure all Linux drives. After that comment (#) the make_scsi_dev line at
If you have people installing new hba drivers or re-arranging hba's on your systems without your knowledge, then you clearly have procedural issues to deal with. Not a technical problem. In any event