Of course, even with a NODENAME statement and reworking the scheduler, the
filespace names are still based on the hostname.  We have renamed plenty
of other servers that had nodename statements and the first backup was
brand-new.


Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html



From:   David Longo <David.Longo AT HEALTH-FIRST DOT ORG>
To:     ADSM-L AT VM.MARIST DOT EDU
Date:   08/22/2011 12:58 PM
Subject:        Re: [ADSM-L] Renaming a Windows node - where does it get
the nodename if no nodename statement?
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>



All you have to do is use the same "Wizard" that you used
to create the "Service" and update instead of create.  This let's you
change the node name used by the service.

David Longo

>>> Thomas Denier <Thomas.Denier AT JEFFERSONHOSPITAL DOT ORG> 8/22/2011 12:27 
>>> PM
>>>
-----Zoltan Forray wrote: -----

>Please correct me if I am wrong, but I was under the impression that
>if a Windows node does NOT have a NODENAME statement in it's dsm.opt,
>it simply asks the OS for the hostname and uses that.  This value is
>also used for the filespace names.

The documented default is the Windows machine name. This is often the
same as the IP host name, but it is possible for the two names to be
different.

[Material removed]

>Or does the scheduling process use the registry keys, not caring
>about the hostname changed?

Our experience with renamed Windows nodes indicates that the scheduler
service locks in the node name in effect at the time when dsmcutil
was used to create the service. I don't know whether this behavior
is documented. The service presumably uses the registry to store the
node name. When a Windows node is renamed, we tell the system
administrator do remove and recreate the service.



#####################################
This message is for the named person's use only.  It may
contain private, proprietary, or legally privileged information.
No privilege is waived or lost by any mistransmission.  If you
receive this message in error, please immediately delete it and
all copies of it from your system, destroy any hard copies of it,
and notify the sender.  You must not, directly or indirectly, use,
disclose, distribute, print, or copy any part of this message if you
are not the intended recipient.  Health First reserves the right to
monitor all e-mail communications through its networks.  Any views
or opinions expressed in this message are solely those of the
individual sender, except (1) where the message states such views
or opinions are on behalf of a particular entity;  and (2) the sender
is authorized by the entity to give such views or opinions.
#####################################