Hi Andy,

And what if the password gets expired by passexp parm? This during the
scheduled back-up caused many of my scheduler services to stop on both
windows and Unix and failing the running back-up. 

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Andrew Raibeck
Sent: woensdag 3 januari 2007 19:10
To: [email protected]
Subject: Re: Resetting Passwords on Clients

Some things that can cause the encrypted password to "break":

- Switching between CLUSTERNODE NO and CLUSTERNODE YES (password
encryption based on host or cluster name, depending on CLUSTERNODE
value).

- If the host or cluster name changes (password encryption based on host
or cluster name, depending on CLUSTERNODE value).

- If the password is changed by means external to PASSWORDACCESS
GENERATE functionality. For example, if you use UPDATE NODE to change
the password, or you connect with that node name from a different
machine, and subsequently change the password.

- Using the same node name to connecting to two different TSM servers
that have the same TSM server name but different node passwords.

There are other trivial cases, too, such as changing NODENAME in dsm.opt
file to a node whose password has not already been encrypted.

Regards,

Andy

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew
Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED]

IBM Tivoli Storage Manager support web page:
http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageMan
ager.html

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" <[email protected]> wrote on 01/03/2007
10:29:53 AM:

> Hi,
>
> I don't know the reason why (it is at least a bit annoying) this 
> happens, but changing to using the CAD to manage the scheduler service

> help me to reduce the number of failed schedules because of this 
> problem.
>
> Regards,
>
> Karel
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf 
> Of Dennis, Melburn IT7
> Sent: woensdag 3 januari 2007 17:55
> To: [email protected]
> Subject: Resetting Passwords on Clients
>
> It seems that the biggest reason that I get reports of nodes missing 
> their schedules is because the scheduling services have stopped due to

> passwords no longer syncing up.  To remedy this I usually have to 
> reset the password, and this corrects this issue.  Is there any rhyme 
> or reason as to why this occurs.  This happens on both UNIX and 
> Windows clients.
>
>
> Mel Dennis
> Backup Systems Engineer
> Siemens Business Services
> 4400 Alafaya Trail
> Orlando, FL 32826
> MC Q1-108
> Tel:  (407) 736-2360
> Win:  439-2360
> Fax: (407) 243-0260
> Email:  [EMAIL PROTECTED]
>
> [attachment "disclaimer.txt" deleted by Andrew Raibeck/Tucson/IBM]

ÿþDit bericht is vertrouwelijk en kan 
geheime informatie bevatten enkel

bestemd voor de geadresseerde. Indien 
dit bericht niet voor u is bestemd,

verzoeken wij u dit onmiddellijk aan 
ons te melden en het bericht te

vernietigen.

Aangezien de integriteit van het 
bericht niet veilig gesteld is middels

verzending via internet, kan Atos 
Origin niet aansprakelijk worden 
gehouden

voor de inhoud daarvan.

Hoewel wij ons inspannen een virusvrij 
netwerk te hanteren, geven

wij geen enkele garantie dat dit 
bericht virusvrij is, noch aanvaarden 
wij

enige aansprakelijkheid voor de 
mogelijke aanwezigheid van een virus in 
dit

bericht.

 

Op al onze rechtsverhoudingen, 
aanbiedingen en overeenkomsten 
waaronder

Atos Origin goederen en/of diensten 
levert zijn met uitsluiting van alle

andere voorwaarden de 
Leveringsvoorwaarden van Atos Origin 
van toepassing.

Deze worden u op aanvraag direct 
kosteloos toegezonden.

 

This e-mail and the documents attached 
are confidential and intended solely

for the addressee; it may also be 
privileged. If you receive this e-mail

in error, please notify the sender 
immediately and destroy it.

As its integrity cannot be secured on 
the Internet, the Atos Origin group

liability cannot be triggered for the 
message content. Although the

sender endeavours to maintain a 
computer virus-free network, the sender

does not warrant that this transmission 
is virus-free and will not be

liable for any damages resulting from 
any virus transmitted.

 

On all offers and agreements under 
which Atos Origin supplies goods and/or

services of whatever nature, the Terms 
of Delivery from Atos Origin

exclusively apply. 

The Terms of Delivery shall be promptly 
submitted to you on your request

Reply via email to