first time cloning server rp7410 -> rp5450 - HP UX

This is a discussion on first time cloning server rp7410 -> rp5450 - HP UX ; We recently purchased a replacement for out 'test' server and I need to clone it like the production server. The old 'test' server has a different array type & layout that makes it more reasonable to use the production server ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: first time cloning server rp7410 -> rp5450

  1. first time cloning server rp7410 -> rp5450

    We recently purchased a replacement for out 'test' server and I need to
    clone it like the production server. The old 'test' server has a
    different array type & layout that makes it more reasonable to use the
    production server as the starting point. (production rp7410, new
    rp5450)

    The production server has two vg's vg00 is the OS and vg01 is the array
    for an Informix database.

    Now from what I have read to do something like this you make a
    make_tape_recovery of both vg's to get the systems files needed and a
    full file system backup to get the other files and in our case also a
    database backup for the database. That all seems straight forward and
    simple.

    Now after I got the make_tape_recovery, I assume I do a recovery using
    the tapes on the new server. Do I have to worry about server names or
    ip addresses or any other differences between the production and test
    server at this point or do I make changes after the recovery tapes are
    done.

    What things should I look out for (possible gotchas)?

    Besides kernel parameters what other configurations will not be covered
    by the make_tape_recovery process?

    Any help, suggestions, check lists you can give me would be
    appreciated.

    John Adamski
    Network Specialist/DBA
    Graceland University


  2. Re: first time cloning server rp7410 -> rp5450

    Hi John

    > The production server has two vg's vg00 is the OS and vg01 is the array
    > for an Informix database.
    >
    > Now from what I have read to do something like this you make a
    > make_tape_recovery of both vg's to get the systems files needed and a
    > full file system backup to get the other files and in our case also a
    > database backup for the database. That all seems straight forward and
    > simple.

    I definitely recommend make_tape_recovery with options "-X inc_entire =
    VGXX" where XX is the number of the volumegroup. If you have several VGs
    use the option as often as required.


    > Now after I got the make_tape_recovery, I assume I do a recovery using
    > the tapes on the new server. Do I have to worry about server names or
    > ip addresses or any other differences between the production and test
    > server at this point or do I make changes after the recovery tapes are
    > done.

    Recovering from an ignite tape is running through the standard
    installation routine. So you will be asked for IP and hostname.

    > What things should I look out for (possible gotchas)?
    >
    > Besides kernel parameters what other configurations will not be covered
    > by the make_tape_recovery process?

    See above about the option.
    Databases may require licenses which are related to some unique system
    characteristics (IP, systemID, MAC address,...).


    Florian

+ Reply to Thread