NFS remote tape drive && mount error

[yazgoo]

Hello to everyone.
I am currently trying to copy files to a remote tape device.
I used SAM to configure that. Here's what I've done

+ (on machine 1) Exported my file system /dev/rmt
+ (on machine 2) Added Remote FileSystem to be mounted on /dev/mydir

I don't think I added it automounted.
Anyway, when I mount, I got a timout error :

nfs mount: get_fh: lune:: RPC: Rpcbind failure - RPC: Timed out

Thanks for your help

[Steven E. Protter]

Shalom,

Its not supported to export a tape drive with NFS.

Better to do a script that transfers the files and remotely archives them to tape on the machine with the tape drive.

SEP

[Patrick Wallek]

NFS = Networked File System (notice the File System in NFS).

You cannot "mount" a tape via NFS. It just isn't going to work. What you are doing is never going to work.

[Tim Nelson]

1) You can use rmt ( man rmt ) but it has always been slow and unreliable.

2) pipe the data through a remote shell then onto the tape. again slow and not completely reliable.

3) Copy files to NFS mount, then back them up to tape.

[yazgoo]

Thank you all.

Then if I understand Tim correctly, what I have to do is option 3).
Then, my question would be :
How to make it look like a local fbackup of the machine without tape drive?
Because backing up is good, but recover easily is better.

[Peter Nikitka]

Hi,

the answer of Tim means: do it the other way round.
machine1: export filesystem /backup/machine2
machine2: mount /backup/machine2
copy backup data to /backup/machine2
machine1: include /backup/machine2 in backup

mfG Peter

[Bill Hassell]

The real problem is that you have a computer with no backup device. Copying the files in any manner to another machine's tape drive will do absolutely no good if your machine cannot bootup. There is nothing in the processor that knows anything about backup programs and network pipes, etc.

So you have to do 2 things:

1. setup an Ignite network server
2. use fbackup to backup your data files over the network

The first requires downloading the latest version of Ignite from http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.do?productNumber=IGNITEUXB and then setup this server with an area large enough to hold two copies of vg00 from your local server-without-a-tape. The documentation is here:

http://www.docs.hp.com/en/IUX/index.html

Then make a network backup of your system saving just vg00 and run this command weekly. Ignite will save the most recent two backups by default.

For #2, you must setup a .rhosts file in the server with a tape drive and configure .rhosts to allow your local system to use remsh from root without a password. Then you can run a complete backup over the network. NOTE: You MUST use a low performance tape drive that matches your network speed. If you have a 10Mbit link, use a DDS3 or DDS2 tape. DDS4 and later, or DLT or Ultrium drives cannot function correctly (the LAN is far too slow). 100Mbit link is too slow for DLT 8000 or Ultrium but 1000Mbit should be OK.

Now when you have to restore a few files, you use frecover specifying the remote system and a special program called rmt will handle the tape operations. If you have to replace the boot disk on the local system, use your Ignite server to provide your boot disk image. Do NOT wait until you need this feature to test the connection. Always test that you can bootup from your Ignite server and at least see the backup menu and saved images.