DRIVE ISSUE

[wannawin]

I am  new in Netbackup and i want to know that how to configure drive  by command line.

And how to rename drive by command line.

Can someone plz help me out.

[AlanTLR]

Devices and Tape Drives are generally automatically named by NetBackup (you might try looking into sgscan, tpautoconf, and scan (ref: http://www.symantec.com/business/support/index?page=content&id=TECH53659 ).  You can change the base of this name at the discovery (I only know how to do this from the GUI), but if you're just looking to create a stoorage unit (disk and tape), you want to use /usr/openv/netbackup/bin/admincmd/bpstuadd.

USAGE: bpstuadd -label storage_unit_label [-verbose]

                    -path path_name [-dt disk_type]

                        or

                    -dp disk_pool [-dt disk_type]

                        or

                    -density density_type [-rt robot_type -rn robot_number]

                    [-host host_name]

                    [-cj max_jobs]

                    [-odo on_demand_only_flag]

                    [-mfs max_fragment_size]

                    [-maxmpx mpx_factor]

                    [-nh NDMP_attach_host]

                    [-tt transfer_throttle]

                    [-nodevhost]

                    [-flags flags]

                    [-cf clearfiles]

                    [-hwm high_water_mark]

                    [-lwm low_water_mark]

                    [-okrt ok_on_root]

                    [-hostlist host_name [host_name]

                    [-M master_server[,master_server]

                    [-reason "<reason>"]

                        or

       bpstuadd -group storage_unit_group storage_unit_label [storage_unit_label]

                    [-sm selection_method]

[Marianne]

If you want to change the NBU drive name, you can use tpconfig.

For detailed explanation and command usage, see NetBackup Commands Reference Guide  http://www.symantec.com/docs/DOC3684 :

You will need something like this:

UNIX and Linux systems: tpconfig -update -drive drvindex [-type
drvtype] [-path drivepath] [-nh ndmp_hostname] [-noverify]
[-newasciiname asciidrivename]] [-shared [yes|no]] [-cleanfreq hours]
[-comment comment] [-drstatus [UP|DOWN|DISABLED]] [-robot robnum
-robtype robtype] [-robdrnum robdrvnum]
Windows systems: tpconfig -update -drive drvindex [-type drvtype]
[-port port -bus bus -target target -lun lun ] [-nh ndmp_hostname
-path drivepath] [-noverify] [-newasciiname asciidrivename]] [-shared
[yes|no]] [-cleanfreq hours] [-comment comment] [-drstatus
[UP|DOWN|DISABLED]] [-robot robnum -robtype robtype] [-robdrnum
robdrvnum]

As you can see, tpconfig is a fairly complex command that requires a good understanding of each parameter.
Why do you need to config or re-config? Or rename?
Why cmd?
What exactly is your DRIVE ISSUE?

[revarooo]

If you're not worried about your drive names (and why should you be?) then use

volmgr\bin\tpautoconf -a

This will configure all robots/drives it sees automatically. After which, you restart ltid and you are good to go.

[wannawin]

Actually the thing is that DRIVE is down and it was not coming up. I have dismount the stuck media but still drive is not coming up. So i want to reconfigure the drive..

or secondly one drive is in SCAN mode. What does SCAN mode means.. What i will do with that.

[Marianne]

Can we please start at the beginning?

What is the OS on the Master and/or media server(s)?

What is your NBU version?

Are your tape drives shared between media servers?

As an application, NetBackup has no direct access to a device, instead relying on the operating system (OS) to handle any communication with the device.
This means that during a write operation NetBackup asks the OS to write to the device and report back the success or failure of that operation. If there is a failure,
NetBackup will merely report that a failure occurred, and any troubleshooting should start at the OS level.
If the OS is unable to perform the write, there are three likely causes; OS configuration, a problem on the SCSI path, or a problem with the device.

So, before you re-config in NBU, you need to find to out what is is causing the problem, fix it, then re-config.

If we know which OS, we can assist with OS/device troubleshooting steps.

[mph999]

Marianne is 100% correct.

NetBackup does NOT write to tape drives.  The write (or read) operation is done by the operating system.

If a drive is down, then the system log (Event logs windows/ messages log Solaris/ Linux etc ...) should give a reason why.

NetbCakup does log events :

/usr/openv/volmgr/debug/tpcommand

/usr/openv/volmgr/debug/robots 

.. are usful logs.  I normally create two empty files called:

/usr/openv/volmgr/DRIVE_DEBUG

/usr/openv/volmgr/ROBOT_DEBUG

.. but these are not always necessary.

If a path to the drive has changed, then yes, reconfigure in NBU would fix, but, the problem really is why has the drive path changed at the OS level.

The /usr/open/netbackup/logs/bptm log can also contain info, are drive issues.

Most drive cases I deal with (and I do a lot) are faults/ issues on the hardware side.

It isn't impossible for a prolem with NetBackup to cause a drive to go down, but it is very rare, and you should eliminate issues outside of NBU first.

Martin

[wannawin]

OS on Master /Media server is SunOS 5.9
 

NBU version is 6.5.6

Yes tape drive is shared between master and media server.

Please help me out from this.

Thanks for your quick response

[wannawin]

How we manually mount the media in drive.

[Marianne]

You can use robtest on robot control host (master?) to test mount and dismount.

See this TN for command usage and examples: http://www.symantec.com/docs/TECH83129

Please let us know results.

Also post output all of the following (on both master and media server):

/usr/openv/volmgr/bin/tpconfig -l

/usr/openv/volmgr/bin/vmoprcmd -d

copy /var/adm/messages of master and media server and post as attachments (please rename files to master.txt and media server to media.txt).

If you have not done so already, please add VERBOSE entry to /usr/openv/volmgr/vm.conf on master and media server and restart NBU on master and media. Media Manager actions and errors will be logged to /var/adm/messages (including reason for DOWN drive(s).)