On the suggestion of another list member, I tried something on my lab
server.

I renamed a random test client to a new name
Then I did a cp -R of
/usr/openv/netbackup/db/oldclient to
/usr/openv/netbackup/db/newclient

I didn't bounce daemons, or anything else......

Ran a diff backup of newclient, and it came out looking like another
diff of oldclient.

When I tried to do a restore, I browsed newclient and saw the image of
the recent diff, as well as all previous diffs and fulls of oldclient.

Anyone else tried this?

(a lot of my clients don't have a STREAMS file????) 

> -----Original Message-----
> From: Ed Wilts [mailto:ewilts AT ewilts DOT org] 
> Sent: November 22, 2005 10:50 AM
> To: Paul Keating
> Cc: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] tricking netbackup
> 
> 
> On Tue, Nov 22, 2005 at 08:33:48AM -0500, Paul Keating wrote:
> > On Friday night it had a full backup, and on Sunday the data was
> > migrated to SAN attached disk on a different, but same configuration
> > server.
> >  
> > is there any way to make Netbackup think that the "server1" 
> that had the
> > full on Friday night is the same machine as "server1san"?
> > The data is the same, and the system config is the same, 
> just the system
> > name, and where the physical data is located has chaged (though the
> > directory structure and drive letter is the same.)
> 
> I'm guessing (but have not verified) that the following might work:
> 
> - shut down NetBackup
> - edit the STREAMS file for server1san and include the full 
> backup entry
>   from server1
> - start NetBackup
> 
> If you try this and it works, please let me know.
> 
>         .../Ed
> -- 
> Ed Wilts, Mounds View, MN, USA
> mailto:ewilts AT ewilts DOT org
>