Andy,
since i want to collect and analyse the dsmsched.log of the done backups i
like to do the following:
- a daily second schedule for each node that does a backup of dsmsched.log -
easy and e.g. no access problems for firewalled systems, no different access
methods for different operating systems,...
- restore of that logs from a central secure point for analysis and
reporting - i would like to do this auotmated with as less effort as
possible. (no set access for new nodes,...)
so: can the admin logon with commandline be done full automated?
Thanks a lot
Stefan Holzwarth
-----Ursprüngliche Nachricht-----
Von: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
Gesendet: Mittwoch, 7. Juli 2004 18:38
An: ADSM-L AT VM.MARIST DOT EDU
Betreff: Re: AW: Antwort: Restore from node to another node
If you use -VIRTUALNODENAME=<nodename> from the command line, then enter
your admin ID and password when prompted for the user ID, you can access
the node's data. Some considerations:
1) In general, most users do not (or should not) have admin IDs that can
access another node's data. As a TSM administrator (as most ADSM-L
subscribers are) you have this access, but if non-admin user A wants to
share data with non-admin user B, the -VIRTUALNODENAME option won't work.
2) In general, I would hope that admins with the authority to access other
node's data would not do so indiscriminately or without the user's
knowledge.
3) My comments are for very general cases (which is why I say "in
general..." quite a bit) since the original question was not very
specific. Of course, depending on your exact circumstances, one method
might be preferable to the other. But for the very general question of
"how can I access node A's data from node B?", my general answer is still
to use SET ACCESS and -FROMNODE. The -VIRTUALNODENAME method is available
only to TSM administrators (almost certainly the minority of your TSM user
community) and -NODENAME should be used rarely, if ever, as I've already
mentioned.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/07/2004
08:55:52:
> Within the gui i have another option to use my admin account at the tsm
> server for authentication.
> Can you do this from the commandline? Ist very comfortable and you have
no
> password issues and no set access stories...
> Kind Regards
> Stefan Holzwarth
>
>
> -----Ursprüngliche Nachricht-----
> Von: Andrew Raibeck [mailto:storman AT US.IBM DOT COM]
> Gesendet: Mittwoch, 7. Juli 2004 17:45
> An: ADSM-L AT VM.MARIST DOT EDU
> Betreff: Re: Antwort: Restore from node to another node
>
>
> I do not recommend putting NODE1's node name in NODE2's options file. If
> PASSWORDACCESS GENERATE is being used (which is the likely case) then
this
> will cause NODE1's password to be encrypted on NODE2's machine. For
> example, if you came over to my machine and put your node name in my
> options file so we could restore one of your files to my machine, then
> once you enter the password, it will be encrypted on my machine,
allowing
> me access to all your files whenever I want (or until the password is
> changed externally). Not only that, but I could change your password and
> thus deny you access to your own node data, at least until you can get
the
> TSM admin to straighten out the situation. So except in specific cases
> where the behavior I describe is acceptable or desirable, I do not
> recommend using the NODENAME method. Instead, either use SET ACCESS to
> allow NODE2 to access NODE1's data, or else use -VIRTUALNODENAME=NODE1
if
> you want to come over to my machine and enter the password. With
> -VIRTUALNODENAME, the password will not be stored on my machine.
>
> Regards,
>
> Andy
>
> Andy Raibeck
> IBM Software Group
> Tivoli Storage Manager Client Development
> Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
> Internet e-mail: storman AT us.ibm DOT com
>
> The only dumb question is the one that goes unasked.
> The command line is your friend.
> "Good enough" is the enemy of excellence.
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 07/07/2004
> 08:31:57:
>
> > You can change the DSM.OPT/SYS and specify the NODENAME of the server
> you
> > want to restore FROM. Or you can start the GUI with the
> -VIRTUALNODENAME=
> > parameter. Another way is to grant access to the FROM nodes' data to
the
> TO
> > node.
> >
> > But you are still limited to restoring to the SAME operating
> > system...Windows-Windows Unix-Unix and Novell-Novell....no cross
system
> > restores.
> >
> > Bill Boyer
> > DSS, Inc.
> >
> > -----Original Message-----
> > From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf
Of
> > Christian Demnitz
> > Sent: Wednesday, July 07, 2004 11:11 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Antwort: Restore from node to another node
> >
> >
> > yes, you have to modify the dsm.opt/sys entry with you restore node!
> >
> >
> >
> > Christian Demnitz
> > CoC ADSM/TSM
> >
> > Sinius GmbH
> > mailto:christian.demnitz AT sinius DOT com
> > WWW -> http://www.sinius.com
> >
> >
> >
> >
> > Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>
> > Gesendet von: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > 07.07.2004 17:03
> > Bitte antworten an
> > "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> >
> > An
> > ADSM-L AT VM.MARIST DOT EDU
> > Kopie
> >
> > Thema
> > Restore from node to another node
> >
> >
> >
> >
> >
> >
> > Hello, All
> >
> > Is it possible to restore a file from one Node to another Node
> > using the GUI?
> >
> > Also Is it possible to restore a file on a Novell box to a Windows
Box?
> >
> > Thanks in advance for all responses!
> >
> > TSM version 5.2.1.3
> > Running AIX 5.1
|
