Replace the tape drive

[goSymantec]

Hi all, we have a SUN V240 running Solaris 9 with a SUN L8 auto loader with LTO drive and Netbackup 6 , the tape library has been replaced to a new one SUN C2 Auto loader with LTO2 drive and the old L8 has been physically removed and the new C2 attached to the same SCSI port. Now when I try to configure the new tape auto loader using the jnbSA graphical tool wizard, I get the error an error , kindly note that from the Solaris OS level I can write on the new tape drive. Any ideas what could have gone wrong? should I first delete any old configuration regarding the old L8 drive?

[DavidParker]

Yes, you will want to delete your device info in NBU for the old hardware.

Take a look through this document for some good information:

VERITAS NetBackup (tm) 6.0 Media Manager Device Configuration Guide for UNIX and Windows

[goSymantec]

Thanks David, I will try and post the result

[Rakesh_Khandelw]

As David has suggested, you will have to delete the existing Device configuration from NetBackup and add new devices, which includes changer as well as drives. You can do it either by using tpconfig command or through GUI.
As a best practice you may want to use differnet media density for these new tape drives.

[goSymantec]

When I run the "/usr/openv/volmgr/bin/sgscan all" the output is :

/dev/sg/c1t6l0: Tape (/dev/rmt/1): "HP      Ultrium 2-SCSI"
/dev/sg/c1t6l1: Changer: "QUANTUM UHDL"

So the new drive seems to have the (/dev/rmt/1) maybe because the old drive configuration still exists, what is the syntax to use to remove the old tape drive from the Netbackup configuration using the CLI  tpconfig(no GUI), and also is it possible to add the new drive to Netbackup using line command?

[DavidParker]

From:
http://support.veritas.com/docs/279299

VERITAS NetBackup (tm) 6.0 Commands for UNIX

Page 427

I'd recommend using the Java GUI though, if you can.

tpconfig(1M)
NAME
tpconfig - tape configuration utility
SYNOPSIS
Display drive configuration
/usr/openv/volmgr/bin/tpconfig -d
/usr/openv/volmgr/bin/tpconfig -dl
/usr/openv/volmgr/bin/tpconfig -l
Add drive
/usr/openv/volmgr/bin/tpconfig -add -drive -type drvtype -path
drivepath [-nh ndmp_hostname] [-vhname
optical_volume_header_drive_name] [-asciiname asciidrivename]
[-index drvindex]] [-shared [yes|no]] [-cleanfreq hours]
[-comment comment] [-drstatus [UP|DOWN|DISABLED]]
[-robot robnum -robtype robtype] [-noverify] [-robdrnum
robdrvnum | -VendorDrvName venddrvname | -ACS acsnum
-LSM lsmnum -PANEL panelnum -DRIVE drivenum] [-preview]
Update drive
/usr/openv/volmgr/bin/tpconfig -update -drive drvindex [-type
drvtype] [-path drivepath] [-nh ndmp_hostname]
[-noverify] [-vhname optical_volume_header_drive_name]
[-newasciiname asciidrivename]] [-shared [yes|no]]
[-cleanfreq hours] [-comment comment] [-drstatus
[UP|DOWN|DISABLED]] [-robot robnum -robtype robtype]
[-robdrnum robdrvnum | -VendorDrvName venddrvname | -ACS
acsnum -LSM lsmnum -PANEL panelnum -DRIVE drivenum]
Delete drive
/usr/openv/volmgr/bin/tpconfig -delete -drive drvindex
/usr/openv/volmgr/bin/tpconfig -multiple_delete -drive
drvindex1:drvindex2:drvindexN
Add robot
/usr/openv/volmgr/bin/tpconfig -add -robot robnum -robtype
robtype -robpath devfile [-nh ndmp_hostname]
/usr/openv/volmgr/bin/tpconfig -add -robot robnum -robtype
robtype -cntlhost cntlhost
tpconfig(1M)
428 NetBackup Commands for UNIX and Linux
Update robot
/usr/openv/volmgr/bin/tpconfig -update -robot robnum [-robtype
robtype] [-robpath devfile] [-cntlhost cntlhost]
For updating NDMP controlled robots
/usr/openv/volmgr/bin/tpconfig -update -robot robnum [-robtype
robtype] [-robpath devfile] [-nh ndmp_hostname ][-bus bus
-target target -lun lun]
/usr/openv/volmgr/bin/tpconfig -update -robot robnum [-robtype
robtype] [-pird [yes|no]]
Delete robot
/usr/openv/volmgr/bin/tpconfig -delete -robot robnum
/usr/openv/volmgr/bin/tpconfig -multiple_delete -robot
robnum1:robnum2:robnumN
Add drive path
/usr/openv/volmgr/bin/tpconfig -add -drpath -path drivepath [-nh
ndmp_hostname] [-asciiname asciidrivename] [-drstatus
[UP|DOWN|DISABLED]] [-noverify]
Update drive path
/usr/openv/volmgr/bin/tpconfig -update -drpath -oldpath drivepath
-path drivepath [-nh ndmp_hostname] [-asciiname
asciidrivename] [-drstatus [UP|DOWN|DISABLED]]
[-noverify]
Delete drive path
/usr/openv/volmgr/bin/tpconfig -delete -drpath -path drivepath
-asciiname asciidrivename [-nh ndmp_hostname]
Display NDMP host credentials for this host
/usr/openv/volmgr/bin/tpconfig -dnh
Display NDMP host credentials for all hosts
/usr/openv/volmgr/bin/tpconfig -dnh -all_hosts
Display NDMP default credentials for this host
/usr/openv/volmgr/bin/tpconfig -ddnh
Add NDMP host using default credentials
/usr/openv/volmgr/bin/tpconfig -add -nh ndmp_hostname
Add NDMP host credentials
Chapter 1, NetBackup Commands
tpconfig(1M)
429
/usr/openv/volmgr/bin/tpconfig -add -nh ndmp_hostname -user_id
| -filer_user_id user ID [-password password [-key
encryption key]] -snap_vault_filer
Update NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -update -nh ndmp_hostname
-user_id | -filer_user_id user ID [[-password password
[-key encryption key]]
Delete NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -delete -nh ndmp_hostname
-user_id | -filer_user_id user ID
Update mulitple NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -multiple_delete -nh
ndmp_hostname_1:ndmp_hostname_2: ... ndmp_hostname_N:
Add default NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -add -default_user_id user ID
[-password password [-key encryption key]]
Update default NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -update -default_user_id user ID
[-password password [-key encryption key]]
Delete default NDMP host credentials
/usr/openv/volmgr/bin/tpconfig -delete -default_user_id
Retrieve default information from a device
/usr/openv/volmgr/bin/tpconfig -devping [-drive -path drivepath
| robpath robotpath] [-nh ndmp_hostname]


Message Edited by David Parker on 10-09-2007 03:29 PM

[Rakesh_Khandelw]

Here are the steps -

To delete the old drive from NetBackup

tpconfig -delete -drive <drvindex>

To delete old robot from NetBackup

tpconfig -delete -robot <robot>

If this was the only tape drive you had on this system, go to /dev/rmt directory and remove everything. Assuming your drive is SCSI attached. If drive is Fiber connected and you are using zoning, then you need to update the zone at switch and/or host level.

Now reboot your server with -r option

reboot -- -r

after server reboot, you should be able to see devices created in /dev/rmt directory

run sgscan or scan command to check the new devices.

Now, you can add robot and drive either by using GUI or from the command line

Add new robot -

 tpconfig -add -robot <robnum> -robtype <robtype> -robpath <devfile>

restart NBU daemons

Add tape drive -

tpconfig -add -drive -type <drvtype> -path <drivepath> -asciiname <asciidrvname> -index <drvindex> -shared [yes|no] -drstatus UP|DOWN|DISABLED [-robot <robnum> -robtype <robtype> -robdrnum <robdrvnum>

Restart NBU daemons. Update/recreate STU and you should be good to go

[goSymantec]

After deleting the old robot and drive, now the

# tpconfig -l
Device Robot Drive       Robot                    Drive             Device  Second
Type     Num Index  Type DrNum Status  Comment    Name              Path  Device Path
robot      0    -    TLD    -       -  -          -                 /dev/sg/c1t0l0
  drive    -    0  hcart    1      UP  -          HPUltrium2-SCSI0

However, under the "Device Path" column for the new tape drive "HPUltrium2-SCSI0
", it doesnot show the /dev/rmt/1  , while in the old drive that I deleted it was showing "/dev/rmt/0" , is this normal

regards

[goSymantec]

I have ran the "tpconfig" and deleted the old drive, then added the new tape auto loader then added the new LTO2 drive fro the tpconfig menu:

1. When adding the tape auto loader, there was no option for "Ultrium2" , I chosen TLD , is this OK?

2. When adding the tape drive , there was no option for LTO2 drive , I chosen "dlt", is this OK?

3. When I run a backup for a policy, I get the error:

** START OF ERROR STACK **

Try 1
REQUESTING_RESOURCE 1192023619 __ANY__
REQUESTING_RESOURCE 1192023619 bkpsrv.NBU_CLIENT.MAXJOBS.srv1
REQUESTING_RESOURCE 1192023619 bkpsrv.NBU_POLICY.MAXJOBS.srv2
RESOURCE_GRANTED 1192023620 bkpsrv.NBU_CLIENT.MAXJOBS.srv1
RESOURCE_GRANTED 1192023620 bkpsrv.NBU_POLICY.MAXJOBS.srv2
RESOURCE_GRANTED 1192023620 K461L2
RESOURCE_GRANTED 1192023620 HP.Ultrium2-SCSI.000
RESOURCE_GRANTED 1192023620 bkpsrv-dlt-robot-tld-0
PROCESS 1192023623 1789 bpbrm
CONNECT 1192023623
CONNECTED 1192023623
FW 1192023623 1
PATH_WRITTEN 1192023623 /
MOUNTING 1192023627 K461L2
LOG 1192023630 16 bptm 1790 error requesting media, TpErrno = Robot operation failed
LOG 1192023631 8 bptm 1790 media id K461L2 load operation reported an error
REQUESTING_NEXT_MEDIA 1192023631 K461L2 __ANY__
LOG 1192023653 16 bptm 1790 NBJM returned an extended error status: resource request failed (800)
END_WRITING 1192023654
Started 1192023620
Files 1
ActivePid 1789
Status 252
DestStorageUnit bkpsrv-dlt-robot-tld-0
DestMediaServer bkpsrv
Ended 1192023657

** END OF ERROR STACK **

Please note that the output of the "tpconfig -l " is as follows:

root# tpconfig -l
Device Robot Drive       Robot                    Drive                 Device         Second
Type     Num Index  Type DrNum Status  Comment    Name                  Path           Device Path
robot      0    -    TLD    -       -  -          -                     /dev/sg/c1t0l1
  drive    -    0    dlt    1    DOWN  -          HP.Ultrium2-SCSI.000  /dev/rmt/2hbn

Which shows that the drive is down? is this OK.

[DavidParker]

1. When adding the tape auto loader, there was no option for "Ultrium2" , I chosen TLD , is this OK?
    TLD should be ok

2. When adding the tape drive , there was no option for LTO2 drive , I chosen "dlt", is this OK?

    No, you want to choose hcart2 for LTO2 (hcart = 1/2" cartrige = LTO)