• Please help support our sponsors by considering their products and services.
    Our sponsors enable us to serve you with this high-speed Internet connection and fast webservers you are currently using at ADSM.ORG.
    They support this free flow of information and knowledge exchange service at no cost to you.

    Please welcome our latest sponsor Tectrade . We can show our appreciation by learning more about Tectrade Solutions
  • Community Tip: Please Give Thanks to Those Sharing Their Knowledge.

    If you receive helpful answer on this forum, please show thanks to the poster by clicking "LIKE" link for the answer that you found helpful.

  • Community Tip: Forum Rules (PLEASE CLICK HERE TO READ BEFORE POSTING)

    Click the link above to access ADSM.ORG Acceptable Use Policy and forum rules which should be observed when using this website. Violators may be banned from this website. This notice will disappear after you have made at least 3 posts.

Datamover registration fails

#1
Hey all. New to TSM/large data backups in general.

I recently installed a few tape arrays, an AIX server with TSM, a couple of Dell 7610's with Fluid FS, and 4 Dell 6510 Equallogic disk storage arrays. We have about 200 TB of large data files to backup.

The problem I'm having is that datamover registration fails after TSM receives the backup type information. A packet capture and the logs confirm that TSM and NDMPD exchange authentication, which passes, server information, host information, and backup type information then TSM reports that registration fails.

Since the TSM disconnects immediately after receiving the backup type info I assume that the packet contains incomplete information. Below is the NDMPD logs which outlines the information passed to the TSM before the TSM closes the connection.

DG:CM 06/19 11:08:56.208112 802:7a4a8160 msg_diag.c:ndmp_config_get_butype_info_reply_pri START BUTYPE_INFO, error: NDMP_NO_ERR​
DG:CM 06/19 11:08:56.208128 802:7a4a8160 msg_diag.c:ndmp_config_get_butype_info_reply_pri butype_name:dump​
DG:CM 06/19 11:08:56.208143 802:7a4a8160 msg_diag.c:logNdmpPvals:2635 len: 19​
DG:CM 06/19 11:08:56.208159 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: FILESYSTEM, value: }​
DG:CM 06/19 11:08:56.208174 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: EXCLUDE, value: }​
DG:CM 06/19 11:08:56.208190 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: HIST, value: Y}​
DG:CM 06/19 11:08:56.208212 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: VERBOSE, value: N}​
DG:CM 06/19 11:08:56.208231 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: LEVEL, value: 0}​
DG:CM 06/19 11:08:56.208252 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: UPDATE, value: Y}​
DG:CM 06/19 11:08:56.208267 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: COMPRESS_DATA_STREAM, value: N}​
DG:CM 06/19 11:08:56.208283 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: SNAPSHOT, value: Y}​
DG:CM 06/19 11:08:56.208298 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: EXTRACT_ACL, value: Y}​
DG:CM 06/19 11:08:56.208313 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: BLOCKING_FACTOR, value: 0}​
DG:CM 06/19 11:08:56.208329 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: BASE_DATE, value: -1}​
DG:CM 06/19 11:08:56.208344 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: LISTED_INCREMENTAL, value: N}​
DG:CM 06/19 11:08:56.208359 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: DEREF_HARD_LINK, value: N}​
DG:CM 06/19 11:08:56.208374 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: NUM_DATA_READER, value: -1}​
DG:CM 06/19 11:08:56.208390 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: DIRECT, value: N}​
DG:CM 06/19 11:08:56.208405 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: RECURSIVE, value: Y}​
DG:CM 06/19 11:08:56.208420 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: RESTORE_OVERWRITE, value: Y}​
DG:CM 06/19 11:08:56.208435 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: READ_AHEAD, value: }​
DG:CM 06/19 11:08:56.208451 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: NUM_FILE_OPENER, value: -1}​
DG:CM 06/19 11:08:56.208466 802:7a4a8160 msg_diag.c:ndmp_config_get_butype_info_reply_pri butype_name:tar​
DG:CM 06/19 11:08:56.208481 802:7a4a8160 msg_diag.c:logNdmpPvals:2635 len: 19​
DG:CM 06/19 11:08:56.208496 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: FILESYSTEM, value: }​
DG:CM 06/19 11:08:56.208512 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: EXCLUDE, value: }​
DG:CM 06/19 11:08:56.208527 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: HIST, value: Y}​
DG:CM 06/19 11:08:56.208543 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: VERBOSE, value: N}​
DG:CM 06/19 11:08:56.208558 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: LEVEL, value: 0}​
DG:CM 06/19 11:08:56.208573 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: UPDATE, value: Y}​
DG:CM 06/19 11:08:56.208590 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: COMPRESS_DATA_STREAM, value: N}​
DG:CM 06/19 11:08:56.208606 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: SNAPSHOT, value: Y}​
DG:CM 06/19 11:08:56.208621 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: EXTRACT_ACL, value: Y}​
DG:CM 06/19 11:08:56.208639 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: BLOCKING_FACTOR, value: 0}​
DG:CM 06/19 11:08:56.208654 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: BASE_DATE, value: -1}​
DG:CM 06/19 11:08:56.208669 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: LISTED_INCREMENTAL, value: N}​
DG:CM 06/19 11:08:56.208689 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: DEREF_HARD_LINK, value: N}​
DG:CM 06/19 11:08:56.208705 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: NUM_DATA_READER, value: -1}​
DG:CM 06/19 11:08:56.208721 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: DIRECT, value: N}​
DG:CM 06/19 11:08:56.208736 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: RECURSIVE, value: Y}​
DG:CM 06/19 11:08:56.208759 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: RESTORE_OVERWRITE, value: Y}​
DG:CM 06/19 11:08:56.208775 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: READ_AHEAD, value: }​
DG:CM 06/19 11:08:56.208790 802:7a4a8160 msg_diag.c:logNdmpPvals:2638 {name: NUM_FILE_OPENER, value: -1}​
DG:CM 06/19 11:08:56.208805 802:7a4a8160 msg_diag.c:ndmp_config_get_butype_info_reply_pri END BUTYPE_INFO​

