Results 1 to 3 of 3
  1. #1
    Newcomer
    Join Date
    Feb 2012
    Location
    Minneapolis, MN
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default ASNODENAME vs. using the same NODENAME on different servers

    We have two servers which share a clustered filesystem. The servers themselves are not in a clustered configuration--they just share a common directory. Currently both servers have a unique nodename: server1 and server2. The problem is they're both backing up our /shared directory so we're getting two copies. The solution which I went with (and what I think is probably best practice) was to create a new TARGET NODE on TSM (cluster1) with authority to two agent nodes cluster1-server1 and cluster1-server2 which are defined as asnodenames on each servers dsm.sys file. I then modified the dsm.sys files so that /shared is excluded on server1 and server2 node stanzas and is in a domain statement for cluster1-server1 and cluster1-server2 node stanzas. Through this setup, everything seems to be working fine.

    My question is this: wouldn't it be easier just to create a new node called "cluster1" which is definied on both servers for just the /shared directory and still keeping each server's unique nodename as well. What kinds of problems could I encouter with this? Put another way, what's the point of ASNODENAME and agent/target nodes when you could just create an additional node which both servers use just for the cluster.

  2. #2
    Senior Member GregE's Avatar
    Join Date
    May 2006
    Posts
    2,100
    Thanks
    9
    Thanked 17 Times in 16 Posts

    Default

    I have several servers clustered like that, and I don't use asnodename. To me it's much simpler to do the additional nodename to backup the shared disks.

  3. #3
    Newcomer
    Join Date
    Feb 2012
    Location
    Minneapolis, MN
    Posts
    7
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hmm. Maybe the only benefit is for troubleshooting. By using asnodename you might be able to see which client node was having issues?

Similar Threads

  1. different nodename on one WINOS Client
    By sai0001 in forum TSM Client
    Replies: 2
    Last Post: 07-15-2008, 11:24 AM
  2. Demystify Servername nodename and the such.
    By Stephan in forum TSM Client
    Replies: 2
    Last Post: 04-14-2007, 07:00 AM
  3. Multiple nodename
    By retrack in forum Backup / Archive Discussion
    Replies: 1
    Last Post: 09-07-2005, 10:40 AM
  4. Replies: 1
    Last Post: 09-26-2003, 10:11 AM
  5. Different Nodename, TDP for Oracle
    By djofly in forum TDP/Application Layer Backup
    Replies: 3
    Last Post: 03-26-2003, 10:59 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •