Alec,
I am again back after soft time ... after to do some other stuffs...
I thank you for your suggestions i will test that but not for this migration
..
And I am very prudent with this copy od the resources directory /nsr.
because the ressource id (and other stuff ?) will not be the same in the new
server, as i guess. the desaster recovery is a better solution to recover the
old config in the new server.(not the same ip/hostname)
I know that our customer alreday did a copy of /nsr from an old to antoher.
he reported me that was ok , but i was not sure that is 100% true.. Open
question...
We will stay at 7.4.4 , no upgrade to 7.5.1 actually...
There are lot of issues solved but it still a confirmation about the directory
/nsr-file-dev0, which is a filesystem (not a device) to save the log filess
from Informix...
I (and our customer ) will stop one day the both networker servers and copy
this directory form the old to the new... before to start it...
has anyone already to work like that tranfer-copy about this /nsr-file-dev0
?
thank in advance ...
Claude
----- Mail Original -----
De: "Anacreo" <anacreo AT gmail DOT com>
À: "Claude Angéloz" <angelozc AT acceleris DOT ch>, "EMC NetWorker discussion"
<NETWORKER AT listserv.temple DOT edu>
Envoyé: Vendredi 4 Septembre 2009 19h22:00 GMT +01:00 Amsterdam / Berlin /
Berne / Rome / Stockholm / Vienne
Objet: Re: [Networker] Migration
Claude,
You're not really doing a disaster recovery here... your doing as you say a
server migration. Based on your environment if I was doing this I'd do the
following:
On old server:
Put in NSR Upgrade Enabler code for NetWorker 7.5.1
Shutdown old NetWorker...
Copy all the /nsr directory from old server to new server
On new server:
I'd recommend a ZFS file system on new server for /nsr, if done, make a
snapshot before running installs.
* We enable compression on the /nsr volume (currently at 1.24:1 compression)
Install NetWorker 7.5.1 over the now existing /nsr directory.
Startup NetWorker 7.5.1
Delete all JukeBoxes and drives
Scan for new JukeBoxes and drives
If any problems exist rollback...
I also didn't want to have any media problems so I only had a few new tapes
available for my first few backups, but this is just a precaution so I could
safely rollback.
Good luck and happy huntings... I'd recommend doing the nsrck -L6 before and
after, the upgrade but we didn't have time for this before the upgrade.
Alec
On Fri, Sep 4, 2009 at 2:42 AM, Claude Angéloz < angelozc AT acceleris DOT ch >
wrote:
Anacreo, Alec
Thany you for your help, but I am not sure that help . May I was not 100% clear
with my english, I apologize that.
Some comments :
>>>>If you're doing a straight migration, in my experience, from the same
>>>>platform Windows 2 Windows, Solaris 2 Solaris,
>From OS view , I will make a straight migration (Solaris 8 to Solaris 10) ,
>but not from the HW , old platform Sun V480 to Sun M4000, same
>robotics-libraries and VTL to switch to the new HW as well new hostname/ip ...
>>etc... Then stop NetWorker, copy /nsr (Make sure you don't harm your old data
>>for a rollback),
In the past , I alreday made a migration from an old platform to a new HW (not
the same hostname and ip, etc ), according the procedure form the DRG
Documentation ( for example bakup all indexes from whole groups, and restore
with mmrecov, ans so one at end nsrck -L7, etc.. ) , not only transfer the /nsr
to the new sysrem .
Procedure much more complex as described in the documentation DRG (desaster
recovery guide) . I wrote in relation with the customer a detailed
documentation what we did, not in english... It was ok ,except the fact there
is , in some file /nsr/res from the new server , still the old name server...I
must solve that but it is not urgent... if anybody had an idea .. it concerns
"localhost" configuration files.. i dont know how to remove 100% the old name
server in the new ..but it is not the purpose of this email. The old one is
completly remove from the network..
>>>start NetWorker, delete all your Jukebox and Device info... (yes its a pain
>>>to remove them from your media pools), add them in.
We have installed from scratch into th new HW the networker 7.4.4 , not yet
licensed , will be done later...
>>>If you're going to do a NetWorker upgrade during this move, make sure you
>>>put in the upgrade enabler BEFORE shutting down the old environment. If
>>>you're licenses I highly recommend going to 7.5.1, seems pretty good to me
>>>so far in terms of new features.
As wroten before :
>>>- there is a module for Informix , which write Logs to a special device
>>>called /nsr_file_dev0 , a file system on a partition.
I guess that is possible to do a simple copy of these files to the new
server...but i would like to be sure..
This not in /nsr , that are the backup of the log files in Informix... I
guessed That I can copy after the stop of the source Networker
to the target networker. But I am not sure...
>> there are some storage nodes configured , which are NAS with datamovers. I
>> guess that the mmrecov procedure revocevers the configuration from the old
>> server about these storage nodes without issues..
In my previous migration of an other networker server , it was only a storage
node , which was the networker server itself..
I hope that the mmrecover will transfer right the config
As the first step the test of recovering of all indexes group and the bootstrap
of the source networker server was ok..
Thanks
Claude Angeloz
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
|