Operating System - HP-UX
1834773 Members
3108 Online
110070 Solutions
New Discussion

Re: make_tape_recovery question

 
SOLVED
Go to solution
Amiel Tutolo
Frequent Advisor

make_tape_recovery question

I have a new server that doesn't have a tape drive attached to it. I am installing ignite-ux in order to use the make_tape_recovery app. Can I create the image on a remote tape drive? or do I just write it to a disk and then copy it to a system with a tape drive? Also if I have to do the recovery can I use a remote drive or does it need to be direct connect? Thanks for all your help.
Live, love and laugh
4 REPLIES 4
John Dvorchak
Honored Contributor
Solution

Re: make_tape_recovery question

No you can't make the Ignite tape on a remote drive. But if there is another HPUX box on the LAN you can make it an Ignite server and use make_net recovery to create an archive on the server.

IgniteUX is free and any HPUX system can be an Ignite server.

With the price of external tape drives, especially used ones, you really should have a tape attached.

Good luck
If it has wheels or a skirt, you can't afford it.
Dario_1
Trusted Contributor

Re: make_tape_recovery question

Amiel:

You can't make the Ignite tape on a remote tape drive. You could do it to another HPUX server but my opinion will be to get a tape drive.

Regards,

DR
Kelli Ward
Trusted Contributor

Re: make_tape_recovery question

Sorry, must be a direct connect.
Short term solution, borrow a drive from another system, put it in, load the tape drivers and Ignite and go, long term, get a tape drive or implement the Ignite server where the backups will be stored on the server hard drive(s)
Good Luck,
Kel
The more I learn, the more I realize how much more I have to learn. Isn't it GREAT!
Tim Sanko
Trusted Contributor

Re: make_tape_recovery question

OK lets get this straight:
There are just a few tips.

1. to Ignite direct to tape, the drive needs to be directly connected.

2. If you have about 100GB free on another server make it an IGNITE server, and run
make_net_recovery. It is really straight forward as long as you remember these keys. Export the target, get the mac addresses of the ethernet cards on the source machines available via netstat or sam. and follow the directions in the white paper.

There are also good suggestions through the man pages.
Tim