cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Unable to configure replaced tape drive | netbackup 6.5

Hi All,

Recently a tape drive was replaced. This tape drive is connecetedn to filer through FC end to end connection. While configuring this tape drive we are unable to detect this tape drive at Netbackup level. Checkpoint infront of this tape library is disabled and it displays a message "tape drive attached to remote host". Any suggestions on how to get this corrected?

Thanks in advance 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Re: Unable to configure replaced tape drive | netbackup 6.5

Hi All,

 

Issue has been resolved by rebooting the filer. After the filer reboot we are able to see the tape drive discovered at Netbackup level. 

Thaks all for your comments. 

View solution in original post

7 Replies
Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

NBU6.5??  So old I cannot even find relevent technotes any more.  Try this link:

https://saifulaziz.com/2006/12/18/how-to-configure-drive-on-solaris-for-veritas-netbackup/

(I don't miss those days)

 

 

Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

Since you do not indicate your OS type or the NDMP filer type, or the tape drive types, all we can do is throw out SWAG.

I have had issues with my NDMP drives where if the filer/drives were disconnected for a while, I had to manually stop and start the process on the filer. (cough, cough NetAPP)

fcadmin config   -   Check output - one will be online - that is the active adapter:

Adapter Type      State                  Status

---------------------------------------------------

  0a   initiator  CONFIGURED.            online          - THIS IS THE ONE TO RESET!

  0b   initiator  CONFIGURED.            offline

sysconfig -t      ( see no drives )

storage disable adapter 0a

storage enable adapter 0a

sysconfig -t    ( see all the drives )

Now you can scan your drives 

 

I have had other issues with NDMP drives, where I had to manually run the OS Level commands to update them.

Of course, any tape drive first must be visible at the OS level - make sure you can run scan or sgscan and see them

If you can see the drive at the OS level, you can run this 

tpconfig -update -drive -type HCART -path DRIVE.PATH -nh NDMP.HOST -asciiname NB.DRIVE.NAME -shared NO -drstatus UP -robot NUMBER -robtype TLD -robdrnum DRIVENUMBER

You will need to replace the uppercase stuff with your values.

 

 

 

NetBackup 8.1.2 on Solaris 11, writing to DataDomain 9800 6.0.2.50
duplicating via SLP to LTO5 in SL8500 via ACSLS
Tags (1)
Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

Hi Genericus,

 

Our OS is solaris. We are using Netapp filers through local NDMP. The tape drive is LTO4. The drive is not coming in scan command as the drive is not connected to server instead it is directly connected to filer. On filer i can see the new tape drive through storage show command. 

At OS level if I run scan -changer, I can see the new tape drive listed. However, if I try to configure the drive through netbackup utility I see new drive is mentioned as attached to remote host. I have attached the screenshot of Properties tab of new tape drive. 

 


Also, we have tried to reset the port. But no luck.

Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

You forgot to attach the screenshot.

Please read through previous post again.
Scan on media server will not show devices attached to filer. It will only show devices attached to the media server.
Please use commands shared in above post to check drive connectivity on the filer.

The NBU for NDMP Admin guide will also guide you regarding device config.

Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

Hi Marriana ,

 

We have tried these enable and disable adapter from filer end. Please find the requested output

 

bbtflrva301> fcadmin config

Local
Adapter Type State Status
---------------------------------------------------
1a initiator CONFIGURED. online
1b initiator CONFIGURED. online

 

bbtflrva301*> sysconfig -t

Tape drive (1b.21) IBM LTO 4 ULT3580
rst0l - rewind device, format is: LTO 2 ro 200GB cmp
nrst0l - no rewind device, format is: LTO 2 ro 200GB cmp
urst0l - unload/reload device, format is: LTO 2 ro 200GB cmp
rst0m - rewind device, format is: LTO 3 800GB cmp
nrst0m - no rewind device, format is: LTO 3 800GB cmp
urst0m - unload/reload device, format is: LTO 3 800GB cmp
rst0h - rewind device, format is: LTO 4 800GB
nrst0h - no rewind device, format is: LTO 4 800GB
urst0h - unload/reload device, format is: LTO 4 800GB
rst0a - rewind device, format is: LTO 4 1600GB cmp
nrst0a - no rewind device, format is: LTO 4 1600GB cmp
urst0a - unload/reload device, format is: LTO 4 1600GB cmp

Tape drive (1a.20) IBM ULT3580-TD2
rst2l - rewind device, format is: LTO-I tape only 100GB
nrst2l - no rewind device, format is: LTO-I tape only 100GB
urst2l - unload/reload device, format is: LTO-I tape only 100GB
rst2m - rewind device, format is: LTO-I tape 200GB cmp
nrst2m - no rewind device, format is: LTO-I tape 200GB cmp
urst2m - unload/reload device, format is: LTO-I tape 200GB cmp
rst2h - rewind device, format is: LTO-II tape only 200GB
nrst2h - no rewind device, format is: LTO-II tape only 200GB
urst2h - unload/reload device, format is: LTO-II tape only 200GB
rst2a - rewind device, format is: LTO-II tape 400GB cmp
nrst2a - no rewind device, format is: LTO-II tape 400GB cmp
urst2a - unload/reload device, format is: LTO-II tape 400GB cmp

 

 

 

Highlighted
Accepted Solution!

Re: Unable to configure replaced tape drive | netbackup 6.5

Hi All,

 

Issue has been resolved by rebooting the filer. After the filer reboot we are able to see the tape drive discovered at Netbackup level. 

Thaks all for your comments. 

View solution in original post

Highlighted

Re: Unable to configure replaced tape drive | netbackup 6.5

IMHO, you should've mark @Genericus's post as solution.

Rebooting the filer would have the same effect as stopping and restarting processes on the filer.