Emc vtl dld3d & tsm 5.5

faisalsiddiqui

Active Newcomer
Joined
Feb 9, 2010
Messages
15
Reaction score
0
Points
0
Hello,

i'm using EMC -VTL (DLD3D) with TSM 5.5, im facing some issue i need an urgent help in this regard.
VTL is emulating ADIC iScalar 2000.
TSM 5.5 is running on AIX 5.3 TL 06, i can see changer as /dev/lb2 on server machine,

Issue1:-
10 drives allocated to TSM for lanfree backup.
i load the virtual tapes in VTL to all my tsm drives from EMC VTL console, whenever i initiate the backup or audit VTL LIB, tsm unmount these tapes. why???

can any please explain this?

Issue 2:-
whenever i initiate the backup of any host, i found this in actitivy log that im sharing.

please suggest how to fix this issue.

ANR0406I Session 6 started for node MYLOCAL-DB (Linux86) (Tcp/Ip
10.X.X.XXX (3639)).
ANR8337I LTO volume 000020 mounted in drive EMCVTL10 (/dev/rmt10).
ANR8468I LTO volume 000020 dismounted from drive EMCVTL10 (/dev/rmt10) in library VTL.
ANR1404W Scratch volume mount request denied - mount failed.
ANR8337I LTO volume 000021 mounted in drive EMCVTL11 (/dev/rmt11).
ANR8468I LTO volume 000021 dismounted from drive EMCVTL11 (/dev/rmt11) in library VTL.
ANR1404W Scratch volume mount request denied - mount failed.
ANR8337I LTO volume 000022 mounted in drive EMCVTL15 (/dev/rmt15).
ANR8468I LTO volume 000022 dismounted from drive EMCVTL15 (/dev/rmt15) in library VTL.
.
.
.
.
.
.
 
Because I am nice...

1. Are you running 5.5.3 TSM Server code?
2. You have to use the TSM Device Drivers so you will be using LB and MT not RMT.
3. Emulate LTO3 on your VTL it works better.
4. Did you label the volumes or just do an Audit?
 
Here your answers are

find your answers in between the line

Because I am nice...

1. Are you running 5.5.3 TSM Server code?
TSM Integrated Soultion Console Version 6.0.1.1
TSM Administration Center Version 5.5.0.0


2. You have to use the TSM Device Drivers so you will be using LB and MT not RMT.
Yes, im using the same.
EMC dont provide device driver for EMC VTL, so we have to discover the devices driver support by TSM.

I'm Using AIX,

$lsdev -C | grep lb
lb2 Available 0B-08-02 Library/Medium Changer


$lsdev -Cc tape
rmt2 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt3 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt4 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
.
.
.
rmt10 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)


can you exectlay tell me "DEVICE ELEMENT NUMBER" for VTL tape Drives, i'm using "284"

I've Added these tapes and changer in TSM
IN TSM i've Added these tape drives i.e.
EMCVTL2 /dev/rmt2

i dont understand what your point regarding LB & MT not RMT.
devices comes in unix as /dev/...
for chnager we r seeing /dev/lb2
for tape drives we use /dev/rmt....

can you please explain what your point is..

3. Emulate LTO3 on your VTL it works better.
EMC support will change this to LTO3, with 8 digit label volume.
actually, we were running 6 digit vol without media type extension with LT04. IBM Suggested us tto change this to LTO3.


4. Did you label the volumes or just do an Audit?
I labeled & checked in,
i ran the audit due to the error i was getting.
one more the TSM dont dicover the tape that mounts on VTL drive.
when i initiate the backup i also umount he VTL tapes and unable to load the tapes. why i dont know???

thank for your support ask me fruthermore if you need any clarification...

waiting for your advices & please help me out in this regard ... thanks.
 
Againt the RMT is wrong it has to be an MT. You need to remove all RMT and MT Devices and LB. You need to discover the devices in the Tivoli Storage Device Drivers via Smitty. Do not run CFGMGR before you do this. Because if you have RMT device available first the MT because Defined mode. You didnt give me the TSM server level you put Admin Center 5.5.0.0. You have to be at level TSM 5.5.3. Do a q status and post it.
 
Request output and other queries !!!

Thank for your as usual support.

Do i still need to upgrade TSM server level? advice anything whatever you want but please help me out to resolve this issue. i'm messed up with EMC & IBM support. can i have your personal Email address and cell phone details?

Here is your requested output, find others output and my others queries at the bottom of this msg.

tsm: TSMPRD>q status
Storage Management Server for AIX-RS/6000 - Version 5, Release 5, Level 4.0

Server Name: TSMPRD
Server host name or IP address: 10.16.200.79
Server TCP/IP port number: 1500
Crossdefine: Off
Server Password Set: Yes
Server Installation Date/Time: 12/17/08 17:21:32
Server Restart Date/Time: 02/09/10 19:02:46
Authentication: On
Password Expiration Period: 90 Day(s)
Invalid Sign-on Attempt Limit: 0
Minimum Password Length: 0
Registration: Closed
Subfile Backup: No
Availability: Enabled
Accounting: Off
Activity Log Retention: 10 Day(s)
Activity Log Number of Records: 212116
Activity Log Size: 31 M
Activity Summary Retention Period: 30 Day(s)
License Audit Period: 1 Day(s)
Last License Audit: 02/10/10 08:00:19
Server License Compliance: Valid
Central Scheduler: Active
Maximum Sessions: 25
Maximum Scheduled Sessions: 12
Event Record Retention Period: 10 Day(s)
Client Action Duration: 5 Day(s)
Schedule Randomization Percentage: 25
Query Schedule Period: Client
Maximum Command Retries: Client
Retry Period: Client
Scheduling Modes: Any
Log Mode: Normal
Database Backup Trigger: Not Defined
BufPoolSize: 32,768 K
Active Receivers: CONSOLE ACTLOG
Configuration manager?: Off
Refresh interval: 60
Last refresh date/time:
Context Messaging: Off
Table of Contents (TOC) Load Retention: 120 Minute(s)
Machine Globally Unique ID: 00.00.00.00.cc.91.11.dd.98.42.08.63.0a.00.00.65
Archive Retention Protection: Off
Encryption Strength: AES


Your are right all MT are in define state. i'm also pasting the output of lb, mt and rmt also Atape.driver version.

tsmprd:/>lslpp -l Atape.driver

Fileset Level State Description
----------------------------------------------------------------------------
Path: /usr/lib/objrepos
Atape.driver 11.7.6.0 COMMITTED IBM AIX Enhanced Tape and
Medium Changer Device Driver

tsmprd:/>lsdev -C | grep lb

lb0 Defined 0B-08-02 Library/MediumChanger
lb1 Defined 0B-08-02 Library/MediumChanger
lb2 Available 0B-08-02 Library/MediumChanger
lb3 Defined 0B-08-02 Library/MediumChanger

tsmprd:/>lsdev -C | grep mt
mt0 Defined 0B-08-02 Tape Drive
mt1 Defined 0B-08-02 Tape Drive
mt2 Defined 0B-08-02 Tape Drive
mt3 Defined 0B-08-02 Tape Drive
mt4 Defined 0B-08-02 Tape Drive
mt5 Defined 0B-08-02 Tape Drive
mt6 Defined 0B-08-02 Tape Drive
mt7 Defined 0B-08-02 Tape Drive
mt8 Defined 0B-08-02 Tape Drive
mt9 Defined 0B-08-02 Tape Drive
mt10 Defined 0B-08-02 Tape Drive
mt11 Defined 0B-08-02 Tape Drive
mt12 Defined 0B-08-02 Tape Drive
mt13 Defined 0B-08-02 Tape Drive
mt14 Defined 0B-08-02 Tape Drive
mt15 Defined 0B-08-02 Tape Drive
mt16 Defined 0B-08-02 Tape Drive
mt17 Defined 0B-08-02 Tape Drive
rmt0 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt1 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt2 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt3 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt4 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt5 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt6 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt7 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt8 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt9 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt10 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt11 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt12 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt13 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt14 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt15 Available 0B-08-02 LTO Ultrium Tape Drive (FCP)
rmt16 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)
rmt17 Available 0B-08-02 IBM 3580 Ultrium Tape Drive (FCP)


hmmm i got your point,
System Workaround


  1. remove all RMT's, MT's, SCM's & LB's
  2. smitty devices (TSM device... --> discover devices by tsm.-->FCP)
  3. after verifying lsdev -C | grep lb must be in available state.
  4. run cfgmgr
  5. ALL VTL DRIVES must be available in MT mode.