I'm increasing the verbosity of the TSM logs to get more information but I don't have it yet. I was hoping that someone could point me in the right direction as to what I need to change.
 

moon-buddy

ADSM.ORG Moderator
#2
Have you set the right parameters when you defined the datamover - IP address (or DNS entry), TCPPort, correct user nme, etc?

Is the NAS device zoned or wired correctly?
 
#3
Those parameters are correct, I have confirmed by packet capture and checking the logs on the Dell Fluid FS device.

The wiring is correct otherwise I wouldn't get the packet capture. As for zoning, I'm not 100% sure. My TSM consultant has done most of the configuration and flat file backups work (but are slow) this probably means that the zoning is correct.
 

moon-buddy

ADSM.ORG Moderator
#4
Those parameters are correct, I have confirmed by packet capture and checking the logs on the Dell Fluid FS device.

The wiring is correct otherwise I wouldn't get the packet capture. As for zoning, I'm not 100% sure. My TSM consultant has done most of the configuration and flat file backups work (but are slow) this probably means that the zoning is correct.
If flat file backups are slow and the intent was LAN Free backups (datamover setup is NOT the same as LAN Free), then you don't have the right settings.
 
#5
Unfortunately I don't really have the specifics as far as that goes. I'm relying heavily on my consultant for the configuration details. If you can be more specific as to what settings I should be looking for or what resources I can research to confirm the correct settings I would appreciate it. I'm flipping through online manuals but I'm not exactly sure what I'm even looking for at this point.
 

Advertise at ADSM.ORG

If you are reading this, so are your potential customer. Advertise at ADSM.ORG right now.

UpCloud high performance VPS at $5/month

Get started with $25 in credits on Cloud Servers. You must use link below to receive the credit. Use the promo to get upto 5 month of FREE Linux VPS.

The Spectrum Protect TLA (Three-Letter Acronym): ISP or something else?

  • Every product needs a TLA, Let's call it ISP (IBM Spectrum Protect).

    Votes: 17 19.5%
  • Keep using TSM for Spectrum Protect.

    Votes: 53 60.9%
  • Let's be formal and just say Spectrum Protect

    Votes: 10 11.5%
  • Other (please comement)

    Votes: 7 8.0%

Forum statistics

Threads
31,468
Messages
134,117
Members
21,565
Latest member
Chrescht
Top