make_net_recovery

[Chrisl_2]

PARISC 11.11 and 11.23

Hi all,

I am trying setup an ignite archive recovery from a client system to a server system that has a tape drive. I used ignite on the server system to setup the client, then went to the client to run the recovery archive. My question is how do I get the client archive onto the server tape drive instead of the server disk drive. I'm thinking that the answer is right in front of me, but I'm blind.

TIA

[Torsten. · Accepted solution]

The archive will be stored on the disk, after this you can store it on the tape.

alternative you can connect the tape drive directly to the system you want to backup and run make_tape_recovery.

[Lynn Hsu_2]

You also can export the tape drive to the
client. Then use ignite tool "make_tape_recovery". Example:
> make_tape_recovery -x inc_extire=vg00 \
-x exclude /tmp -a remote_host:/dev/rmt/0mn

man page has all the details.

Lynn

[Jaime Bolanos Rojas.]

Chris, also this is a really nice page that will be able to answer several how to do questions about a ignite.

http://www.docs.hp.com/en/IUX/faq.html#d0e3715

Regards,

Jaime.

[Chrisl_2]

Lynn,

That sounds like what I want to do. How do I export the server tape drive...add /dev/rmt/0mn to /etc/exports?

[Steven E. Protter]

Shalom,

The OS, with the possible exception of Serviceguard can't share tape devices on remote systems.

You can use make_net_recovery to a shared NFS mount point and then use the machine with the tape drive to back up the make_net_recovery images.

Vertias Netbackup does have expensive ways of making tape drives available remotely but they cost is rather high.

So my scheme works like this.

All the archives reside on a common NFS mount point. The server with the tape drive can back those up by first mounting the nfs mount point and then use fbackup to do the backup.

Works great.

I do not believe Lynn's idea will work.

SEP

[Torsten.]

The make_tape_recovery option "-a remote_host:/dev/rmt/0mn" sounds really fantastic, but I doubt this works, because ignite is expecting a local tape.

Another question to think about: If you get somehow the archice to a remote tape, how do you want to restore if needed?

Is it a (space) problem to store the archive on the ignite servers disk?

[Chrisl_2]

Yes, space is the issue. But I guess that I can work something out. I knew exporting the tape drive was too dang good of an idea!!!!

[Lynn Hsu_2]

Chris,
To use remote tape drive (however, the speed will be slow). Steps:

1. you export the device in /etc/exports:
/dev/rmt/0m -rw=host:ip
where host=client host name
and ip = client ip address

> exportfs -av

2. create a /.rhosts file with the client ip in it.

3. on client, try to tar a small file to
the remote tape drive:
> tar -cvf remote_host_ip:/dev/rmt/0m \
/etc/hosts

Let me know if this works. I have done remote fbackup using above method.

Lynn

[Torsten.]

@Lynn: Even this is working with fbackup (of course) and tar, it won't work with ignite.
Ignite is not only writing a tar backup.


@thread owner
IMHO, you have to think about to eliminate your disk space limitations, since you can have a simple JBOD (e.g. MSA30) with around 2 Terabytes. One or two new disks will solve your problem too.

[Steven E. Protter]

Ignite will fail with any variation of Lynn's command. It uses a local device and if you use the Ignite option and try to use a remote tape drive it will fail to detect the drive and fail.

If that procedure tests out with Ignite, I'll happily apologize for my remarks.

SEP

[Lynn Hsu_2]

Sorry guys - My way only works for fbackup.
Plus it is "remsh" involved. I tried with
make_tape_recovery, it did not work.

Lynn