TSM Workaround

  1. remove vtl library & device class,
  2. all relevant PD & Stg pools.
  3. create library, device class, add all VTL drives as
    Device name Device Special File name
    VTLDRIVE2 /dev/mt2
    .
    .
    .
    VTLDRIVE10 /dev/mt10

  4. can you exactly tell me "DEVICE ELEMENT NUMBER" for VTL tape Drives, i'm using "284", or leave this field blank TSM will pick this up automatically.

  5. Label Vol & checkin via Discover vloumes.

    Please correct me if im wrong in any step. Actually im newbie in TSM but not in the world of *ix
    :up:
  6. do i need to install any MT special driver ? or Atape.driver is sufficient. if not please refer me MT driver download link, i've seen that at ibm site with Atape.driver
No one told me that neither EMC support nor IBM, i'm surprised.
MT must be in available state if changer is LB. what can i say, being as a unix admin i thought VTL drive should be RMT as traditional in AIX.

Thank again, kindly keep me posted. waiting for your prompt reply.
 
private message me your phone number and name and I can call you when i get it..help out a TSM'er :)
 
TSM does not use the aTape Drivers. it uses the TSM drivers. do the following.

1. Remove the RMT, MT and LB devices.
2. type in smitty
3. Go to Devices->Tivoli Storage Manager Devices->Fiber Channel San Attached Devices
4. Discover Devices Support by TSM
5. List the Attributes of a Discoverd Device.

After you do all of them you need to just create each drive in TSM and do not need an Element number. It will be able to connect based on the order in which you submit it.
 
Thanks

Thank for your as usual support,

now i can take backup on TSM using VTL, might i further need your help in implementation of SAN Agents. i'll keep you posted.

any suggestion and tips are welcome :)

Thanks & Regards
Faisal

TSM does not use the aTape Drivers. it uses the TSM drivers. do the following.

1. Remove the RMT, MT and LB devices.
2. type in smitty
3. Go to Devices->Tivoli Storage Manager Devices->Fiber Channel San Attached Devices
4. Discover Devices Support by TSM
5. List the Attributes of a Discoverd Device.

After you do all of them you need to just create each drive in TSM and do not need an Element number. It will be able to connect based on the order in which you submit it.
 
hi,

Again i need your help, i've configured one AIX SAN Agent, discoverd changer as same method, i can see changer as lb3 and drive as mt6, after configure the rest on tsm and client side, when i initiate the rman backup, i'm facing this error in TSM activity log. i dont know what to do or is still need to configure. at the end of this msg im pasting few output that might u need.

i've one more question for you please dont laugh :redface: on that, how do u determine if u've configure BA and TDPO on AIX node, when u do BA backup, will it use Fiber channel or TCP/IP? im asking this bullshit bcoz all lanfree entries i put in TDP not for BA. please can you explain this,

ANR0409I Session 668 ended for server TEST9132_SANAGENT (AIX-RS/6000).
ANR0408I Session 669 started for server TEST9132_SANAGENT (AIX-RS/6000)
(Tcp/Ip) for library sharing.
ANR1772E The path from source TEST9132_SANAGENT to destination EDL06 is taken
offline.
ANR0409I Session 669 ended for server TEST9132_SANAGENT (AIX-RS/6000).
ANR0408I Session 670 started for server TEST9132_SANAGENT (AIX-RS/6000)
(Tcp/Ip) for library sharing.
ANR1772E The path from source TEST9132_SANAGENT to destination EDL06 is taken
offline.




tsm: TSMPRD>validate lanfree TEST912_TDPO TEST9132_sanagent
ANR0387I Evaluating node TEST912_TDPO using storage agent TEST9132_SANAGENT for
LAN-free data movement.
Node Storage Operation Mgmt Class Destination LAN-Free Explanation
Name Agent Name Name capable?
----- -------- --------- ---------- ------------ --------- --------------------
TEST- TEST913- BACKUP STANDARD EDL-TESTPOOL Yes
912- 2_SANA-
_TD- GENT
PO
TEST- TEST913- ARCHIVE STANDARD EDL-TESTPOOL Yes
912- 2_SANA-
_TD- GENT
PO
ANR1706I Ping for server 'TEST9132_SANAGENT' was able to establish a
connection.
ANR0388I Node TEST912_TDPO using storage agent TEST9132_SANAGENT has 2 storage
pools capable of LAN-free data movement and 0 storage pools not capable of
LAN-free data movement.

