I have read the documentation on this in the Installation Guide and still
have some issues.  Most notably, changing the password on the source server
is not a good thing when it is a production server TDP SAP R/3 node name.
That can interrupt the production operation (redo logs, etc).  The case is
the restore is going to run for 4 hours because it is a 1.5TB database to
restore.

We like the password generate option for security reasons, but recognize
there are limitations when doing cross system restores of any type.  TSM
backint goes through all these gyrations to provide a feature "-f password"
to store the node password encrypted in the .bki file, yet does not have a
way to handle the problem.

A feature is really needed to be able to not interfere with the production
operation.  We do a lot of restores of production to test.

What is everyone else doing?

Paul D. Seay, Jr.
Technical Specialist
Naptheon Inc.
757-688-8180