transferring ignite images/files?

[Craig E.]

Would it be possible to...
Use ignite version A2.2160 (yes i know very old, but cannot be changed) to make_recovery_tape or some other command then copy all those files to a differnet machine entirely, hook up a SCSI hard drive to this machine then recover the backup that ignite made, to that hard drive. Then hook that SCSI hard drive back up to its original machine and have it work? The reason i ask is i want to be able to make recovery images in the lab on the same hardware then copy those images to a large hard drive, so i can store multiple images on a machine, then take this machine to another location hook up different SCSI hard drives to a SCSI port, copy the correct image using ignite, plug the hard drives back up to thier original machines and be good to go.

The ignite recovery would be done on the same machine as the target machine then copied to a server/workstation then copied to a hard drive to be hooked back up to the same type of machine that the image was made from.

Any other ideas like these are welcome and appreciated.

Thanks for the time,
Craig

[Mark Grant]

Craig,

I might be misunderstanding you here but it sounds like you are trying to build an Ignite Server. That is a server that stores Ignite images and you can build machines off of it. This is all covered in the Ignite documentation. You might want to take a look.

[Craig E.]

I am trying to build a server of sorts. However i want to hook hard drives directly up to the server and ignite to them. So i would unplug the hard drive from my 744 card and plug it into an open SCSI port on the server then ignite dirctly to the hard drive from a storage area off the server, then plug the hard drive back into the 744 card and be on my way.

Is this still posible?

[Steven E. Protter]

The docs(goods)
http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90772/B2355-90772_top.html&con=/hpux/onlinedocs/B2355-90772/00/00/11-con.html&toc=/hpux/onlinedocs/B2355-90772/00/00/11-toc.html&searchterms=10.20%7cconfiguration%7cIgnite&queryid=20040203-083857

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90153/B2355-90153_top.html&con=/hpux/onlinedocs/B2355-90153/00/00/24-con.html&toc=/hpux/onlinedocs/B2355-90153/00/00/24-toc.html&searchterms=10.20%7cconfiguration%7cIgnite&queryid=20040203-083857

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90126/B2355-90126_top.html&con=/hpux/onlinedocs/B2355-90126/00/00/25-con.html&toc=/hpux/onlinedocs/B2355-90126/00/00/25-toc.html&searchterms=10.20%7cconfiguration%7cIgnite&queryid=20040203-083857

http://docs.hp.com/cgi-bin/fsearch/framedisplay?top=/hpux/onlinedocs/B2355-90772/B2355-90772_top.html&con=/hpux/onlinedocs/B2355-90772/00/00/7-con.html&toc=/hpux/onlinedocs/B2355-90772/00/00/7-toc.html&searchterms=10.20%7cconfiguration%7cIgnite&queryid=20040203-083857

I have specifically pulled version specific documents for you.

SEP

[Nivesh Patnaik]

I'm not sure you can ignite the disks connected directly to the ignite server.
Is there any reason you cannot boot the target system and do a network install off the Ignite server?

[Nivesh Patnaik]

If I understand you correctly, you are trying to put the image of disk A on disk B, and plug disk B back in the original system and have it boot up.
make_tape_recovery creates an archive using tar or cpio. Putting that archive on the disk won't do anything for you. You would first need to have filesystems on that disk
with a kernel to boot off.

[Craig E.]

Nivesh, Out network runs at 1MB/sec so it would be really slow. We currently use 4mm tapes with ignite and they transfer at roughly 1MB/sec also (takes 1 hour to transfer everything we need from tapes). If we could bypass the ethernet port on the 744 cards and write directly to the hard drive somehow we could write at about 15-20MB/sec. Right now i am trying to come up with concepts as an alternative to the 4mm tape method. Using the LAN and ignite server is definatly one of the concepts but we need to have multiple installs occurring at the same time to benefit.

This concept is to put an image of disk A onto some storage area of disk B, then unhook Disk C from machine C transfer image A from disk B to disk C then plug disk C back into machine C.

[Nivesh Patnaik]

I'm not sure how many disks your target system has or what is the total amount of
data constituting a complete target system.

Also, based on your time constraints, I would
recommend the following:
-Put an archive of the minimal OS and put it on the DDS4 tape. Use the -x include=/exclude= options if you must to trim the fat. Make sure all your OS mount points are all contained on one disk.
Igniting the system with the boot tape shouldn't take more than 15 min.
-If you must, put the rest of the voluminous
data on disk C from the archive server, so that when you take dick C and attach it to your target system, you can add it as a whole disk on some mount point.

I haven't tried this approach, but it is for
your digestion.

[Steven E. Protter]

You will get more throughput on the network.

Try make_net_recovery

attaching a script.

These images are only good to restore the server that generated them. Not good for golden image or system transfer.

make_net_recovery -s tzfat -a tzfat:/images/tzfat.juf.net -x inc_entire=vg00

This will work against a supposedly secure NFS mountpoint.

SEP