You should be able to use scanner on the media and get the information
on the old backups, however.

Not that is practical, depending on your enviornment, but you can do
restores from those old backups if need be.

On Fri, 2008-08-08 at 14:35 -0500, Tim Mooney wrote:
> In regard to: Re: [Networker] Problems renaming NW 7.4.2 server in 
> Windows,...:
> 
> > Here's what I am having VAST amounts of trouble understanding ... why
> > can't I rename this server back to the old name; run a mmrecov on the
> > bootstrap tape made by the last server, and have it all Just Work? Tech
> > Support is telling me it won't work, because the new server will have a
> > different client ID than the old server.
> 
> I'm wondering if perhaps there's a bit of miscommunication somewhere.
> 
> mmrecov will certainly work to get a networker server back, to the exact
> point it was at when the bootstrap you're using was taken.  Unless the
> procedure has changed since the last time I had to do it, you don't need
> to know much of anything about the old server.  Knowing the bootstrap id
> and what tape it's on is about it.  Having the correct partitions set up
> (because mmrecov is going to bring the data back to the same spot it was
> before on disk) would be useful, but as long as there's space, you don't
> even need that.
> 
> However, if I've followed other emails you've sent in the past couple
> days correctly, your current server also has 2+ weeks of backup data on
> it.  If you mmrecov back to a bootrap from several weeks ago, your
> NetWorker server is going to "forget" about all backups that have taken
> place since then.  It doesn't merge (that I know of) the old data with
> the new, because it's meant to be used in a situation where there is no
> new data.
> 
> Is it possible that what tech support is telling you is that you could
> indeed get your old data back, at the expense of losing information about
> the backups that have been done in the past couple weeks?
> 
> > So how in hades does a D/R recovery work, then?
> 
> Pretty well and fairly easily, in the few times I've had to do it.  After
> you bring the old config back, especially if you're on new hardware (or
> a new OS) you may have to adjust a few things (device paths) and if your
> host id or host name changed you may need to relicense, but other than
> that, there's not much to it.
> 
> > If my building had burned
> > down, you mean to tell me I'd have to know that 24 digit client ID,
> > *before* I could install NetWorker on the replacement hardware and run a
> > mmrecov? Seriously! That doesn't seem right to me; shouldn't the mmrecov
> > just overwrite everything, and get back all my old clients and their
> > client IDs?
> 
> It does.
> 
> IIRC, you were having tremendous problems with your previous install.
> Why would you want to run mmrecov, and risk bringing those problems back?
> What is it that you need from the previous incarnation?
> 
> Tim

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER