08-22-2012 08:14 AM
Hi Folks,
I have replaced failed drive in our library and we used to follow below steps.
Solved! Go to Solution.
08-22-2012 11:58 AM
Yes, the replace drive option is one way, the other is just delete the old drive an use the wizard to add the new one, which is the way I generally do it.
martin
08-22-2012 10:00 AM
Follow this TN to replace the drive within NBU with the new one
or
Just delete the old drive and run the wizard to add the new.
Simply, Solaris has configured the drive with a different xcbn number, it's not an issue.
martin
08-22-2012 10:59 AM
Thanks martin..We also did the same after replaced old drive.Below steps i got from here only.
/usr/openv/volmgr/bin/tpautoconf -report_disc
This produces information similar to the following:
======================= New Device (Tape) ============
Inquiry = "QUANTUM DLT7000 245F"
Serial Number = PXA51S3232
Drive Path = /dev/rmt/21cbn
Found as TLD(0), Drive = 1
===================== Missing Device (Drive) =========
Drive Name = QUANTUMDLT70001
Drive Path = /dev/rmt/11cbn
Inquiry = "QUANTUM DLT7000 245F"
Serial Number = PXA51S3587
TLD(0) definition, Drive = 1
Hosts configured for this device:
Host = HOSTA
Host = HOSTB
This reports the discrepancy between the device database and the new device found. Take note of the new Drive Path for the device as this will be needed for the tpautoconf command. To resolve this, run:
# cd /usr/openv/volmgr/bin
#./tpautoconf -replace_drive QUANTUMDLT70001 -path /dev/rmt/21cbn
08-22-2012 11:58 AM
Yes, the replace drive option is one way, the other is just delete the old drive an use the wizard to add the new one, which is the way I generally do it.
martin
08-22-2012 12:09 PM
Thanks martin...