st Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Paul
>Zarnowski
>Sent: Tuesday, June 07, 2011 2:31 PM
>To: ADSM-L@VM.MARIST.EDU
>Subject: Re: TSM & client machine renames
>
>Thank you for all of your suggestions.
>
>To answer some of your questions:
>- The nod
t: Re: TSM & client machine renames
Thank you for all of your suggestions.
To answer some of your questions:
- The nodename is usually specified in the dsm.opt, not defaulted from the
machine name;
- Our nodenames are generally NOT related to the machine name (but this may
change as a result
Thank you for all of your suggestions.
To answer some of your questions:
- The nodename is usually specified in the dsm.opt, not defaulted from the
machine name;
- Our nodenames are generally NOT related to the machine name (but this may
change as a result of our AD reorg);
- We do not have cent
Paul,
Regarding the characteristic where the TSM Scheduler remembers the nodename.
For Windows:
" The service seems to remember the node name in effect when the service was
created, even in the absence of a 'nodename' option in dsm.opt. I don't know
whether there is a way to change the node nam
i used dsmadmc has a backend for a CGI script. used perl modules DBD::TSM and
DBI, but you can call dsmadmc directly. Access was controlled thru clear text
file that was no way related to TSM access and deleted after we were done.
Timing was key but well documented for users to follow. Hope this
-Paul Zarnowski wrote: -
>We are contemplating a massive Active Domain reorganization which
>would involve renaming hundreds of Windows machines that we backup
>into TSM. We forsee a few problems with this, and I am looking to
>see if any other TSM sites have faced a similar problem and w
You can form a SQL query to get the nodes from a TSM instance of a given
OS platform.
If hostnames are related in some deterministic fashion to the nodenames,
and you have remote r/w access to \\nodename\c$\path\to\dsm.opt via AD,
and you have something equivalent to sed you can script the dsm.opt
We have on occasion created a batch job that runs on the TSM servers that users
can feed a few parameters to then have our operations group run it through the
enterprise scheduler. This allows a user to run a command of higher privilege
but still be under control. Also the users may have the j
