backup stgpool format netappdump fails

[saisai74]

Hi All,
here is the config i'm working on:
2 sites A and B, on site A one TSM_A (6.1.3.3) and on site B one TSM_B same level
on each site i've a library connected, LIB_A to TSM_A (with 8 lto3 drives) and LIB_B to TSM_B also 8 drives
TSM_A is library manager of LIB_A and library client of LIB_B trough TSM_B

i've got one NAS node on site A and we are running NDMP backups on TSM_A, all works fine, data backups are going on stgpools NASPOOL (type NETAPPDUMP), and toc is going to a normal stgpool NASTOC. ( NAS node is defined as type NAS on TSM_A, the datamover is also defined, and also the paths on TSM_A)

i've created copy stgpools using the devc pointing to the remote location
when i run a backup stg of NASTOC on the remote location, it works fine.
when i try to run a backup stgpool of my primary NASPOOL on the remote library, it fails, with error:
no datamover available or no paths defined

somebody get the same issue or an idea ?

 

[MAG]

Hi,

Nice timing - I'm currently reading the IBM Redbook for using N-Series with TSM.

For a start can you post the output for:

q datamover f=d type=nas
q path f=d
q node type=nas

 

[saisai74]

infos

tsm: TSMSERV1>q datamover t=nas f=d

Data Mover Name: DETROIT_NAS
Data Mover Type: NAS
IP Address: 135.23.43.212
TCP/IP Port Number: 10000
User Name: netbck
Storage Pool Data Format: NetApp Dump
On-Line: Yes
Last Update by (administrator): ADMIN
Last Update Date/Time: 03/16/2010 15:43:34

tsm: TSMSERV1>q no t=nas f=d

Node Name: DETROIT_NAS
Platform: IBM
Client OS Level: Data ONTAP Release 7.3.2 (Network Appliance)
Client Version:
Policy Domain Name: POL_NAS
Last Access Date/Time: 04/27/2010 15:14:50
Days Since Last Access: 3
Password Set Date/Time: 03/16/2010 15:36:40
Days Since Password Set: 45
Invalid Sign-on Count: 0
Locked?: No
Contact:
Compression:
Archive Delete Allowed?: Yes
Backup Delete Allowed?: No
Registration Date/Time: 03/16/2010 15:36:40
Registering Administrator: ADMIN
Last Communication Method Used: NDMP
Bytes Received Last Session:
Bytes Sent Last Session:
Duration of Last Session:
Pct. Idle Wait Last Session:
Pct. Comm. Wait Last Session:
Pct. Media Wait Last Session:
Optionset:
URL:
Node Type: NAS
Password Expiration Period:
Keep Mount Point?: No
Maximum Mount Points Allowed: 1
Auto Filespace Rename : No
Validate Protocol: No
TCP/IP Name:
TCP/IP Address:
Globally Unique ID:
Transaction Group Max: 0
Data Write Path: ANY
Data Read Path: ANY
Session Initiation: ClientOrServer
High-level Address:
Low-level Address:
Collocation Group Name:
Proxynode Target:
Proxynode Agent:
Node Groups:
Email Address:

