I use virtualnode="node to access" in the dsm.opt this will prevent the TSM records for the client from being updated.
We use this for a lot of restores or retrieves for systems that do not exist anymore. Duane -----Original Message----- From: Lawrence Clark [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 04, 2004 11:25 AM To: [EMAIL PROTECTED] Subject: Re: Access to archived files from a different node I just set the node name on the new node to the node name on the old node in dsm.sys 1st start of the client prompts for password. >>> [EMAIL PROTECTED] 2/4/2004 12:21:03 PM >>> We want to be able to retrieve archived files to a different system for cases in which the original system is no longer available (crash, DR, etc.). I tested doing a retrieve from a different system using the -fromnode option, but it worked only after I did a 'set access' for the new node from the original system. In a real situation, I wouldn't be able to go back to the original system to do a 'set access'. Is there any way to handle this scenario other than doing a preemptive 'set access' from all systems allowing retrieves anywhere? Thanks, Dan Sidorick
