|
Re: [Networker] Moving client to a different Networker server
2009-08-13 15:19:01
Oh.
Interesting that it would appear then that EMC's own documentation and
support reps have led me astray on this! The scanner -i suggestion
(which the man page says "Rebuilds both the media and the online file
indexes from the volumes read.") came from both the 7.4 DR Guide (pg.
46) and from an EMC support rep. Though they always have been giving the
caveat on engaging professional services to assist.
I can certainly see that concurrent saveset IDs could cause a problem -
but what I fail to see is how they don't become a problem in all
scenarios you describe. Either via scanning in all old savesets or
scanning as necessary; if you hit a saveset with a duplicate ssid,
wouldn't you cause the same problems? And does the conflict arise from
standard ssids, long ssids, or both? I only appear to have one short
ssid conflict and no long ssid conflicts.
Lastly, in scenarios 1 and 2, recognizing the limitations you have
described, how do you use scanner to scan in savesets from which you
need to restore, if the media db entries do not exist? Given that our
retention period for these save sets is only three months, I will likely
use scenario 2 but before I go forward I need to be sure to know how to
run saveset and file level restores in the intervening three months.
Thanks so much for your help on this, it has been most illuminating.
Regards,
Greg
Davina Treiber wrote:
Greg Etling wrote:
Hi all,
I'm working to migrate a few clients from one Networker 7.4.4 server to
another, and I'm trying to discern the quickest way to merge the index
and db entries into the new server. The documents (DRG) are a little
vague on this process, so I'd love if anyone could recommend. Leaving
the old server operational is not an option as I need to convert it into
a storage node, which will necessitate wiping out the /nsr folder and
starting clean.
Seems to me like the recommended procedure would be as follows:
On old server, run 'savegrp -O -G GROUP' for all clients on to one tape.
Insert tape into library for new server.
Run scanner -i on new server to populate indexes.
My question is: is this the most efficient way (or can I move index
files and run some iteration of nsrck), and will this give me all the
volume, saveset and expiration information?
I'm sorry to tell you this, but your plan will not work at all.
You seem to be confusing the use of scanner and index backups.
The main thing wrong with your plan is that you cannot merge media
databases from two servers. savegrp -O will backup your indices, not the
media database entries. The media database is backed up as part of the
bootstrap, but you cannot restore a bootstrap in such a way that it
merges it with the existing one.
The next thing wrong is that scanner is not used to restore index
backups. nsrck -L7 is used for this, but only if the media database
entries already exist for the save sets in question. In order to run
scanner, you need to run this on all the tapes containing backup data,
not just on the index backups.
There are three options for you here:
1) Run scanner on all the tapes containing backups for the clients in
question - a long and involved process.
2) Extract a report using mminfo which will show you what backups are on
each tape, then scan them on an individual basis if any restores are
required.
3) Engage EMC Professional Services to merge the two media databases. It
is rumoured that this is possible, but it is not common knowledge how
this is done, even within EMC. The main problem is when save set IDs
clash between the two servers.
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
|
|
|
