Hi Nicola,

There is a supported process - but has to be done by EMC Professional Services or a service enabled EMC partner (and your company may be one of those partners?). Cross-platform migrations performed solely by end-customers are not supported.

-Eric

Are there some tricks or some roles about NW platform migration?

There is more than one and perhaps that might be the reason why this is not good idea to be performed on your own.  But I'm wondering another thing, why from Solaris to Windows?  I suppose you are consolidating and move away from Sun/Oracle, but why Windows?  Linux, as far as I see it, would be better choice for backup server...

Hi ,i must move to windows because Emc SA had decided so. I'd prefer move to linux ,me too :-(

Thank you

-Nicola

I've a big problem about transfering index because costumer LAN is very slow. I've 200GB for /nsr/index. I've tried with nsrck -L6 & -L7 in order to reduce index size..without any benefits. I cannot wait 8/10 hours for index transferring completation (i'll lost too much backup jobs).

Have you some ideas in order to reduce index size or in order to moving index faster ?
thx
-Nicola

about index trasfering ,we'll do so:
day 1 : ftp copy from solaris to windows2008 folder

day 2,3,4 ftp completation

day 5 NFS mount of windows folder (where index was copied) on solaris NW  server, installing rsync tool on solaris server. The production is  running normally on solaris NW server. Resyncing solaris /nsr/index with  folder index-copied mounted NFS.

day 6 stop NW services on solaris Nw server . Last resync of /nsr/index  and folder index-copied . Cross platform migration procedure . Start  services on new windows NW server

In this way i must stop NW services only for last resync time. I've  seen that /nsr/index have a delta < 1Gb for day. So i'll stop nw  services in order to have consistence indexes only for resyncing less  than 1 Gb of data.


-Nicola

Well, I'm not sure your approach will take care of endian compatibility.  But, I'm quite sure if you would use dedicated asms to dump both index and mdb from one system to other that would do the trick.  And most probably you would be done in single afternoon (unless you use USB 1.1 external disk to move the data).

Hi all,

i've used rsync for index transfering.

After last rsync with NW services down (about 30 minutes) ,in order to have consistency,i've imported mediadb .

After operation on new NW windows server (rename,DNS,etc) ,i've restarted NW services and tried some critical restore.

All has work fine!

thx all for the suggestions

-Nicola