tsm: TSMPRD>q path
Source Name Source Type Destination Destination On-Line
Name Type
----------- ----------- ----------- ----------- -------
TEST9132_S- SERVER EDL06 DRIVE Yes
ANAGENT


tsm: TSMPRD>q ses
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------ ------ ------ ------ ------- ------- ----- -------- --------------------
312 Tcp/Ip IdleW 2 S 46.4 K 19.5 K Serv- AIX-RS/- TEST9132_SANAGENT
er 6000
318 Tcp/Ip SendW 0 S 1.0 M 139 Admin AIX ADMIN
2,892 Tcp/Ip Run 0 S 3.0 K 313 Admin AIX ADMIN
 
If you are using Oracle with TDP it will use the API directory located in /usr/tivoli/tsm/client/api/bin64 (if 64 bit). In there that is the dsm.sys file you need to update. the TDPo_Opt file in /usr/tivoli/tsm/oracle/bin64 tell you what dsm.opt file you use but it will go to the dsm.sys file in the API directory not BA.
 
If you are using Oracle with TDP it will use the API directory located in /usr/tivoli/tsm/client/api/bin64 (if 64 bit). In there that is the dsm.sys file you need to update. the TDPo_Opt file in /usr/tivoli/tsm/oracle/bin64 tell you what dsm.opt file you use but it will go to the dsm.sys file in the API directory not BA.
hmmm ok,

but what about the error that im getting, can you please help me in this regard.
 
Can you give me the paths of the drive for the SAN Client and the Server. Are they both defined?
 
Yes, they are both defined.
if these output are not sufficient please do let me know what u need.

Client Drive and LB
mt6 and lb3 (available)

TSM Server Drive and LB
mt5 & mt6 and lb3 (available)
mt6 im using for my san agent

tsm: TSMPRD>q path
Source Name Source Type Destination Destination On-Line
Name Type
----------- ----------- ----------- ----------- -------
TSMPRD SERVER EDL LIBRARY Yes
TSMPRD SERVER EDL05 DRIVE Yes
TSMPRD SERVER EDL06 DRIVE Yes
TEST9132_S- SERVER EDL06 DRIVE Yes
ANAGENT


tsm: TSMPRD>validate lanfree TEST912_TDPO TEST9132_sanagent
ANR0387I Evaluating node TEST912_TDPO using storage agent TEST9132_SANAGENT for LAN-free data movement.
Node Storage Operation Mgmt Class Destination LAN-Free Explanation
Name Agent Name Name capable?
----- -------- --------- ---------- ------------ --------- --------------------
TEST- TEST913- BACKUP STANDARD EDL-TESTPOOL Yes
912- 2_SANA-
_TD- GENT
PO
TEST- TEST913- ARCHIVE STANDARD EDL-TESTPOOL Yes
912- 2_SANA-
_TD- GENT
PO

tsm: TSMPRD>q ses
Sess Comm. Sess Wait Bytes Bytes Sess Platform Client Name
Number Method State Time Sent Recvd Type
------ ------ ------ ------ ------- ------- ----- -------- --------------------
318 Tcp/Ip SendW 0 S 2.9 M 139 Admin AIX ADMIN
3,228 Tcp/Ip IdleW 6 S 61.9 K 18.7 K Serv- AIX-RS/- TEST9132_SANAGENT
er 6000
7,124 Tcp/Ip Run 0 S 6.0 K 419 Admin AIX ADMIN
7,126 Tcp/Ip IdleW 51.5 M 23.4 K 1.1 K Admin DSMAPI ADMIN
 
I am currently stumped since I am unable to log into the system and the server. I would assume that you are using the 5.5.4 Drivers for the storage agent as well with the MT and LB. I would have you contact TSM support and see from logs what may be causing error.
 
I was at Pulse 2010 for IBM. Without taking a hands on dive on this I would recommend talking to IBM per support.
 
I was at Pulse 2010 for IBM. Without taking a hands on dive on this I would recommend talking to IBM per support.


Ok, i'll do the same, sorry i wasnt posting anything, i was quiet busy 24/7 in disaster recovery issues of SAN and HA. i'll keep you posted. if u found anything precious for me please let me know.

thank for your as usual support.
 
Back
Top