Multiple Data Mover Nodes Issue

dcharles226

ADSM.ORG Member
Joined
Apr 2, 2015
Messages
37
Reaction score
1
Points
0
Hello,

I am having an issue with my set up of TSM for VE 7.1.1.

So, we have two VM Datacenters, that each have their own set of VMs that we need to backup. I've configured two separate Datacenter nodes, and two separate Data Mover nodes, one for each VM datacenter that we have.

My issue is that I can only get one Data Mover node to work, it seems.

In my dsm.sys file, I have a stanza for each data mover, however when I try to run a dsmc q sess -optfile=<datamover.opt> I only get the results for the stanza that comes first in my dsm.sys file. Also, in the web gui for TSM for VE, the Configuration Status tab only shows one data mover node as being able to be reached.

Is there something I'm missing in my configs that I need to differentiate my Data Movers?

Here is an example of my dsm.sys file:

SErvername backup02
NODename OFFICE_DM
COMMMethod TCPip
TCPPort 1500
TCPServeraddress backup02
PASSWORDAccess generate
VMCHOST vcenter
VMBACKUPTYPE FULLVM
MANAGEDSERVICES WEBCLIENT SCHEDULE
HTTPPORT 1583
tcpcadaddress 192.168.106.66
errorlogname /opt/tivoli/tsm/client/ba/bin/office_dm_error.log
schedlogname /opt/tivoli/tsm/client/ba/bin/office_dm_dsmsched.log

SErvername backup02
NODename SERVERS_DM
COMMMethod TCPip
TCPPort 1500
TCPServeraddress backup02
PASSWORDAccess generate
VMCHOST vcenter
VMBACKUPTYPE FULLVM
MANAGEDSERVICES WEBCLIENT SCHEDULE
HTTPPORT 1584
tcpcadaddress 192.168.106.66
errorlogname /opt/tivoli/tsm/client/ba/bin/servers_dm_error.log
schedlogname /opt/tivoli/tsm/client/ba/bin/servers_dm_dsmsched.log

In my example, backup02 is the name of our main TSM Server, running TSM 7.1. OFFICE_DM is the name of one data mover node, and SERVERS_DM is the other data mover node. Please let me know if this makes sense to anyone.

Thanks in advance for your help.
 
Actually, here is an example of the output I am getting when trying to query each data mover node:

dsmc q sess -optfile=office_dm.opt

IBM Tivoli Storage Manager
Command Line Backup-Archive Client Interface
Client Version 7, Release 1, Level 1.0
Client date/time: 09/21/2015 14:23:54
(c) Copyright by IBM Corporation and other(s) 1990, 2014. All Rights Reserved.

Node Name: OFFICE_DM
Session established with server BACKUP02: Linux/x86_64
Server Version 7, Release 1, Level 1.100
Server date/time: 09/21/2015 14:23:54 Last access: 09/21/2015 14:01:24

TSM Server Connection Information

Home Server Name........: BACKUP02
Server Type.............: Linux/x86_64
Archive Retain Protect..: "No"
Server Version..........: Ver. 7, Rel. 1, Lev. 1.100
Last Access Date........: 09/21/2015 14:01:24
Delete Backup Files.....: "Yes"
Delete Archive Files....: "Yes"
Deduplication...........: "Server Only"

Node Name...............: OFFICE_DM
User Name...............: root

Secondary Server Information
Not configured for failover

I get the same exact response when running dsmc q sess -optfile=servers_dm.opt

Any help would be appreciated.

Thanks!
 
dsm.sys file based configuration is valid in *nix world. Are you running tsm4ve on Linux?
Also post content of your .opt files
 
I have a dsm.opt file for each data mover node:

office_dm.opt
servers_dm.opt

and they both have the same contents:

servername backup02

Yes, this is running off of CentOS 6.5. which is the vStorage Backup Server I built that is running in tandem with our main backup server running TSM 7.1.

Thanks for your response!
 
dchpost: 126124 said:
office_dm.opt
servers_dm.opt

and they both have the same contents:

servername backup02
Why? There can't be multiple stanzas in dsm.sys file with same "servername" variable.
Variable servername doesn't mean you have to insert there name of your TSM server. It has to be some unique identifier for each stanza.
To-do:
- modify each servername, to:
Servername servers_dm
Servername office_dm
- update opt files with these new servernames
 
Back
Top