tsm TSMSERV1: q path f=d
( but without non valuable infos)
Source Name Source Type Destination Destination Library Node Name Device External LUN Initiator
Manager
----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- -----------
TSMSERV1 SERVER LIBR_1 LIBRARY \\.\changer0 0 TSMSERV1 SERVER DRIVE0_MA DRIVE LIBR_1 \\.\tape4801101 0 TSMSERV1 SERVER DRIVE1_MA DRIVE LIBR_1 \\.\tape4801102 0 TSMSERV1 SERVER DRIVE2_MA DRIVE LIBR_1 \\.\tape4801103 0 TSMSERV1 SERVER DRIVE3_MA DRIVE LIBR_1 \\.\tape4801104 0 TSMSERV1 SERVER DRIVE4_MA DRIVE LIBR_1 \\.\tape4801105 0 TSMSERV1 SERVER DRIVE5_MA DRIVE LIBR_1 \\.\tape4801106 0 TSMSERV1 SERVER DRIVE6_MA DRIVE LIBR_1 \\.\tape4801107 0 TSMSERV1 SERVER DRIVE7_MA DRIVE LIBR_1 \\.\tape4801108 0 DETROIT_NAS DATAMOVER DRIVE0_MA DRIVE LIBR_1 rst129h 0 DETROIT_NAS DATAMOVER DRIVE1_MA DRIVE LIBR_1 rst128h 0 DETROIT_NAS DATAMOVER DRIVE2_MA DRIVE LIBR_1 rst132h 0 DETROIT_NAS DATAMOVER DRIVE3_MA DRIVE LIBR_1 rst131h 0 DETROIT_NAS DATAMOVER DRIVE4_MA DRIVE LIBR_1 rst130h 0 DETROIT_NAS DATAMOVER DRIVE5_MA DRIVE LIBR_1 rst133h 0 DETROIT_NAS DATAMOVER DRIVE6_MA DRIVE LIBR_1 rst134h 0 DETROIT_NAS DATAMOVER DRIVE7_MA DRIVE LIBR_1 rst138h 0 TSMSERV2 SERVER DRIVE0_MA DRIVE LIBR_1 \\.\tape4801101 0 TSMSERV2 SERVER DRIVE1_MA DRIVE LIBR_1 \\.\tape4801102 0 TSMSERV2 SERVER DRIVE2_MA DRIVE LIBR_1 \\.\tape4801103 0 TSMSERV2 SERVER DRIVE3_MA DRIVE LIBR_1 \\.\tape4801104 0 TSMSERV2 SERVER DRIVE4_MA DRIVE LIBR_1 \\.\tape4801105 0 TSMSERV2 SERVER DRIVE5_MA DRIVE LIBR_1 \\.\tape4801106 0 TSMSERV2 SERVER DRIVE6_MA DRIVE LIBR_1 \\.\tape4801107 0 TSMSERV2 SERVER DRIVE7_MA DRIVE LIBR_1 \\.\tape4801108 0

 

[saisai74]

infos correction

as it was not really understandable

q path f=d ( but without non valuable infos)
Source Name Source Type Destination Destination Library Node Name Device External LUN Initiator
Manager
----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- ----------- -----------
TSMSERV1 SERVER LIBR_1 LIBRARY \\.\changer0 0
TSMSERV1 SERVER DRIVE0_MA DRIVE LIBR_1 \\.\tape4801101 0
TSMSERV1 SERVER DRIVE1_MA DRIVE LIBR_1 \\.\tape4801102 0
TSMSERV1 SERVER DRIVE2_MA DRIVE LIBR_1 \\.\tape4801103 0
TSMSERV1 SERVER DRIVE3_MA DRIVE LIBR_1 \\.\tape4801104 0
TSMSERV1 SERVER DRIVE4_MA DRIVE LIBR_1 \\.\tape4801105 0
TSMSERV1 SERVER DRIVE5_MA DRIVE LIBR_1 \\.\tape4801106 0
TSMSERV1 SERVER DRIVE6_MA DRIVE LIBR_1 \\.\tape4801107 0
TSMSERV1 SERVER DRIVE7_MA DRIVE LIBR_1 \\.\tape4801108 0
DETROIT_NAS DATAMOVER DRIVE0_MA DRIVE LIBR_1 rst129h 0
DETROIT_NAS DATAMOVER DRIVE1_MA DRIVE LIBR_1 rst128h 0
DETROIT_NAS DATAMOVER DRIVE2_MA DRIVE LIBR_1 rst132h 0
DETROIT_NAS DATAMOVER DRIVE3_MA DRIVE LIBR_1 rst131h 0
DETROIT_NAS DATAMOVER DRIVE4_MA DRIVE LIBR_1 rst130h 0
DETROIT_NAS DATAMOVER DRIVE5_MA DRIVE LIBR_1 rst133h 0
DETROIT_NAS DATAMOVER DRIVE6_MA DRIVE LIBR_1 rst134h 0
DETROIT_NAS DATAMOVER DRIVE7_MA DRIVE LIBR_1 rst138h 0
TSMSERV2 SERVER DRIVE0_MA DRIVE LIBR_1 \\.\tape4801101 0
TSMSERV2 SERVER DRIVE1_MA DRIVE LIBR_1 \\.\tape4801102 0
TSMSERV2 SERVER DRIVE2_MA DRIVE LIBR_1 \\.\tape4801103 0
TSMSERV2 SERVER DRIVE3_MA DRIVE LIBR_1 \\.\tape4801104 0
TSMSERV2 SERVER DRIVE4_MA DRIVE LIBR_1 \\.\tape4801105 0
TSMSERV2 SERVER DRIVE5_MA DRIVE LIBR_1 \\.\tape4801106 0
TSMSERV2 SERVER DRIVE6_MA DRIVE LIBR_1 \\.\tape4801107 0
TSMSERV2 SERVER DRIVE7_MA DRIVE LIBR_1 \\.\tape4801108 0

 

