cancel
Showing results for 
Search instead for 
Did you mean: 

What are the steps to be done after replacing the drive in ACSLS & TLD library

RaymT___
Level 4

Hi All,

How do we need to ensure the drives needs to be replaced and please provide me the steps to check after replacing the drives in Acls & TLD library.

 

/Raymt

1 ACCEPTED SOLUTION

Accepted Solutions

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

9940B and LTO4 are drive types, meaning we still don't anything about your robot/silo or ACSLS.

I will try...

Check that ACSLS sees the drive and correct serial #:
ACSSA> q dr all    (note the drive address)
ACSSA> display drive *,*,*,* -f type serial_num   (drive address noted above)

On media server, verify that drive is seen at OS level:
# devfsadm    (to refresh OS device names)
# /usr/openv/volmgr/bin/tpautoconf -t  (look for drive serial # noted above and note OS device name (/dev/rmt/#cbn).
# /usr/openv/volmgr/bin/tpautoconf -report_disc   (to report the discrepancy)
# /usr/openv/volmgr/bin/tpautoconf -replace_drive NBU-drive-name -path /dev/rmt/#cbn
 

Hope this helps. See TN  http://www.symantec.com/docs/TECH34296 for more details.
 


 


 

View solution in original post

5 REPLIES 5

Amarnath_Sathis
Level 5

Please provide more details.

 

Netbackup / Backup Exec ?

Version ?

Server Type ? Windows / UNIX

Omar_Villa
Level 6
Employee
Also the silo type please some are smart enough that u dont need to do nothing at acs level

RaymT___
Level 4

Netbackup 6.5.6

Solaris 10

StorageTek, Type 9940B, LTO4, LSM

Is that enough....

 

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

9940B and LTO4 are drive types, meaning we still don't anything about your robot/silo or ACSLS.

I will try...

Check that ACSLS sees the drive and correct serial #:
ACSSA> q dr all    (note the drive address)
ACSSA> display drive *,*,*,* -f type serial_num   (drive address noted above)

On media server, verify that drive is seen at OS level:
# devfsadm    (to refresh OS device names)
# /usr/openv/volmgr/bin/tpautoconf -t  (look for drive serial # noted above and note OS device name (/dev/rmt/#cbn).
# /usr/openv/volmgr/bin/tpautoconf -report_disc   (to report the discrepancy)
# /usr/openv/volmgr/bin/tpautoconf -replace_drive NBU-drive-name -path /dev/rmt/#cbn
 

Hope this helps. See TN  http://www.symantec.com/docs/TECH34296 for more details.
 


 


 

varunthilak
Level 2

To Add Marianne's post.

Once the drive replaced, Check the serial number whether it's new or old.

In case if it shows old serial number, just make the drive offline and then bring it online.

Eg :

ACSSA>dismount
ACSSA>drive
ACSSA><drive id>
ACSSA>(enter blank)
ACSSA>offline
ACSSA>force

ACSSA>dismount
ACSSA>drive
ACSSA><drive id>
ACSSA>(enter blank)
ACSSA>online
ACSSA>force

Now, check the drive serial number.. It should show new one and you can test backup.
Note : If you are using VTL and if it's backend drive then you should drop and add from VTL level.