Migration from K260 to rp5470

[ajk_5]

Dear all,

I am doing the migration from K260 (non-trusted system) to rp5470 (trusted system) today. Could you all give me some practical details of OS parameter setting, OS directory setting, User logins/ User groups/ User password/ Users' owned files in their /home directories migration, Print spooler (pcprint), and Backup strategy for the new server rp5470?

Thanks Very Much!

Best Regards
ajk

[malay boy]

wow!!! I can't answer all your question but this what I do when I migrate from K220 to K570 different machine(I guest it is the same migrating from K to L).The server running oracle and network monitoring system from nokia application,NIS,MC Service Guard.

1) We ignite the K220 ->make_recovery -Av
This will create a backup for vg00 only.
(New Ignite allowed to port to different server).

2) Make backup frecover K220 for all directories which are not in VG.

3) Create a cold oracle backup.

4) Stop all application running on that system.

5) Next,boot new server K570 with Ignite from K220.
(all the user are restored from K220 to K260,etc)

6) Changed the Service Guard Configuration .As new disk path are different.

7) Restored the oracle database.

8) Bring Up application and asked user to test it out.

9) Done.

Note:Before we does this we have month of planning and discussion including discussion with HP.
Size does matters.Make sure the new server are capable of handling the ported data.

That all I can say....

still learning,
mB

[Lee Tae-kyung]

If I do this work, I will check following things.

1. files that copy new server.
/etc/hosts,/etc/rc.config.d/netconf, /.profile , /home/*
/etc/passwd,/etc/group, /var/spool

2. #sysdef => kernel values.

3. #swapinfo

4. #swlist

5. Check the home directory of special user.

6. Check /etc/fstab

7. bdf info

8. #crontab -l

and so on....

I hope these answers help you.

Good luck~~

^^ From korean..

[ajk_5]

Sorry guys! I means I don't know how to do those stuff in detail that I did mention before. Could you tell the procedure doing them, please? Thank you!!

Best Regards
ajk

[Steven E. Protter]

This is not a pc migration.

Because your target system is trusted and the source is not, you can't just cut and paste out of the /etc/passwd file.

The only supported methodology as far as I know would be to manually enter the user id's setting the passwords to default value.

Good security practice would be to make sure all user id's expire in seven days if they are not used.

Backup Strategy:

With all apps and databases down, fbackup once a week.

Use sam to do it, eventually go to a scripted backup.

You will need an ignite backup of the system once a week, make_tape_recovery

Kernel parameters:

on the K box.

kmtune

Do your best in sam to meet or exceed kernel setting from the old box. Be generous especially with shared memory segments.

Now all you need is six months to properly do the migration and test all your applications.

In my shop, the process from specifcying the hardware to final prodution on a 3 new machine for two production machines class D is two years.

The first year was spent drawing up specs and getting bids. The next YEAR was spent dealing with the issues you brought up in your post.

We are in parital production right now and should be full production by June 27.

SEP