[MAG]

Thanks I was wondering which end of the q path was which.

Can you also post the results of the following for both TSM_A & TSM_B:

q server f=d
q libr f=d (are the libraries on both servers called libr_1?)

The only thing I can see that you don't have is a datamover path from detroit_nas to the drives on tsmserv2 but being as it's only a stgpool backup I'm not sure it should need them. You could try setting them up though just in case.

 

[MAG]

On second thoughts, I don't think the paths really apply for the 2nd library on the library manager. It's been quite a while since I looks at sharing libraries across TSM servers.

 

[saisai74]

answer

Hi MAG,

as i explained there is one library onb each site
the output shows paths only on TSM_A

that's quite the same on TSM_B, except tis side, no datamover is defined neither paths from datamover to drives, only path from TSM_B to libr_B, paths from TSM_B to drives and paths from TSM_A to drives

the lib sharing works fine for all stgpools non netappdump type

 

[MAG]

Just found this in the TSM docs for NDMP requirements:

Library Sharing: The Tivoli Storage Manager server that performs NDMP operations can be a library manager for either an ACSLS, SCSI, or 349X library, but cannot be a library client.The Tivoli Storage Manager server can also be a library client, in a configuration where the NAS filer sends data to a Tivoli Storage Manager server using TCP/IP rather than to a tape library attached to the NAS filer. If the Tivoli Storage Manager server that performs NDMP operations is a library manager, that server must control the library directly and not by passing commands through the NAS file server.

How are your libraries/tape drives connected? If they're fibre and the NAS writes directly to them then you may have a problem. As far as I remember the NDMP storage pools are of a format that is unrecognised by TSM stgpool backups so stgpool backups to another library manager may not be possible. The NASTOC works though because it's a native TSM stgpool format.

I might be reading it wrong though.

 

[saisai74]

Hi,

you 're right, and in my config instead having a backup stg from primary to copy, then i'm gonna create a second datamover on the other site with right format and then two backups one on the TSM_A an dthe other one on the TSM_B, in this way i'll have my data available on both locations.

thx for enlighting the TSM stanza.

 

[MAG]

Doesn't seem right having two backups though. You could do the backup stgp locally and just send the tapes to the remote site physically using DRM.

 

[saisai74]

last info

Hi MAG,

it could be nice if the libraries were physical libraries, but with VTL, that's a bit more complicated...so i just talked with my customer and he agreed making two backups, there will be around 2 hours of difference on the two sites, but it doesn't really matter, anyway, thanks for your help.

owe you one...

regards

 

[mter]

Hello Everybody,

I'm surprised that the NDMP is not "planned" to do a backup stg but Thanks both for the expressed details and workaroud.

Saluti
MT