You know, I think there's some nbemmcmd -renamehost or something like that. Seems to me that will get things squared away. Devices, media and all.
-Tim On 10/23/07, Tharp, Trey <[EMAIL PROTECTED]> wrote: > Here's what you need to do to resolve this from the customer side. On > the master that you are running the 'bpmedia -movedb' command create a > host entry for the old_server name and put the IP address of that as the > master. What you need to do is have bpmedia able to talk to a NBU host, > it doesn't actually do anything but want to verify connectivity. At that > point the 'bpmedia -movedb' should work and then once all the media is > no longer assigned to that server you can run 'nbemmcmd -deletehost' and > get rid of it. > > The alternative is to have Support write a sql script to update the > database references for the old media server, but they aren't always > willing to do this for all customers I don't think. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Cruice, > Daniel (US - Glen Mills) > Sent: Wednesday, October 17, 2007 2:26 PM > To: Justin Piszcz > Cc: veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Need some help > > Well...my issue is not resolved, I have gone to the extent of building a > new box with the same old media server name, and that STILL did not do > the trick. Symantec is recommending I install MP5 on the Master node. > As they have seen this issue with other customers and MP5 seemed to have > done the trick. So now I turn to my fella NBU friends are there any > gotcha's or issues with MP5 and does anyone know how long it has been > out? > > > Thanks > Dan > > -----Original Message----- > From: Justin Piszcz [mailto:[EMAIL PROTECTED] > Sent: Monday, October 15, 2007 3:20 PM > To: Cruice, Daniel (US - Glen Mills) > Cc: veritas-bu@mailman.eng.auburn.edu > Subject: RE: [Veritas-bu] Need some help > > That sounds right, do a test restore to make sure it works! > > Justin. > > On Mon, 15 Oct 2007, Cruice, Daniel (US - Glen Mills) wrote: > > > Old one back in is not an option. Where do I put the > > Force_Restore_media_Server = OLD_Retiree new_server. > Remember...Master > > server is a W2K3 box. If it goes in via the GUI of Host Properties of > > > the Master...General Server...Media host override, then I did already > > enter them. > > > > > > Thanks > > Dan > > -----Original Message----- > > From: Justin Piszcz [mailto:[EMAIL PROTECTED] > > Sent: Monday, October 15, 2007 3:04 PM > > To: Cruice, Daniel (US - Glen Mills) > > Cc: veritas-bu@mailman.eng.auburn.edu > > Subject: Re: [Veritas-bu] Need some help > > > > Hm.. > > > > Put the old one back and do it properly OR.. > > > > Use: > > > > (workaround) > > > > FORCE_RESTORE_MEDIA_SERVER = old_retiree new_server > > > > Hmm, there are probably more options but those are the ones that > > immediately come to mind. > > > > On Mon, 15 Oct 2007, Cruice, Daniel (US - Glen Mills) wrote: > > > >> I rebuilt two media servers and renamed one. And no like a dope I > did > >> not following the "retiring the media server" whitepaper that Veritas > > so > >> gracefully wrote. So now I have an issue. > >> > >> > >> > >> My entire Master / media servers are Windows 2003 6.0 MP4. The issue > > I > >> am having is getting all the media changed to the new media servers. > >> I've tried the: > >> > >> Bpmedia -movedb -ev media_ID -oldserver old_server newserver > > new_server > >> command and it seems to run fine, but when I do a bpmedialist the > > media > >> is still assigned to the old media server name. > >> > >> > >> > >> Anyone have an ideas? I've gone as far as changing the display name > > on > >> the new media server to read the old server name, modified my host > > files > >> so the old name points to the new server's IP address and simply can > > not > >> get this figured out. > >> > >> > >> > >> The caveat is I have to retain all the images on all these tapes. > >> UGGGGG > >> > >> > >> > >> Dan Cruice > >> > >> This message (including any attachments) contains confidential > > information intended for a specific individual and purpose, and is > > protected by law. If you are not the intended recipient, you should > > delete this message and are hereby notified that any disclosure, > > copying, or distribution of this message, or the taking of any action > > based on it, is strictly prohibited. > >> > > > > This message (including any attachments) contains confidential > information intended for a specific individual and purpose, and is > protected by law. If you are not the intended recipient, you should > delete this message and are hereby notified that any disclosure, > copying, or distribution of this message, or the taking of any action > based on it, is strictly prohibited. > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu