Yes, right now we are using nodename.ids1.intelonline.com to the new
providers name nodename.heyiamthenewprovider.com.  All of the clients are
currently registered with the first name so all of the images are associated
with it.  We will still need to be able to restore the old data after they
move, they have an infinite retention policy (don't ask...).  It sounds like
Tim McMurphy's method would probably work, though I will investigate a
little further, I want to save the pooch :)

Michael French
Platform Engineer
Intel IOS
(408)765-6676


-----Original Message-----
From: David A. Chapa [mailto:david AT datastaff DOT com]
Sent: Tuesday, January 21, 2003 3:28 PM
To: Len Boyle
Cc: French, Michael P; Veritasbu (E-mail)
Subject: RE: [Veritas-bu] Migration question


SAVE THE POOCH!

so you have an existing NBU environment and it uses

clientname.theirdomain.com

for the clients?

and you want to be able to restore data from those to the new FQDN

clientname.intel.com

?

I'm thinking that you want to look at using altnames...but I would want to 
clarify some of this information first.


David
Quoting Len Boyle <Len.Boyle AT sas DOT com>:

> Hello Michael
>  
> As far as I know, netbackup has no command or support function like the
tsm
> rename node command. 
> Most likely because one was planning on doing a full backup on the next
> weekend anyway. Something TSM tries to stay away from. 
>  
> Since the netbackup catalog is a series of flat files, a guru might have a
> perl script for renaming all the parts required to rename a node. But I
have
> not heard of it. (Not an auth answer).  
>  
> If not it is not that bad. If one deletes all the nodes from the old
classes
> (policies in nbu 4.5) this does not delete the image files in the
netbackup
> catalog, so one can still do restores using  the old node names. 
>  
> If you did not want to have all the old FQDN names deleted from policys
and
> do not mind having double entries, one could mark the existing classes
> incactive and define new classes with the new node names. 
>  
> Let us know how it works out. 
>  
> len boyle
>  
>  
>  
>  
>  
>  
> 
>       -----Original Message----- 
>       From: French, Michael P [mailto:michael.p.french AT intel DOT com] 
>       Sent: Tue 1/21/2003 2:12 PM 
>       To: Veritasbu (E-mail) 
>       Cc: 
>       Subject: [Veritas-bu] Migration question
>       
>       
> 
>               My company is in the process of transitioning one of our 
customers
> 
>       to another provider.  The customer is using Netbackup 3.4 and all of

the 
>       clients are setup using the FQDN.  Since the current names reflect
my 
>       companies FQDN, we need to change this to the new provider's.  I am 
more 
>       familiar with TSM, where I just rename the node and all of the data
is 
kept
> 
>       in tact with the client, does Netbackup work the same?  I don't want
to 
>       screw the pooch on this, any suggestions would be welcome.  Please 
email me
> 
>       with questions if I have been unclear in this post.  Thanks in
advance. 
> 
>       Michael French 
>       Platform Engineer 
>       Intel IOS 
>       (408)765-6676 
> 
>       _______________________________________________ 
>       Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu 
>       http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu 
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>