Hi to all,

One way that maybe tricks netbackup that the new servers were backed up is to 
rename the image directory of the old server to the new server name.
>From /usr/openv/netbackup/db/images/old_server_name
To /usr/openv/netbackup/db/images/new_server_name

One other think I can imagine, is to copy the streams file from the old 
server?s image dir to the new server?s image dir.

Always do a copy of the destination directory or file.

stefanos


>  -------Original Message-------
>  From: Paul Keating <pkeating AT bank-banque-canada DOT ca>
>  Subject: [Veritas-bu] tricking netbackup
>  Sent: 22 Nov '05 13:33
>  
>  I have a fileserver  with a 800Gig SCSI attached array configured as S
>  drive.
>  
>  
>  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.
>  
>  
>  A manual full was  not performed, so when the schedule ran last night, the
>  cumulative took a long time to run......
>  
>  I can't afford to  run this cumulative every night.....matter of fact I
>  can't even afford to run a  full now, as it will run into production hours
>  (can't hit the server or network  with that right now)
>  
>  
>  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.)
>  
>  
>  Paul